Boszormenyi Zoltan writes:
> even contributed a little to it. To correct my e-mail address,
> here is a patch:
Applied.
> I have some problems with it now. I couldn't log in as root. Again. :-)
> However, adding [1-8] to /etc/securetty helped. /dev/tty[1-8] are symlinks
> to /dev/vc/[1-8]... Just in case someone else has fallen into this trap.
>
> Now the real problems. The provided modules.conf sample does not work,
> I mean it does not load all SCSI drivers correctly for me. Try this patch
> against the provided modules.conf for e.g. SCSI disks.
>
> **************************************
> --- modules.conf.devfs Fri Feb 18 09:15:24 2000
> +++ modules.conf Fri Feb 18 11:02:04 2000
> @@ -8,7 +8,10 @@
> alias gen-watchdog pcwd
> alias gen-md raid0
> alias /dev/joysticks joystick
> -probeall scsi-hosts sym53c8xx
> +alias scsi-hosts sym53c8xx
> +add above scsi-hosts ppa
> +alias parport_lowlevel parport_pc
> +options parport_pc io=0x378 irq=7
OK, this bit is just specific to your setup, right?
> ###############################################################################
> # Generic section: do not change
> @@ -29,7 +32,8 @@
> probeall /dev/ide ide-probe-mod ide-disk ide-cd ide-tape ide-floppy
>
> # SCSI HDDs
> -probeall /dev/sd scsi-hosts sd_mod
> +below sd_mod scsi-hosts
> +alias /dev/sd sd_mod
> alias /dev/sd* /dev/sd
>
> # SCSI CD-ROMs
> **************************************
>
> This way it works for me with and without devfs. E.g. "mdir z:"
> (Z: refers to /dev/sda4) nicely loads sym53c8xx and ppa drivers
> in this order. Maybe it is the fault of modutils-2.3.9 but using
> simply "probeall scsi-hosts sym53c8xx ppa" didn't work.
> Which is a shame because this "probeall" thing would be a shorter
> and nicer way to describe what I want to load and in what order.
So this is a bug in modutils? Could you please talk to Keith and check
this out? I don't want to add hacks to the sample config file to work
around bugs elsewhere.
> And a note at the end. I start devfsd on boot and I had to put a
> "sleep 2" after starting it because the boot sequence stops at
> "Mounting local filesystems" twice from five. It is with
> devfsd-1.3.1. I looked at devfsd.c and before it forks, it
> generates the register events for the already existing device nodes
> but the events are handled by the child process. This first round of
> events should be handled by the parent process so the startup
> scripts will not need this (unreliable amount of) delay. Maybe
> do_scan_and_service() should send a "finished startup" event after
> the last device node and before the fork() main() should service the
> events until this "finished startup"...
But devfsd does the initial scanning in the parent process. It's not
done in the child process. Even the comments describe this. Maybe your
boot scripts start devfsd with a "daemon" programme, which itself does
a fork-and-exec?
I'm pretty sure that devfsd does the right thing (it didn't
originally, and then I fixed it because my system broke).
BTW: please keep sending devfs reports directly to me and not the
list. I don't always see everything on the list...
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:25 EST