Bug#121110: boot-floppies: TFTP boot on Alpha broken
On Sun Dec 02, 2001 at 09:50:16PM -0800, [EMAIL PROTECTED] wrote: > > > > No, I don't think this is related to the problem reported in 121110. > > I'm guessing 121110 has been fixed along with bug#116829 -- the > > problem was the way that busybox init and telinit didn't get along > > together in the context when init wasn't pid 1. > > > > I don't think the "fix" you outlined will fix anything. > > > > Assuming the good alpha folks are installing over the network, they > > should be using sysvinit 2.84-1, in which case, this bug should have > > already gone away. > > I think your right there. My "fix" does fix something else though. > It fixes reboot when in initrd, which doesn't work without > the fix. > > I'll post a bugreport against busybox. > > I mixed up the two bugs in my mind cause they both disappeared at the > same time for me, prob. when the new sysvinit came out and I started using > my patched busybox. I saw and very much dislike your patch. If there is a problem with busybox reboot failing to find the init process, I'm anxious to understand _why_, not just ignore it and hope it goes away. -Erik -- Erik B. Andersen http://codepoet-consulting.com/ --This message was written using 73% post-consumer electrons-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#121110: boot-floppies: TFTP boot on Alpha broken
> > No, I don't think this is related to the problem reported in 121110. > I'm guessing 121110 has been fixed along with bug#116829 -- the > problem was the way that busybox init and telinit didn't get along > together in the context when init wasn't pid 1. > > I don't think the "fix" you outlined will fix anything. > > Assuming the good alpha folks are installing over the network, they > should be using sysvinit 2.84-1, in which case, this bug should have > already gone away. I think your right there. My "fix" does fix something else though. It fixes reboot when in initrd, which doesn't work without the fix. I'll post a bugreport against busybox. I mixed up the two bugs in my mind cause they both disappeared at the same time for me, prob. when the new sysvinit came out and I started using my patched busybox. Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#121110: boot-floppies: TFTP boot on Alpha broken
If this is the init q thing that kill syour system during an install
when running with initrd, I have a patch to busybox that
fixes it on the powerpc.
The problem is that ... when reboot.c
does 'pid_t *pid = find_pid_by_name("init");',
then there is code in find_pid_by_name that "makes sure" init is found
by passing '1' back if it couldn't find it.
This is the fix I used:
Add the comments to libbb/find_fid_by_name.c:
if (pidList)
pidList[i]=0;
// else if ( strcmp(pidName, "init")==0) {
// /* If we found nothing and they were trying to kill "init",
// * guess PID 1 and call it good... Perhaps we should simply
// * exit if /proc isn't mounted, but this will do for now. */
// pidList=xrealloc( pidList, sizeof(pid_t));
// pidList[0]=1;
else {
Sorry I am too lazy to do a proper diff, but it is a small file and
an easy hack.
I am even too lazy to submit a proper bug report.
Peter
On Sat, Dec 01, 2001 at 07:37:43PM +0100, Falk Hueffner wrote:
> Adam Di Carlo <[EMAIL PROTECTED]> writes:
>
> >
> > Falk Hueffner <[EMAIL PROTECTED]> writes:
> >
> > > Package: boot-floppies
> > > Version: N/A; reported 2001-11-25
> > > Severity: normal
> > >
> > > Installing via tftpboot.img will stall at installation of libc6.1, as
> > > has been reported to debian-alpha several times,
> > > e.g.
>http://lists.debian.org/debian-alpha/2001/debian-alpha-200110/msg00010.html. "rgh"
>told me on IRC:
> > >
> > > mellum: re "init q", when I had that problem ia64, it was
> > > because I forgot to boot with root=/dev/ram
> > > mellum: without that, the kernel wants to do it's initrd magic,
> > > and runs /linuxrc before starting sbin/init. linuxrc is linked to
> > > init, so effectively init gets run as pid 12 (or something > 1,
> > > anyway)
> > > linuxrc is run with a pid > 1, and the kernel expects that to
> > > return before it starts init as pid 1
> > > root=/dev/ram makes the kernel realise that the ramdisk si a
> > > real ramdisk, and not an initrd, so it disables the running of
> > > linuxrc
> > >
> > > So we need to find a way to force this parameter.
> >
> > Isn't this the same as #116829 and wasn't it fixed in sysvinit 2.84-1 ?
>
> Hm, yes, seems to be the same problem. I'll try to find a tester,
> since netboot doesn't work for me.
>
> Falk
>
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#121110: boot-floppies: TFTP boot on Alpha broken
Adam Di Carlo <[EMAIL PROTECTED]> writes: > > Falk Hueffner <[EMAIL PROTECTED]> writes: > > > Package: boot-floppies > > Version: N/A; reported 2001-11-25 > > Severity: normal > > > > Installing via tftpboot.img will stall at installation of libc6.1, as > > has been reported to debian-alpha several times, > > e.g. http://lists.debian.org/debian-alpha/2001/debian-alpha-200110/msg00010.html. >"rgh" told me on IRC: > > > > mellum: re "init q", when I had that problem ia64, it was > > because I forgot to boot with root=/dev/ram > > mellum: without that, the kernel wants to do it's initrd magic, > > and runs /linuxrc before starting sbin/init. linuxrc is linked to > > init, so effectively init gets run as pid 12 (or something > 1, > > anyway) > > linuxrc is run with a pid > 1, and the kernel expects that to > > return before it starts init as pid 1 > > root=/dev/ram makes the kernel realise that the ramdisk si a > > real ramdisk, and not an initrd, so it disables the running of > > linuxrc > > > > So we need to find a way to force this parameter. > > Isn't this the same as #116829 and wasn't it fixed in sysvinit 2.84-1 ? Hm, yes, seems to be the same problem. I'll try to find a tester, since netboot doesn't work for me. Falk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#121110: boot-floppies: TFTP boot on Alpha broken
Processing commands for [EMAIL PROTECTED]: > tags 121110 + moreinfo Bug#121110: boot-floppies: TFTP boot on Alpha broken Tags added: moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#121110: boot-floppies: TFTP boot on Alpha broken
Falk Hueffner <[EMAIL PROTECTED]> writes: > mellum: re "init q", when I had that problem ia64, it was > because I forgot to boot with root=/dev/ram > mellum: without that, the kernel wants to do it's initrd magic, > and runs /linuxrc before starting sbin/init. linuxrc is linked to > init, so effectively init gets run as pid 12 (or something > 1, > anyway) Can we just link /linuxrc to /bin/true? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#121110: boot-floppies: TFTP boot on Alpha broken
Package: boot-floppies Version: N/A; reported 2001-11-25 Severity: normal Installing via tftpboot.img will stall at installation of libc6.1, as has been reported to debian-alpha several times, e.g. http://lists.debian.org/debian-alpha/2001/debian-alpha-200110/msg00010.html. "rgh" told me on IRC: mellum: re "init q", when I had that problem ia64, it was because I forgot to boot with root=/dev/ram mellum: without that, the kernel wants to do it's initrd magic, and runs /linuxrc before starting sbin/init. linuxrc is linked to init, so effectively init gets run as pid 12 (or something > 1, anyway) linuxrc is run with a pid > 1, and the kernel expects that to return before it starts init as pid 1 root=/dev/ram makes the kernel realise that the ramdisk si a real ramdisk, and not an initrd, so it disables the running of linuxrc So we need to find a way to force this parameter. Falk -- System Information Debian Release: testing/unstable Architecture: alpha Kernel: Linux borkum 2.4.15-pre6 #2 Wed Nov 21 19:23:16 CET 2001 alpha Locale: LANG=C, LC_CTYPE=de_DE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
