Re: fd0c mount(8) Race
Crist J. Clark [EMAIL PROTECTED] wrote: mount: /dev/fd0c: No such file or directory It seems there is some type of race to get the fd0c symlink in place and I am not winning it. The symlink DEVFS nodes are going to be created first time they are referenced. Your mount attempt thus does create it, but has got reported it as ENOENT already by that time. I switched to /dev/fd0 and the boot went fine, but if this is real, it should be fixed. Maybe. Btw., there's no point in trying to mount /dev/fd0c anyway. There are no partitioned floppy device nodes (except perhaps in Bruce Evans' private tree :) anyway. Pseudo-partitions fd0a through fd0h have been aliases for just fd0 for years. -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: fd0c mount(8) Race
Sat, Jun 30, 2001 at 00:16:53, cristjc (Crist J. Clark) wrote about fd0c mount(8) Race: mount: /dev/fd0c: No such file or directory That is, even though once I drop into single-user mode we see the symlink for /dev/fd0c, it does not seem like it was there when 'mount -a -t nonfs' is run in /etc/rc. I don't see it too. It appears if is created explicitly. Log follows (showing quite strange behavior): root@iv:~##ls -l /dev/fd0* crw-r- 1 root operator9, 0 Jul 1 15:01 /dev/fd0 root@iv:~##ls -l /dev/fd0c ls: /dev/fd0c: No such file or directory root@iv:~##mknod /dev/fd0c c 0 0 mknod: /dev/fd0c: File exists root@iv:~##ls -l /dev/fd0c lrw-rw-rw- 1 root wheel 4 Jul 1 19:31 /dev/fd0c - fd0 root@iv:~##rm /dev/fd0c root@iv:~##rm /dev/fd0c rm: /dev/fd0c: No such file or directory root@iv:~##ls -l /dev/fd0c ls: /dev/fd0c: No such file or directory root@iv:~##ls -l /dev/fd0c ls: /dev/fd0c: No such file or directory root@iv:~##mknod /dev/fd0c c 0 0 root@iv:~##ls -l /dev/fd0c lrw-rw-rw- 1 root wheel 4 Jul 1 19:31 /dev/fd0c - fd0 I'm surprised mainly that first mknod reported bogus failure. reproduce the problem? Or is it well known (I can't find it in the mail archive)? I think you can't - current devfs is too young. /netch To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
fd0c mount(8) Race
I mount a floppy at boot time. The entry was, /dev/fd0c /twfloppy ufs ro 0 0 However, as of a recent CURRENT build I started getting, [normal kernel boot messages] Mounting root from ufs:/dev/ad0s1a Entropy harvesting: interrupts ethernet point_to_point. Using /entropy as an entropy file swapon: adding /dev/ad0s1b as swap device Automatic boot in progress... /dev/ad0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1a: clean, 33463 free (647 frags, 4102 blocks, 0.7% fragmentation) /dev/ad0s1e: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1e: clean, 446216 free (12512 frags, 54213 blocks, 1.2% fragmentation) mount: /dev/fd0c: No such file or directory Mounting /etc/fstab filesystems failed, startup aborted Enter full pathname of shell or RETURN for /bin/sh: # ls -l /dev/fd0* crw-r- 1 root operator9, 0 Jun 29 23:26 /dev/fd0 lrw-rw-rw- 1 root wheel4 Jun 29 23:26 /dev/fd0c - fd0 # That is, even though once I drop into single-user mode we see the symlink for /dev/fd0c, it does not seem like it was there when 'mount -a -t nonfs' is run in /etc/rc. It seems there is some type of race to get the fd0c symlink in place and I am not winning it. I switched to /dev/fd0 and the boot went fine, but if this is real, it should be fixed. Can anyone else reproduce the problem? Or is it well known (I can't find it in the mail archive)? -- Crist J. Clark [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
