Re: current install failure
Jordan Hubbard wrote: As you've already noticed, sysinstall basically tries to create the device nodes it needs under the old assumption that /dev will be mostly empty. Now that devfs is the default, phk needs to update libdisk so that it doesn't attempt to make the device nodes in this way. Fortunately, the person who wrote libdisk is also the same person who made devfs the default, so this ball is very clearly in his court. :-) If someone is going to be in the bowels of that code, I've noticed that the sysinstall doesn't does the right thing with the /dev node fixup in the upgrade case on 4.x, if you run the sysinstall over the network to upgrade from an NFS mounted CDROM. This is half the reason ssh doesn't work when you do this (the other half is /etc/pam.conf not having SSL lines). For people working on embedded systems that don't have floppy or CDROM drives, this is the only way to do the upgrade, short of ripping apart the box and using another box to do the work. Booting from the CDROM to do the upgrade doesn't have the problem. Yeah, I know that this doesn't apply to 5.x, but 4.5 (and perhaps 4.6, 4.7, ...) is going to be out before 5.x, so if you happen to be in the area and fixing code, you may want to keep an eye out for this, too... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current install failure
Hello. I have submitted a PR (bin/31009) with a followup including the patch. Hoping you have time to fix this soon... jkh = Jordan Hubbard [EMAIL PROTECTED] wrote: jkh mostly empty. Now that devfs is the default, phk needs to update jkh libdisk so that it doesn't attempt to make the device nodes in this jkh way. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
current install failure
I tried to install current snapshot as of October 2, 2001 from current.jp.FreeBSD.org, but it seems to fail at sysinstall.c:installFilesystems(). The function installFilesystems() calls MakeDevChunk() of lib/libdisk/create_chunk.c, which then calls mknod(2) via MakeDev(). The error message I see come from MakeDev() which, after mknod(2) failure, says: mknod of /dev/rad0a1b returned failure status! Typing `mount' from fixit shell, the install kernel of the Octover 2nd's snapshot has devfs enabled. I could start installation with the snapshot of September 11, with which devfs seems to be disabled (I do not see devfs on /dev (devfs, local) by typing `mount' on the fixit shell). Is there any way to install current with recent snapshots' install floppies? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current install failure
As you've already noticed, sysinstall basically tries to create the device nodes it needs under the old assumption that /dev will be mostly empty. Now that devfs is the default, phk needs to update libdisk so that it doesn't attempt to make the device nodes in this way. Fortunately, the person who wrote libdisk is also the same person who made devfs the default, so this ball is very clearly in his court. :-) - Jordan I tried to install current snapshot as of October 2, 2001 from current.jp.FreeBSD.org, but it seems to fail at sysinstall.c:installFilesystems(). The function installFilesystems() calls MakeDevChunk() of lib/libdisk/create_chunk.c, which then calls mknod(2) via MakeDev(). The error message I see come from MakeDev() which, after mknod(2) failure, says: mknod of /dev/rad0a1b returned failure status! Typing `mount' from fixit shell, the install kernel of the Octover 2nd's snapshot has devfs enabled. I could start installation with the snapshot of September 11, with which devfs seems to be disabled (I do not see devfs on /dev (devfs, local) by typing `mount' on the fixit shell). Is there any way to install current with recent snapshots' install floppies? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current install failure
* Jordan Hubbard [EMAIL PROTECTED] [011003 15:33] wrote: As you've already noticed, sysinstall basically tries to create the device nodes it needs under the old assumption that /dev will be mostly empty. Now that devfs is the default, phk needs to update libdisk so that it doesn't attempt to make the device nodes in this way. Fortunately, the person who wrote libdisk is also the same person who made devfs the default, so this ball is very clearly in his court. :-) Just reminding you all that phk's suggested way of finding this information out is to test for the presense of the devfs sysctl as done in vinum. If libdisk does it a different way, then vinum should be updated. -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current install failure
sysinstall, by design, knows very little about devices. It uses libdisk(3) as the abstraction for dealing with all disks in particular. * Jordan Hubbard [EMAIL PROTECTED] [011003 15:33] wrote: As you've already noticed, sysinstall basically tries to create the device nodes it needs under the old assumption that /dev will be mostly empty. Now that devfs is the default, phk needs to update libdisk so that it doesn't attempt to make the device nodes in this way. Fortunately, the person who wrote libdisk is also the same person who made devfs the default, so this ball is very clearly in his court. :-) Just reminding you all that phk's suggested way of finding this information out is to test for the presense of the devfs sysctl as done in vinum. If libdisk does it a different way, then vinum should be updated. -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current install failure
* Jordan Hubbard [EMAIL PROTECTED] [011003 15:33] wrote: As you've already noticed, sysinstall basically tries to create the device nodes it needs under the old assumption that /dev will be mostly empty. Now that devfs is the default, phk needs to update libdisk so that it doesn't attempt to make the device nodes in this way. Fortunately, the person who wrote libdisk is also the same person who made devfs the default, so this ball is very clearly in his court. :-) Just reminding you all that phk's suggested way of finding this information out is to test for the presense of the devfs sysctl as done in vinum. If libdisk does it a different way, then vinum should be updated. --^^^ * Jordan Hubbard [EMAIL PROTECTED] [011003 15:51] wrote: sysinstall, by design, knows very little about devices. It uses libdisk(3) as the abstraction for dealing with all disks in particular. fed ex commercial You just said the same thing that I did except you did this... *makes up/down hand waving motion* /fed ex commercial :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current install failure
Well, since I don't own libdisk(3) and had no idea why you'd be addressing this to me unless you were still confused, I presumed you were confused. In any case, you need to be talking to phk about this. - Jordan From: Alfred Perlstein [EMAIL PROTECTED] Subject: Re: current install failure Date: Wed, 3 Oct 2001 16:12:21 -0500 * Jordan Hubbard [EMAIL PROTECTED] [011003 15:33] wrote: As you've already noticed, sysinstall basically tries to create the device nodes it needs under the old assumption that /dev will be mostly empty. Now that devfs is the default, phk needs to update libdisk so that it doesn't attempt to make the device nodes in this way. Fortunately, the person who wrote libdisk is also the same person who made devfs the default, so this ball is very clearly in his court. :-) Just reminding you all that phk's suggested way of finding this information out is to test for the presense of the devfs sysctl as done in vinum. If libdisk does it a different way, then vinum should be updated. --^^^ * Jordan Hubbard [EMAIL PROTECTED] [011003 15:51] wrote: sysinstall, by design, knows very little about devices. It uses libdisk(3) as the abstraction for dealing with all disks in particular. fed ex commercial You just said the same thing that I did except you did this... *makes up/down hand waving motion* /fed ex commercial :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
