D-I spellchecker: separate "critical" errors from cosmetic ones

[Christian Perrier]

Davide, 

In http://d-i.alioth.debian.org/spellcheck/level1/index.html, under
"specific checks", we currently have various checks:

-wrong number of choices
-too long strings
-unbalanced quotes
-missing "Choose Language" in localechooser
...

Among these, some are "critical" such as the wrong number of choices,
which can break some D-I screens, while others are more cosmetci (a
too long string is simply cut and thereforre does not "break D-I").

Could you separate those in different lists?

That would help us, i18n coordinators, to spot the critical ones more
easily and fix them ourselves (I think this is needed for things that
are likely to "break" D-I)

-- 




signature.asc
Description: Digital signature

Re: PowerPC request for Help

[Sven Luther]

CCing debian-boot since that is the best place for having this kind of
discussion. None of them regularly reads debian-powerpc.

On Sat, May 06, 2006 at 06:55:36AM -0400, Daniel Dickinson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi,
> 
> I'm interested in actually contributing to d-i (finally), and I noticed
> that you've put out a request for the PowerPC architecture.  As I only
> have a single StarMax 3000/160 I probably can't help with the entire
> arch, but I can help with Old World Mac (and clones, obviously, since
> the StarMax is a Motorola mac clone from the period when apple gave
> there blessing to such endeavours).  I have a fair level of script and
> C knowledge, but no experience with kernel, or deb/udeb packaging.  I
> have been working on boot disks for i386 (from scratch, and I don't
> mean cookbook LFS-type from scratch), so I have a fairly good
> understanding of the linux boot process (though I still have to
> learn mac-specific parts).
> 
> (In fact I am trying to solve a d-i
> problem for getting floppies with 2.6 kernels, within the d-i way; so
> far I've gotten it to work non-d-i by using the ramdisk_xx kernel
> parameters, but I haven't yet managed to get a small enough initramfs).

What is wrong with the miboot d-i floppies for oldworld ?

Actually one of the work that needs doing is to get the miboot floppy set in
shape. the root floppy seems fine, but afterward there is some awkward things
happening that could benefit from someone with your skills.

Have you managed to build d-i already ? Please try it, it is not so difficult,
and the instructions are linked out from :

  http://www.debian.org/devel/debian-installer

Please do a checkout, and try building it, and once you have done that, i
would be pleased to guide you toward the actual floppy stuff (mostly in
pkg-list//powerpc or so).

> I would be best able to help with a more experienced mentor, and
> probably my initial role would be (on Old World PPC Macs & Clones) to
> test the installer regularly (weekly, semiweekly, daily?), tracking
> installation reports, and reproducing, tracing, and (where knowledge
> allows) resolving bugs.
> 
> I probably am not in a position to do the daily builds, since the
> machine I would be testing the installer on is the only PPC I've got.

This has been taken care of, and i am still letting mine run as backup in
case.

> If you think I could be of assistance, please let me know.  I am
> subscribed to the list, but a CC wouldn't hurt.

Ok, done. debian-boot is the place you want to be for this though.

Friendly,

Sven Luther


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

[g-i] Segfault: missing symbol

[Davide Viti]

A few days ago I realized g-i was building but caused
a segfault when running debconf.
Using an unstripped version of libc the segfault disappeared, meaning
that some needed symbol was stripped from libc. Hopefully I found out
what is missing:

~ # debconf -o d-i /usr/bin/main-menu
/build/buildd/cdebconf-0.100/src/frontend.c:175 (frontend_new): Cannot load 
frontend module /usr/lib/cdebconf/frontend/gtk.so: /usr/lib/libfontconfig.so.1: 
symbol iconv_open, version GLIBC_2.1 not defined in file libc.so.6 with link 
time reference

hope this helps,
Davide


signature.asc
Description: Digital signature

Re: [g-i] Segfault: missing symbol

[Davide Viti]

On Sun, May 07, 2006 at 05:13:08PM +0200, Davide Viti wrote:
> ~ # debconf -o d-i /usr/bin/main-menu
> /build/buildd/cdebconf-0.100/src/frontend.c:175 (frontend_new): Cannot load 
> frontend module /usr/lib/cdebconf/frontend/gtk.so: 
> /usr/lib/libfontconfig.so.1: symbol iconv_open, version GLIBC_2.1 not defined 
> in file libc.so.6 with link time reference

I tried to rebuild fontconfig-2.3.2 without stripping debug symbols and the 
missing symbol is
definitely referenced from there:

[EMAIL PROTECTED]:~/fontconfig$ nm -g test/usr/lib/libfontconfig.so.1 | grep 
iconv
 U iconv_close@@GLIBC_2.1
 U iconv@@GLIBC_2.1
 U iconv_open@@GLIBC_2.1

regards,
Davide


signature.asc
Description: Digital signature

Bug#266691: Re: Re: Bug#266691: Is Italian USB keyboard now working with the etch installer for PowerPC?

[Giovanni Ridolfi]

On Sun, Apr 30, 2006 at 07:44:48AM +0200, Christian Perrier wrote:
> G.Ridolfi wrote:
> > 
> > How can an ibook-user choose this keymap?
> > I tried a "normal" i.e. "not-expert" installation
> > and I was not able to choose or load the "/i386/qwerty/it.kmap.gz"
> > Is there an option of the installer that
> > allows users to find a keymap among _all_ the possible choiches
> > they have?
> 
> I don't think that this problem is restricted to users of italian
> environments.
> 
> Things have changed recently when it comes at keyboard chooser for PPC
> users, IIRC. Are you able to test with a recent image of the
> installer?
> 

I tried the netinst cd of the 6 May 2006.
a) :-)The keymap selected with the italian language was a "qwerty"  
b) :- however it did not allow to write accented letters, 
neither at or numbersign 
Since @ is S-2 I think that the layout is the us one.

c) :-(( I've not been able to load the right 
keymap:/usr/share/keymap/i386/qwerty/it.kmap.gz
  both in "install" mode and in "expert mode".
  When I tried to choose the keymap the only 'option'
- well it wasn't really an option since the user was forced to accept the
  installer choice :-/
 was to *keep* the kernel keyboard.

Can a user select the keymap from a list of available layouts?

Regards,

Giovanni
-- 
Giovanni Ridolfi, Chemist


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

Re: D-I spellchecker: separate "critical" errors from cosmetic ones

[Davide Viti]

Hi Christian,

On Sun, May 07, 2006 at 09:04:26AM +0200, Christian Perrier wrote:
> ...
> 
> Among these, some are "critical" such as the wrong number of choices,
> which can break some D-I screens, while others are more cosmetci (a
> too long string is simply cut and thereforre does not "break D-I").
> 
> Could you separate those in different lists?

yes, sure.
Actually many improvements have to be done: for example, check for unbalanced
braces and such should not be performed on level1, but should be extended to
all levels.

Let's start identifying what has to be considered critical: apart the obvious
number of choices in multiselect messages, should the wrong variables considered
critical?

ciao,
Davide


signature.asc
Description: Digital signature

Re: debian installer and automatic partition option

[Go do]

El Jueves 27 Abril 2006 18:49, Joey Hess escribió:
> Where did you download this installation CD? It's broken; don't select
> that "Particionar Automáticamente" menu item[1].
>
Thanks, Joey. I fortunatelly didn't select that option... ;-)

I don't remember where I downloaded this installacion DVD from... I think that 
I probably used a official mirror but... I don't know.

> Have you tried downloading a
> current CD image from ?

Yes, I have downloaded this image and now all is working fine, I have 
partitioned my hard disk manually (as I usually did).

Thanks for your help. I only wanted to help to the community but I didn't know 
if the problem was my problem (I was doing anything badly) or it was a 
installer problem.

Best regards.

Processing of busybox_1.1.2-1_amd64.changes

[Archive Administrator]

busybox_1.1.2-1_amd64.changes uploaded successfully to localhost
along with the files:
  busybox_1.1.2-1.dsc
  busybox_1.1.2.orig.tar.gz
  busybox_1.1.2-1.diff.gz
  busybox_1.1.2-1_amd64.deb
  busybox-static_1.1.2-1_amd64.deb
  busybox-udeb_1.1.2-1_amd64.udeb

Greetings,

Your Debian queue daemon


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

Processing of linux-kernel-di-s390-2.6_0.02_s390.changes

[Archive Administrator]

linux-kernel-di-s390-2.6_0.02_s390.changes uploaded successfully to localhost
along with the files:
  linux-kernel-di-s390-2.6_0.02.dsc
  linux-kernel-di-s390-2.6_0.02.tar.gz
  kernel-image-2.6.16-1-s390-di_0.02_s390.udeb
  nic-modules-2.6.16-1-s390-di_0.02_s390.udeb
  scsi-core-modules-2.6.16-1-s390-di_0.02_s390.udeb
  scsi-modules-2.6.16-1-s390-di_0.02_s390.udeb
  xfs-modules-2.6.16-1-s390-di_0.02_s390.udeb
  md-modules-2.6.16-1-s390-di_0.02_s390.udeb
  crypto-modules-2.6.16-1-s390-di_0.02_s390.udeb
  dasd-modules-2.6.16-1-s390-di_0.02_s390.udeb

Greetings,

Your Debian queue daemon


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

Re: D-I spellchecker: separate "critical" errors from cosmetic ones

[Christian Perrier]

Quoting Davide Viti ([EMAIL PROTECTED]):

> yes, sure.
> Actually many improvements have to be done: for example, check for unbalanced
> braces and such should not be performed on level1, but should be extended to
> all levels.
> 
> Let's start identifying what has to be considered critical: apart the obvious
> number of choices in multiselect messages, should the wrong variables 
> considered
> critical?


IMHO, yes, because in all cases they have to be fixed.





signature.asc
Description: Digital signature

busybox override disparity

[Debian Installer]

There are disparities between your recently accepted upload and the
override file for the following file(s):

busybox-static_1.1.2-1_amd64.deb: package says priority is optional, override 
says extra.

Either the package or the override file is incorrect.  If you think
the override is correct and the package wrong please fix the package
so that this disparity is fixed in the next upload.  If you feel the
override is incorrect then please reply to this mail and explain why.

[NB: this is an automatically generated mail; if you replied to one
like it before and have not received a response yet, please ignore
this mail.  Your reply needs to be processed by a human and will be in
due course, but until then the installer will send these automated
mails; sorry.]

--
Debian distribution maintenance software

(This message was generated automatically; if you believe that there
is a problem with it please contact the archive administrators by
mailing [EMAIL PROTECTED])


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

busybox_1.1.2-1_amd64.changes ACCEPTED

[Debian Installer]

Accepted:
busybox-static_1.1.2-1_amd64.deb
  to pool/main/b/busybox/busybox-static_1.1.2-1_amd64.deb
busybox-udeb_1.1.2-1_amd64.udeb
  to pool/main/b/busybox/busybox-udeb_1.1.2-1_amd64.udeb
busybox_1.1.2-1.diff.gz
  to pool/main/b/busybox/busybox_1.1.2-1.diff.gz
busybox_1.1.2-1.dsc
  to pool/main/b/busybox/busybox_1.1.2-1.dsc
busybox_1.1.2-1_amd64.deb
  to pool/main/b/busybox/busybox_1.1.2-1_amd64.deb
busybox_1.1.2.orig.tar.gz
  to pool/main/b/busybox/busybox_1.1.2.orig.tar.gz
Announcing to debian-devel-changes@lists.debian.org
Closing bugs: 329406 


Thank you for your contribution to Debian.


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

linux-kernel-di-s390-2.6_0.02_s390.changes is NEW

[Debian Installer]

(new) crypto-modules-2.6.16-1-s390-di_0.02_s390.udeb extra debian-installer
crypto modules
 This package contains crypto modules.
(new) dasd-modules-2.6.16-1-s390-di_0.02_s390.udeb standard debian-installer
dasd modules
 This package contains dasd modules.
kernel-image-2.6.16-1-s390-di_0.02_s390.udeb
  to 
pool/main/l/linux-kernel-di-s390-2.6/kernel-image-2.6.16-1-s390-di_0.02_s390.udeb
linux-kernel-di-s390-2.6_0.02.dsc
  to pool/main/l/linux-kernel-di-s390-2.6/linux-kernel-di-s390-2.6_0.02.dsc
linux-kernel-di-s390-2.6_0.02.tar.gz
  to pool/main/l/linux-kernel-di-s390-2.6/linux-kernel-di-s390-2.6_0.02.tar.gz
md-modules-2.6.16-1-s390-di_0.02_s390.udeb
  to 
pool/main/l/linux-kernel-di-s390-2.6/md-modules-2.6.16-1-s390-di_0.02_s390.udeb
nic-modules-2.6.16-1-s390-di_0.02_s390.udeb
  to 
pool/main/l/linux-kernel-di-s390-2.6/nic-modules-2.6.16-1-s390-di_0.02_s390.udeb
scsi-core-modules-2.6.16-1-s390-di_0.02_s390.udeb
  to 
pool/main/l/linux-kernel-di-s390-2.6/scsi-core-modules-2.6.16-1-s390-di_0.02_s390.udeb
scsi-modules-2.6.16-1-s390-di_0.02_s390.udeb
  to 
pool/main/l/linux-kernel-di-s390-2.6/scsi-modules-2.6.16-1-s390-di_0.02_s390.udeb
xfs-modules-2.6.16-1-s390-di_0.02_s390.udeb
  to 
pool/main/l/linux-kernel-di-s390-2.6/xfs-modules-2.6.16-1-s390-di_0.02_s390.udeb
Changes: linux-kernel-di-s390-2.6 (0.02) unstable; urgency=low
 .
  [ Joey Hess ]
  * Add crypto-modules.
 .
  [ Bastian Blank ]
  * Add dasd-modules.
Announcing to debian-devel-changes@lists.debian.org


Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the override file about once a week.

You may have gotten the distribution wrong.  You'll get warnings above
if files already exist in other distributions.


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

Bug#329406: marked as done (busybox sh sets but does not export PATH)

[Debian Bug Tracking System]

Your message dated Sun, 07 May 2006 14:47:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#329406: fixed in busybox 1:1.1.2-1
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.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: busybox
Version: 1:1.01-2
Severity: normal

If /sbin/init is a /bin/sh script using busybox sh, then when this
script tries to run a program that in turn forks and runs a program in
the PATH, running that program will fail. PATH is set by busybox sh to a
default value, but it's not exported.

Take a look at bug #328729 for an example.

Of course if busybox init is used, it sets PATH in a way that causes it
to be available to child processes. So this doesn't affect most uses of
busybox.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages busybox depends on:
ii  libc6 2.3.5-6GNU C Library: Shared libraries an

busybox recommends no packages.

-- no debconf information

-- 
see shy jo


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: busybox
Source-Version: 1:1.1.2-1

We believe that the bug you reported is fixed in the latest version of
busybox, which is due to be installed in the Debian FTP archive:

busybox-static_1.1.2-1_amd64.deb
  to pool/main/b/busybox/busybox-static_1.1.2-1_amd64.deb
busybox-udeb_1.1.2-1_amd64.udeb
  to pool/main/b/busybox/busybox-udeb_1.1.2-1_amd64.udeb
busybox_1.1.2-1.diff.gz
  to pool/main/b/busybox/busybox_1.1.2-1.diff.gz
busybox_1.1.2-1.dsc
  to pool/main/b/busybox/busybox_1.1.2-1.dsc
busybox_1.1.2-1_amd64.deb
  to pool/main/b/busybox/busybox_1.1.2-1_amd64.deb
busybox_1.1.2.orig.tar.gz
  to pool/main/b/busybox/busybox_1.1.2.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank <[EMAIL PROTECTED]> (supplier of updated busybox package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun,  7 May 2006 19:31:17 +
Source: busybox
Binary: busybox-floppy-udeb busybox busybox-udeb busybox-static
Architecture: source amd64
Version: 1:1.1.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team 
Changed-By: Bastian Blank <[EMAIL PROTECTED]>
Description: 
 busybox- Tiny utilities for small and embedded systems
 busybox-static - Standalone rescue shell with tons of builtin utilities
 busybox-udeb - Tiny utilities for the debian-installer (udeb)
Closes: 329406
Changes: 
 busybox (1:1.1.2-1) unstable; urgency=low
 .
   * New upstream version.
   * debian/config*:
 - Rework.
 - Remove modutils support.
   * modutils:
 - Remove modutils patch.
   * shell:
 - Export PATH. (closes: #329406)
Files: 
 6a1ac06c0597c28925bba0d59d813975 692 - optional busybox_1.1.2-1.dsc
 6a7fe3589b1f15ee29e386c03f83d27e 1722854 - optional busybox_1.1.2.orig.tar.gz
 4ada3f975167df5425aa7229fb3fd10b 18330 - optional busybox_1.1.2-1.diff.gz
 de9d9f403fb0461b8f2d2a808da2f529 329886 utils optional 
busybox_1.1.2-1_amd64.deb
 97af01f3b940f9f721ffe1125d771ea1 919162 shells optional 
busybox-static_1.1.2-1_amd64.deb
 9bd5adaaa4f34e99be043235e89577bd 141942 debian-installer extra 
busybox-udeb_1.1.2-1_amd64.udeb
Package-Type: udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)

iEYEARECAAYFAkReTFMACgkQLkAIIn9ODhF3XwCeNhb5/Qe3pM1pKG1fdTGrf73J
LNMAoOClgju71gF1Hxp9ObUup2t0MaYv
=ME9O
-END PGP SIGNATURE-

--- End Message ---

Netinstall Etch or Sid

[Matthias Popp]

Hallo,
Why I cant't install Etch or Sid without a working networkconnection. With 
Sarge no problem.  But the kernel is sometimes to old. 


-- 
with best regards from Dortmund 
Matthias


pgpP9cADI325g.pgp
Description: PGP signature

A note on busybox bugfix: (Fw: [BusyBox 0000843]: Busybox init requires tty device files to exist before the sysinit script is run and init -q doesn't work)

[Daniel Dickinson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The problem with busybox not recognizing tty's not present as devices
before busybox init is run has been fixed (or rather init -q works)

Cheers,

Daniel

Begin forwarded message:

Date: Sun, 7 May 2006 14:17:14 -0700
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [BusyBox 843]: Busybox init requires tty device files to
exist before the sysinit script is run and init -q doesn't work



A NOTE has been added to this issue. 
== 
http://busybox.net/bugs/view.php?id=843 
== 
Reported By:alemc
Assigned To:BusyBox
== 
Project:BusyBox
Issue ID:   843
Category:   Other
Reproducibility:always
Severity:   major
Priority:   normal
Status: assigned
== 
Date Submitted: 04-20-2006 00:03 PDT
Last Modified:  05-07-2006 14:17 PDT
== 
Summary:Busybox init requires tty device files to
exist before the sysinit script is run and init -q doesn't work
Description: 
If the /etc/tty0 - /etc/tty63 files do no exist before inittab is read
(e.g. on init start), init can't use the virtual terminals.  This is a
problem when trying to use a udev only system (i.e. where the tty# files
do not exist until udev is started), when udev is executed from the
::sysinit 'runlevel' (e.g. no /linuxrc, or /linuxrc does the absolute
minimum to boot into init).  The workaround is the have static device
files for these devices, either in the root filesystem or created by
linuxrc for initrd-based systems).

I just found a thread about this here (after I figured it out with a
completely different google search; it seems my googling skills need to
improve):

http://lists.debian.org/debian-boot/2006/02/msg00562.html

Apparently 'init -q' doesn't work, and even if it did it's not
documented (in busybox.txt generated during busybox build at any rate).

Which concludes with:  

On Friday 17 February 2006 12:57 pm, Martin Michlmayr wrote:
> * Rob Landley <[EMAIL PROTECTED]> [2006-02-15 12:12]:
> > Lemme see if I understand this:
> >
> > You have an inittab telling busybox init to spawn things on three
> > consoles that either don't exist when you run init,
>
> No, they do exist because we create them before running init.

You seem to have ignored the word "either".

> > or are invalid device nodes.
>
> Right, on some devices they are invalid device nodes because we have
> to create them before init starts.  If we don't create them before
> init starts, the following from inittab will be ignored:
>
> vc/3::respawn:/usr/bin/tail -f /var/log/messages
> vc/4::respawn:/usr/bin/tail -f /var/log/syslog
>
> > The current busybox init is not failing gracefully when you do this.
> >
> > That's a sequencing issue.  Whoever wrote this didn't expect the
sysinit
> > script to completely redo the contents of /dev.  If I can get it
> > clear
in
> > my head exactly what you want to do, I can take a whack at fixing
> > it.
>
> Basically, we use udev.  However, we have to manually create /dev/vc/*
> before init is started because busybox doesn't behave properly if this
> doesn't exist.  What I'd like to see is that we only have to create
> /dev/vc/0 and vc/1, then start init,

This would be the "either" case, above.

> then run udev which will (or not) 
> crate /dev/vc/2-4.  Current bb init doesn't allow this because it will
> ignore the above vc/3|4::respawn statements if those devices don't
> exist _by the time_ init is started.

Technically, it will ignore lines out of inittab that refer to consoles
that 
don't exist at the time it reads the line out of inittab.

This is not a new behavior on the part of busybox.

> And init -q doesn't seem to work, so we cannot start with a minimal
inittab
> and then add more later and tell init to spawn it.

I think this one's the real problem.  Bug boils down to "init -q
doesn't work".

There's a major rework of init pending for about the 1.2 timeframe,
which kind 
of sapped my personal interest in messing with the current init too
much. 

But you need a bug fix before that, so I'll take a look...

I the short term, if you could add an entry in our bug thing 
(http://bugs.busybox.net) about -q not working, it would make sure we
don't 
forget this and that you get notified when we fix it.

> > In the short term, there are a few possible workarounds.  You could
> > have your wrapper figure out whether or not it needs to create the
> > device nodes before calling /init.
>
> Yeah, that's what we thought too.  Colin tried to implement this but
> he said our script

Re: Netinstall Etch or Sid

[Christian Perrier]

Quoting Matthias Popp ([EMAIL PROTECTED]):
> Hallo,
> Why I cant't install Etch or Sid without a working networkconnection. With 
> Sarge no problem.  But the kernel is sometimes to old. 


There is work in progress about this. See
http://wiki.debian.org/DebianInstaller/EtchBeta3Prep




signature.asc
Description: Digital signature