Re: still-extant potato boot problems (kmod/runany modprobe loop)

[Martin Schulze]

This is the proper list, I'm forwarding.

Daniel Barclay wrote:
> 
> Are there any fixes (or even diagnoses) yet for the following problem?
> Has anyone else even seen these symptoms?
> 
> 
> 
> Earlier I reported a problem with installing potato (from scratch)
> and getting errors at boot time like:
> 
>kmod: runaway modprobe loop assumed and stopped
> 
> and many occurrences of:
> 
>modprobe: modprobe: Can't open dependencies files /lib/modules/2.2.17/modules.dep 
>(No such file or directory)
> 
> (Note that those errors were from booting the installation boot 
> diskettes (rescue.bin/root.bit).  Specifically, it was from 
> before I had a chance to make any choices or affect anything.)
> 
> 
> 
> 
> I thought I'd try getting to potato by upgrading (a clone of) my 
> slink system.  The upgrade went pretty well (well, I accidentally
> upgraded the original instead of the clone, but the clone seems
> to be working fine) until I installed the 2.2.17 kernel and rebooted.  
> Those boot-time errors returned.
> 
> I also started getting a bunch of other errors, such as:
> 
>- "modprobe: Can't locate module xxx"
>  (at bootup; for roughly half of the modules)
> 
>- "start ppp0: SIOCSIFMETRIC: Operation not supported"
>  (asynchonously, after something had triggered diald)
> 
>- "Use of setserial/setrocket to set SPD_* flags is deprecated"
>  (asynchonously)
> 
>- something like "xmit when interface down"
>  (asynchonously)
> 
>- (I can't even ping the other end of my diald's PPP connection 
>   (I used the numeric IP address logged by pppd when it
>   connected).)
> 
> 
> 
> Are there any known hardware dependencies that could affect this
> (especially when just booted of the installation diskettes)?
> 
> Here's what I can think of regarding mysystem:
> 
> - Gigabyte GX-5AX revision 3.0 motherboard
> - AMD K6-2 300MHz
> - 128MB DRAM
> - dual IDE controller, UDMA/33
> - IDE disks on hda, hdc
> - IDE CD-ROM on hdd
> - Diamond Viper V330
> - TekRam DC390-F SCSI card (for tape drive; no disks attached)
> - SoundBlaster 16 (?; version that causes "missing second channel" message in
>   2.0.38/slink )
> - USB ports (not used)
> - standard floppy
> - no network card (I use ppp via diald)
> - no ZIP drive
> - nothing special or weird that I can think of
> 
> - works fine under my Slink system 
> 
> 
> Can anyone help me with this?  I've been trying to upgrade
> to potato for over a week.  
> 
> 
> Thanks,
> Daniel
> -- 
> Daniel Barclay
> [EMAIL PROTECTED]
> (Hmm.  A little worrisome:  http://www.junkbusters.com/cgi-bin/privacy
> http://www.anonymizer.com/snoop.cgi )
> 
> 
> -- 
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

-- 
GNU GPL: "The source will be with you... always."


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

New release of boot-floppies

[Martin Schulze]

I've been told that Adam plans a new release.  I highly appreciate
that since the 'cant find /lib/modules/2.2.16/modules.dep file' error
gives a really bad idea of what Debian is doing.

Wrt other stuff, what is high on your priority list that needs to
be fixed?  I'd like to help.  At the moment I have some spare time
to use for useful stuff.

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."


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

Re: debiandoc-sgml and Russian, Polish

[Ardo van Rangelrooij]

Adam Di Carlo ([EMAIL PROTECTED]) wrote:
> 
> As I understand it, we need the woody debiandoc-sgml pakcage in order
> to build Russian and Polish installation manual and release notes
> (assuming they are otherwise ok), correct?

For Polish yes, for Russian I'm not aware of any changes made since the
last potato update.

> It's a little annoying to be in the situation again where for frozen
> or stable updates we need stuff from woody.  Do you think it's
> possible to upload debiandoc-sgml, at some point, to frozen/stable in
> an effort to achieve this consistency?  I know it breaks normal rules
> for upgrades to stable, but on the other hand, it's needed for proper
> boot-floppies builds, so I think that would justify its inclusion.

It's no problem making the version uploaded to woody also go into potato.
I've made some more changes than just adding Polish locale support, but
none is likely to break anything which isn't already broken. ;-)

Just say the word and I'll upload it.

Thanks,
Ardo
-- 
Ardo van Rangelrooij
home email: [EMAIL PROTECTED], [EMAIL PROTECTED]
home page:  http://home.flevonet.nl/~avrangel, http://www.debian.org/~ardo
PGP fp: 3B 1F 21 72 00 5C 3A 73  7F 72 DF D9 90 78 47 F9


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

Re: Partition file proposal

[Martin Schulze]

Chris Rutter wrote:
> I have a fairly wacky proposal which concerns, mainly, boot-floppies on
> Linux/ARM.  I've attached the proposal here; it should actually of generic
> relevance, but I'm only working on ARM for the time being.  If anyone had
> any comments I'd be hugely hugely greatful.  If not, skip the message.

I'm not quite sure if debian-boot would be the proper forum to discuss
this issue since it looks like it affects any Linux on ARM/Acorn
installation.  Therefore I guess general linux-arm lists and arm
kernel hackers would be required to decide, no?

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."

Please always Cc to me when replying to me on the lists.


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

Bug#68659: mke2fs(8) is inaccurate

[Martin Schulze]

> The filesystem image on the root disk (root.bin) shouldn't
> use ext2 extensions that are incompatible with 2.0.x kernels.
> 
> The current image uses those extensions, making it impossible to
> modify the filesystem with a slink system.
> 
> (I'm trying to see some error message that are quickly erased
> by an installation dialog, but I can't even look at the filesystem
> to see if I can modify the script to preserve the messages.)

Looking at the current code I see how it is created:

mke2fs -F -q -N $inodes -m 0 $floppy

-F   is force even for odd geometry
-q   is quiet
-N   looks like it sets the number of inodes or the inode/byte ratio
-m   sets the reserved-blocks-percentage

Nothing that looks 2.2 specific.  However there may be some implicit
extensions if one creates an ext2 with current mke2fs and 2.2.x.

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."

Please always Cc to me when replying to me on the lists.


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

Bug#68659: mke2fs(8) is inaccurate

[Herbert Xu]

Martin Schulze <[EMAIL PROTECTED]> wrote:
>
> Looking at the current code I see how it is created:

> mke2fs -F -q -N $inodes -m 0 $floppy

> -F   is force even for odd geometry
> -q   is quiet
> -N   looks like it sets the number of inodes or the inode/byte ratio
> -m   sets the reserved-blocks-percentage

> Nothing that looks 2.2 specific.  However there may be some implicit
> extensions if one creates an ext2 with current mke2fs and 2.2.x.

-O none is needed if you want 2.0 compatibility whill running mke2fs on
a 2.2 system.
-- 
Debian GNU/Linux 2.1 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]

Bug#68659: mke2fs(8) is inaccurate

[Martin Schulze]

Herbert Xu wrote:
> Martin Schulze <[EMAIL PROTECTED]> wrote:
> >
> > Looking at the current code I see how it is created:
> 
> > mke2fs -F -q -N $inodes -m 0 $floppy
> 
> > -F   is force even for odd geometry
> > -q   is quiet
> > -N   looks like it sets the number of inodes or the inode/byte ratio
> > -m   sets the reserved-blocks-percentage
> 
> > Nothing that looks 2.2 specific.  However there may be some implicit
> > extensions if one creates an ext2 with current mke2fs and 2.2.x.
> 
> -O none is needed if you want 2.0 compatibility whill running mke2fs on
> a 2.2 system.

Thanks.  Can you give me some mor information?
I'll add that.

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."

Please always Cc to me when replying to me on the lists.


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

Bug#68659: mke2fs(8) is inaccurate

[Herbert Xu]

On Sun, Aug 13, 2000 at 01:53:38PM +0200, Martin Schulze wrote:
> 
> Thanks.  Can you give me some mor information?
> I'll add that.

>From mke2fs(8):

   -O feature[,...]
  Create  the  filesystem  with  the  listed  set  of
  features  (filesystem  options).The   following
  features  are  supported: sparse_super, which cause
  the  filesystem  to  use  sparse  superblocks,  and
  filetype,  which will cause the filesystem to store
  file  type  information   in   directory   entries.
  Currently,  both  features are turned on by default
  unless mke2fs is run on a  system  with  a  pre-2.2
  Linux  kernel.   Warning:  Pre-2.2 Linux kernels do
  not  properly  support  the  filesystems  that  use
  either  of  these  two features.   Filesystems that
  may need to mounted on pre-2.2  kernels  should  be
  created  with  -O  none  which will disable both of
  these features, even if mke2fs is run on  a  system
  which can support these features.
-- 
Debian GNU/Linux 2.1 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]

Bug#68659: mke2fs(8) is inaccurate

[Jean-Philippe Guérard]

Le 2000-08-13 13:27:38 +0200, Martin Schulze écrivait :
> > The filesystem image on the root disk (root.bin) shouldn't
> > use ext2 extensions that are incompatible with 2.0.x kernels.
> > 
> > The current image uses those extensions, making it impossible to
> > modify the filesystem with a slink system.
>
> Looking at the current code I see how it is created:
> 
> mke2fs -F -q -N $inodes -m 0 $floppy
> 
> Nothing that looks 2.2 specific.  However there may be some implicit
> extensions if one creates an ext2 with current mke2fs and 2.2.x.

mke2fs defaults to 2.2 specific extension when used with a 2.2+ kernel,
unless told otherwise :

   -O feature[,...]
  Create  the  filesystem  with  the  listed  set  of
  features  (filesystem  options).The   following
  features  are  supported: sparse_super, which cause
  the  filesystem  to  use  sparse  superblocks,  and
  filetype,  which will cause the filesystem to store
  file  type  information   in   directory   entries.
  Currently,  both  features are turned on by default
  unless mke2fs is run on a  system  with  a  pre-2.2
  Linux  kernel.   Warning:  Pre-2.2 Linux kernels do
  not  properly  support  the  filesystems  that  use
  either  of  these  two features.   Filesystems that
  may need to mounted on pre-2.2  kernels  should  be
  created  with  -O  none  which will disable both of
  these features, even if mke2fs is run on  a  system
  which can support these features.

-- 
Jean-Philippe Guérard


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

Bug#68911: marked as done (boot-floppies: dbootstrap.h missing)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2000 13:49:41 +0200
with message-id <[EMAIL PROTECTED]>
and subject line dbootstrap.h not missing
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 10 Aug 2000 23:37:58 +
>From [EMAIL PROTECTED] Thu Aug 10 18:37:58 2000
Return-path: <[EMAIL PROTECTED]>
Received: from gondor.apana.org.au [:::203.14.152.114] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 13N1tY-00051r-00; Thu, 10 Aug 2000 18:37:55 -0500
Received: (from herbert@localhost)
by gondor.apana.org.au (8.11.0.Beta1/8.11.0.Beta1/Debian 8.11.0-1) id 
e7ANbcn17105;
Fri, 11 Aug 2000 09:37:39 +1000
Date: Fri, 11 Aug 2000 09:37:39 +1000
Message-Id: <[EMAIL PROTECTED]>
From: <[EMAIL PROTECTED]>
Subject: boot-floppies: dbootstrap.h missing
To: [EMAIL PROTECTED]
X-Mailer: bug 3.3.4
Delivered-To: [EMAIL PROTECTED]

Package: boot-floppies
Version: 2.2.16
Severity: normal

The file utilities/dbootstrap/dbootstrap.h is missing from the source
package.

-- System Information
Debian Release: 2.2
Kernel Version: Linux gondor 2.2.12 #2 Sat Sep 18 12:11:40 EST 1999 i586 unknown


---
Received: (at 68911-done) by bugs.debian.org; 13 Aug 2000 11:49:44 +
>From [EMAIL PROTECTED] Sun Aug 13 06:49:44 2000
Return-path: <[EMAIL PROTECTED]>
Received: from kuolema.infodrom.north.de [:::195.27.69.163] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 13NwGs-00066g-00; Sun, 13 Aug 2000 06:49:43 -0500
Received: from finlandia.Infodrom.North.DE (finlandia.Infodrom.North.DE 
[195.27.69.162])
by kuolema.infodrom.north.de (Postfix) with ESMTP id 72295146E7E
for <[EMAIL PROTECTED]>; Sun, 13 Aug 2000 13:45:54 +0200 (CEST)
Received: at Infodrom Oldenburg (/\##/\ Smail-3.2.0.102 1998-Aug-2 #2)
by finlandia.Infodrom.North.DE
via smail from stdin
id <[EMAIL PROTECTED]>
for [EMAIL PROTECTED]; Sun, 13 Aug 2000 13:49:41 +0200 (CEST) 
Date: Sun, 13 Aug 2000 13:49:41 +0200
From: Martin Schulze <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: dbootstrap.h not missing
Message-ID: <[EMAIL PROTECTED]>
Reply-To: Martin Schulze <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0i
Delivered-To: [EMAIL PROTECTED]

Prove:

auric!joey(pts):~>  tar tvfz 
/org/ftp.debian.org/ftp/dists/potato/main/source/admin/boot-floppies_2.2.16.tar.gz|grep
 dbootstrap.h
-rw-rw-r-- apharris/staff   7852 2000-05-26 18:23:59 
boot-floppies-2.2.16/utilities/dbootstrap/dbootstrap.h  <---+
-rw-rw-r-- apharris/staff  12853 2000-06-13 22:29:37 
boot-floppies-2.2.16/utilities/dbootstrap/http-fetch.c  |
-rw-rw-r-- apharris/staff   1437 2000-01-06 07:48:25 
boot-floppies-2.2.16/utilities/dbootstrap/http-fetch.h  |
auric!joey(pts):~> 
  |
   
  |
   
  There it is...

-- 
GNU GPL: "The source will be with you... always."

Please always Cc to me when replying to me on the lists.


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

Bug#68659: mke2fs(8) is inaccurate

[Steve Bowman]

On Sun, Aug 13, 2000 at 01:27:38PM +0200, Martin Schulze wrote:
> > The filesystem image on the root disk (root.bin) shouldn't
> > use ext2 extensions that are incompatible with 2.0.x kernels.
> > 
> > The current image uses those extensions, making it impossible to
> > modify the filesystem with a slink system.
> > 
> > (I'm trying to see some error message that are quickly erased
> > by an installation dialog, but I can't even look at the filesystem
> > to see if I can modify the script to preserve the messages.)
> 
> Looking at the current code I see how it is created:
> 
> mke2fs -F -q -N $inodes -m 0 $floppy
> 
> -F   is force even for odd geometry
> -q   is quiet
> -N   looks like it sets the number of inodes or the inode/byte ratio
> -m   sets the reserved-blocks-percentage
> 
> Nothing that looks 2.2 specific.  However there may be some implicit
> extensions if one creates an ext2 with current mke2fs and 2.2.x.

Yes, implicit extensions.  mke2fs(8) says that "-O none" is needed to
create a filesystem usable on a pre-2.2 kernel.

> 
> Regards,
> 
>   Joey
> 
> -- 
> GNU GPL: "The source will be with you... always."
> 
> Please always Cc to me when replying to me on the lists.
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
> 

-- 
Steve Bowman  <[EMAIL PROTECTED]> (preferred)
Buckeye, AZ   <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
  

Powered by Debian GNU/Linux 


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

Bug#68911: acknowledged by developer (boot-floppies: dbootstrap.h missing)

[Herbert Xu]

retitle 68911 Should not include dbootstrap.h in .cvsignore
reopen 68911
quit

On Sun, Aug 13, 2000 at 07:04:19AM -0500, Debian Bug Tracking System wrote:
> 
> Prove:
> 
> auric!joey(pts):~>  tar tvfz 
>/org/ftp.debian.org/ftp/dists/potato/main/source/admin/boot-floppies_2.2.16.tar.gz|grep
> dbootstrap.h
> -rw-rw-r-- apharris/staff   7852 2000-05-26 18:23:59 
>boot-floppies-2.2.16/utilities/dbootstrap/dbootstrap.h  <---+
> -rw-rw-r-- apharris/staff  12853 2000-06-13 22:29:37 
>boot-floppies-2.2.16/utilities/dbootstrap/http-fetch.c  |
> -rw-rw-r-- apharris/staff   1437 2000-01-06 07:48:25 
>boot-floppies-2.2.16/utilities/dbootstrap/http-fetch.h  |
> auric!joey(pts):~>   
>|
>  
>|
>  
>There it is...

Sorry, wrong bug title :)  It left my directory tree when I imported it into
CVS and unfortunately the .cvsignore file has "dbootstrap*" in it.
-- 
Debian GNU/Linux 2.1 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]

Processed: Re: Bug#68911 acknowledged by developer (boot-floppies: dbootstrap.h missing)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 68911 Should not include dbootstrap.h in .cvsignore
Bug#68911: boot-floppies: dbootstrap.h missing
Changed Bug title.
(By the way, that Bug is currently marked as done.)

> reopen 68911
Bug#68911: Should not include dbootstrap.h in .cvsignore
Bug reopened, originator not changed.

> quit
Stopping processing here.

Please contact me if you need assistance.

Darren Benham
(administrator, Debian Bugs database)


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

Bug#68872: Cannot reproduce

[Martin Schulze]

>  I have reinstalled the system but this time when initializing the root
> partirtion I chose compatibility with 2.0 kernels. This time the installation
> proceeded swiftly, and the modules list appeared in the Configure Driver
> modules phase.

FWIW: I am unable to reproduce this.

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."

Please always Cc to me when replying to me on the lists.


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

Processed: hmm

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 68872 [can't reproduce] Modconf does not locate module list.
Bug#68872: Modconf does not locate module list. 
Changed Bug title.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Darren Benham
(administrator, Debian Bugs database)


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

Bug#67771: marked as done (Modconf fails to start)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2000 14:34:33 +0200
with message-id <[EMAIL PROTECTED]>
and subject line modconf or not?
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 26 Jul 2000 18:30:34 +
>From [EMAIL PROTECTED] Wed Jul 26 13:30:34 2000
Return-path: <[EMAIL PROTECTED]>
Received: from (exchange.corp.myplay.com) [216.216.10.228] 
by master.debian.org with esmtp (Exim 3.12 2 (Debian))
id 13HVwu-mn-00; Wed, 26 Jul 2000 13:30:34 -0500
Received: from myplay.com (192.168.1.205 [192.168.1.205]) by exchange.corp.myplay.com 
with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
id P2KGDND2; Wed, 26 Jul 2000 11:29:30 -0700
Sender: aaron
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 26 Jul 2000 11:30:37 -0700
From: Aaron Brashears <[EMAIL PROTECTED]>
Organization: myplay
X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.17 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: Modconf fails to start
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]

Package: Modconf
Version: 0.2.26.14

When I attempt to invoke modconf from a console, it doesn't start. There
is no error message. Here's a transcript of what happens:

# modconf
# 

Linux aaron-tp20 2.2.17 #1 Tue Jul 25 17:18:54 PDT 2000 i686 unknown
lrwxrwxrwx1 root root   13 Jul 21 07:28 /lib/libc.so.6
-> libc-2.1.3.so

modconf dependencies on my machine:
ii  whiptail   0.50-7 Displays user-friendly
dialog boxes from shell scripts.
ii  modutils   2.3.11-8   Linux module
utilities.

---
Received: (at 67771-done) by bugs.debian.org; 13 Aug 2000 12:34:46 +
>From [EMAIL PROTECTED] Sun Aug 13 07:34:46 2000
Return-path: <[EMAIL PROTECTED]>
Received: from kuolema.infodrom.north.de [:::195.27.69.163] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 13NwyT-og-00; Sun, 13 Aug 2000 07:34:46 -0500
Received: from finlandia.Infodrom.North.DE (finlandia.Infodrom.North.DE 
[195.27.69.162])
by kuolema.infodrom.north.de (Postfix) with ESMTP id 03D93146E7E
for <[EMAIL PROTECTED]>; Sun, 13 Aug 2000 14:30:46 +0200 (CEST)
Received: at Infodrom Oldenburg (/\##/\ Smail-3.2.0.102 1998-Aug-2 #2)
by finlandia.Infodrom.North.DE
via smail from stdin
id <[EMAIL PROTECTED]>
for [EMAIL PROTECTED]; Sun, 13 Aug 2000 14:34:33 +0200 (CEST) 
Date: Sun, 13 Aug 2000 14:34:33 +0200
From: Martin Schulze <[EMAIL PROTECTED]>
To: Debian Bugs Control <[EMAIL PROTECTED]>
Subject: modconf or not?
Message-ID: <[EMAIL PROTECTED]>
Reply-To: Martin Schulze <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0i
Delivered-To: [EMAIL PROTECTED]

The bug was fixed by reinstalling whiptail...

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."

Please always Cc to me when replying to me on the lists.


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

Bug#68517: Not enough RAID ida devices

[Martin Schulze]

retitle 68517 [CVS-fixed] Not enough RAID ida devices
thanks

> Installing on a Compaq DL380 with onboard RAID controller and PCI
> Smart Array 221 card the compact set is required (requisite support for
> RAID + onboard ethernet does not appear top be in the standard set).
> 
> However, the file system shipped with the compact set includes device
> nodes for the first RAID controller only (i.e. /dev/ida/c1* ).  This is a
> problem if you wish/need to install to the second controller (i.e.
> /dev/ida/c1* ).
> 
> Note that the machine that this occured on has an onboard controller
> (first RAID controller) which has no disks.
> 
> Workaround: after booting and loading teh root file system, go to 2nd VC
> and manually make the necessary device nodes (i.e. "cd /dev/ida; mknod
> c1d0 b 73 0; mknod c1d0p1 b 73 1;...") then go back to the first VC and
> select re-start the installation (otherwise you don't get the chance to
> partition on the second controller).
> 
> Suggested fix: root file system to have devices for /dev/ida/c1* (and
> possibly /dev/ida/c2* also?).

I'll add ida.1 to the list of devices.

> IMHO, this is an "important" bug.
> 
> Furthermore, attempts to use makedev to make these devices ("cd /dev ;
> /sbin/MAKEDEV ida.1") fail miserably (sorry, messages lost but it did
> include references to file system full - I'll try to recreate this on
> another machine next week, if necessary).

This would be a bug in makedev, however I cannot reproduce this.  Both
in test mode (add '-n') and in real mode I don't get an error message.

> Apart from this, the installation on this machine appears to have gone
> flawlessly (LILO installed on c1d0p1 and MBR on c1d0) - thanks :-)

good.

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."

Please always Cc to me when replying to me on the lists.


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

Bug#68665: Please add devices

[Martin Schulze]

retitle 68665 [CVS-fixed] Missing devices in base system
thanks

I've worked on the boot-floppies code recently...

Martin Schulze wrote:
> Package: boot-floppies
> Version: 2.2.16-2000-07-14
> 
> When people select one out of a couple of non-ATA-CD-ROMs they'll
> run into an error, resulting in bug reports like Bug#35435.
> 
> I've investigated this a little bit more.  A couple of device files
> are missing in the base system.
> 
> These device files are expected to be present in /dev by modconf
> which manages driver modules to be inserted in the kernel as well
> as the link to /dev/cdrom
> (done via "cd /dev && rm -f cdrom && ln -s aztcd0 cdrom")
> 
> aztcd0: brw-rw root/cdrom 29,0 2000-07-05 19:44 ./dev/aztcd0
> sonycd: brw-rw root/cdrom 15,0 2000-07-05 19:44 ./dev/sonycd
> cm206cd:

manually added

> gscd:

manually added

> isp16:

Oops, commented out, not present in devices.txt anyway...

> mcd: brw-rw root/cdrom 23,0 2000-07-05 19:44 ./dev/mcd
> mcdx0:
>brw-rw root/cdrom 20,0 2000-07-05 19:44 ./dev/mcdx

Added workaround until MAKEDEV is fixed:

(cd $B/dev && mv mcdx mcdx0 && ln -s mcdx0 mcdx)

 Is it possible to have more than one mcdx in the system and does Linux support 
this?
 Joey: yes, yes
 Joey: just modprobe more than once
 then a) devices.txt is inaccurate and MAKEDEV is buggy
 How many devices are possible?
 Joey: try Configure.help
 Joey: and Documentation/cdrom/mcdx
 Joey: it supports up to 5 drives
 Aha, ok, so 0-4 need to be added.

> optcd:

Added to MAKEDEV call

> sbpcd0: lrwxrwxrwx root/root 0 2000-07-05 19:44 ./dev/sbpcd -> sbpcd0
> brw-rw root/cdrom 25,0 2000-07-05 19:44 ./dev/sbpcd0
> sjcd:

ditto

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."

Please always Cc to me when replying to me on the lists.


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

Bug#68900: CVS-fixed

[Martin Schulze]

retitle 68900 [CVS-fixed] Misterious boot-floppies error
thanks

I've fixed this bug (and related) and committed it to the CVS
repository.

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."

Please always Cc to me when replying to me on the lists.


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

Processed: CVS-fixed

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 68900 [CVS-fixed] Misterious boot-floppies error
Bug#68900: Misterious boot-floppies error
Changed Bug title.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Darren Benham
(administrator, Debian Bugs database)


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

Processed: Re: Please add devices

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 68665 [CVS-fixed] Missing devices in base system
Bug#68665: Please add devices
Changed Bug title.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Darren Benham
(administrator, Debian Bugs database)


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

Processed: Re: Not enough RAID ida devices

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 68517 [CVS-fixed] Not enough RAID ida devices
Bug#68517: [compact] not enough RAID ida devices
Changed Bug title.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Darren Benham
(administrator, Debian Bugs database)


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

Processed: cvs fixed mke2fs

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 68659 [CVS-fixed] root disk filesystem shouldn't use new ext2 extensions
Bug#68659: root disk filesystem shouldn't use new ext2 extensions
Changed Bug title.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Darren Benham
(administrator, Debian Bugs database)


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

Re: YAIE: Debian on a PowerTower Pro

[Adam Di Carlo]

Well, unless someone turns the problems listed into bug reports,
theres absolutely no chance it will ever get fixed.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


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

Re: Bug#68900: CVS-fixed

[Adam Di Carlo]

Martin Schulze <[EMAIL PROTECTED]> writes:

> retitle 68900 [CVS-fixed] Misterious boot-floppies error
> thanks
> 
> I've fixed this bug (and related) and committed it to the CVS
> repository.

It's nice to retitle but please do the right thing and add entries
with the proper (closes: Bug#X) into debian/changelog .

Please?

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


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

Bug#68911: acknowledged by developer (boot-floppies: dbootstrap.h missing)

[Adam Di Carlo]

Herbert Xu <[EMAIL PROTECTED]> writes:

> Sorry, wrong bug title :)  It left my directory tree when I imported it into
> CVS and unfortunately the .cvsignore file has "dbootstrap*" in it.

Ok, fixed in cvs sources.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


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

Re: debiandoc-sgml and Russian, Polish

[Adam Di Carlo]

Ardo van Rangelrooij <[EMAIL PROTECTED]> writes:

> Adam Di Carlo ([EMAIL PROTECTED]) wrote:
> > 
> > As I understand it, we need the woody debiandoc-sgml pakcage in order
> > to build Russian and Polish installation manual and release notes
> > (assuming they are otherwise ok), correct?
> 
> For Polish yes, for Russian I'm not aware of any changes made since the
> last potato update.

With Russian and potato debiandoc-sgml, I get a failure in
saspconvert2, "leftover comment".

> It's no problem making the version uploaded to woody also go into potato.
> I've made some more changes than just adding Polish locale support, but
> none is likely to break anything which isn't already broken. ;-)
> 
> Just say the word and I'll upload it.

Please do -- with the understanding that this is for 2.2 r1 and by no
means to hinder the current potato release attempts.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


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

Re: New release of boot-floppies

[Adam Di Carlo]

Martin Schulze <[EMAIL PROTECTED]> writes:

> I've been told that Adam plans a new release.  I highly appreciate
> that since the 'cant find /lib/modules/2.2.16/modules.dep file' error
> gives a really bad idea of what Debian is doing.

Yeah -- it's not release critical is it?  Because 2.2.17 would be for
2.2 r1, not for 2.2 (r0).

> Wrt other stuff, what is high on your priority list that needs to
> be fixed?  I'd like to help.  At the moment I have some spare time
> to use for useful stuff.

I love how you've been going thru and taking care of bugs.  I think we
need to just continue doing that.  

BTW, I worry about all the new devices you just added.  Are you sure
we didn't just make the rootdisk too large for powerpc?  Didn't exceed
our 

I'm focusing on the documentation bugs and improvements, so you can
leave those to me if you like.

Although, if you know some Debiandoc stuff and wanna help with the
documentation, even dealing with just that is a little overwhelming
and I could use the help (i.e., right now I'm running a link checker
on all the files, which itself is a bit too much work for me to deal
with it all).

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


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

Re: still-extant potato boot problems (kmod/runany modprobe loop)

[Adam Di Carlo]

Martin Schulze <[EMAIL PROTECTED]> writes:

> This is the proper list, I'm forwarding.

> > Are there any fixes (or even diagnoses) yet for the following problem?
> > Has anyone else even seen these symptoms?

> > Earlier I reported a problem with installing potato (from scratch)
> > and getting errors at boot time like:
> > 
> >kmod: runaway modprobe loop assumed and stopped

I've never seen that.

> > and many occurrences of:
> > 
> >modprobe: modprobe: Can't open dependencies files 
>/lib/modules/2.2.17/modules.dep (No such file or directory)

Joey seem to indicate he had already made a fix in CVS for this -- is
that so?  

Is this problem preventing installation or just annoying?

You can probably work around it by running 'depmod -a' on the cmdline.

> > (Note that those errors were from booting the installation boot 
> > diskettes (rescue.bin/root.bit).  Specifically, it was from 
> > before I had a chance to make any choices or affect anything.)

Oh -- so they are just pretty much cosmetically annoying.

I don't know why, in rootdisk.sh, we couldn't run 'depmod -a' chrooted
in the new file system prior to making the drivers floppy or floppies.

I am loath to touch this though since it often breaks.

> > I thought I'd try getting to potato by upgrading (a clone of) my 
> > slink system.  The upgrade went pretty well (well, I accidentally
> > upgraded the original instead of the clone, but the clone seems
> > to be working fine) until I installed the 2.2.17 kernel and rebooted.  
> > Those boot-time errors returned.

Ah, hum.  The loop bug you mentioned looks like a kernel bug.  Can you
file a bug against kernel-image-2.2.16[-flavor] where flavor is
(optionally) the kernel flavor you are using? 

> > I also started getting a bunch of other errors, such as:
> > 
> >- "modprobe: Can't locate module xxx"
> >  (at bootup; for roughly half of the modules)

Use depmod (see the man page) to check dependancies and locatable
modules.  

If you are having a problem with the modules themselves, file bugs
against kernel-image.  If the modules were simply placed in the wrong
place by the potato boot-floppies, file a bug here.

> >- "start ppp0: SIOCSIFMETRIC: Operation not supported"
> >  (asynchonously, after something had triggered diald)

Kernel issue.

> >- "Use of setserial/setrocket to set SPD_* flags is deprecated"
> >  (asynchonously)
> > 
> >- something like "xmit when interface down"
> >  (asynchonously)

ditto ditto

> >- (I can't even ping the other end of my diald's PPP connection 
> >   (I used the numeric IP address logged by pppd when it
> >   connected).)

You are having serial / ppp problems and we cannot help you here.

Are you on i386?  If so, try [EMAIL PROTECTED]  Otherwise,
try debian-@lists.debian.org.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


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

Re: debiandoc-sgml and Russian, Polish

[Ardo van Rangelrooij]

Adam Di Carlo ([EMAIL PROTECTED]) wrote:
> Ardo van Rangelrooij <[EMAIL PROTECTED]> writes:
> 
> > Adam Di Carlo ([EMAIL PROTECTED]) wrote:
> > > 
> > > As I understand it, we need the woody debiandoc-sgml pakcage in order
> > > to build Russian and Polish installation manual and release notes
> > > (assuming they are otherwise ok), correct?
> > 
> > For Polish yes, for Russian I'm not aware of any changes made since the
> > last potato update.
> 
> With Russian and potato debiandoc-sgml, I get a failure in
> saspconvert2, "leftover comment".

The functionality of saspconvert2 has been moved into the backends, so you won't
get this failure anymore (which was not restricted to Russian, by the way).

> > It's no problem making the version uploaded to woody also go into potato.
> > I've made some more changes than just adding Polish locale support, but
> > none is likely to break anything which isn't already broken. ;-)
> > 
> > Just say the word and I'll upload it.
> 
> Please do -- with the understanding that this is for 2.2 r1 and by no
> means to hinder the current potato release attempts.

It's being moved into incoming as we speak.  I'll email Anthony and let him
know what's up (I'll CC you).

Thanks,
Ardo
-- 
Ardo van Rangelrooij
home email: [EMAIL PROTECTED], [EMAIL PROTECTED]
home page:  http://home.flevonet.nl/~avrangel, http://www.debian.org/~ardo
PGP fp: 3B 1F 21 72 00 5C 3A 73  7F 72 DF D9 90 78 47 F9


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

Re: update of debiandoc-sgml for potato

[Adam Di Carlo]

Ardo van Rangelrooij <[EMAIL PROTECTED]> writes:

> Per request of Adam I've uploaded for potato the version of debiandoc-sgml that went
> already into woody.  This version provides Polish locale support (and fixes some 
>other
> problems as well) which is needed for the boot floppies related documentation.  This
> version doesn't break anything which isn't already broken ;-), so there should be no
> fear for more RC bugs.  Could you allow this to go into potato?

To clarify, I'm targetting 2.2 r1 not attempting to cram something in
for 2.2 release upcoming.  The 2.2.16 boot floppies (and even upcoming
2.2.17) do not rely on this potato debiandoc-sgml.

Therefore you could just wait for the potato release, then put this
pkg in proposed updates.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


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

root disk capacity exceeded

[Adam Di Carlo]

Joey, you just exceeded the root disk, as I suspected you might.  I'm
a little suprised because I thought the i386 root disk had plenty of
room.  Anyhow, please test it and fix that.

Did you also conditionalize any new devices so they are i386 only?

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>

make resc1440.bin resc1440-s.bin
make[1]: Entering directory `/usr/local/apharris/debian/boot-floppies/boot-floppies'
case i386 in \
alpha)   ./rootdisk.sh "" /archive/debian/dists/potato/main/binary-i386 3500 2.2 \
"" C "" ;; \
*)   ./rootdisk.sh "" /archive/debian/dists/potato/main/binary-i386 3200 2.2 \
"" C "" ;; \
esac
I: ld.so on this architecture is ld-linux.so.2
I: making disk image loop filesystem, size 3200k
3200+0 records in
3200+0 records out
mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
I: mounting loop file /tmp/fimgApAtlw on /var/tmp/boot-floppies/mnt.rootdisk
I: extracting packages (EXTRACT_LIST) into extract area, 
'/var/tmp/boot-floppies/extract-tmp-32652'
I: stripping executables in extract area
I: making devices in root area (/var/tmp/boot-floppies/root-tmp-32652)
I: making prototype filesystem in /var/tmp/boot-floppies/prototype-tmp-32652
./rootdisk.sh: [: =: unary operator expected
I: modifying init script; making lazybox links
I: moving prototype area to root staging area
I: moving extracted files (SMALL_BASE_LIST) from 
/var/tmp/boot-floppies/extract-tmp-32652 to root area 
(/var/tmp/boot-floppies/root-tmp-32652)
I: copying fonts, passwd, group, modules.conf into root area
I: determining set of required libraries
I: copying required libraries to root filesystem
I: adding busybox and links to it
make[2]: Entering directory 
`/usr/local/apharris/debian/boot-floppies/boot-floppies/utilities/busybox'
./install.sh /var/tmp/boot-floppies/root-tmp-32652
  /var/tmp/boot-floppies/root-tmp-32652/bin/cat -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/chgrp -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/chmod -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/chown -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/cp -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/date -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/dd -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/df -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/dmesg -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/du -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/false -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/grep -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/gunzip -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/head -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/kill -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/ln -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/ls -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/mkdir -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/mknod -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/mktemp -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/more -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/mount -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/mv -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/ping -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/ps -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/pwd -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/rm -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/rmdir -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/sleep -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/sync -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/tar -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/true -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/umount -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/uname -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/bin/zcat -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/sbin/chroot -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/sbin/init -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/sbin/loadkmap -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/sbin/mkswap -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/sbin/reboot -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/sbin/swapoff -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/sbin/swapon -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/sbin/syslogd -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/usr/bin/chvt -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/usr/bin/clear -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/usr/bin/find -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/usr/bin/id -> /bin/busybox
  /var/tmp/boot-floppies/root-tmp-32652/

Bug#68911: boot-floppies: dbootstrap.h missing

[Adam Di Carlo]

retitle 68911 [fixed in CVS] dbootstrap.h missing
thanks

<[EMAIL PROTECTED]> writes:

> The file utilities/dbootstrap/dbootstrap.h is missing from the source
> package.

Thanks.  Fixed that.  Bad craziness.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


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

Processed: Re: Bug#68911: boot-floppies: dbootstrap.h missing

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 68911 [fixed in CVS] dbootstrap.h missing
Bug#68911: Should not include dbootstrap.h in .cvsignore
Changed Bug title.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Darren Benham
(administrator, Debian Bugs database)


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

Re: still-extant potato boot problems (kmod/runany modprobe loop)

[Herbert Xu]

Adam Di Carlo <[EMAIL PROTECTED]> wrote:
>
>> >kmod: runaway modprobe loop assumed and stopped

> I've never seen that.

This is just the unix.o loop.  It's a harmless warning.  We used to use a
patch which didn't print out a warning, but now a new patch has been
integrated into the upstream kernel which does print out a nasty warning.
-- 
Debian GNU/Linux 2.1 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]

Bug#68373: fresh install: some dependency problems ?

[Yann Dirson]

On Sat, Aug 12, 2000 at 07:01:38PM -0400, Adam Di Carlo wrote:
> Hmm.  This isn't a boot-floppies bug.  It's either a bug in the
> individual packages you mentioned (i.e., missing deps) or else an apt
> bug.

I guess so.  Maybe some chroot environment could be used to track potential
dependancy issues.  Maybe I'll find some time to do this - but maybe not ;)

-- 
Yann Dirson<[EMAIL PROTECTED]> |Why make M$-Bill richer & richer ?
debian-email:   <[EMAIL PROTECTED]> |   Support Debian GNU/Linux:
| Cheaper, more Powerful, more Stable !
http://ydirson.free.fr/ | Check 


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

Re: /boot nonexistant on sun4cdm install disk set

[Adam Di Carlo]

William Cordis <[EMAIL PROTECTED]> writes:

> I have a SPARCstation 5 that I'm trying to install debian on. I downloaded
> the 2.2.16-2000-07-14 disks from /debian/dists/potato/main/disks-sparc/sun4cdm
> and the root.bin that I used came from 
> debian/dists/potato/main/disks-sparc/images-1.44
> 
> All went fine until I tried to download the driver.tgz from http.us.debian.org
> Since I was using DHCP to configure the machine I checked /etc/resolve.conf.
> It was empty so I put our DNS server in there and was able to ping 
> http.us.debian.org.  Unfortunately the perl method didn't notice the change
> and still reported the name as unable to resolve.  Putting in the ip worked
> and nothing else went wrong until I tried to install SILO.  It failed so I
> ran it manually from the console.  It reported that it couldn't load the 
> second stage boot-loader /boot/second.b.  A quick survey showed no /boot at all.
> Did I download a bad image for my root.bin??

Try the newer 3 August versions, I think.

If that fails, please submit a bug against boot-floppies.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


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

Re: on which branch should I commit my patch ?

[Adam Di Carlo]

Guillaume Morin <[EMAIL PROTECTED]> writes:

>   Since everoby seems happy with my patch (that you can find at
> http://www.debian.org/~gemorin/boot), I'd like to commit it to the CVS.
> I've seen that there is a lot of branches. Should I create a new branch
> or commit it in an existing one ?

If you want it to be part of the main code line, then you ought to
merge the branch to the trunk.  See the CVS info pages on how to do
this.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


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

Re: New release of boot-floppies

[Martin Schulze]

Adam Di Carlo wrote:
> Martin Schulze <[EMAIL PROTECTED]> writes:
> 
> > I've been told that Adam plans a new release.  I highly appreciate
> > that since the 'cant find /lib/modules/2.2.16/modules.dep file' error
> > gives a really bad idea of what Debian is doing.
> 
> Yeah -- it's not release critical is it?  Because 2.2.17 would be for
> 2.2 r1, not for 2.2 (r0).
> 
> > Wrt other stuff, what is high on your priority list that needs to
> > be fixed?  I'd like to help.  At the moment I have some spare time
> > to use for useful stuff.
> 
> I love how you've been going thru and taking care of bugs.  I think we
> need to just continue doing that.  
> 
> BTW, I worry about all the new devices you just added.  Are you sure
> we didn't just make the rootdisk too large for powerpc?  Didn't exceed
> our 

I don't know.  (your sentence broke there somehow...)

If we don't provide the devices, we should create them online, that
would be a feasable solution for me.  Or alternatively we have to
remove the drivers that make use of them...

> I'm focusing on the documentation bugs and improvements, so you can
> leave those to me if you like.

Yes, I already skipped the documentation stuff, since for a long time
I haven't coded I want to do coding instead of documenting this time.

> 
> Although, if you know some Debiandoc stuff and wanna help with the
> documentation, even dealing with just that is a little overwhelming
> and I could use the help (i.e., right now I'm running a link checker
> on all the files, which itself is a bit too much work for me to deal
> with it all).

If time comes, documentation comes as well.

At the moment my priorities are bug fixing in the code, not in the
documentation.  Reading the changelog, there are a couple of people
out there working on documentation.  Only very few people work on
the code.

Speaking of code, do you know where the libc is shrinked?  I'd like
to review it and/or to add a function (tracking down the mke2fs bug report)

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."

Please always Cc to me when replying to me on the lists.


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

Re: New release of boot-floppies

[Martin Schulze]

Adam Di Carlo wrote:
> Martin Schulze <[EMAIL PROTECTED]> writes:
> 
> > I've been told that Adam plans a new release.  I highly appreciate
> > that since the 'cant find /lib/modules/2.2.16/modules.dep file' error
> > gives a really bad idea of what Debian is doing.
> 
> Yeah -- it's not release critical is it?  Because 2.2.17 would be for
> 2.2 r1, not for 2.2 (r0).

Forgot about that.  Well, I don't consider it release critical but
since everybody will see it, it will give a very bad impression of
Debian, they can't even create boot-floppies.

When do you plan to release 2.1.17 and when will the release manager
release 2.2r1?  If there is not much time between, pressed CDs will
contain r1, if not they'll contain this bug.

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."

Please always Cc to me when replying to me on the lists.


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

Re: /boot nonexistant on sun4cdm install disk set

[Ben Collins]

On Sun, Aug 13, 2000 at 06:08:02PM -0400, Adam Di Carlo wrote:
> William Cordis <[EMAIL PROTECTED]> writes:
> 
> > I have a SPARCstation 5 that I'm trying to install debian on. I downloaded
> > the 2.2.16-2000-07-14 disks from /debian/dists/potato/main/disks-sparc/sun4cdm
> > and the root.bin that I used came from 
> > debian/dists/potato/main/disks-sparc/images-1.44
> > 
> > All went fine until I tried to download the driver.tgz from http.us.debian.org
> > Since I was using DHCP to configure the machine I checked /etc/resolve.conf.
> > It was empty so I put our DNS server in there and was able to ping 
> > http.us.debian.org.  Unfortunately the perl method didn't notice the change
> > and still reported the name as unable to resolve.  Putting in the ip worked
> > and nothing else went wrong until I tried to install SILO.  It failed so I
> > ran it manually from the console.  It reported that it couldn't load the 
> > second stage boot-loader /boot/second.b.  A quick survey showed no /boot at all.
> > Did I download a bad image for my root.bin??
> 
> Try the newer 3 August versions, I think.
> 
> If that fails, please submit a bug against boot-floppies.

No, there should be no /boot in the root.bin. The /boot that silo uses is
/target/boot. Silo us run as "silo -r /target" so that it will chroot to
the new installed filesystem. Try running that and see if there is an
error. I'm wondering what happened to make you think it failed. Was there
an error message? If so, what was it?

Ben

-- 
 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'


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

Re: New release of boot-floppies

[Adam Di Carlo]

Martin Schulze <[EMAIL PROTECTED]> writes:

> Adam Di Carlo wrote:
> > BTW, I worry about all the new devices you just added.  Are you sure
> > we didn't just make the rootdisk too large for powerpc?  Didn't exceed
> > our 
> 
> I don't know.  (your sentence broke there somehow...)

Um, the root disk cannot be made.

> If we don't provide the devices, we should create them online, that
> would be a feasable solution for me.  Or alternatively we have to
> remove the drivers that make use of them...

Well, the stupid raid drivers that need all those controller-specific
devices is what is consuming all the inode space.

You may be able to tweak the controllers that are built.  The
compromise we *explicitly* made was to only support one controller,
and only support so many devices, to keep the root disk size down.

If you can find another workaround, great; otherwise, we need to back
that out so bf can build again.

> > I'm focusing on the documentation bugs and improvements, so you can
> > leave those to me if you like.
> 
> Yes, I already skipped the documentation stuff, since for a long time
> I haven't coded I want to do coding instead of documenting this time.
[...]
> At the moment my priorities are bug fixing in the code, not in the
> documentation.  Reading the changelog, there are a couple of people
> out there working on documentation.  Only very few people work on
> the code.

No problem at all.  Leave the documentation side to me.

My only request, as I said before, is that you make changelog entries
with the bug closing directives in there.

> Speaking of code, do you know where the libc is shrinked?  I'd like
> to review it and/or to add a function (tracking down the mke2fs bug report)

Yeah, it's in scripts/rootdisk/mklibs.sh ?

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


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

Re: New release of boot-floppies

[Adam Di Carlo]

Martin Schulze <[EMAIL PROTECTED]> writes:

> Forgot about that.  Well, I don't consider it release critical but
> since everybody will see it, it will give a very bad impression of
> Debian, they can't even create boot-floppies.

>From source?  Eh?  What bug# is this?

> When do you plan to release 2.1.17 and when will the release manager
> release 2.2r1?  If there is not much time between, pressed CDs will
> contain r1, if not they'll contain this bug.

I'm not sure.  I guess I'm cool with releasing 2.2.17 once we go thru
the build process and give it some testing.  Perhaps no point in
waiting.

Even without a point release, the CD vendors often pickup new version
of boot-floppies and such.

As for 2.2r1, I don't know whne that will happen.  We'd have to ask on
debian-release.  I would guess within 6 weeks of potato release we'll
have at least one point release.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


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

Re: New release of boot-floppies

[Erik Andersen]

On Sun Aug 13, 2000 at 11:30:47PM -0400, Adam Di Carlo wrote:
> Martin Schulze <[EMAIL PROTECTED]> writes:
> 
> > If we don't provide the devices, we should create them online, that
> > would be a feasable solution for me.  Or alternatively we have to
> > remove the drivers that make use of them...
> 
> Well, the stupid raid drivers that need all those controller-specific
> devices is what is consuming all the inode space.
> 
> You may be able to tweak the controllers that are built.  The
> compromise we *explicitly* made was to only support one controller,
> and only support so many devices, to keep the root disk size down.
> 
> If you can find another workaround, great; otherwise, we need to back
> that out so bf can build again.

I supposr we could construct a small (~100k) ramdisk with a zillion inodes on
it and untar a tarball full of device special files into it and then remount
the ramdisk over /dev.  That would do the job while not taking up too much
space...   Just a thought...

 -Erik

--
Erik B. Andersen   email:  [EMAIL PROTECTED]
--This message was written using 73% post-consumer electrons--


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