Re: 3.0.19 install issues

[Daniel Jacobowitz]

On Mon, Jan 07, 2002 at 07:21:41PM -0700, Chris Tillman wrote:
> On Mon, Jan 07, 2002 at 04:07:35PM -0500, Daniel Jacobowitz wrote:
> >   - Mount Previously Initialized Partition failed to mount the FAT32
> > filesystem.  The error was "No such file or directory".  Not so useful.
> > 
> >   - Choosing "harddisk" as an installation medium fails.  Error was "No
> > such device".  No idea.
> 
> There have been other reports of this.
> 
> >   - Perl gave me a lot of locale warnings.  These are because LANG is set
> > to "English (QWERTY/US)".  Someone's picked a bad name for a variable, I
> > think.
> 
> I submitted a bug on this, I think pb just committed a fix.

Good, thanks.  That was the one that worried me.

-- 
Daniel Jacobowitz   Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer


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

Re: 3.0.19 install issues

[Daniel Jacobowitz]

On Mon, Jan 07, 2002 at 02:46:21PM -0800, John H. Robinson, IV wrote:
> On Mon, Jan 07, 2002 at 04:07:35PM -0500, Daniel Jacobowitz wrote:
> > I just ran through a clean Woody installation on 3.0.19; here's my
> > observations from it.  Hope these are useful.  Please CC me on any comments;
> > I no longer read debian-boot.
> > 
> >   - Choosing "mounted" defaults to /instmnt but is actually RELATIVE TO
> > "/instmnt/".  This results in a lot of confusion and some ugly doubled
> > slashes.
> 
> you gotta be kidding me :(
> i thought i had fixed all that :( :(
> 
> were you using fresh-from-the-cvs sources?

I was using the set Adam built; did you fix it after 3.0.19 was
uploaded?

-- 
Daniel Jacobowitz   Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer


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

Bug#128237: Slight misunderstanding

[Joe Drew]

The images-1.44 directory _does_ exist under the 32 and 64 directories;
however, when selecting the directory, no mention of 32 or 64 is made.

This is probably not an 'important' bug anymore, but I'll let you be the
judge.
-- 
Joe Drew <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

Please encrypt email sent to me.


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

Bug#128237: boot-floppies: [hppa] net install should not use nonexistent images-1.44

[Joe Drew]

Package: boot-floppies
Version: N/A; reported 2002-01-07
Severity: important

Using the network base installation on hppa, images-1.44 is searched for, which
doesn't exist in hppa. Instead, boot-floppies should use 32 or 64, depending 
on the kernel currently booted.

-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux pisces 2.4.13 #1 Fri Nov 2 17:29:57 EST 2001 i686
Locale: LANG=en_US, LC_CTYPE=



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

Re: PReP hackers wanted

[Colin Walters]

On Mon, 2002-01-07 at 20:28, Tom Rini wrote:

> And it just works now.  I'll test this tomorrow too probably and post
> the patches (I've cleaned up a few things too..)

Very cool!  

Now we just need someone to look at CHRP :)

Let's move this discussion completely to debian-boot; that's the most
appropriate mailing list.


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

Re: 3.0.19 install issues

[Chris Tillman]

On Mon, Jan 07, 2002 at 04:07:35PM -0500, Daniel Jacobowitz wrote:
>   - Mount Previously Initialized Partition failed to mount the FAT32
> filesystem.  The error was "No such file or directory".  Not so useful.
> 
>   - Choosing "harddisk" as an installation medium fails.  Error was "No
> such device".  No idea.

There have been other reports of this.

>   - Perl gave me a lot of locale warnings.  These are because LANG is set
> to "English (QWERTY/US)".  Someone's picked a bad name for a variable, I
> think.

I submitted a bug on this, I think pb just committed a fix.

-- 
*--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: PReP hackers wanted

[Tom Rini]

On Mon, Jan 07, 2002 at 06:05:32PM -0700, Tom Rini wrote:
> On Tue, Jan 08, 2002 at 01:42:43AM +0100, christian mock wrote:
> > > On Sun, 2002-01-06 at 14:15, Adam Di Carlo wrote:
> > > 
> > > > Well, the only reason I could see is if it either needs a kernel
> > > > config option enabled, not provided by the kernel-image-*-prep
> > > > package, or else if it needs a file from the kernel build not normally
> > > > provided by the package.  It should be pretty easy to read bootprep.sh
> > > 
> > > Probably.  But I have basically zero knowledge of the PReP architecture,
> > > and no way to test the resulting kernel image.  
> > > 
> > > So, I'd like to take this opportunity to call for anyone with a working
> > > knowledge of the PReP architecture, shell script, and preferably C to
> > > help work on the Debian boot-floppies for PReP.  Right now it doesn't
> > > even build because the root disk is too large. 
> > 
> > by 1954 bytes, yes.
> > 
> > are we sure we need /sbin/macfdisk on the _PReP_ root image? removing it 
> > allows the root disk to build (and even leaves 10 kB free!).
> 
> But what about the rescue image?  Right now I'm dying with:
> E: rootprep.bin is larger than root1440prep.bin (1482757 > 1474560)

And it just works now.  I'll test this tomorrow too probably and post
the patches (I've cleaned up a few things too..)

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/


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

Re: PReP hackers wanted

[Tom Rini]

On Tue, Jan 08, 2002 at 01:42:43AM +0100, christian mock wrote:
> > On Sun, 2002-01-06 at 14:15, Adam Di Carlo wrote:
> > 
> > > Well, the only reason I could see is if it either needs a kernel
> > > config option enabled, not provided by the kernel-image-*-prep
> > > package, or else if it needs a file from the kernel build not normally
> > > provided by the package.  It should be pretty easy to read bootprep.sh
> > 
> > Probably.  But I have basically zero knowledge of the PReP architecture,
> > and no way to test the resulting kernel image.  
> > 
> > So, I'd like to take this opportunity to call for anyone with a working
> > knowledge of the PReP architecture, shell script, and preferably C to
> > help work on the Debian boot-floppies for PReP.  Right now it doesn't
> > even build because the root disk is too large. 
> 
> by 1954 bytes, yes.
> 
> are we sure we need /sbin/macfdisk on the _PReP_ root image? removing it 
> allows the root disk to build (and even leaves 10 kB free!).

But what about the rescue image?  Right now I'm dying with:
E: rootprep.bin is larger than root1440prep.bin (1482757 > 1474560)

> well, so far for today, I gotta get me a floppy drive to test this 
> tomorrow...

Er, how do you have one w/o a floppy drive?  And at least mine needs its
own floppy drive..

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/


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

nfs directory was not umounted when the installed system reboot?

[Shaul Karl]

I used nfs to install the base system. After having the installed 
system rebooted via the `reboot the system' option I still had a line 
with the installed system in the server's /var/lib/nfs/rmtab file.
Does that mean that the nfs server still consider the client to be 
using the previously mounted directory? I also get `device is busy' 
when trying to umount the server fs though there seem to be no process 
that is actually using this fs other then nfsd.

Some more reasons to be sceptic about this report are:
(1) I am new to nfs.
(2) I replaced the kernel and modules of the 2.2r0 boot floppies with 
the ones from woody boot floppies. Other then that I was installing 
2.2r0.
(3) When I have tried to use the menu in order to configure the drivers 
I did not get the list of modules. The only option that I was offered 
was to exit. Therefore I got the modules loaded by doing a manual 
insmod from the 2nd vt. One reason that this is bad is that I do not 
know the dependencies of the nfs module. I was satisfied by seeing that 
nfs is working after insmoding the sunrpc and nfs modules. I am not 
sure but it could be that I insmod the lockd module as well. I also 
manually insmoded the required modules for the Ethernet card.
(4) I believe that with woody installation one get 2 modules loaded 
automatically. Yet when I changed to the 2nd vt during the installation 
process I could not see that these modules are installed. Therefore I 
also insmod manually the unix module. I did not remember the name of 
the other module and did not bother to find it since the installation 
seemed to work properly.
-- 

Shaul Karl
email: shaulka(at-no-spam)bezeqint.net 
   Please replace (at-no-spam) with an at - @ - character.
   (at-no-spam) is meant for unsolicitate mail senders only.



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

Re: PReP hackers wanted

[christian mock]

> On Sun, 2002-01-06 at 14:15, Adam Di Carlo wrote:
> 
> > Well, the only reason I could see is if it either needs a kernel
> > config option enabled, not provided by the kernel-image-*-prep
> > package, or else if it needs a file from the kernel build not normally
> > provided by the package.  It should be pretty easy to read bootprep.sh
> 
> Probably.  But I have basically zero knowledge of the PReP architecture,
> and no way to test the resulting kernel image.  
> 
> So, I'd like to take this opportunity to call for anyone with a working
> knowledge of the PReP architecture, shell script, and preferably C to
> help work on the Debian boot-floppies for PReP.  Right now it doesn't
> even build because the root disk is too large. 

by 1954 bytes, yes.

are we sure we need /sbin/macfdisk on the _PReP_ root image? removing it 
allows the root disk to build (and even leaves 10 kB free!).

well, so far for today, I gotta get me a floppy drive to test this 
tomorrow...

ciao,

cm.

-- 
** christian mock in vienna, austria -- http://www.tahina.priv.at/~cm/
Vielleicht ist es aber auch nur einfach Zeit, dem Wolfi wieder den
root-Account wegzunehmen. Er ist noch zu klein dafuer.
 Ferdinand Goldmann in at.gesellschaft.politik





msg14709/pgp0.pgp
Description: PGP signature

Bug#127971: boot-floppies: Missing loopback device and localhost in /etc/hosts

[Petter Reinholdtsen]

[Philip Blundell]
> Did you actually use this option, or did you continue the installation in 
> some other way (e.g. using the new "chroot without rebooting", or by hitting
> Ctrl-Alt-Delete, or anything of that kind)?

I'm pretty sure I used the "Reboot the system" entry, after making the
boot floppy and skipping the lilo config.


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

Re: 3.0.19 install issues

[John H. Robinson, IV]

On Mon, Jan 07, 2002 at 04:07:35PM -0500, Daniel Jacobowitz wrote:
> I just ran through a clean Woody installation on 3.0.19; here's my
> observations from it.  Hope these are useful.  Please CC me on any comments;
> I no longer read debian-boot.
> 
>   - Choosing "mounted" defaults to /instmnt but is actually RELATIVE TO
> "/instmnt/".  This results in a lot of confusion and some ugly doubled
> slashes.

you gotta be kidding me :(
i thought i had fixed all that :( :(

were you using fresh-from-the-cvs sources?

-john


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

cvs commit to boot-floppies/utilities/dbootstrap/po by mss

[Debian Boot CVS Master]

Repository: boot-floppies/utilities/dbootstrap/po
who:mss
time:   Mon Jan  7 13:53:59 PST 2002
Log Message:
  removed ALV from the authors list by his request

Files:
changed:ru.po


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

Re: 3.0.19 install issues

[Herbert Xu]

Daniel Jacobowitz <[EMAIL PROTECTED]> wrote:

> I picked the udma100-ext3 flavor; I wanted ext3 for my root FS.  I think a

Hmm, you do know that ext2 can be trivially converted to ext3 right?
-- 
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


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

One last issue

[Daniel Jacobowitz]

Interestingly, the installer also decided to remove PCMCIA support.  I don't
know why; the module loaded just fine, and it seems to work.

-- 
Daniel Jacobowitz   Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer


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

More 3.0.19 woes

[Daniel Jacobowitz]

... and I thought I was done...

Base-config somehow got run a second time, after a number of packages had
configured.  I didn't see any errors, but some (like exim) just never came
up.

Pretty good otherwise!

-- 
Daniel Jacobowitz   Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer


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

3.0.19 install issues

[Daniel Jacobowitz]

I just ran through a clean Woody installation on 3.0.19; here's my
observations from it.  Hope these are useful.  Please CC me on any comments;
I no longer read debian-boot.

The machine was a Sony Vaio R505JL.  It has a roughly firewire-driven
expansion bay, but the BIOS successfully masquerades the floppy drive as a
real drive, so I was able to use a normal rescue/root set.  The CD (DVD)
drive wasn't seen, unsurprisingly.

I picked the udma100-ext3 flavor; I wanted ext3 for my root FS.  I think a
fair number of these problems are related to that.

In particular:
  - Mount Previously Initialized Partition failed to mount the FAT32
filesystem.  The error was "No such file or directory".  Not so useful.

  - Choosing "harddisk" as an installation medium fails.  Error was "No
such device".  No idea.

  - Choosing "mounted" defaults to /instmnt but is actually RELATIVE TO
"/instmnt/".  This results in a lot of confusion and some ugly doubled
slashes.

  - Installing from mounted failed to copy the kernel off the rescue disk. 
The loop device was successfully configured (I checked by mounting it on
VT2) but the mount failed again with "No such device".  del_loop failed
repeatably, also - negative return code from LOOP_CLEAR_FD.

  - bterm glitch: Last line of the screen remained colored.  I'll
investigate this in a few days.

  - Some error messages are still written to the screen where dialog is
running.  I don't know which, since they flash by pretty quickly.  My guess
is right after the installation failed to read kernel off of rescue.bin,
above.

  - Network install, conveniently, did not have most of these problems.

  - Perl gave me a lot of locale warnings.  These are because LANG is set
to "English (QWERTY/US)".  Someone's picked a bad name for a variable, I
think.


Minor nits: Tasksel still wraps top to bottom in its scroll list, which I
find massively unintuitive.  Debootstrap alphabetizes downloaded packages by
package name rather than by source package / URL; that's just personal
preference for organization.


Any of these I should file particular bug reports on?
-- 
Daniel Jacobowitz   Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer


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

mice

[James Bennett]

I've been trying to install linux 2.2 r4 on a 
Windows98 system from CD1 (and others) but cannot get the X system to respond to 
the "mouse".
The computer is an intel pentium ii of very 
ordinary variety (an NEC package) with a Logitech M-S48 mouse which seems to be 
of the ordinary PS2 sort with two buttons and a centre wheel cum button that 
ought to be using /dev/psaux. I can find no documentation to clarify what the 
problem might be (I haven't looked with great thoroughness since using the 
system without graphics, while not as bad as using a keypunch, is not 
pleasing).
 
Can you give me any idea how to make the mouse 
work? I'm very tired of editing lilo.conf.
 
James Bennett14/4 Craigmillar 
CourtCraigmillar Castle GardensEdinburgh EH16 4AEScotland[EMAIL PROTECTED]

Processed: your mail

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 127413 pending
Bug#127413: base-config: 101 instances of Setting locale failed message during install
Tags added: pending

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

Bug#127971: boot-floppies: Missing loopback device and localhost in /etc/hosts

[Philip Blundell]

The appropriate stuff should get written to /etc/hosts and
/etc/network/interfaces when you choose "Reboot the system" from the main
menu, if the network hasn't ever been configured at that point.  It seems
that this didn't happen on your machine, for whatever reason.

Did you actually use this option, or did you continue the installation in 
some other way (e.g. using the new "chroot without rebooting", or by hitting
Ctrl-Alt-Delete, or anything of that kind)?

p.



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

cvs commit to boot-floppies/debian by pb

[Debian Boot CVS Master]

Repository: boot-floppies/debian
who:pb
time:   Mon Jan  7 12:18:50 PST 2002
Log Message:
  log them changes
  

Files:
changed:changelog


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

cvs commit to boot-floppies by pb

[Debian Boot CVS Master]

Repository: boot-floppies
who:pb
time:   Mon Jan  7 12:17:00 PST 2002
Log Message:
  correct arm kernel numbering
  enable LC on alpha
  

Files:
changed:config


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

cvs commit to boot-floppies/utilities/dbootstrap by pb

[Debian Boot CVS Master]

Repository: boot-floppies/utilities/dbootstrap
who:pb
time:   Mon Jan  7 12:15:23 PST 2002
Log Message:
  Comment out no-longer-included Greek keymap
  

Files:
changed:kbdconfig.c


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

cvs commit to boot-floppies/utilities/dbootstrap by pb

[Debian Boot CVS Master]

Repository: boot-floppies/utilities/dbootstrap
who:pb
time:   Mon Jan  7 12:13:19 PST 2002
Log Message:
  Write out locale properly in dbootstrap_settings
  

Files:
changed:util.c


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

Re: problem with console-data 1999.08.29-23 ?

[Phil Blundell]

>Yes, we can disable gr and make sure none of the below are used:
>
>> [1] Those are: mac-usb-pt-latin1.kmap, mac-de-latin1-nodeadkeys and
>> mac-us-dvorak.kmap.
>
>...
>
>Anyone on the debian-boot list wanna take it or must I do it tonight?

I've removed gr (from keymaps.sh anyway; I haven't dealt with
dbootstrap/kbdconfig.c yet) and the build seems to work okay.  
None of the other three seemed to be used.

p.


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

cvs commit to boot-floppies by pb

[Debian Boot CVS Master]

Repository: boot-floppies
who:pb
time:   Mon Jan  7 10:22:00 PST 2002
Log Message:
  Remove "gr" keymap
  

Files:
changed:keymaps.sh


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

솔직히 짱폰 엽기폰 광고입니다.

[여상엽]

Title: »õ·Î¿î »ý°¢ÀÌ ¼¼»óÀ» ¹Ù²ß´Ï´Ù.
 ¸ÞÀÏÀ» ¹Þ±â ¿øÄ¡ ¾ÊÀ¸½Ã¸é ²À! ¼ö½Å°ÅºÎ¸¦ ÇØÁÖ¼¼¿ä. ¼ö½Å °ÅºÎ´Â ÀÌ°÷À» ´­·¯ÁÖ¼¼¿ä. 

Re: powerpc b-f build compiles the kernel

[Tom Rini]

On Sun, Jan 06, 2002 at 10:02:01PM -0700, Erik Andersen wrote:
> On Sun Jan 06, 2002 at 01:54:12PM -0700, Tom Rini wrote:
> > On Sun, Jan 06, 2002 at 02:15:11PM -0500, Adam Di Carlo wrote:
> > > Colin Walters <[EMAIL PROTECTED]> writes:
> > > 
> > > > What annoys me about bootprep.sh is that it builds a kernel as part of
> > > > the boot-floppies build process; I don't see why it can't just use a
> > > > kernel-image package like every other arch.
> > > 
> > > Well, the only reason I could see is if it either needs a kernel
> > > config option enabled, not provided by the kernel-image-*-prep
> > > package, or else if it needs a file from the kernel build not normally
> > > provided by the package.  It should be pretty easy to read bootprep.sh
> > > and take a look.
> > 
> > Can someone post that?  I'm sort-of curious what needs to be done
> > 'special' for a prep box..
> 
> I used a prep box a while back.  I recall the build process
> needed to compile the initrd into some special section in the
> kernel so the thing could netboot...

Okay.  What's going on is that we can't fit the initrd and kernel on the
same floppy.  It _should_ be possible to do them on seperate floppies
(since PReP uses the normal PC floppy driver) like x86.  What this
script does is build a kernel with the ramdisk inside (all ppc arches
can do this, but only chrp can do it w/ yaboot (right now)) of the
'zImage', and then boot that off of CD or network.

Right now I'm not sure if kernel-package will actually produce a working
kernel-image for PReP, unless (maybe) it's compiled on a PReP box.

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/


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

Bug#124386: french + euro keyboard is latin15, not latin0 (which naturally does not work).

[Sven]

On Sun, Jan 06, 2002 at 06:52:23PM +, Philip Blundell wrote:
> What's the situation with this bug now?  If the problem still happens, I think
> we need to see the exact error messages in order to make any headway.

Didn't have time to check, don't have floppies around right now, will get some
and do the test tomorrow, if that is ok with you ...

Friendly,

Sven Luther


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

Re: One should be patient with root.bin and modules.dep

[Erik Andersen]

On Mon Jan 07, 2002 at 10:58:28AM +, Richard Hirst wrote:
> On Mon, Jan 07, 2002 at 03:08:42AM -0700, Erik Andersen wrote:
> > to console.  If people want to see what the kernel has to say,
> > (like that module foo didn't load) they can visit the syslog
> > output on another VT,
> 
> ... but not if running on serial console.

shell out and read /var/log/syslog

 -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: One should be patient with root.bin and modules.dep

[Shaul Karl]

> On Sun Jan 06, 2002 at 02:58:53PM -0500, Adam Di Carlo wrote:
> > Shaul Karl <[EMAIL PROTECTED]> writes:
> > 
> > > When using the latest root.bin that I could find (18-dec-2001) the 
> > > screen get flooded with messages about modprobe not being able to read 
> > > the modules.dep. Altough it is able to recover and continue the 
> > > installation process one should be patient in order for this to happen.
> > 
> > Well, you're english is a little bit shakey, but I know the issue you
> > are taking about.  These messages IIRC are caused by kmod (the kernel
> > module loader) not being happy.  We try to force it to shut up and
> > work-around but ...  anyhow, it's either something we can fix by
> > messing around in root.bin, or it's a limitation in kmod.
> 
> How about adding this to boot-floppies/utilities/dbootstrap/main.c
> 
> - /* Downgrade kernel verbosity */
> - klogctl(8, NULL, 4);
> + /* Don't let the kernel printk stuff to the console. */
> + klogctl(6, NULL, 0);
> 
>  -Erik
> 
> --
> Erik B. Andersen http://codepoet-consulting.com/
> --This message was written using 73% post-consumer electrons--


Suppose those lines will be used and it works, won't the result be that 
from a user point of view the machine will be seemingly doing nothing 
for some time?
As it was without this patch it took some time for my 486 to continue 
with the installation. Although it was not a very long time it was 
still somewhat significant. I do believe that some people would have 
thought that something goes wrong and boot the machine.
-- 

Shaul Karl
email: shaulka(at-no-spam)bezeqint.net 
   Please replace (at-no-spam) with an at - @ - character.
   (at-no-spam) is meant for unsolicitate mail senders only.



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

INIT: Id "1" respawning too fast .....

[Adam F. Bogacki]

Hi,
I recently installed kernel 2.4.14 on hdb, fixed up a minor LILO problem -
and for a while it worked. I was impressed with the boot speed and the
number of
drivers...

Yesterday, however, when I tried to boot up it worked until gdm and I
received the following messages:

"Starting Gnome Display Manager: gdm.
INIT: Id "1" respawning too fast: disabled for 5 minutes.
INIT: Id "1" respawning too fast: disabled for 5 minutes.
INIT: Id "1" respawning too fast: disabled for 5 minutes.
INIT: Id "1" respawning too fast: disabled for 5 minutes."

and so on.

I have unsuccessfully tried to boot in via disk and CD-ROM but I always
get more of the above.

How do I fix this ?

Adam Bogacki,
[EMAIL PROTECTED]


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

cvs commit to tasksel/po by claush

[Debian Boot CVS Master]

Repository: tasksel/po
who:claush
time:   Mon Jan  7 04:15:52 PST 2002
Log Message:
  Update tasksel da.po

Files:
changed:da.po


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

Re: problem with console-data 1999.08.29-23 ?

[Wartan Hachaturow]

On Mon, Jan 07, 2002 at 10:45:32AM +0100, Martin Michlmayr wrote:

> gr.kmap is broken anyway and should imho not be used.  On my system,
> loading it results in
> 
> | findfile(): timeout waiting for undead child(ren) ?

There is a bug #50587 opened by Yann on that matter.

-- 
Regards, Wartan.
echo "Your stdio isn't very std." 
-- Larry Wall in Configure from the perl distribution


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

Re: One should be patient with root.bin and modules.dep

[Richard Hirst]

On Mon, Jan 07, 2002 at 03:08:42AM -0700, Erik Andersen wrote:
> to console.  If people want to see what the kernel has to say,
> (like that module foo didn't load) they can visit the syslog
> output on another VT,

... but not if running on serial console.

Richard


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

Re: One should be patient with root.bin and modules.dep

[Erik Andersen]

On Mon Jan 07, 2002 at 01:19:42AM -0500, Adam Di Carlo wrote:
> Erik Andersen <[EMAIL PROTECTED]> writes:
> 
> > How about adding this to boot-floppies/utilities/dbootstrap/main.c
> > 
> > -   /* Downgrade kernel verbosity */
> > -   klogctl(8, NULL, 4);
> > +   /* Don't let the kernel printk stuff to the console. */
> > +   klogctl(6, NULL, 0);
> 
> Well, I'd love to if either (a) I understood what this meant, or (b)
> someone had testing this and shown that it works.

man 2 syslog

klogctl is the libc name for the syslog system call.  As is, we
tell the kernel is is fine to spam the console (i.e.  even when
dbootstrap is running) as long as the priority is less then 4
(KERN_WARNING).

Since we log everything to the syslog (i.e. the sysklogd proces
which is why libc changed the syscall name to something less
confusing), there is no need to spam the console.

So 'klogctl(6, NULL, 0);' can be used to disable all printk's 
to console.  If people want to see what the kernel has to say,
(like that module foo didn't load) they can visit the syslog
output on another VT,

 -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: Booting from PCMCIA CD-ROM

[Martin Michlmayr]

* David B Harris <[EMAIL PROTECTED]> [20020106 21:19]:
> > Is this i386-specific?
> 
> Hell, I think it's even *device*-specific.

Might be.  I could't tell, sorry.  I think it should be documented
anyway since it's the only way to boot from a PCMCIA CD-ROM -- at
least on those which use that particular address for their controller.

-- 
Martin Michlmayr
[EMAIL PROTECTED]


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

Processed: your mail

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 107591 [sparc] network boot broken for sun4u
Bug#107591: sun4u tftpboot, unable to mount root fs
Changed Bug title.

> severity 107591 serious
Bug#107591: [sparc] network boot broken for sun4u
Severity set to `serious'.

> 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: problem with console-data 1999.08.29-23 ?

[Martin Michlmayr]

* tbm <[EMAIL PROTECTED]> [20020107 10:45]:
> Can you try to load another keymap with imports the euro (e.g. uk, fr,
> de).  If it fails, you'll probably need a newer loadkeys.  If this is

I just tried loadkeys from boot-floppies.  Most keymaps work fine,
apart from gr and those which fail anyway (which are included in the
package but should not be used[1]).  Can you just disable gr?
Upgrading to a newer loadkeys seems like a bad idea since the newer
version doesn't appear to have the -b option which you use.

[1] Those are: mac-usb-pt-latin1.kmap, mac-de-latin1-nodeadkeys and
mac-us-dvorak.kmap.
-- 
Martin Michlmayr
[EMAIL PROTECTED]


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

Re: smc-ultra module: woody has the same problem as potato? An odd work around?

[Phil Blundell]

>I tried to reproduce it and failed. Now it works as expected, apart 
>from a few messages about not being able to create 
>/target/usr/sbin/modules (probably wrong about the exact path) which 
>goes away.
>>From memory the error message said the device or resource are busy and 
>suggested that it could be due to wrong parameters that were given as 
>input. I believe the same message was written more then once.

Sounds like the card detection is just a bit flaky then.  You probably need
to take this up with the kernel folks if you want to pursue it; I don't think
that there is anything we can do in the boot-floppies to improve the situation.

p.


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

Re: problem with console-data 1999.08.29-23 ?

[Martin Michlmayr]

* Adam Di Carlo <[EMAIL PROTECTED]> [20020106 21:58]:
> utilities/writemaps/loadkeys -b -v .../usr/share/keymaps/i386/qwerty/gr.kmap.gz
> Loading .../usr/share/keymaps/i386/qwerty/gr.kmap.gz
> switching to euro
> unknown keysym `cent'
> 
> Is this a problem in our loadkeys program or a problem in the keymaps
> file?  I note that the 'cent' keysym according to our sources is
> actually called 'currency'.  

gr.kmap is broken anyway and should imho not be used.  On my system,
loading it results in

| findfile(): timeout waiting for undead child(ren) ?

I have no idea why since all the files it tries to import exist afaik.

Can you try to load another keymap with imports the euro (e.g. uk, fr,
de).  If it fails, you'll probably need a newer loadkeys.  If this is
a problem for boot-floppies, the cent can be turned off again in
console-data since the euro is more important anyway.

-- 
Martin Michlmayr
[EMAIL PROTECTED]


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

Bug#127677: boot-floppies: problems with reinstalling base-system

[Tomas Pospisek]

Is it appropriate to Cc: you? Or do you guys get the bugreport anyway?

On Sun, 6 Jan 2002, Philip Blundell wrote:

> In message <[EMAIL PROTECTED]>, Tomas Pospisek? writes:
> >That when something breaks during install of the basesystem, as f.ex.
> >a disk error etc., a newby will *not* be able to finish the installation.
> >He will have to start from scratch (reformat partition!)
>
> What stops the old base system from just being overwritten?  Did you see an
> error message?  If so, what was it?  There shouldn't be any need to remove
> the old files first.

No I haven't seen any error. It just wouldn't work (chroot would complain
about non-ELF format afterwards, since there still was the powercp stuff).

> That said, I don't think that failures while installing from basedebs.tgz
> are worth busting a gut to legislate for.  Once basedebs.tgz is in the right
> place in the archive it should be much less likely that people are going to
> make the mistake you did and install a totally bogus archive;

talking about basedebs.tgz - it'd be nice to either remove the option to
"install base from floppy" (it's in the choice menu when you go choose to
install the base system) or to provide those disks (like it was in potato)
as well (unfortunately that will be *many* disks now!). Otherwise it's
just confusing.

> and considering
> that this stuff is being both read from and written to a local hard disk,
> the possibility of transient problems seems quite remote too.  (As opposed to
> debootstrap, where there is a real danger that a brief network outage might
> screw you up halfway.)
>
> And, in the worst case, having to go back and reinitialise the partition is
> hardly the end of the world.

I do agree with you that it's not the end of the world. But IMO it's
strange that something like this happens, which tells me that there's
something wrong maybe there are a couple other problems that come
together to create this effect. It can be expected that this will affect
you elsewhere as well.

And thanks to all of you there doing the work on the install system!!!
*t

---
 Tomas Pospisek
 sourcepole-   Linux & Open Source Solutions
 http://sourcepole.com
 Elestastrasse 18,  7310 Bad Ragaz,  Switzerland
 Tel:+41 (81) 330 77 13,  Fax:+41 (81) 330 77 12




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