Re: cdebconf state

2002-08-08 Thread Tollef Fog Heen

* Martin Sjögren 

| tor 2002-08-08 klockan 09.50 skrev Petter Reinholdtsen:
| > 
| > [Tollef Fog Heen]
| > > Well, it works. :) So, I'd rather not change it again.  Also, I
| > > don't know the binary-tree stuff in glibc.  I kinda know this hash
| > > library by now.
| > 
| > Using glibc functions would reduce the size of cdebconf, wouldn't it?
| > I suggest adding a rewrite to the glibc binary-tree functions on the
| > TODO list.

*shrug*.  If somebody does it without breaking rfc822db, please go
ahead.

| What is the binary tree API for glibc? The tsearch stuff?

yes.

| Perhaps I should introduce myself :) I'm a student of computer science
| in Sweden who's on the nmlist. I've been lurking here for a while and
| I'm interested in Debian having a great installer, so I'd be happy to
| help with what I can.

well, if people think rewriting it to use tsearch and friend -- please
go ahead.  If you are looking for other stuff to research -- partition
seems to be hot ATM. :)  Look at the TODO list and start hacking.

If you don't have a CVS account, post the patches to the list and
somebody will apply them.  If they are good, we'll get you a CVS
account proper (or you'll have access anyhow when you get to be a DD).

-- 
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky about who its friends are  : :' :
  `. `' 
`-  


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




cvs commit to debian-installer/build by tfheen

2002-08-08 Thread Debian Boot CVS Master

Repository: debian-installer/build
who:tfheen
time:   Thu Aug  8 14:15:18 PDT 2002
Log Message:
  initial checkin
  

Files:
added:  uptodatecheck.sh


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




Re: d-i udebs up-to-dateness of archive

2002-08-08 Thread Tollef Fog Heen

* Joey Hess 

| Tollef Fog Heen wrote:
| > did you generate this table by hand or through some script?  if the
| > latter, could you put it somewhere?
| 
| That was by hand I'm afraid.

ok, I've just checked in a script which generates a list like this.

-- 
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky about who its friends are  : :' :
  `. `' 
`-  


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




d-i: make demo needs slang frontend

2002-08-08 Thread Thomas Poindessous

Hi,
I'm still trying to test d-i with make demo.
I have rebuild all udeb needed which are in the debian-installer cvs.
But when I launch make demo, I got an error because it can't find slang
frontend (which is defined in chroot:/etc/cdebconf.conf). I have rebuild
cdebconf-udeb with slang frontend,  but it needs libslang1.so. And I didn't
managed to get it installed with mklibs

How do you test d-i at the moment ? Is there a step that I'm missing ?

Thanks.

-- 
Thomas Poindessous
[EMAIL PROTECTED]


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




Re: d-i: make demo needs slang frontend

2002-08-08 Thread Tollef Fog Heen

* Thomas Poindessous 

| How do you test d-i at the moment ? Is there a step that I'm missing ?

I like the text frontend better, so I've just hacked around it by
changing the cdebconf.conf-dist file.

-- 
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky about who its friends are  : :' :
  `. `' 
`-  


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




cvs commit to mklibs by dwhedon

2002-08-08 Thread Debian Boot CVS Master

Repository: mklibs
who:dwhedon
time:   Thu Aug  8 19:39:09 PDT 2002
Log Message:
  +  * Ensure that the dynamic linker is installed along with the small
  +libs.  In the case of glibc, libc.so has calls into ld-linux.so
  +(glibc dynamic linker) so mklibs will always install ld-linux.so
  +when it resolves external references.  However, uClibc's libc
  +doesn't call it's dynamic linker (ld-uClibc.so).  In that case
  +we have to copy it in manually.
  

Files:
changed:mklibs.py


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




cvs commit to mklibs/debian by dwhedon

2002-08-08 Thread Debian Boot CVS Master

Repository: mklibs/debian
who:dwhedon
time:   Thu Aug  8 19:39:09 PDT 2002
Log Message:
  +  * Ensure that the dynamic linker is installed along with the small
  +libs.  In the case of glibc, libc.so has calls into ld-linux.so
  +(glibc dynamic linker) so mklibs will always install ld-linux.so
  +when it resolves external references.  However, uClibc's libc
  +doesn't call it's dynamic linker (ld-uClibc.so).  In that case
  +we have to copy it in manually.
  

Files:
changed:changelog


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




Bug#156015: boot-floppies: PCMCIA network device is not configured during install

2002-08-08 Thread Hidetaka Iwai


Package: boot-floppies
Version: +N/A; reported 2002-08-09
Severity: normal

I tried to install "woody" with boot-floppies 3.0.23-2002-05-21 and 
configured PCMCIA and network, but I received the message as follows;

  Your network is configured, but not activated. This may be 
  caused by a broken previous installation attempt, or because 
  you are installing over another installation. It is ok to skip 
  this step if you dou not need to use the network for the rest 
  of the instllation, since your network will become active 
  after reboot (assuming it is setup properly).

and I can't use network-install at "Install the Base System".

I think this results from ifconfig and route not being called owing to
'has_pcmcia' flag in activate_static_network() in
utilities/dbootstrap/netconfig.c .

--- netconfig.c.bak 2002-03-05 22:30:31.0 +0900
+++ netconfig.c 2002-08-08 00:48:01.0 +0900
@@ -757,7 +757,7 @@
  */
 
 ret = execlog("/sbin/ifconfig lo 127.0.0.1", LOG_INFO);
-if (!use_dhcp && !has_pcmcia && (ret==0) && netinterface) {
+if (!use_dhcp && (ret==0) && netinterface) {
   char cmdline[MAXLINE];
 
   /* Down the interface to clear old gateways.  */

I think this change will fix the problem.

-- System Information
Debian Release: testing/unstable
Kernel Version: Linux rock 2.4.18 #1 Wed Aug 7 17:36:01 JST 2002 i586 unknown unknown 
GNU/Linux

--
 Hidetaka Iwai
 [EMAIL PROTECTED]


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




Help! Bug with lilo and initrd?

2002-08-08 Thread Andrew

 I have a problem that I have been wrestling with now for a number of days
with no solution, and I'm hoping someone can help.

I have a stock 2.2.20 kernel with ramdisk and initrd support compiled in.
RAMdisk size is 64MB although I've also tried 32MB and 128MB.
I have tried kernel builds with module support and without (everything
compiled in)
I'm using the latest lilo I can find with the following config:

boot=/dev/hdc
disk=/dev/hdc
 bios=0x80
map=/map
install=/boot.b
backup=/boot.1600
prompt
linear
timeout=50
password=maintenance
restricted
image=/vmlinuz-2.2.20up
label=test
ramdisk=65536
initrd=/rootfs.img
root=/dev/ram

The server is a uni processor PIII server with 512MB of RAM

The sizes of my rootfs.img and kernel are:
 8713856 Aug  7 12:55 rootfs.img (this is an ext2 compressed image)
 787022 Aug  7 12:17 vmlinuz-2.2.20up (this is a monolithic bzImage kernel)

My problem is that when my kernel loads, lilo doesn't seem to load
the rootfs.img into RAM for the kernel to find. That is I don't get the
kernel message 'RAMDISK found at block 0' message and thus Linux panics with
something like "root file system not found on dev 1:0".

Lilo when building doesn't report any errors in fact it says it successfully
maps the RAMdisk ok

It almost seems like there is some finite size limit that my
rootfs.img+kernel is greater than, that stops the
RAMdisk being loaded or being found if it is infact being loaded at all.

Is there a finite limit on the size initrd can be? Enlarging the ramdisk
size doesn't seem to make any difference.

I have not tried a 2.4 level kernel as I need this to work consistently with
2.2.

Any help much appreciated.

Andrew.
ps. Can you please reply to me directly, thanks.


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




Re: Help! Bug with lilo and initrd?

2002-08-08 Thread Eduard Bloch

#include 
* Andrew [Fri, Aug 09 2002, 02:59:45PM]:
>  I have a problem that I have been wrestling with now for a number of days
> with no solution, and I'm hoping someone can help.
> 
> I have a stock 2.2.20 kernel with ramdisk and initrd support compiled in.

Where did you get your source? Prescine source from kernel.org must be
patched to work properly with initrd and cramfs on it. Or use
kernel-source from Debian package. Do not ask me why the people removed
it cramfs from initrd's accepted filesystems. 

Gruss/Regards,
Eduard.
-- 
User: Ich hätte gern ein paar MByte Speicher.
malloc(): OK. Welche Sicherheiten haben sie?


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




unsubscribe

2002-08-08 Thread Thomas Scherk




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




Re: Help! Bug with lilo and initrd?

2002-08-08 Thread Andrew Hall

I'm not using cramfs. The compressed root is ext2 fs because I need to load
it Read-write. What initrd patch do I need for 2.2.20 (I got it from
kernel.org) as I thought it already contained the latest initrd sources?

- Original Message -
From: "Eduard Bloch" <[EMAIL PROTECTED]>
To: "Andrew" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, August 09, 2002 3:31 PM
Subject: Re: Help! Bug with lilo and initrd?


> #include 
> * Andrew [Fri, Aug 09 2002, 02:59:45PM]:
> >  I have a problem that I have been wrestling with now for a number of
days
> > with no solution, and I'm hoping someone can help.
> >
> > I have a stock 2.2.20 kernel with ramdisk and initrd support compiled
in.
>
> Where did you get your source? Prescine source from kernel.org must be
> patched to work properly with initrd and cramfs on it. Or use
> kernel-source from Debian package. Do not ask me why the people removed
> it cramfs from initrd's accepted filesystems.
>
> Gruss/Regards,
> Eduard.
> --
> User: Ich hätte gern ein paar MByte Speicher.
> malloc(): OK. Welche Sicherheiten haben sie?
>
>


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




Re: cvs commit to mklibs by dwhedon

2002-08-08 Thread Erik Andersen

On Thu Aug 08, 2002 at 07:39:09PM -0700, Debian Boot CVS Master wrote:
> Repository: mklibs
> who:dwhedon
> time:   Thu Aug  8 19:39:09 PDT 2002
> Log Message:
>   +  * Ensure that the dynamic linker is installed along with the small
>   +libs.  In the case of glibc, libc.so has calls into ld-linux.so
>   +(glibc dynamic linker) so mklibs will always install ld-linux.so
>   +when it resolves external references.  However, uClibc's libc
>   +doesn't call it's dynamic linker (ld-uClibc.so).  In that case
>   +we have to copy it in manually.

Our of curiosity, which version of uClibc are you working with?
uClibc does cause apps to link vs the dynamic linker these days.
Are you using the 6 month old stuff from Woody?

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