Re: [Cooker] dev-3.3.1 install problem
On Tue, 2002-08-20 at 06:32, Thierry Vignaud wrote: > John Johnson <[EMAIL PROTECTED]> writes: > > > Thank you for all your help! I'm finally back online! However, I'm > > getting the following error message at boot up: mount point /dev/pts > > does not exist [failed]. > > already fixed in later dev releases > > Yep.Updated to latest dev and MAKEDEV. Reran mdk_makedev /dev and the above problem went away. I did lose my symlinks for my DVD ( /dev/scd0 -> /dev/cdrom) and CDWriter (/dev/scd1 -> /dev/cdrw). Once I recreated then, everything worked fine. John
Re: [Cooker] dev-3.3.1 install problem
John Johnson <[EMAIL PROTECTED]> writes: > Thank you for all your help! I'm finally back online! However, I'm > getting the following error message at boot up: mount point /dev/pts > does not exist [failed]. already fixed in later dev releases
Re: [Cooker] dev-3.3.1 install problem
On Mon, 2002-08-19 at 18:00, Thierry Vignaud wrote: > "John Johnson" <[EMAIL PROTECTED]> writes: > > >> /dev/hda1 -> /mnt (root partition) > >> /dev/hda6 -> /usr > >> > >> /dev/ram3 is mounted to / > >> > >> After which, I ran /usr/sbin/mdk_makedev /mnt/dev > > > > chroot /mnt > > /usr/sbin/mdk_makedev /dev > > > > "find /dev|wc -l" should report ~19k files > > > > > > My /dev directory has ~16.8k files in it after executing these commands. The > > system now gets further along in the boot process but now I'm getting the > > following errors: > > > > setting default font: dup2: bad file descriptor [Failed] > > /etc/rc.sysinit: /dev/null: read-only file system > > something has accedded /dev/null at the bad time and create a file > instead of a device. > > on the rescue, you can do "find /dev/ | xargs rm -fr" in the chrooted > environment before running mdk_makedev (which don't overwite already > existing entries). > > longer explanation: > >1) 1mdk and 2mdk had typos :-( > >2) while updating from <3.3.1-1mdk, there's a 7 seconds race > window, which make possible to have a program that write to > /dev/null whereas the old one has been delete by rpm but the > new one isn't yet created, thus resulting in a file insead > of a special device; > then the next process which'll try to access /dev/null 'll > have some problems > > >as /dev/null is one of the rare /dev/ entries one write to, and >is the device that get 99% of the writes in /dev/, i'll put a >special case in dev-3.3.1-4mdk, something as: > > while [[ ! -c /lib/root-mirror/dev/null ]]; do > rm -f /lib/root-mirror/dev/null > mknod -m 0666 /lib/root-mirror/dev/null c 1 3 > chown root.root /lib/root-mirror/dev/null > done > >so that we'll be sure to have a valid /dev/null after dev update > > Thank you for all your help! I'm finally back online! However, I'm getting the following error message at boot up: mount point /dev/pts does not exist [failed]. In my fstab file I have: none /dev/pts devpts mode=0620 0 0. But there's no pts device in /dev. Prior to upgrading dev, I wasn't getting this error. John
Re: [Cooker] dev-3.3.1 install problem
"John Johnson" <[EMAIL PROTECTED]> writes: >> /dev/hda1 -> /mnt (root partition) >> /dev/hda6 -> /usr >> >> /dev/ram3 is mounted to / >> >> After which, I ran /usr/sbin/mdk_makedev /mnt/dev > > chroot /mnt > /usr/sbin/mdk_makedev /dev > > "find /dev|wc -l" should report ~19k files > > > My /dev directory has ~16.8k files in it after executing these commands. The > system now gets further along in the boot process but now I'm getting the > following errors: > > setting default font: dup2: bad file descriptor [Failed] > /etc/rc.sysinit: /dev/null: read-only file system something has accedded /dev/null at the bad time and create a file instead of a device. on the rescue, you can do "find /dev/ | xargs rm -fr" in the chrooted environment before running mdk_makedev (which don't overwite already existing entries). longer explanation: 1) 1mdk and 2mdk had typos :-( 2) while updating from <3.3.1-1mdk, there's a 7 seconds race window, which make possible to have a program that write to /dev/null whereas the old one has been delete by rpm but the new one isn't yet created, thus resulting in a file insead of a special device; then the next process which'll try to access /dev/null 'll have some problems as /dev/null is one of the rare /dev/ entries one write to, and is the device that get 99% of the writes in /dev/, i'll put a special case in dev-3.3.1-4mdk, something as: while [[ ! -c /lib/root-mirror/dev/null ]]; do rm -f /lib/root-mirror/dev/null mknod -m 0666 /lib/root-mirror/dev/null c 1 3 chown root.root /lib/root-mirror/dev/null done so that we'll be sure to have a valid /dev/null after dev update
RE: [Cooker] dev-3.3.1 install problem
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Thierry Vignaud Sent: Monday, August 19, 2002 3:32 PM To: [EMAIL PROTECTED] Subject: Re: [Cooker] dev-3.3.1 install problem "John Johnson" <[EMAIL PROTECTED]> writes: > /dev/hda1 -> /mnt (root partition) > /dev/hda6 -> /usr > > /dev/ram3 is mounted to / > > After which, I ran /usr/sbin/mdk_makedev /mnt/dev chroot /mnt /usr/sbin/mdk_makedev /dev "find /dev|wc -l" should report ~19k files My /dev directory has ~16.8k files in it after executing these commands. The system now gets further along in the boot process but now I'm getting the following errors: setting default font: dup2: bad file descriptor [Failed] /etc/rc.sysinit: /dev/null: read-only file system At which point the system halts: John
Re: [Cooker] dev-3.3.1 install problem
"John Johnson" <[EMAIL PROTECTED]> writes: > /dev/hda1 -> /mnt (root partition) > /dev/hda6 -> /usr > > /dev/ram3 is mounted to / > > After which, I ran /usr/sbin/mdk_makedev /mnt/dev chroot /mnt /usr/sbin/mdk_makedev /dev "find /dev|wc -l" should report ~19k files
RE: [Cooker] dev-3.3.1 install problem
OK. Did as instructed. Still getting "Unable to open an initial console" After booting into rescue mode, I mounted my partitions to the following mount points: /dev/hda1 -> /mnt (root partition) /dev/hda6 -> /usr /dev/ram3 is mounted to / After which, I ran /usr/sbin/mdk_makedev /mnt/dev -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Thierry Vignaud Sent: Monday, August 19, 2002 2:22 PM To: [EMAIL PROTECTED] Subject: Re: [Cooker] dev-3.3.1 install problem "John Johnson" <[EMAIL PROTECTED]> writes: > Upgraded dev to dev-3.3.1 following instructions (option 1) as > outlined in earlier mandrake cooker email. Now system will not boot > and I'm getting the dreaded "Unable to open an initial console" > message. > > What cerrective actions should I take to get system back online. boot on rescue, mount your root fs, run /usr/sbin/mdk_makedev /dev your problem was fixed in -2mdk
Re: [Cooker] dev-3.3.1 install problem
"John Johnson" <[EMAIL PROTECTED]> writes: > Upgraded dev to dev-3.3.1 following instructions (option 1) as > outlined in earlier mandrake cooker email. Now system will not boot > and I'm getting the dreaded "Unable to open an initial console" > message. > > What cerrective actions should I take to get system back online. boot on rescue, mount your root fs, run /usr/sbin/mdk_makedev /dev your problem was fixed in -2mdk
[Cooker] dev-3.3.1 install problem
Hi, Upgraded dev to dev-3.3.1 following instructions (option 1) as outlined in earlier mandrake cooker email. Now system will not boot and I'm getting the dreaded "Unable to open an initial console" message. What cerrective actions should I take to get system back online. John
