[5885] in linux-scsi channel archive
Re: WG: AW: cdrecord problems on recent Linux versions
daemon@ATHENA.MIT.EDU (Joerg Schilling)
Thu Feb 11 19:52:53 1999
Date: Fri, 12 Feb 1999 01:43:20 +0100 (MET)
From: Joerg Schilling <schilling@fokus.gmd.de>
To: rgooch@atnf.csiro.au, schilling@fokus.gmd.de
Cc: Dominik.Stadler@btk.de, bsc@fleggaard.dk,
cdwrite@lists.debian.org, dgilbert@interlog.com,
heiko_eissfeldt@z.detesystem.de, linux-scsi@vger.rutgers.edu,
michaels@stochastik.rwth-aachen.de, xiphmont@mit.edu
>From rgooch@vindaloo.atnf.CSIRO.AU Thu Feb 11 21:51:13 1999
>> >> Interesting, this is a SYSVr4 idea (around since 1987).
>>
>> >Perhaps. I note that the Solaris 2 implementation is in part or in
>> >full a user space solution (when you do boot -r from the PROM). Their
>> >scheme doesn't appear particularly robust, since old (invalid) device
>> >entries are sometimes left around.
>>
>> This is not right, it is very robust.
>>
>> /dev/rdsk/c0t1d0s2 is only a symlink to the real device nodes
>> which are located in /devices
>>
>> e.g.
>>
>> /dev/rdsk/c0t1d0s2 -> ../../devices/sbus@1,f8000000/esp@0,800000/sd@1,0:c,raw
>>
>> the /devices entries are in the real root partition but are created
>> directly by the driver each time when a driver reconfiguration is done.
>>
>> The symlinks are created by user level programs.
>> If you follow the manual and do a boot -r, these user level programs
>> are called correctly and will remove unneeded entries.
>>
>> Howerver, it is possible to add hardware to a running system.
>> Then you need to call:
>>
>> drvconfig tells the kernel to reconfigure the drivers
>> devlinks general symlinks program
>> disks symlink program for disks
>> tapes symlink program for tapes
>> ports symlink program for serial lines
>> audlinks symlink program for audio devices
>> ucblinks creates BSD compat dev entries
>>
>> If you don't call all programs corectly, it's your fault.
>In the case I noticed recently, I think it was done correctly. Someone
>upgraded the FORE ATM drivers on a system (the new drivers use
>different /dev entries), booted with -r and the old device entries in
>/dev were still around. This caused much confusion.
>It may be a bug due to FORE not doing something right (like adding to
>one of those scripts), but either way, it points to a bug/design flaw
>in Solaris. Problems like this should not happen. Linux devfs doesn't
>suffer from this problem.
This definitely must be a FORE bug. They then seem not to provide a correct
/etc/devlink.tab which is needed to make devlinks work properly.
I know that there are other bugs in the FORE installation.
Jörg
EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni) If you don't have iso-8859-1
schilling@fokus.gmd.de (work) chars I am J"org Schilling
URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
