Re: 3.0.18 status confirmation

[John H. Robinson, IV]

On Sun, Dec 16, 2001 at 12:00:33AM -0800, John H. Robinson, IV wrote:
> On Sat, Dec 15, 2001 at 03:27:41PM -0700, Chris Tillman wrote:
> > are showing. Here's what they say:
> > 
> > init started: Busybox v. 0.60.3-pre (2001.12.07-03:53+)
> > Bummer, could not run '/etc/init.d/rcS': Permission denied
> > grep: /proc/cmdline: No such file or directory
> 
> ah, damn.  my fault.   i'll fix if not already fixed.

false alarm, not really my fault. but i removed the ``grep:
/proc/cmdline: No such file or directory'' error message.

-john


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 3.0.18 status confirmation

[John H. Robinson, IV]

On Sat, Dec 15, 2001 at 03:27:41PM -0700, Chris Tillman wrote:
> are showing. Here's what they say:
> 
> init started: Busybox v. 0.60.3-pre (2001.12.07-03:53+)
> Bummer, could not run '/etc/init.d/rcS': Permission denied
> grep: /proc/cmdline: No such file or directory

ah, damn.  my fault.   i'll fix if not already fixed.

-john


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 3.0.18 status confirmation

[Chris Tillman]

On Sat, Dec 15, 2001 at 01:26:54PM -0500, Adam Di Carlo wrote:
> Chris Tillman <[EMAIL PROTECTED]> writes:
> 
> > On powerpc, I'm getting a sudden increase in the root disk size from
> > a couple of nights ago. The build fails with:
> > 
> > rootpmac.bin larger than rootpmac1440.bin (1711223 > 1474560)
> 
> It builds for me  Are you sure 'make check' is succeeding?  I
> don't know if our dependancy checks are yet tight enough.

OK, after I got it built I gave it a shot and it's still a flasher.

I got an inspiration and tried holding Control C when it started
flashing -- if I time it right, I can stop it when the boot messages
are showing. Here's what they say:

init started: Busybox v. 0.60.3-pre (2001.12.07-03:53+)
Bummer, could not run '/etc/init.d/rcS': Permission denied
grep: /proc/cmdline: No such file or directory
usb.c: USB new device connect, assigned device number 2
hub.c: USB hubfound
hub.c: 3 ports detected
grep: /proc/cmdline: No such file or directory
usb.c: USB new device connect, assigned device number 3
keybdev.c: Adding keyboard: input1
event1: Event device for input1
input1: USB HID 0.01 Keyboard [Misumi ...] on usb1:3.0
grep: /proc/cmdline: No such file or directory
usb.c: USB new device connect, assigned device number 4
mouse1: PS/2 mouse device for input2
event2: Event device for input2
input2: USB HID 0.01 Mouse [Misumi ...] on usb1:4.0
grep: /proc/cmdline: No such file or directory

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|    |
|   debian-imac (potato):    |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 3.0.18 status confirmation

[Erik Andersen]

On Fri Dec 14, 2001 at 02:02:48AM -0500, Adam Di Carlo wrote:
> 
> Sorry, I've been away on business travel but I'm back now.
> 
> >From my scan of the debian-boot list, I take it these bugs are holding
> 3.0.18 release:
> 
>   Bug#123387 -- busybox wget won't work with debootstrap anymore
> 

I just got back into town myslef.  I'll be uploading a fixed 
busybox package in a few hours (after I shovel all the show
out of my driveway),

 -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]

Re: 3.0.18 status confirmation

[Chris Tillman]

On Sat, Dec 15, 2001 at 01:26:54PM -0500, Adam Di Carlo wrote:
> Chris Tillman <[EMAIL PROTECTED]> writes:
> 
> > On powerpc, I'm getting a sudden increase in the root disk size from
> > a couple of nights ago. The build fails with:
> > 
> > rootpmac.bin larger than rootpmac1440.bin (1711223 > 1474560)
> 
> It builds for me  Are you sure 'make check' is succeeding?  I
> don't know if our dependancy checks are yet tight enough.
> 

You're right, I didn't have slang1-utf8-pic installed.

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|    |
|   debian-imac (potato):    |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 3.0.18 status confirmation

[Chris Tillman]

On Sat, Dec 15, 2001 at 01:26:54PM -0500, Adam Di Carlo wrote:
> Chris Tillman <[EMAIL PROTECTED]> writes:
> 
> > On powerpc, I'm getting a sudden increase in the root disk size from
> > a couple of nights ago. The build fails with:
> > 
> > rootpmac.bin larger than rootpmac1440.bin (1711223 > 1474560)
> 
> It builds for me  Are you sure 'make check' is succeeding?  I
> don't know if our dependancy checks are yet tight enough.
> 
> > As soon as it's buildable again, I'll try the flashing screen test
> > again. I did finish the build after David's fix was put in, and the
> > problem was still there. So I'm hoping Adam's fix is nicer.
> 
> I've uploaded some my people.debian.org/~aph/

I tried these (dated 12/15/2001) just now. Still get the flashing
screen. I'm downloading linux and root.bin to my hard disk, and using
yaboot to load them directly from OpenFirmware. So I don't see how I
could be going wrong. I verified the yaboot.conf points to the root.bin 
I downloaded. 

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|    |
|   debian-imac (potato):    |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 3.0.18 status confirmation

[Chris Tillman]

On powerpc, I'm getting a sudden increase in the root disk size from
a couple of nights ago. The build fails with:

rootpmac.bin larger than rootpmac1440.bin (1711223 > 1474560)

As soon as it's buildable again, I'll try the flashing screen test
again. I did finish the build after David's fix was put in, and the
problem was still there. So I'm hoping Adam's fix is nicer.

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|    |
|   debian-imac (potato):    |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 3.0.18 status confirmation

[David Kimdon]

> The issue was the wrong library to begin with getting put on the root
> disk, I think.  We've seen lots of conflicting successes and failures
> on this one so it is difficult to be certain.  Hopefully I can get
> somethign built/tested and uploaded today or tomorrow and that will
> clear things up.

i386 test build at (out of cvs as of sometime this morning):
http://people.debian.org/~dwhedon/dists/woody/main/disks-i386/current/

I've tested the idepci flavor an it doesn't have the flashing screen
problem.  I think I have a good busybox fix (didn't get a chance to
actually complete an install), but I built these before the official
fix was available.

-David



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 3.0.18 status confirmation

[Philip Blundell]

In message <[EMAIL PROTECTED]>, Adam Di Carlo writes:
>Actually, after talking to Eduard, I think disabling parted on
>udma100-ext3 would be better.  Why would we have this on one and only
>one flavor?  Thoughts?

Yeah, I think this might be best.  The menus say that parted is "new, not 
complete and not 100% stable" which is probably going to put most people off 
using it in any case.

p.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 3.0.18 status confirmation

[Eduard Bloch]

#include 
Attila Nagy wrote on Fri Dec 14, 2001 um 11:22:16AM:

> > We have a workaround for this now so I don't think it's a blocker for
> > 3.0.18. I'd rather leave well alone for the moment.
> Yesterday I built b-f and still got the flashing screen. I will try it
> with the changes, committed today.

Please install libnewt0-utf8-pic and try again.

> 1440+0 records out
> 1440+0 records in
> 1440+0 records out
> E: rootudma100-ext3.bin is larger than root1440udma100-ext3.bin (1523152 >
> 1474560)
> E: ./rescue.sh abort
> make[1]: *** [resc1440udma100-ext3.bin] Error 255
> make[1]: *** Deleting file `resc1440udma100-ext3.bin'

I know. There are two options: 

 - drop 2-3 languagues and it does perfectly fit
 - drop parted program (removing the scripts/root/*udma100-ext3 files)

 Adam should decide.
 
 BTW, I allready though about creating an "extension" disk with parted,
 ppp and pppoe for users that want to install with 2+1 floppies via
 Network/ADSL.

Gruss/Regards,
Eduard.
-- 
Zum 1.000.001. Mal: Jedes Programm, das kompliziertere Funktionen
bietet als Space Invaders verlangt eine 'zeitraubende intensive
Einarbeitung' wenn man es vernünftig nutzen möchte.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 3.0.18 status confirmation

[Attila Nagy]

Hello,

> >-- newt/slang damage, flashing dbootstrap screen on start
> We have a workaround for this now so I don't think it's a blocker for
> 3.0.18. I'd rather leave well alone for the moment.
Yesterday I built b-f and still got the flashing screen. I will try it
with the changes, committed today.

BTW,
I: rescue image complete: -rw-r--r-- 1 root root 1474560 Dec 14 11:10
resc1440udma100-ext3.bin
I: making detached root disk root1440udma100-ext3.bin from
rootudma100-ext3.bin
1440+0 records in
1440+0 records out
1440+0 records in
1440+0 records out
E: rootudma100-ext3.bin is larger than root1440udma100-ext3.bin (1523152 >
1474560)
E: ./rescue.sh abort
make[1]: *** [resc1440udma100-ext3.bin] Error 255
make[1]: *** Deleting file `resc1440udma100-ext3.bin'

Now what?

--
Attila Nagye-mail:  [EMAIL PROTECTED]
Budapest Polytechnic (BMF.HU)   @work: +361 210 1415 (194)
H-1084 Budapest, Tavaszmezo u. 15-17.   cell.: +3630 306 6758


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 3.0.18 status confirmation

[Phil Blundell]

>  Bug#123387 -- busybox wget won't work with debootstrap anymore

Well, busybox wc actually, but yeah.  This is a critical issue, installing
the base system will be impossible until it's fixed.

>-- newt/slang damage, flashing dbootstrap screen on start

We have a workaround for this now so I don't think it's a blocker for 3.0.18.
I'd rather leave well alone for the moment.

p.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 3.0.18 status confirmation

[David Kimdon]

Fri, Dec 14, 2001 at 02:02:48AM -0500 wrote:
> 
> Sorry, I've been away on business travel but I'm back now.
> 
> >From my scan of the debian-boot list, I take it these bugs are holding
> 3.0.18 release:
> 
>   Bug#123387 -- busybox wget won't work with debootstrap anymore
yup, based on what Matt wrote in the BTS it sounds like this one will
be uploaded soon.

> -- newt/slang damage, flashing dbootstrap screen on start
I'm getting good behavior on my builds with the fix in rootdisk.sh
that makes sure i18n builds get the utf8 newt.  I think we are okay,
I'm building a full set of i386 out of cvs now (including my own
version of the busybox fix) that I hope to upload to klecker.

> 
> Aren't there any clues on this one yet?  Was there a diagnosis/fix for
> this that I missed?  Is it fixed in the new libnewt0 0.50.18 ?
> 
> It seems to me it's a question the build dependancies or 'make check'
> doing some extra checking to ensure consistency in slang/newt pic and
> utf8 libraries currently installed...

The issue was the wrong library to begin with getting put on the root
disk, I think.  We've seen lots of conflicting successes and failures
on this one so it is difficult to be certain.  Hopefully I can get
somethign built/tested and uploaded today or tomorrow and that will
clear things up.

-David


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]