Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!ira.uka.de!fauern!lrz-muenchen.de!regent!gjung
From: gjung@guug.de (Guenter Jung)
Subject: [386bsd] can't mount cdrom after PK-0.2.3
Message-ID: <gjung.736550942@guug.de>
Summary: Can't mount the cdrom after installing patchkit-0.2.3
Keywords: cdrom 386bsd patchkit-0.2.3
Sender: news@regent.e-technik.tu-muenchen.de (News System.)
Organization: Technical University of Munich, Germany
Date: Tue, 4 May 1993 21:29:02 GMT
Lines: 33
I have installed patchkit-0.2.3 and now I can't mount my cdrom anymore.
If I try a "mount -r -t isofs /dev/cd0d /cdr", I only get the message
"mount: Read-only filesystem" and, after accessing the root (eg with
'ls /'), the system hangs.
I have searched 'kern/vfs_syscalls.c' and 'isofs/isofs_vfsops.c' for
the problem and it seams that isofs_mount gets completely wrong
parameters.
I have inserted print-statements like
printf("isofs mp=%x dir=%x data=%x ndp=%x p=%x\n",mp,path,data,ndp,p)
as the first statement in "isofs_mount" and just before "VFS_MOUNT"
in "mount" and I get the following output:
vfs: mp=fe2b3x00 dir=fdbf9015 data=fdbeefd4 ndp=fdbfff0c p=fe2e9200
isofs: mp=fe2e9200 dir=fdbfffa4 data=fdbfff9c ndp=fdbef000 p=5
Note the value for p at vfs and for mp at isofs is the same.
Mounts to ufs are ok, I have not tested nfs, mfs and pcfs.
Maybe this is a known bug and someone has solved the problem.
Please reply be email, as I can't read the news regularly.
My hardware:
'386 '387 33MHz SIS Chipset
8 MB RAM
AHA1542B
190 MB Seagate
2 * 650 MB Siemens Megafile
Toshiba 3301 CDROM
Adaptec Viper 150MB Streamer
WD Controller
Maxtor XT1150 (115 MB)
ET4000 1MB
10 Serial-Ports (2 Standard, 1 8-Port Card)
1 Parallel-Port
Guenter Jung
gjung@guug.de