Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
[ I don't know why, but for some reason installation-reports go to ] [ debian-testing, so I'm forwarding this to debian-boot for discussion ] Package: installation-reports Version: netboot daily image from 2003-11-10 Severity: normal Tags: d-i INSTALL REPORT Debian-installer-version: daily netboot image from http://people.debian.org/~sjogren/d-i/images/2003-11-10/ uname -a: Linux (none) 2.4.22-1-386 #9 Sat Oct 4 14:30:39 EST 2003 i686 unknown Date: Tue Nov 11 01:03:47 EST 2003 Method: netboot via PXE Machine: Dell Inspiron 1100 laptop Processor: Intel Celeron 2GHz Memory: 256MB Root Device: N/A Root Size/partition table: N/A Output of lspci: /bin/sh: lspci: not found Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [E] Config network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Alright, here are the highlights of how this install went: 0) OK, after much struggling (and dealing with my nemesis error message 'VFS: Cannot open root device or 3a:04') I managed to get the d-i netboot image to work via PXE. For posterity (and the installation guide) the magic kernel options I needed to make this work are ramdisk_size=8192 root=/dev/ram0. If anyone would like assistance setting up a PXE testbed or copies of various configs I use please don't hesitate to ask. 1) Install boots into the main menu. Interface looks alot snazzier than the old text interface, however the line-drawing characters are all messed up on my terminal (corners are displayed as '', c.) Known bug? 2) Picking Choose language doesn't get very far. This is what I can piece together from syslog: DEBUG: Menu item 'languagechooser' selected DEBUG: configure languagechooser, status: 4 WARNING **: Configuring 'languagechooser' failed with error code 1 WARNING **: Menu item 'languagechooser' failed. Any ideas? Known unfiled bug? File a new bug against languagechooser? 3) After doing 'Select a Keyboard Layout', I chose 'Detect network hardware'. This generated the following two (fatal looking) errors: a. An error occured while running 'modprobe -v floppy false`. b. An error occured while running 'modprobe -v ide-cd false`. Since this is a netboot install, these errors should not be fatal. 4) When finally presented with a list of ethernet drivers to pick from, the requisite driver for this laptop -- b44 -- is missing. I tried switching to vc2 and doing 'modprobe -v b44', but this fails since the module doesn't exist on the image. How do we get it added? Well, that's as far as I got. Hope this helps! Joe PS - This particular laptop doesn't have a serial port, so all output/error messages are hand-typed and subject to typos, c. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux laptop 2.4.22-1-686 #6 Sat Oct 4 14:09:08 EST 2003 i686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Second stage console problem
[Kenshi Muto] I tried debian-installer beta1 CD (net-install), and it worked on first stage. :-) Sounds good. But I noticed second stage (after reboot) had a problem for non-Latin users (Japanese, Chinese, Korean, and other non-Latin people needs special console). Hm, I suspected this. 1. On second stage, termwrap (in base-config) checks whether jfbterm (jfbterm is multilingual console) was installed or not. jfbterm wasn't installed because its udeb wasn't exist. Second stage (base-config) do not use udebs. It uses normal .deb packages. 1. Ask jfbterm maintainer to provide udeb package. (I've already asked maintainer Ukai, but not reported BTS yet) No need for an udeb to solve the problem with base-config. 2. In first stage, if selected locale needs multilingual console, prebaseconfig(?) installs jfbterm.udeb and bterm-unifont.udeb to /target. If we allow to waste some disk space, it is easier to install always these packages without checking locale. I was planning to come up with a solution to this problem in languagechooser, but haven't come around to it yet. One solution need some way to know which choices need which terminals, and to call apt-install with the given package as argument to get it installed. Another idea was to always run base-config in an UTF-8 terminal, and always install an UTF-8 capable framebuffer terminal. This way, we use the same system for all languages, and it is less likely that the lesser used configurations contain errors. 3. In second stage, try to install FB (FrameBuffer) driver if terminal is console. I suspect this is missing. 4. If terminal is console and FB is enable, run jfbterm such as 'jfbterm -c other,EUC-JP,iconv,UTF-8' (this means EUC-JP terminal with UTF-8 conversion) from termwrap. This is partly implemented in base-config. 5. If terminal is console and FB is disable, set LANG=C in termwrap. This is implemented, I believe. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219928: debian-installer: build failures on sparc
tag 219928 d-i severity 219928 important merge 211092 219928 thanks On Tue, Nov 11, 2003 at 12:02:34AM +0100, Falk Hueffner wrote: Can I get more information on why this is a bug in mklibs? Does some library actually provide timeout_yet? If so, can I please see readelf -s -W output of it? See bug 211092 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=211092 ) It was original titled 'building debian-installer on sparc fails' This message is an other attempt to merge these bugs. Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[Fwd: [debian-installer] sarge-i386-netinst.iso]
fwd'ing on. i asume he got the image from a link on my page. Original Message Subject:[debian-installer] sarge-i386-netinst.iso Date: Sat, 08 Nov 2003 14:04:44 +0100 From: Dirk Meul [EMAIL PROTECTED] Organization: RWTH-Aachen To: [EMAIL PROTECTED] Hello. I'm not able to boot this image successfully. My system is: * ASUS P3B-F (BIOS: 1008beta4) * Celeron (Coppermine) 850Mhz * 768MB Ram * sym53c810a SCSI-controller * Toshiba DVD-ROM (SD-M1401) (SCSI) The boot menu will work and i'm able to load the kernel and the ramdisk, but after Ready. the machine will not do anything. Even using smart boot manager will not work. Without SCSI-BIOS enabled the DVD-Rom is not listed in the menu and with SCSI-BIOS the boot manager will not start. Best regards, -- /\ Dirk Meul \ /ASCII Ribbon Campaign [EMAIL PROTECTED]X Against HTML Mail / \ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#219928: debian-installer: build failures on sparc
Processing commands for [EMAIL PROTECTED]: tag 219928 d-i Bug#219928: debian-installer: build failures on sparc There were no tags set. Tags added: d-i severity 219928 important Bug#219928: debian-installer: build failures on sparc Severity set to `important'. merge 211092 219928 Bug#211092: mklibs can't handle noweak symbols Bug#219928: debian-installer: build failures on sparc Merged 211092 219928. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219928: debian-installer: build failures on sparc
[EMAIL PROTECTED] (Geert Stappers) writes: On Tue, Nov 11, 2003 at 12:02:34AM +0100, Falk Hueffner wrote: Can I get more information on why this is a bug in mklibs? Does some library actually provide timeout_yet? If so, can I please see readelf -s -W output of it? See bug 211092 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=211092 ) It was original titled 'building debian-installer on sparc fails' I cannot find this information there, either. -- Falk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Webpage fix
On Tue, Nov 11, 2003 at 04:40:45AM +0100, Steinar H. Gunderson wrote: Could somebody add the URL for the daily-built images (http://people.debian.org/~sjogren/d-i/images/daily/) back to the website? They seem to have been removed, and they are useful for people who want to test the d-i beta via netboot or floppy. Or provide those usefull images on a more offical place. Also, the last built images are from the 9th; isn't that a day old...? :-) The 11-11 images were build. /* Steinar */ Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219928: debian-installer: build failures on sparc
On Tue, Nov 11, 2003 at 10:02:44AM +0100, Falk Hueffner wrote: [EMAIL PROTECTED] (Geert Stappers) writes: On Tue, Nov 11, 2003 at 12:02:34AM +0100, Falk Hueffner wrote: Can I get more information on why this is a bug in mklibs? Does some library actually provide timeout_yet? If so, can I please see readelf -s -W output of it? See bug 211092 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=211092 ) It was original titled 'building debian-installer on sparc fails' I cannot find this information there, either. | Can I get more information on why this is a bug in mklibs? See bug 211092 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=211092 ) | Does some library actually provide timeout_yet? | If so, can I please see readelf -s -W output of it? I don't care about a single accidentically missing symbol. -- Falk Proost Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220139: isolinux/syslinux
I used google a while. Maybe it is interesting for you: http://lists.debian.org/debian-cd/2002/debian-cd-200205/msg00165.html http://www.zytor.com/pipermail/syslinux/2002-December/001324.html Björn Lässig -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219928: debian-installer: build failures on sparc
[EMAIL PROTECTED] (Geert Stappers) writes: On Tue, Nov 11, 2003 at 10:02:44AM +0100, Falk Hueffner wrote: | Can I get more information on why this is a bug in mklibs? See bug 211092 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=211092 ) | Does some library actually provide timeout_yet? | If so, can I please see readelf -s -W output of it? I don't care about a single accidentically missing symbol. I don't understand. Are you saying if a symbol is missing, mklibs should ignore that and create a binary that cannot be executed? -- Falk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
Am Die, den 11.11.2003 schrieb Joe Nahmias um 09:16: [ I don't know why, but for some reason installation-reports go to ] [ debian-testing, so I'm forwarding this to debian-boot for discussion ] probably someone should reassign the pseudo-package installation-reports to debian-boot. I, Sebastian and Sesse sorted and closed a bunch of reports last night. They all went to the pseudo package installation-reports and were only forwarded to debian-testing. gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#201191: partconf: mkfs should indicate progress
Am Die, den 11.11.2003 schrieb Steinar H. Gunderson um 04:02: A quick test indicates that most interesting mkfs-variations (ext2, ext3, reiserfs; vfat and jfs are so quick it doesn't need progress, and xfs seems only a bit slower than that) has at least some kind of progress output, so we _could_ theoretically grok that. It will be ugly, though... This depends on the size of the filesystem and if dma is enabled or not. enabling DMA speeds up filesystem creation a lot on big disks. With DMA disabled it can take several minutes to create a big filesystem. I suggest a simple solution. I think the most important thing is that users don't see a blue screen for several seconds like it's now, but a progress bar. I would only step it forward after one filesystem is created, so we don't have to parse mkfs.* output. A setup with only one root partition and one swap would have two steps: 0% creating filesystem on /dev/... 50% creating swap on /dev/... 100% finished libparted1.6 supports ext2, ext3, vfat and reiserfs, but no jfs or xfs. One _could_ use libparted for the first four and fall back to mkfs.* for everything else; that would be a definitive improvement for 95% of our users (as I said, jfs and xfs seem fast already). More code that could go wrong, though... I think one point of having partitioner is, that it does not use libparted for filesystem creation and is therefore more versatile and less prone to errors. This should really be fixed for beta 2. :-) ACK. gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: My experience with d-i
Quoting Bill Allombert ([EMAIL PROTECTED]): Then it proceed with the `Configure network via DHCP'. This one is really painful, since it lock the install for a long time since I have no DHCP server, but I was not offered to skip this stage and go directly to 'Configure a static network'. That one also pisses me off (sorry for maybe too trivial language, folks...I do not really intend to be rude, just a bit humor). I think this is a design choice mostly. People, from the d-i team, who worked during the earlier stages of d-i development can probably explain this choice. I think 'Configure a static network' asks question in the wrong order. In a lot of case, hostname, domainname are not required for installing. (and a lot of people don't have a domainname either. Even the DNS server is not always needed. So it should ask first: the IP the netmask the gateway I definitely confirm. Most OS (including Windows flavors) ask these basic question in this order (or, for WIndows, by first showing the IP address/netmask tab) I indeed entered the wrong parameters during some of my own tests and put my IP addressin the domain field.. :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220180: cdrom-detect: Debconf templates polishing
Package: cdrom-detect
Severity: normal
Tags: patch d-i
Now usual debconf templates polishing bug report.
Proofreading by native English speakers needed. Chris, I'm sure you're
reading this..:)
Detailed rationale:
Template: cdrom-detect/manual_config
Type: boolean
Default: true
-_Description: Do you want to manually select the CDROM module and device ?
- No common CDROM reader was detected. But you may have an old Mitsumi or
- another non-IDE, non-SCSI CDROM reader. In that case you can indicate
- which module to load and which device to use. If you don't know what
- module and device are needed, look for some documentation or try a net
- install instead of a CDROM install.
+_Description: Manually select the CD-ROM module and device?
+ No common CD-ROM reader was detected.
+ .
+ Your CD-ROM reader may be an old Mitsumi or another non-IDE, non-SCSI
+ CD-ROM reader. In that case you may choose which module to load and
+ which device to use. If you don't know what module and device are
+ needed, look for some documentation or try a network installation
+ instead of a CD-ROM installation.
1) Removed space before question mark. Shorten the question
2) Better readability by splitting in two paragraphs with the most important
one at the top
3) s/CDROM/CD-ROM for general d-i consistency
4) Drop the but you may have.which seems too french to me..:-)
English native speakers, please proofread this 2nd paragraph
Template: cdrom-detect/is_cd_inserted
Type: boolean
Default: false
-_Description: Perform manual CD configuration ?
- Your installation CD couldn't be mounted. That probably means that the CD
- is not yet inserted. If that's the case, just insert it and don't perform
- the manual configuration; the CD mount will be re-tried. If your CD was
- already in the drive, there was another problem; try the manual CD
- configuration.
+_Description: Perform manual CD-ROM configuration?
+ Your installation CD-ROM couldn't be mounted.
+ .
+ That probably means that the CD-ROM is not yet inserted. If that's the case,
+ just insert it and don't perform the manual configuration. The CD-ROM mount
+ will be re-tried.
+ .
+ If your CD-ROM was already in the drive, some other problem happened. You
+ should then try the manual CD-ROM configuration.
1) Removed space before QM
2) split into paragraphs for readability. Minor rewrite of the third one
Template: cdrom-detect/cdrom_module
Type: select
Choices: ${choices}
Default: none
-_Description: Select a module to load for the CDROM support
- Apparently the autodetection didn't find any CDROM reader. You can try to
- load one of the modules if you have a specific CDROM reader (that is
+_Description: Module needed for accessing the CD-ROM:
+ The automatic detection didn't find any CD-ROM reader. You can try to
+ load a specific module if you have a specific CD-ROM reader (that is
neither IDE nor SCSI).
1) Short desc=prompt
2) Just give facts..:-)
Template: cdrom-detect/cdrom_device
Type: string
Default: /dev/cdrom
-_Description: Give the corresponding device file
- In order to get access to your CDROM reader, I must know which device file
- should be used since non-standard CDROM readers use non-standard device
- files (like /dev/mcdx for example).
+_Description: Device file for accessing the CD-ROM:
+ In order to get access to your CD-ROM reader, please enter which device file
+ should be used. Non-standard CD-ROM readers use non-standard device
+ files (such as /dev/mcdx).
.
You may switch to the shell on the second terminal (ALT+F2) to check the
- available devices in /dev with ls /dev. You can come back here with
- ALT+F1.
+ available devices in /dev with ls /dev. You can come back to this screen
+ with ALT+F1.
1) Prompt
2) s/CDROM/CD-ROM
3) removed 1st person. English proofreading needed
4) s/here/to this screen
Template: cdrom-detect/success
Type: note
-_Description: A CDROM has been detected.
- CD autodetection worked. A CDROM reader has been found with the following
- CD inserted : ${cdname} You can continue the install.
+_Description: CD-ROM detected
+ The CD-ROM autodetection was successful. A CD-ROM reader has been found. It
+ currently contains this CD: ${cdname}. The installation process may continue.
1) Short desc==title
2) worked is a bit trivial, isn't it?
Proofreading needed
Template: cdrom-detect/no-cd
Type: error
-_Description: No CD was detected
- Please make sure that there is a CD in the CDROM reader.
+_Description: No CD detected
+ Please check that a CD has been inserted in the CD-ROM reader.
1) Title so no phrase required...but is this correct?
2) Minor rephrase
Template: cdrom-detect/wrong-cd
Type: error
-_Description: A CDROM has been detected, but it isn't a Debian CD
+_Description: Non-Debian CD-ROM detected
+ A CDROM has been detected, but it isn't a Debian CD.
+ .
Please make sure that the correct CD is inserted.
1) Title
2) Move the former short desc to extended description
Template:
Re: Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
Am Die, den 11.11.2003 schrieb Joe Nahmias um 09:16: Alright, here are the highlights of how this install went: 0) OK, after much struggling (and dealing with my nemesis error message 'VFS: Cannot open root device or 3a:04') I managed to get the d-i netboot image to work via PXE. For posterity (and the installation guide) the magic kernel options I needed to make this work are ramdisk_size=8192 root=/dev/ram0. If anyone would like assistance setting up a PXE testbed or copies of various configs I use please don't hesitate to ask. It would be nice, if you could write a short addition to the INSTALLATION-HOWTO about your way to install d-i via PXE boot. There is already a very short section on netbooting the installer. If you send a patch to debian-boot, I will look at it and commit it to CVS. 1) Install boots into the main menu. Interface looks alot snazzier than the old text interface, however the line-drawing characters are all messed up on my terminal (corners are displayed as '', c.) Known bug? not know bug, please file one. Sorry I don't know which package to blame for that. btw the installation should not boot into main-menu but directly go into languagechooser. 2) Picking Choose language doesn't get very far. This is what I can piece together from syslog: DEBUG: Menu item 'languagechooser' selected DEBUG: configure languagechooser, status: 4 WARNING **: Configuring 'languagechooser' failed with error code 1 WARNING **: Menu item 'languagechooser' failed. Any ideas? Known unfiled bug? File a new bug against languagechooser? bug not know. You should have languagechooser 1.03 on your image, which is the same as on the beta1 which works for most people. Please file a bug. 3) After doing 'Select a Keyboard Layout', I chose 'Detect network hardware'. This generated the following two (fatal looking) errors: a. An error occured while running 'modprobe -v floppy false`. b. An error occured while running 'modprobe -v ide-cd false`. Since this is a netboot install, these errors should not be fatal. please file a bug on hw-detect (or ethdetect?). It's strange that these are tried for network hardware detection. Probably the installer tries to load additional modules from a floppy? 4) When finally presented with a list of ethernet drivers to pick from, the requisite driver for this laptop -- b44 -- is missing. I tried switching to vc2 and doing 'modprobe -v b44', but this fails since the module doesn't exist on the image. How do we get it added? known bug. As of linux-kernel-di 0.12 this driver is in nic-extra-modules. This means you have to load it from an additional floppy. If this is a common NIC then we could add it to nic-modules, which is on the netboot initrd. PS - This particular laptop doesn't have a serial port, so all output/error messages are hand-typed and subject to typos, c. You could try to save /var/log/messages and /var/log/syslog to an already formatted partition. gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220139: isolinux/syslinux on special hardware
On Tue, Nov 11, 2003 at 10:26:52AM +0100, Bjoern Laessig wrote: I used google a while. Maybe it is interesting for you: http://lists.debian.org/debian-cd/2002/debian-cd-200205/msg00165.html | | El Torito BIOSes are absolute crap. There is no question about it. | Unfortunately there is right now *NO* configuration which works on all | machines. If you want a configuration that works on all machines, | you're talking boot floppies. It really is that bad. | | Hello to all you folks who are pushing for us to have all new machines. | I think that going with no-emulation mode is a worst case scenario. | | Go over to Mandrake please and hang with those folks for a while. | Then come back to a sane world populated with debian-heads. | The choice is clear: we will lose a lot of folks with old machines | who will not be able to use Debian any more. Old hands will be upset. | The CD will not boot; they will not know to try the rest of the set; | they will only have the first CD; the CD will be given away; | the old machines will be tossed. We will lose the third world. | We will lose the old office networks of ready-for-linux machines. | They will use windows 95. | | | yes BIOS makers do not follow the standards. | | They do follow the floppy booting standard disk type 00. | A floppy will boot the bad BIOS. | Therefore floppy emulation works on most machines. | | if you want to exclude most machines, simply switch to | no emulation mode. | XP does it. It must be a bad thing. | It does push the sales of new machines. | 'no emulation' mode demands a new machine. | | if you want to boot on most CD booting machines | just like RedHat 7.3 | then use floppy emulation. | | I vote for floppy emulation to boot from CD. | | Cheers, Bill Bennet http://www.zytor.com/pipermail/syslinux/2002-December/001324.html To follow-up http://www.zytor.com/pipermail/syslinux/2002-December/001325.html says: | On Fri, 20 Dec 2002 15:47:18 +, Roberto De Leo [EMAIL PROTECTED] wrote: | | | My main question is the following: a few (windows) users burned an isolinux | image I prepared with isolinux and could not boot the CD, so they tried | to make it bootable with Nero choosing the floppy image as Nero boot image | and it worked! How can it be possible that the CD produced with isolinux | does not boot and the one made with Nero/syslinux does with the very same | BIOS? | | If you use isolinux you are booting with El Torito in no emulation mode, | while if you use a floppy boot image you're likely booting in floppy | emulation mode. Maybe that bios is ok with emulation mode and not the other | way. | | The advantage of isolinux is that you can ignore the limits of floppy images | (large initrd's) and/or choose at boot which floppy image to boot. | | However, if all you need is the equivalent of a floppy image on CD, you can | produce the image with mkisofs and a floppy image (maybe with syslinux) | without using isolinux. This would be more similar to what those windows | users did. | | -- | [EMAIL PROTECTED] To me it looks like that bugreport 220139 is a support request for a range hardware that boots from CD-ROM on special way. Not having the same hardware makes it hard to fix such problems. Björn Lässig Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220182: netcfg: Please re-order the TCP/IP configuration questions
Package: netcfg Severity: wishlist Tags: d-i The current order is not really natural : I suggest using the following order: -IP address -Netmask -Gateway -Machine name -Domain name -DNS servers Bill, feel free to comment as you are the one who motivated me to make this BR..:-) -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux mykerinos 2.4.22 #2 Mon Sep 29 15:12:10 CEST 2003 i686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (ignored: LC_ALL set to fr_FR.UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
On Tue, Nov 11, 2003 at 11:15:01AM +0100, Gaudenz Steinlin wrote: Am Die, den 11.11.2003 schrieb Joe Nahmias um 09:16: [ I don't know why, but for some reason installation-reports go to ] [ debian-testing, so I'm forwarding this to debian-boot for discussion ] probably someone should reassign the pseudo-package installation-reports to debian-boot. If this is the general opinion of d-i folks, then ftpmaster are the people to ask. (I thought sending it to -testing was originally deliberate, though.) -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Priority handling in main-menu
Hello, in my opinion the priority handling on errors in main-menu needs still some work. Presently the logic is simple: Have an initial priority. If a menu item fails, lower the priority by one step. If a menu item suceeds, pump up the priority by one but not greater than the initial priority. However consider the following situation (as also percieved in an installation-report): Initial priority is high. A step fails and the priority gets lowered to medium, showing the menu. The user chooses that the failing step is not relevant or perhaps uses a shell to recover. He then selects the next entry. That entry suceeds again, so priority is set to high again. Which will bring him back to the step that actaully failed, too bad... I do not know if we should think of an entire different solution to handle that but for now we could add some code to main-menu that assures that the priority will not be set = high until the offending menu point actually suceeded. Sebastian -- PGP-Key: http://www.mmweg.rwth-aachen.de/~sebastian.ley/public.key Fingerprint: A46A 753F AEDC 2C01 BE6E F6DB 97E0 3309 9FD6 E3E6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220182: netcfg: Please re-order the TCP/IP configuration questions
On Tue, Nov 11, 2003 at 09:44:48AM +0100, Christian Perrier wrote: Package: netcfg Severity: wishlist Tags: d-i The current order is not really natural : I would like to propose this change; -IP address -Netmask -Gateway -DNS servers -Machine name -Domain name Bill, feel free to comment as you are the one who motivated me to make this BR..:-) My point is that we should ask the most important information first. If you access a Debian archive on the same LAN you only need IP address and netmask. Once d-i know IP address, it can guess default value for 'Netmask' and 'Gateway' (as it does already). If we want to access the Debian mirror we need the DNS server. Machine name and Domain name are not needed at this stage, and a lot of people don't have a Domain name. The order I propose is more in line with usual practice, be in software or in document (the sheet given by the sysadmin with the network info). Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#220181: utils: Debconf templates polishing
Processing commands for [EMAIL PROTECTED]: reassign 220181 di-utils Bug#220181: utils: Debconf templates polishing Warning: Unknown package 'utils' Bug reassigned from package `utils' to `di-utils'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219928: debian-installer: build failures on sparc
On Tue, Nov 11, 2003 at 10:54:31AM +0100, Falk Hueffner wrote: [EMAIL PROTECTED] (Geert Stappers) writes: On Tue, Nov 11, 2003 at 10:02:44AM +0100, Falk Hueffner wrote: | | | I cannot find this information there, either. | Can I get more information on why this is a bug in mklibs? See bug 211092 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=211092 ) | Does some library actually provide timeout_yet? | If so, can I please see readelf -s -W output of it? I don't care about a single accidentically missing symbol. I don't understand. Are you saying if a symbol is missing, mklibs should ignore that and create a binary that cannot be executed? I'm only saying that it is a mklibs bug. Where the timeout_yet or whatever noweak symbol is, is not important(to me). -- Falk Proost Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220198: installation: proper sata support needed
Package: installation Version: sarge beta Severity: normal Current Install Kernels do not include proper Serial-ATA Support. I believe that several install problems with SATA-Devices could be solved when install-kernels included the libata-patch ftp://ftp.kernel.org/pub/linux/kernel/people/jgarzik/libata/ which is also included in 2.6 series kernels. SATA-Devices are treated as SCSI-Devices. Drive mapping issues with ich5 should be solved with this patch and it supports hardware which is quite common nowadays (promise 37x), that is not (yet) supported by vanilla 2.4.22 kernel. May those day's when i had to debootstrap new systems because of lacking kernel-support for thy new hardware be over soon ;-) Bye, O.H1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Failed floppy installation
Hi I have tried a floppy installation both with the daily and the standard images and have the same problem. In standard I can't mount the already existing partitions, I am adviced to repartition. In the partition part cfdisk, when accepting the existing partitions I am getting back even if I write the table to disk. That is I am stuck in the partition part. In the daily I didn't have the choice of keyboard and mount, so this mode was not the 'medium', which was given in the standard one. The hard drive in question was having: hda1 = ntfs hda5 = ext3 hda6 = ext3 hda7 = ext3 hda8 = swap hdb1 = ext3 hdb2 = swap Jag har haft Debian på denna boxen tidigare utan problem. regards guran -- Mandrake Linux 9.2 kernel-2.4.22.21mdk-1-1mdk Only in a society that has 'a priori' defined what is the truth can the result from the evolution of life be defined false. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220048: Your installation report
On Tue, Nov 11, 2003 at 11:55:11AM +0100, Martin Pitt wrote: None unfortunately. On both machines and with all three CD drives, the BIOS tries to boot from CD-ROM, cannot do it and boots from HDD instead. [...] However, I just tried to boot the very same CD on the laptop of a friend of mine: it worked! He has got a Pentium III-850 with a Toshiba DVD-ROM SD-C2502-(PS) drive. Unfortunately I cannot tell anything about his motherboard. OKay, I suppose your BIOS is not able to boot with isolinux, the bootloader used on the netinst CDs. Unfortunatly that means that you have to use disks for now. I hope there will be a solution for this soon, I will rise the topic again. As for floppy images, you can find them in the archive in the [...] Yes, I know. But I did not find bootfloppy-image.img on the Sarge netinstall CD. IMHO it would be nice to have it there for the cases where CD-ROM booting does not work. We wanted to keep the netinstall images as small as possible. Therefore the diskimages have to be obtained elsewhere for now. Feel free to file a wishlist bug if you think this is not appropriate. Regards, Sebastian -- PGP-Key: http://www.mmweg.rwth-aachen.de/~sebastian.ley/public.key Fingerprint: A46A 753F AEDC 2C01 BE6E F6DB 97E0 3309 9FD6 E3E6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219928: debian-installer: build failures on sparc
[EMAIL PROTECTED] (Geert Stappers) writes: On Tue, Nov 11, 2003 at 10:54:31AM +0100, Falk Hueffner wrote: [EMAIL PROTECTED] (Geert Stappers) writes: On Tue, Nov 11, 2003 at 10:02:44AM +0100, Falk Hueffner wrote: | | | I cannot find this information there, either. | Can I get more information on why this is a bug in mklibs? See bug 211092 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=211092 ) | Does some library actually provide timeout_yet? | If so, can I please see readelf -s -W output of it? I don't care about a single accidentically missing symbol. I don't understand. Are you saying if a symbol is missing, mklibs should ignore that and create a binary that cannot be executed? I'm only saying that it is a mklibs bug. Where the timeout_yet or whatever noweak symbol is, is not important(to me). Then how do you know it is a bug in mklibs and it is not actually a missing symbol? -- Falk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Merge isolinux stuff
Processing commands for [EMAIL PROTECTED]: tags 220048 - moreinfo Bug#220048: Cannot boot from CD Tags were: moreinfo d-i Tags removed: moreinfo tags 220139 + d-i Bug#220139: Debian Installer Sarge Beta not boot on (only) my machine There were no tags set. Tags added: d-i merge 220139 220048 Bug#220048: Cannot boot from CD Bug#220139: Debian Installer Sarge Beta not boot on (only) my machine Merged 220048 220139. severity 220139 important Bug#220139: Debian Installer Sarge Beta not boot on (only) my machine Bug#220048: Cannot boot from CD Severity set to `important'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220208: debian-installer-demo: missing build-depends on genromfs
Package: debian-installer Severity: normal After attempting a workaround for bug 219928 building debian-installer for sparc, (removing all referces to brltty) I find that the genromfs command is executed but there is no build-dependancy on the genromfs package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219928: debian-installer: build failures on sparc
Falk Hueffner [EMAIL PROTECTED] writes: [EMAIL PROTECTED] (Geert Stappers) writes: On Tue, Nov 11, 2003 at 10:54:31AM +0100, Falk Hueffner wrote: [EMAIL PROTECTED] (Geert Stappers) writes: On Tue, Nov 11, 2003 at 10:02:44AM +0100, Falk Hueffner wrote: | | | I cannot find this information there, either. | Can I get more information on why this is a bug in mklibs? See bug 211092 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=211092 ) | Does some library actually provide timeout_yet? | If so, can I please see readelf -s -W output of it? I don't care about a single accidentically missing symbol. I don't understand. Are you saying if a symbol is missing, mklibs should ignore that and create a binary that cannot be executed? I'm only saying that it is a mklibs bug. Where the timeout_yet or whatever noweak symbol is, is not important(to me). Then how do you know it is a bug in mklibs and it is not actually a missing symbol? Which was the real reason it failed in every testcase I got my hand on so far. All of those suposedly mklibs weak symbols bugs disapeared when recompiling the faulty binaries against the proper versions of libraries so far. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Usage of isolinux on the beta CDs
Hello, it seems that we are locking out people from testing by using isolinux on our netinst/businesscard CDs, see #220139 and #220139. Since we do not need any of isolinux's features I propose to use syslinux on the CDs. Regards, Sebastian -- PGP-Key: http://www.mmweg.rwth-aachen.de/~sebastian.ley/public.key Fingerprint: A46A 753F AEDC 2C01 BE6E F6DB 97E0 3309 9FD6 E3E6 signature.asc Description: Digital signature
Translation testing
Hi list! Can you tell me please(or redirect to RTFM) how to test an ongoing translation? Regards, Boris Ratner. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Priority handling in main-menu
On Tue, 2003-11-11 at 11:26, Sebastian Ley wrote: Hello, in my opinion the priority handling on errors in main-menu needs still some work. Presently the logic is simple: Have an initial priority. If a menu item fails, lower the priority by one step. If a menu item suceeds, pump up the priority by one but not greater than the initial priority. However consider the following situation (as also percieved in an installation-report): Initial priority is high. A step fails and the priority gets lowered to medium, showing the menu. The user chooses that the failing step is not relevant or perhaps uses a shell to recover. He then selects the next entry. That entry suceeds again, so priority is set to high again. Which will bring him back to the step that actaully failed, too bad... I do not know if we should think of an entire different solution to handle that but for now we could add some code to main-menu that assures that the priority will not be set = high until the offending menu point actually suceeded. Do you really mean = high? I think = medium would make more sense, because then main-menu is always shown until the offending menu entry succeeds. Gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#201191: partconf: mkfs should indicate progress
On Tue, Nov 11, 2003 at 03:30:30PM +0100, Gaudenz Steinlin wrote: It would definitely help compared to what we have today, but it would still suck. Yes, but I don't think it's worth to invest more time in that now. This would be an easy and acceptable solution. Well, it's not a matter of time, really -- adding progress bars to autopartkit was quite easy once libparted1.6 support was in place. It's more a matter of is this an okay way of doing it. I don't know how stable parted on i386 is. Last time I tried to format a partition with parted on my powerbook it just hung forever and did not format the partition. So I thought parted my be a little bit flaky. Actually I don't know if the bug is in the frontend or the library. FWIW, I've used autopartkit quite a lot, and never seen any problems with libparted. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220180: cdrom-detect: Debconf templates polishing
On Tue, Nov 11, 2003 at 11:08:20AM +0100, Christian Perrier wrote:
Package: cdrom-detect
Severity: normal
Tags: patch d-i
Now usual debconf templates polishing bug report.
Proofreading by native English speakers needed. Chris, I'm sure you're
reading this..:)
Detailed rationale:
Template: cdrom-detect/manual_config
Type: boolean
Default: true
-_Description: Do you want to manually select the CDROM module and device ?
- No common CDROM reader was detected. But you may have an old Mitsumi or
- another non-IDE, non-SCSI CDROM reader. In that case you can indicate
- which module to load and which device to use. If you don't know what
- module and device are needed, look for some documentation or try a net
- install instead of a CDROM install.
+_Description: Manually select the CD-ROM module and device?
+ No common CD-ROM reader was detected.
+ .
+ Your CD-ROM reader may be an old Mitsumi or another non-IDE, non-SCSI
+ CD-ROM reader. In that case you may choose which module to load and
+ which device to use. If you don't know what module and device are
+ needed, look for some documentation or try a network installation
+ instead of a CD-ROM installation.
1) Removed space before question mark. Shorten the question
2) Better readability by splitting in two paragraphs with the most important
one at the top
3) s/CDROM/CD-ROM for general d-i consistency
4) Drop the but you may have.which seems too french to me..:-)
English native speakers, please proofread this 2nd paragraph
:) Sounds too French for me.
No really, it's fine, and an improvement.
Template: cdrom-detect/is_cd_inserted
Type: boolean
Default: false
-_Description: Perform manual CD configuration ?
- Your installation CD couldn't be mounted. That probably means that the CD
- is not yet inserted. If that's the case, just insert it and don't perform
- the manual configuration; the CD mount will be re-tried. If your CD was
- already in the drive, there was another problem; try the manual CD
- configuration.
+_Description: Perform manual CD-ROM configuration?
+ Your installation CD-ROM couldn't be mounted.
+ .
+ That probably means that the CD-ROM is not yet inserted. If that's the case,
+ just insert it and don't perform the manual configuration. The CD-ROM mount
+ will be re-tried.
+ .
+ If your CD-ROM was already in the drive, some other problem happened. You
+ should then try the manual CD-ROM configuration.
If your CD-ROM was already in the drive, then your CD-ROM hardware did
not respond. Manual CD-ROM configuration may help.
('occurred' would be better than 'happened' above. But I think a
rewrite is even better.)
1) Removed space before QM
2) split into paragraphs for readability. Minor rewrite of the third one
Template: cdrom-detect/cdrom_module
Type: select
Choices: ${choices}
Default: none
-_Description: Select a module to load for the CDROM support
- Apparently the autodetection didn't find any CDROM reader. You can try to
- load one of the modules if you have a specific CDROM reader (that is
+_Description: Module needed for accessing the CD-ROM:
+ The automatic detection didn't find any CD-ROM reader. You can try to
+ load a specific module if you have a specific CD-ROM reader (that is
neither IDE nor SCSI).
1) Short desc=prompt
2) Just give facts..:-)
Template: cdrom-detect/cdrom_device
Type: string
Default: /dev/cdrom
-_Description: Give the corresponding device file
- In order to get access to your CDROM reader, I must know which device file
- should be used since non-standard CDROM readers use non-standard device
- files (like /dev/mcdx for example).
+_Description: Device file for accessing the CD-ROM:
+ In order to get access to your CD-ROM reader, please enter which device file
+ should be used. Non-standard CD-ROM readers use non-standard device
+ files (such as /dev/mcdx).
.
You may switch to the shell on the second terminal (ALT+F2) to check the
- available devices in /dev with ls /dev. You can come back here with
- ALT+F1.
+ available devices in /dev with ls /dev. You can come back to this screen
+ with ALT+F1.
Non-standard CD-ROM readers use non-standard device files, for example
/dev/mcdx. Please enter the device file which is used to access your
CD-ROM reader.
(I think it reads better to switch these sentences around, and
rewrite the request. YMMV.)
1) Prompt
2) s/CDROM/CD-ROM
3) removed 1st person. English proofreading needed
4) s/here/to this screen
Template: cdrom-detect/success
Type: note
-_Description: A CDROM has been detected.
- CD autodetection worked. A CDROM reader has been found with the following
- CD inserted : ${cdname} You can continue the install.
+_Description: CD-ROM detected
+ The CD-ROM autodetection was successful. A CD-ROM reader has been found. It
+ currently contains this CD: ${cdname}. The installation process may continue.
1) Short desc==title
2)
Processed: Your installation report
Processing commands for [EMAIL PROTECTED]: clone 220132 -1 -2 -3 -4 -5 -6 Bug#220132: install successful, but many oddities Bug 220132 cloned as bugs 220188-220193. reassign -1 netcfg Bug#220188: install successful, but many oddities Bug reassigned from package `installation-reports' to `netcfg'. retitle -1 netcfg: should be smarter with dial-up connections Bug#220188: install successful, but many oddities Changed Bug title. reassign -2 hw-detect Bug#220189: install successful, but many oddities Bug reassigned from package `installation-reports' to `hw-detect'. retitle -2 hw-detect: messages are confusing Bug#220189: install successful, but many oddities Changed Bug title. severity -2 minor Bug#220189: hw-detect: messages are confusing Severity set to `minor'. reassign -3 base-installer Bug#220190: install successful, but many oddities Bug reassigned from package `installation-reports' to `base-installer'. retitle -3 base-installer: strange error message at the end of installation Bug#220190: install successful, but many oddities Changed Bug title. reassign -4 bugreporter-udeb Bug#220191: install successful, but many oddities Bug reassigned from package `installation-reports' to `bugreporter-udeb'. retitle -4 bugreporter-udeb: does not do anything at all Bug#220191: install successful, but many oddities Changed Bug title. severity -4 important Bug#220191: bugreporter-udeb: does not do anything at all Severity set to `important'. reassign -5 lilo-installer Bug#220192: install successful, but many oddities Bug reassigned from package `installation-reports' to `lilo-installer'. retitle -5 lilo-installer: should perhaps always default to first disk in system Bug#220192: install successful, but many oddities Changed Bug title. severity -5 wishlist Bug#220192: lilo-installer: should perhaps always default to first disk in system Severity set to `wishlist'. reassign -6 partconf-mkfstab Bug#220193: install successful, but many oddities Bug reassigned from package `installation-reports' to `partconf-mkfstab'. retitle -6 partconf-mkfstab: creates wrong entry for cdrom Bug#220193: install successful, but many oddities Changed Bug title. close 220132 Bug#220132: install successful, but many oddities 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Frank Otto [EMAIL PROTECTED] Thanks for submitting your installation report! Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
base-config integration, boot-time parameters, and d-i droppings
I am planning to finally integrate base-config properly with d-i. This will involve copying the d-i debconf database to somewhere in /target, probably var/cache/debconf/installation/. In my tests it looks like cdebconf writes the database quite frequently (suprisingly frequently, really), so getting the full db should not be a problem. Then base-config will look at some entries in the config and translate them over to the installed debconf database. It's also possible that I may decide to just have base-config merge the two databases into one. This has some advantages, but also problems, especially if there are question nameing conflicts. One such possible conflict is with, of all things, debconf/priority. high is default in d-i, while medium has historically been the default in debian proper. debconf/frontend is also used by both, but the set of frontends differs and would at least need to be translated. But wouldn't it be nice to be able to boot d-i and on the boot line, tell it to use the text frontend, and low priority (power user settings (or is that critical? :-)) and have that carry through right into the installed system.. Which brings me to boot-time parameters. We have a few, but I think they ought to be rethought. It would be neat if they could be used to override any value in the debconf database, not only the ones it has special environment variables for. So you could boot with debconf/priority=low, or with debconf/language=foo or maybe mirror/distribution=sid. These actually will show up as environment variables, though the shell cannot access them very easily because of the slash, all it needs is a little program to translate these into the cdebconf database and mark them as seen. There are also a few boot parameters (that I added) that have no corresponding question in the cdebconf database, and I should probably try to fix that. The cdebconf datbase then becomes a fairly self-documenting means of overriding lots of the installer's behavior. Of course overriding it at the boot prompt doesn't meet the needs of large installations that need to pre-seed the whole database, but it's a start. Finally, my more oddball idea. d-i drops a few files into various places in /target, and there is no easy way to know you've found them all and cleaned them all out of your installed system. Since we're already much better in this regard than the boot-floppies with their unpackged kernel, I think we could take it a step further, and make sure everything is in a package of a sort. This package could be assembeled on the fly somehow toward the end of the installation (or it could be a regular package that is installed as usual but then it cannot own some files as easily), and when purged would delete the log files, clean out the copy of the d-i database (or if base-config merges the two databases, purge the d-i parts from the main database), and so on. -- see shy jo signature.asc Description: Digital signature
Re: Priority handling in main-menu
On Tue, Nov 11, 2003 at 03:21:03PM +0100, Gaudenz Steinlin wrote: I do not know if we should think of an entire different solution to handle that but for now we could add some code to main-menu that assures that the priority will not be set = high until the offending menu point actually suceeded. Do you really mean = high? I think = medium would make more sense, because then main-menu is always shown until the offending menu entry succeeds. Not be set to prio = high means that is only medium or low. Main-menu is shown with prio medium so it is exactly what we want. Parse error? ;-) Regards, Sebastian -- PGP-Key: http://www.mmweg.rwth-aachen.de/~sebastian.ley/public.key Fingerprint: A46A 753F AEDC 2C01 BE6E F6DB 97E0 3309 9FD6 E3E6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#201191: partconf: mkfs should indicate progress
On Tue, 2003-11-11 at 15:15, Steinar H. Gunderson wrote: I suggest a simple solution. I think the most important thing is that users don't see a blue screen for several seconds like it's now, but a progress bar. I would only step it forward after one filesystem is created, so we don't have to parse mkfs.* output. A setup with only one root partition and one swap would have two steps: 0% creating filesystem on /dev/... 50% creating swap on /dev/... 100% finished It would definitely help compared to what we have today, but it would still suck. Yes, but I don't think it's worth to invest more time in that now. This would be an easy and acceptable solution. I think one point of having partitioner is, that it does not use libparted for filesystem creation and is therefore more versatile and less prone to errors. Why would running mkfs.ext2 be more versatile than using libparted? (Like I said, I'd use mkfs.* for JFS etc., but ATM we don't even have that on our install disks. :-) ) I don't know how stable parted on i386 is. Last time I tried to format a partition with parted on my powerbook it just hung forever and did not format the partition. So I thought parted my be a little bit flaky. Actually I don't know if the bug is in the frontend or the library. Gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#201191: partconf: mkfs should indicate progress
On Tue, Nov 11, 2003 at 11:03:53AM +0100, Gaudenz Steinlin wrote: This depends on the size of the filesystem and if dma is enabled or not. enabling DMA speeds up filesystem creation a lot on big disks. With DMA disabled it can take several minutes to create a big filesystem. It can, even with DMA. autopartkit uses at least a few minutes when creating an ext2 filesystem on a 75GB disk (with DMA). I suggest a simple solution. I think the most important thing is that users don't see a blue screen for several seconds like it's now, but a progress bar. I would only step it forward after one filesystem is created, so we don't have to parse mkfs.* output. A setup with only one root partition and one swap would have two steps: 0% creating filesystem on /dev/... 50% creating swap on /dev/... 100% finished It would definitely help compared to what we have today, but it would still suck. I think one point of having partitioner is, that it does not use libparted for filesystem creation and is therefore more versatile and less prone to errors. Why would running mkfs.ext2 be more versatile than using libparted? (Like I said, I'd use mkfs.* for JFS etc., but ATM we don't even have that on our install disks. :-) ) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220030: prebaseconfig: Debconf templates polishing
On Mon, Nov 10, 2003 at 07:35:12PM +0100, Christian Perrier wrote: Package: prebaseconfig Severity: normal Well, this one is maybe more important than othersAt least, ALL users of d-i will see it So, please, native English speakers, check my suggestions... Detailed rationale: Template: prebaseconfig/reboot_in_progress Type: note -_Description: The machine will now reboot. - When you reboot the system, you'll need to make sure you are booting +_Description: System reboot + The system will now reboot. + . + Before this reboot occurs, you'll need to make sure you are booting from the right media. . - If you are booting from the local disk, make sure there are no + If you are booting from the local disk, check that there are no floppies in the floppy drives and no CD-ROM in the tray. If you made - a custom boot floppy and want to boot from that, you should put that - floppy in the first floppy drive. Finally, you can restart the - installation system by booting from your install media. + a custom boot floppy and want to boot from it, you should put that + floppy in the first floppy drive. + . + You may also restart the installation system by booting from your + installation media. . Please take care of all that before you continue. 1) Make this look more like a title 2) thus add The system will now reboot as a separated paragraph. system seems better than machine to me... 3) Before this reboot occurs is maybe not the best possible. English speakers needed..:-) 4) s/make sure/check that : look sbetter to me but your mileage may vary 5) boot from it or boot from that? 'it' is correct. Everything looks fine here. I add a paragraph as the suggestion for rebooting from the install(ation) media is another idea and should appear more easily, imho -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux mykerinos 2.4.22 #2 Mon Sep 29 15:12:10 CEST 2003 i686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (ignored: LC_ALL set to fr_FR.UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Debian GNU/Linux Operating System By the People, For the People Chris Tillman (a people instance) toff one at cox dot net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Installer: sr mod?
James Bromberger wrote: I just grabbed beta 1 (well done on the milestone); however, I cant see sr_mod in the initrd image on the 100 MB image: lib/modules/2.4.22-1-386/kernel/drivers/scsi# ls scsi_mod.o sd_mod.o While I can see usb-storage, I think I need sr_mod to be able to use the cdrom device (since I think it emulates scsi on top of a USB transport in the IBM bladecenter). The usb-storage module is also not auto-loading the usb-ohci or usb-ehci controller. Is there a danger in automatically loading the ehci-hcd module (which should cover USB2 and USB1), and then modprobe-ing usb-storage and sr_mod to find a device? The deal is that currently we don't support scsi cdrom drives without first loading the extra scsi_drivers floppy. That may eventually change. The usb-storage module should be loaded as of today when it finds usb. It sounds like it is also failing to find your usb bridge. Probably it doesn't know about the PCI id of the bridge, so if you have linux already running on this system and can send the output of lspci that would help. -- see shy jo signature.asc Description: Digital signature
Re: base-config integration, boot-time parameters, and d-i droppings
On Mon, Nov 10, 2003 at 10:08:43PM -0500, Joey Hess wrote: In my tests it looks like cdebconf writes the database quite frequently (suprisingly frequently, really), so getting the full db should not be a problem. To make cdebconf write the database, kill the frontend with SIGUSR1. main-menu does this between each package. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220182: netcfg: Please re-order the TCP/IP configuration questions
On Tue, Nov 11, 2003 at 09:44:48AM +0100, Christian Perrier wrote: Package: netcfg Severity: wishlist Tags: d-i The current order is not really natural : I suggest using the following order: -IP address -Netmask -Gateway -Machine name -Domain name -DNS servers ip address, netmask, gw and dns (perhaps even domain?) can be obtained via dhcp, if available, this leaves out only machine name thus: -IP address -Netmask [guessed from ip address] -Gateway [guessed from previous answers] -DNS servers -Machine name -Domain name sounds sensible to me regards, filippo -- Filippo Giunchedi GNU/PG key: 6B79D401 Random signature follows: I never forget a face, but in your case I'll be glad to make an exception. -- Groucho Marx pgp0.pgp Description: PGP signature
Re: Webpage fix
Steinar H. Gunderson wrote: Could somebody add the URL for the daily-built images (http://people.debian.org/~sjogren/d-i/images/daily/) back to the website? They seem to have been removed, and they are useful for people who want to test the d-i beta via netboot or floppy. People who want to test the *beta* that way should use the official images in the debian archive. I will clarify the web site. The ports-status page has links Martin's daily builds, but not for netboot on i386. (Alastair, could that be added?) I think the ports status page could be clearer and perhaps link to the base directory and not only to individual images. -- see shy jo signature.asc Description: Digital signature
Re: Second stage console problem
Petter Reinholdtsen wrote: Another idea was to always run base-config in an UTF-8 terminal, and always install an UTF-8 capable framebuffer terminal. This way, we use the same system for all languages, and it is less likely that the lesser used configurations contain errors. I'm personally leaning toward this myself. We can steal the already working framebuffer and bogl setup code from rootskel. It will be a rather rude awakening when the user gets out of base-config and into the plain old linux console though. :-/ -- see shy jo signature.asc Description: Digital signature
Bug#220230: Debian Installer II: sr_mod continued
Package: cdrom-detect Version: 0.38 (This is on a IBM bladecenter which has a USB cdrom drive.) James Bromberger wrote: I grabbed the 2.4.22-386 kernel and added a few of the modules for testing: ehci-usb seems to fail to laod (with no explanation in dmesg). ohci-usb works sr_mod works tg3 works (ethernet) And I can access the CD ROM. With it unmounted, the installer still fails to detect the cdrom drive; there is no /dev/cdrom symlink made when the sr_mod detects the /dev/scsi1/host0/bus0/target0/lun0/cd. Lets file a bug to that effect. It sounds to me like cdrom-detect should fall back to prompting with a list of all disks (or at least all scsi disks) in the system if it cannot find a /dev/cdroms/ device. BTW, sr_mod will be available on the CD's in a couple of days. The tg3 network interface I have is detected, but running udhcpc fails. The installer meanwhile has bombed out and also complains about a missing floppy still (these IBM blade machines have a USB floppy, not one that the floppy controller (floppy.o) seems to recognise). Setting the address manually seems to be OK. I'll bet you have a file in /dev for your USB floppy drive, if you have usb-storage loaded in addition to the modules listed above. Problem is the installer doesn't know it's a floppy drive as opposed to a scsi drive. It would know if you booted off the thing.. If there is a device entry for your USB floppy drive, I can make a similar change to have it prompt with a list of scsi devices if it cannot find an obvious floppy drive. -- see shy jo signature.asc Description: Digital signature
Re: Failed floppy installation
tis 2003-11-11 klockan 12.17 skrev guran: Jag har haft Debian på denna boxen tidigare utan problem. For those of you who don't speak Swedish: I've had Debian on this box before without problems. /Martin -- Martin Sjögren [EMAIL PROTECTED] -- [EMAIL PROTECTED] GPG key: http://www.mdstud.chalmers.se/~md9ms/gpg.html let hello = hello : hello in putStr (unlines hello) signature.asc Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel
Re: Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
On Tue, Nov 11, 2003 at 12:35:49PM -0500, Joe Nahmias wrote: Colin Watson wrote: On Tue, Nov 11, 2003 at 11:15:01AM +0100, Gaudenz Steinlin wrote: probably someone should reassign the pseudo-package installation-reports to debian-boot. If this is the general opinion of d-i folks, then ftpmaster are the people to ask. (I thought sending it to -testing was originally deliberate, though.) If installation-reports just contains feedback about d-i, I can't see why that should go to -testing and not -boot. Additionally, both the install and installation pseudo-packages point to -boot, why not this one? I don't really have much of a personal stake in it either way. Do I just file a bug against ftp.debian.org? Yes. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Priority handling in main-menu
Sebastian Ley wrote: in my opinion the priority handling on errors in main-menu needs still some work. Presently the logic is simple: Have an initial priority. If a menu item fails, lower the priority by one step. If a menu item suceeds, pump up the priority by one but not greater than the initial priority. However consider the following situation (as also percieved in an installation-report): Initial priority is high. A step fails and the priority gets lowered to medium, showing the menu. The user chooses that the failing step is not relevant or perhaps uses a shell to recover. He then selects the next entry. That entry suceeds again, so priority is set to high again. Which will bring him back to the step that actaully failed, too bad... I do not know if we should think of an entire different solution to handle that but for now we could add some code to main-menu that assures that the priority will not be set = high until the offending menu point actually suceeded. I would like to see main-menu be smarter about the default item it picks. If the user skips over an earlier item and manager to successfuly use a later item in the menu, then the earlier item is not necessary, and main-menu should avoid making it the default again. This does not apply if the later item has a menu-item-number in the 900's (shell, etc). -- see shy jo signature.asc Description: Digital signature
Bug#220180: cdrom-detect: Debconf templates polishing
OK, here are my edits:
Template: cdrom-detect/manual_config
+_Description: Manually select the CD-ROM module and device?
^^^ use 'a' instead of 'the'.
+ No common CD-ROM reader was detected.
+ .
+ Your CD-ROM reader may be an old Mitsumi or another non-IDE, non-SCSI
+ CD-ROM reader. In that case you may choose which module to load and
^^^ should
+ which device to use. If you don't know what module and device are
^ the which
+ needed, look for some documentation or try a network installation
^
(insert) performing
+ instead of a CD-ROM installation.
Template: cdrom-detect/is_cd_inserted
+_Description: Perform manual CD-ROM configuration?
+ Your installation CD-ROM couldn't be mounted.
+ .
+ That probably means that the CD-ROM is not yet inserted. If that's the case,
This ^^ has^ (insert) been ^^ is
+ just insert it and don't perform the manual configuration. The CD-ROM mount
+ will be re-tried.
+ .
+ If your CD-ROM was already in the drive, some other problem happened. You
^^^ is occured
+ should then try the manual CD-ROM configuration.
(delete)
Template: cdrom-detect/cdrom_module
+_Description: Module needed for accessing the CD-ROM:
+ The automatic detection didn't find any CD-ROM reader. You can try to
^^^ a ^^ drive
+ load a specific module if you have a specific CD-ROM reader (that is
unusual^^ drive
neither IDE nor SCSI).
Template: cdrom-detect/cdrom_device
+_Description: Device file for accessing the CD-ROM:
+ In order to get access to your CD-ROM reader, please enter which device file
^^^(delete)^^ the device file that ^
+ should be used. Non-standard CD-ROM readers use non-standard device
+ files (such as /dev/mcdx).
.
You may switch to the shell on the second terminal (ALT+F2) to check the
+ available devices in /dev with ls /dev. You can come back to this screen
^ return
+ with ALT+F1.
by pressing
Template: cdrom-detect/success
+_Description: CD-ROM detected
+ The CD-ROM autodetection was successful. A CD-ROM reader has been found. It
+ currently contains this CD: ${cdname}. The installation process may continue.
The CD-ROM autodetection was successful. A CD-ROM drive has been found
and it currently contains the CD '${cdname}'. The installation will now
continue.
Template: cdrom-detect/no-cd
+_Description: No CD detected
+ Please check that a CD has been inserted in the CD-ROM reader.
^^ into ^^ drive
Template: cdrom-detect/wrong-cd
+_Description: Non-Debian CD-ROM detected
+ A CDROM has been detected, but it isn't a Debian CD.
The CD-ROM drive contains a non-debian CD.
+ .
Please make sure that the correct CD is inserted.
Please insert a Debian CD to continue with the installation.
Template: cdrom-detect/skip_autodetection
+_Description: Skip CD-ROM automatic detection?
+ You should skip the CD-ROM automatic detection only if it is causing trouble.
If the CD-ROM automatic detection causes trouble, you may skip this step.
+ If you skip it, a manual intervention will be required to mount the
However, you will need to manually mount the
+ CD-ROM on /cdrom before you can proceed.
Template: mirror/distribution
+_Description: Distribution branch to install:
Debian distribution to install:
+ Please select which of the Debian distribution branches you want to install:
(delete) (delete) wish
.
+ - woody is the current stable release of Debian;
+ - sarge is the testing unreleased version of Debian;
+ - sid is unstable and will never be released.
These descriptions will need to be re-written for the release of sarge,
no? Also, shouldn't sarge be the first on the list? The list doesn't
have to (shouldn't) be in chronological order. How about this:
- sarge is the current stable distribution of Debian (3.X)
- sid is the unstable distribution and will never be released
- woody is the previous stable distribution of Debian (3.0)
Hope this helps!
Joe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
Colin Watson wrote: On Tue, Nov 11, 2003 at 11:15:01AM +0100, Gaudenz Steinlin wrote: Am Die, den 11.11.2003 schrieb Joe Nahmias um 09:16: [ I don't know why, but for some reason installation-reports go to ] [ debian-testing, so I'm forwarding this to debian-boot for discussion ] probably someone should reassign the pseudo-package installation-reports to debian-boot. If this is the general opinion of d-i folks, then ftpmaster are the people to ask. (I thought sending it to -testing was originally deliberate, though.) If installation-reports just contains feedback about d-i, I can't see why that should go to -testing and not -boot. Additionally, both the install and installation pseudo-packages point to -boot, why not this one? Do I just file a bug against ftp.debian.org? Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
Joe Nahmias wrote: 1) Install boots into the main menu. Interface looks alot snazzier than the old text interface, however the line-drawing characters are all messed up on my terminal (corners are displayed as '', c.) Known bug? We're missing bogl-bterm and a lot of other utf-8 and terminal stuff on the netboot initrd. I will add it. 2) Picking Choose language doesn't get very far. This is what I can piece together from syslog: DEBUG: Menu item 'languagechooser' selected DEBUG: configure languagechooser, status: 4 WARNING **: Configuring 'languagechooser' failed with error code 1 WARNING **: Menu item 'languagechooser' failed. Any ideas? Known unfiled bug? File a new bug against languagechooser? You should probably make sure that your boot loader passes DEBCONF_DEBUG=5 to the linux kernel at boot time. You may also want to pass DEBCONF_PRIORITY=high to use the standard priority level. The former would probably help track this down. 3) After doing 'Select a Keyboard Layout', I chose 'Detect network hardware'. This generated the following two (fatal looking) errors: a. An error occured while running 'modprobe -v floppy false`. b. An error occured while running 'modprobe -v ide-cd false`. Since this is a netboot install, these errors should not be fatal. The installer simply tries to detect all the hardware it can, if you were running at the standard debconf priority you would not even see these messages. It's not fatal at all. I'd not mind knowing why modprobe of these modules is failing in the first place. There should be no missing symbols. 4) When finally presented with a list of ethernet drivers to pick from, the requisite driver for this laptop -- b44 -- is missing. I tried switching to vc2 and doing 'modprobe -v b44', but this fails since the module doesn't exist on the image. How do we get it added? I'm getting the impression the b44 is a common module, that's two reports in as many days. I have added nic-extra-modules to the netboot image in CVS, so it will support a lot more hardware in the next build, including this one. -- see shy jo signature.asc Description: Digital signature
Re: My experience with d-i
Bill Allombert wrote: I have entered `net' at boot prompt. Why did you do that, instead of just hitting enter? It apparently booted you up in low priority mode, which explains most of the following: The `Choose language' do nothing, but if I run it, the `Detect network hardware' will prompt me whether it should try to detect hardware or not. If I do not run `Choose language', `Detect network hardware' directly process to detect hardware The probe find my hardware (floppy,windbond-840,ide-disk,ide-cd) but then ask me for options or a lot of module irrelevant to my system. It finish with `Something has gone wrong'. -- see shy jo signature.asc Description: Digital signature
new website for Discover hardware detection suite
Progeny URL: http://www.progeny.com/ is pleased to announce the launch of a new website for the Discover project URL: http://platform.progeny.com/discover/ . Discover is a set of libraries and utilities for gathering and reporting information about a system's hardware. Version 1.0 of Discover was released with Debian 3.0 (woody) to a very positive response, and was promptly adopted as the hardware-detection technology of choice by the Debian-Installer team, who are reimplementing Debian's installer technology in a highly modular and flexible fashion that will also be easier to maintain. We're delighted that Discover's mettle has been tested against competing technologies such as Kudzu, and found to be a better fit for Debian's needs. However, the impact of Discover 1.0 has been limited due to the narrow expressiveness of its data format, and the perennial problem of distribution of updates about known hardware. Discover 2.0, over a year in the making, addresses both of these problems. First, it uses an XML-based data format that's designed to permit a high degree of flexibility, and to leave open the possibility of associating hardware devices with any sort of software interface. Secondly, it utilizes the CURL library (which can be enabled - or not - at build time) for retrieval of data stores about hardware from anywhere on the Internet. Discover 2.0 can collate the data from multiple resources, whether stored on a local filesystem or on the network, and will use the most up-to-date information it can find. Ian Murdock, founder of Debian and chief strategist for Progeny, likens the Discover 2.0 method of operation to one of Debian's most impressive technologies: Discover is APT for hardware information. Now that Discover 2.0 is stabilizing, Progeny is looking to the free software and open source communities to set the goals for Discover 2.1, 3.0, and beyond. To that end, we have redesigned Discover's website and made available a snapshot of our CVS developments. These are just baby steps, however, toward the big change: In the coming weeks, we anticipate making the development process of Discover (and other enabling technology initiatives) completely public by means of a web-based Subversion repository. We understand how difficult it is to contribute to a project in which the interesting stuff happens behind a curtain, so we're excited to pull back that curtain, reveal the workbench, and let the community see how we really work on Discover (mistakes and all!). Discover was developed primarily by Branden Robinson, Eric Gillespie, Josh Bressers, and John Daily of Progeny, with assistance from a cast of dozens. If Discover excites you as well, we cordially invite you to participate in Progeny's open development initiative. -- Branden Robinson | GPG signed/encrypted mail welcome [EMAIL PROTECTED] | 1024D/9C0BCBFB Progeny Linux Systems | D5F6 D4C9 E25B 3D37 068C | 72E8 0F42 191A 9C0B CBFB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: My experience with d-i
On Tue, Nov 11, 2003 at 12:47:12PM -0500, Joey Hess wrote: Bill Allombert wrote: I have entered `net' at boot prompt. Why did you do that, instead of just hitting enter? It apparently booted you up in low priority mode, which explains most of the following: The help screen [F3] says that 'net' is good for a network install, and I wanted to test network install. Sorry if it was supposed not to work, I was not aware of the fact. As for the normal boot: Initial boot worked:[X] Configure network HW: [X] Config network: [ ] I have no DHCP server Detect CD: [ ] Load installer modules: [X] Detect hard drives: [X] When I try 'Detect CD' it run 'Config network via DHCP' instead and lock for two minutes. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Slow redraws in the debootstrap stage
Denis Barbier wrote: Could someone please test the attached patch? I cannot test it myself at the moment, but I believe that it eliminates those flashing boxes. It seems rather broken. When the hw-detect progress bar was displayed, it cleared the screen to blue each time the bar was updated. Then it displayed the inside of the dialg box, but not the border. This was very slow and very obvious on vmware. -- see shy jo signature.asc Description: Digital signature
Bug#220135: netcfg fails with two via-rhine cards and dhcp server on eth1
I just tried the new beta ISO images and the problem still occurs. The appropriate ethernet module gets loaded (via-rhine) but Configure the network using dhcp fails. Looking in syslog I see Nov 11 03:10:37 (none) user.debug main-menu[142]: DEBUG: Menu item 'netcfg-dhcp' selected Nov 11 03:10:37 (none) user.debug main-menu[142]: DEBUG: configure netcfg-dhcp, status: 2 Nov 11 03:10:37 (none) user.debug main-menu[142]: DEBUG: configure libc6, status: 0 Nov 11 03:10:37 (none) user.debug main-menu[142]: DEBUG: configure libdebconfclient0, status: 0 Nov 11 03:10:37 (none) user.debug main-menu[142]: DEBUG: virtual package libdebconfclient0 Nov 11 03:10:37 (none) user.info main-menu[142]: INFO: Falling back to the package description for libdebconfclient0-udeb Nov 11 03:10:37 (none) user.info main-menu[142]: INFO: Falling back to the package description for libdebconfclient0-udeb Nov 11 03:10:37 (none) user.debug main-menu[142]: DEBUG: configure libdebconfclient0-udeb, status: 2 Nov 11 03:10:37 (none) user.warn main-menu[142]: WARNING **: Unable to set title for libdebconfclient0-udeb. Nov 11 03:10:37 (none) user.debug main-menu[142]: DEBUG: configure libdebian-installer4, status: 0 Nov 11 03:10:37 (none) user.debug main-menu[142]: DEBUG: configure dhcp-client-udeb, status: 2 Nov 11 03:10:37 (none) user.debug main-menu[142]: DEBUG: configure libc6, status: 0 Nov 11 03:10:37 (none) user.warn main-menu[142]: WARNING **: Unable to set title for dhcp-client-udeb. Nov 11 03:10:41 (none) user.warn main-menu[142]: WARNING **: Configuring 'netcfg-dhcp' failed with error code 1 Nov 11 03:10:41 (none) user.info main-menu[142]: INFO: Priority changed externally, setting main-menu default to 'medium' Nov 11 03:10:41 (none) user.warn main-menu[142]: WARNING **: Menu item 'netcfg-dhcp' failed. -- Philip Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219928: debian-installer: build failures on sparc
Goswin von Brederlow wrote: Then how do you know it is a bug in mklibs and it is not actually a missing symbol? Which was the real reason it failed in every testcase I got my hand on so far. All of those suposedly mklibs weak symbols bugs disapeared when recompiling the faulty binaries against the proper versions of libraries so far. If I read between the lines right, this time it was breakage in brltty on sparc, and I've removed it from the pkg-lists for sparc now. -- see shy jo signature.asc Description: Digital signature
Re: Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
Gaudenz Steinlin wrote: Am Die, den 11.11.2003 schrieb Joe Nahmias um 09:16: Alright, here are the highlights of how this install went: 0) OK, after much struggling (and dealing with my nemesis error message 'VFS: Cannot open root device or 3a:04') I managed to get the d-i netboot image to work via PXE. For posterity (and the installation guide) the magic kernel options I needed to make this work are ramdisk_size=8192 root=/dev/ram0. If anyone would like assistance setting up a PXE testbed or copies of various configs I use please don't hesitate to ask. It would be nice, if you could write a short addition to the INSTALLATION-HOWTO about your way to install d-i via PXE boot. There is already a very short section on netbooting the installer. If you send a patch to debian-boot, I will look at it and commit it to CVS. This was already requested (hi tbm!) and sent to the BTS and the debian-testing list (where the request originated). I titled the message How to create a PXE d-i netboot testbed in 10 easy steps (MSG-ID: [EMAIL PROTECTED]). Please look at it in one of these places. 1) Install boots into the main menu. Interface looks alot snazzier than the old text interface, however the line-drawing characters are all messed up on my terminal (corners are displayed as '', c.) Known bug? not know bug, please file one. Sorry I don't know which package to blame for that. Any takers on where I should file the bug? slang? btw the installation should not boot into main-menu but directly go into languagechooser. That probably happened b/c of the next problem :) 2) Picking Choose language doesn't get very far. This is what I can piece together from syslog: DEBUG: Menu item 'languagechooser' selected DEBUG: configure languagechooser, status: 4 WARNING **: Configuring 'languagechooser' failed with error code 1 WARNING **: Menu item 'languagechooser' failed. Any ideas? Known unfiled bug? File a new bug against languagechooser? bug not know. You should have languagechooser 1.03 on your image, which is the same as on the beta1 which works for most people. Please file a bug. Yes, the image contains version 1.03. I will file a bug. 3) After doing 'Select a Keyboard Layout', I chose 'Detect network hardware'. This generated the following two (fatal looking) errors: a. An error occured while running 'modprobe -v floppy false`. b. An error occured while running 'modprobe -v ide-cd false`. Since this is a netboot install, these errors should not be fatal. please file a bug on hw-detect (or ethdetect?). It's strange that these are tried for network hardware detection. Probably the installer tries to load additional modules from a floppy? I really don't know why it's happening. I will file a bug on hw-detect. 4) When finally presented with a list of ethernet drivers to pick from, the requisite driver for this laptop -- b44 -- is missing. I tried switching to vc2 and doing 'modprobe -v b44', but this fails since the module doesn't exist on the image. How do we get it added? known bug. As of linux-kernel-di 0.12 this driver is in nic-extra-modules. This means you have to load it from an additional floppy. If this is a common NIC then we could add it to nic-modules, which is on the netboot initrd. I believe it is a common NIC and it is used on all of the newer Dell Laptops. For the netboot images, why don't we include nic-extra-modules?? Wouldn't this make sense to do since we know that a network install is being attempted? It's not like we're trying to cram stuff onto a floppy here, so why not put all the network modules we have into this image? PS - This particular laptop doesn't have a serial port, so all output/error messages are hand-typed and subject to typos, c. You could try to save /var/log/messages and /var/log/syslog to an already formatted partition. Unfortunately, I don't have a partition available that I can write to from linux, and fdisk isn't available yet to create one. Thanks for the help! Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: My experience with d-i
Bill Allombert wrote: The help screen [F3] says that 'net' is good for a network install, and I wanted to test network install. IIRC, The help screens are from the boot-floppies and basically useless. Sorry if it was supposed not to work, I was not aware of the fact. As for the normal boot: Initial boot worked:[X] Configure network HW: [X] Config network: [ ] I have no DHCP server Detect CD: [ ] Load installer modules: [X] Detect hard drives: [X] When I try 'Detect CD' it run 'Config network via DHCP' instead and lock for two minutes. Doesn't make sense to me, there is no dependency there. -- see shy jo signature.asc Description: Digital signature
languagechooser_1.04_i386.changes ACCEPTED
Accepted: languagechooser_1.04.dsc to pool/main/l/languagechooser/languagechooser_1.04.dsc languagechooser_1.04.tar.gz to pool/main/l/languagechooser/languagechooser_1.04.tar.gz languagechooser_1.04_all.udeb to pool/main/l/languagechooser/languagechooser_1.04_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219928: debian-installer: build failures on sparc
Joey Hess [EMAIL PROTECTED] writes: Goswin von Brederlow wrote: Then how do you know it is a bug in mklibs and it is not actually a missing symbol? Which was the real reason it failed in every testcase I got my hand on so far. All of those suposedly mklibs weak symbols bugs disapeared when recompiling the faulty binaries against the proper versions of libraries so far. If I read between the lines right, this time it was breakage in brltty on sparc, and I've removed it from the pkg-lists for sparc now. Is any arch still using brltty? Do we care about it? Does brltty break on i386, m68k or alpha too? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: My experience with d-i
Am Di, den 11.11.2003 schrieb Joey Hess um 20:17: As for the normal boot: Initial boot worked:[X] Configure network HW: [X] Config network: [ ] I have no DHCP server Detect CD: [ ] Load installer modules: [X] Detect hard drives: [X] When I try 'Detect CD' it run 'Config network via DHCP' instead and lock for two minutes. Doesn't make sense to me, there is no dependency there. I know it, I know it ;-) Took me a good deal of thinking what this is: - DHCP fails - prio set to medium - user selects Detect CD, which works instantly and without feedback - prio is set to high again - DHCP has not yet been configured and hence runs again For the user it looks like that cdrom-detect has not run but netcfg-dhcp ran again. Sebastian -- PGP-Key: http://www.mmweg.rwth-aachen.de/~sebastian.ley/public.key Fingerprint: A46A 753F AEDC 2C01 BE6E F6DB 97E0 3309 9FD6 E3E6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge-install onto Thinkpad
I would certainly be interested in discussing XFS support for d-i with anyone willing to help work on it. I might be persuaded to put together maintained kernel images using the XFS patch, if there was enough overall interest to support a full d-i build and make the effort worthwhile. Someone just asked me for an install CD that did XFS. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
Am Die, den 11.11.2003 schrieb Joe Nahmias um 19:00: Gaudenz Steinlin wrote: Am Die, den 11.11.2003 schrieb Joe Nahmias um 09:16: It would be nice, if you could write a short addition to the INSTALLATION-HOWTO about your way to install d-i via PXE boot. There is already a very short section on netbooting the installer. If you send a patch to debian-boot, I will look at it and commit it to CVS. This was already requested (hi tbm!) and sent to the BTS and the debian-testing list (where the request originated). I titled the message How to create a PXE d-i netboot testbed in 10 easy steps (MSG-ID: [EMAIL PROTECTED]). Please look at it in one of these places. I added a pointer to your explanation to the INSTALLATION-HOWTO. Although it would be nice, to have it directly in the INSTALLATION-HOWTO. But in the current form I cannot copy it directly, because it does not fit the style and formatting of the rest of the HOWTO. Unfortunately I don't have the time to edit it right now. Gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Usage of isolinux on the beta CDs
Sebastian Ley wrote: it seems that we are locking out people from testing by using isolinux on our netinst/businesscard CDs, see #220139 and #220139. Since we do not need any of isolinux's features I propose to use syslinux on the CDs. I think I agree. The only thing isolinux has the potential to buy us at the moment is a large enough boot initrd to support SCSI cdroms without using a driver floppy, and SCSI cdroms are rare, and we are not even currently using that potential. We also have space to include 5 or 10 of the most common SCSI controllers on the current initrd if we really want to (519k free). Maybe we could put isolinux on the *second* CD, with eventually an initrd that supports SCSI cdroms. -- see shy jo signature.asc Description: Digital signature
Re: Slow redraws in the debootstrap stage
On Tue, Nov 11, 2003 at 01:41:02PM -0500, Joey Hess wrote:
Denis Barbier wrote:
Could someone please test the attached patch?
I cannot test it myself at the moment, but I believe that it eliminates
those flashing boxes.
It seems rather broken. When the hw-detect progress bar was displayed,
it cleared the screen to blue each time the bar was updated. Then it
displayed the inside of the dialg box, but not the border. This was very
slow and very obvious on vmware.
Here is another patch. I managed to get hw-detect to work directly under
cdebconf and so could test it, but I prefer anyway to have it reviewed.
As the previous one, it only addresses the flashing boxes problem, I
still do not know what to do with resized boxes.
Denis
Index: src/modules/frontend/newt/newt.c
===
RCS file:
/cvs/debian-boot/debian-installer/tools/cdebconf/src/modules/frontend/newt/newt.c,v
retrieving revision 1.40
diff -u -r1.40 newt.c
--- src/modules/frontend/newt/newt.c8 Nov 2003 22:39:41 - 1.40
+++ src/modules/frontend/newt/newt.c11 Nov 2003 20:56:29 -
@@ -901,17 +901,19 @@
obj-interactive = 1;
obj-data = calloc(1, sizeof(struct newt_data));
newtInit();
+newtCls();
newtGetScreenSize(width, height);
// Fill the screen so people can shift-pgup properly
for (i = 0; i height; i++)
putchar('\n');
-newtFinished();
+newtRefresh();
return DC_OK;
}
static int
newt_shutdown(struct frontend *obj)
{
+newtFinished();
return DC_OK;
}
@@ -926,36 +928,25 @@
static int
newt_go(struct frontend *obj)
{
-struct newt_data *data = (struct newt_data *)obj-data;
struct question *q = obj-questions;
-int i, ret = DC_OK, cleared;
+int i, ret = DC_OK;
-cleared = 0;
while (q != NULL) {
for (i = 0; i DIM(question_handlers); i++) {
if (strcmp(q-template-type, question_handlers[i].type) == 0) {
-if (!cleared !data-scale_form) {
-cleared = 1;
-newtInit();
-newtCls();
-}
ret = question_handlers[i].handler(obj, q);
if (ret == DC_OK)
obj-qdb-methods.set(obj-qdb, q);
else if (ret == DC_GOBACK q-prev != NULL)
q = q-prev;
-else {
-newtFinished();
+else
return ret;
-}
break;
}
}
if (ret == DC_OK)
q = q-next;
}
-if (cleared !data-scale_form)
-newtFinished();
return DC_OK;
}
@@ -981,8 +972,6 @@
obj-progress_min = min;
obj-progress_max = max;
obj-progress_cur = min;
-newtInit();
-newtCls();
newtGetScreenSize(width, NULL);
win_width = width-7;
newtCenteredWindow(win_width, 5, title);
@@ -1070,7 +1059,6 @@
if (data-scale_form != NULL) {
newtFormDestroy(data-scale_form);
newtPopWindow();
-newtFinished();
data-scale_form = data-scale_bar = data-perc_label = data-scale_textbox =
NULL;
}
}
Bug#220265: Merge duplicates
reassign 220265 cdebconf severity 220265 minor tag 220265 + pending merge 218844 220265 thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Issue mounting partitions
Hello, I'm a Debian newbie, so my issue may be trivial... I'm trying to install the testing version by making a net install with http://gluck.debian.org/cdimage/testing/netinst/i386/sarge-i386-netinst.iso (Nov 9, 2003). Booting starts fine, but I can't find any place to bind mount points to my partitions. Here's what I did: 1. Selected the hard drive to partition: see http://michaelo.free.fr/issues/nov11_2003/1.jpg 2. My existing partitions were recognized with no issue, but I didn't find any way to attach a label/mount point to any of them! See http://michaelo.free.fr/issues/nov11_2003/2.jpg 3. I selected Quit (because I didn't have to make any change) and selected Finish in the next dialog. See http://michaelo.free.fr/issues/nov11_2003/3.jpg 4. The installer complains that no partitions were found: http://michaelo.free.fr/issues/nov11_2003/4.jpg 5. In the main menu, if I chose Configure and mount partitions, nothing happens... I'm still in the main menu: http://michaelo.free.fr/issues/nov11_2003/5.jpg Did I miss anything, or could there be an issue in this testing version of the installer? Thank you in advance for any help. Don't hesitate to ask me more questions. Cheers, Michael. -- Michael Opdenacker [EMAIL PROTECTED], http://michaelo.free.fr Computers are like air conditioners They stop working properly when you open Windows GnuPG Key fingerprint: 978E 71D7 3172 7E9D EB01 BB89 F0E0 0860 003E D701 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Merge duplicates
Processing commands for [EMAIL PROTECTED]: reassign 220265 cdebconf Bug#220265: cdebconf-newt-udeb: buttons have wrong tab ordering Bug reassigned from package `cdebconf-newt-udeb' to `cdebconf'. severity 220265 minor Bug#220265: cdebconf-newt-udeb: buttons have wrong tab ordering Severity set to `minor'. tag 220265 + pending Bug#220265: cdebconf-newt-udeb: buttons have wrong tab ordering Tags were: d-i Tags added: pending merge 218844 220265 Bug#218844: newt frontend button selection glitch Bug#220265: cdebconf-newt-udeb: buttons have wrong tab ordering Merged 218844 220265. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-kernel-di_0.13_source+i386+alpha+m68k.changes REJECTED
Rejected: Unknown distribution `UNRELEASED'. === If you don't understand why your files were rejected, or if the override file requires editing, reply to this email. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220282: partconf: should apt-install userspace tools for created filesystems
Package: partconf Severity: important Tags: d-i Partconf should make sure that appropriate userspace tools for created filesystem are installed to /target. Especially fsck.$FILESYSTEM is needed. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux coyote 2.4.22-1-k7 #5 Sat Oct 4 14:11:12 EST 2003 i686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219765: Languagechooser 1.03 dies on mipsel
Karsten Merker wrote: On Mon, Nov 10, 2003 at 07:02:30PM -0800, Matt Kraai wrote: On Mon, Nov 10, 2003 at 10:26:20PM +0100, Karsten Merker wrote: On Sat, Nov 08, 2003 at 09:38:09PM +, Alastair McKinstry wrote: if echo $LANG $LC_CTYPE | grep -q UTF-8 ; then db_set debconf/language en else db_set debconf/language C fi Hi, The code actually goes: echo $LANG $LC_CTYPE | grep -q UTF-8 if [ $? ] ; then ... That was the original case, which also did not work. The code I cited above is the current state in cvs. if this fails, try the variant if `echo $LANG $LC_CTYPE | grep -q UTF-8 ` ; then What are the backticks for? They have no real function, in fact they are logically wrong here, but they cause the shell to take an additional redirection which does not trigger the shell crash that happens without them. This contruction works only by accident because grep is called with the -q option, so that the backticks end up in delivering an empty string. Nonetheless the grep gets evaluated and the if executes the following code based on the returncode of the grep. In the meantime I have tried making this a legal contruct that also does not trigger the crash. If one executes the echo $LANG $LC_CTYPE | grep -q UTF-8 in a subshell, it also does not crash, so the proper solution would probably be to write if (echo $LANG $LC_CTYPE | grep -q UTF-8 ) ; then This works for me without crashing, and as the return code is passed back from the subshell, the code does what it is supposed to do, i.e. set debconf/language to en in case of an UTF-8 locale and to C otherwise. If nobody objects, I will check this into the CVS. We still have to look into the other problem I have mentioned (d-i hanging after selecting another language than US-English), though. Thanks for the explanation. Would you please file a bug against the shell and add a comment referencing it and indicating that the workaround should be removed once the bug is fixed? -- Matt - This message was sent using the LA Free-Net - LA's best kept secret. http://www.lafn.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Slow redraws in the debootstrap stage
Denis Barbier wrote: On Tue, Nov 11, 2003 at 01:41:02PM -0500, Joey Hess wrote: Denis Barbier wrote: Could someone please test the attached patch? I cannot test it myself at the moment, but I believe that it eliminates those flashing boxes. It seems rather broken. When the hw-detect progress bar was displayed, it cleared the screen to blue each time the bar was updated. Then it displayed the inside of the dialg box, but not the border. This was very slow and very obvious on vmware. Here is another patch. I managed to get hw-detect to work directly under cdebconf and so could test it, but I prefer anyway to have it reviewed. As the previous one, it only addresses the flashing boxes problem, I still do not know what to do with resized boxes. I've sponsored an NMU of debootstrap by Steinar that should make the resizing much less frequent. -- Matt - This message was sent using the LA Free-Net - LA's best kept secret. http://www.lafn.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
arcboot-installer_0.005_mips.changes REJECTED
Rejected: no signature found in arcboot-installer_0.005_mips.changes. Rejected: no signature found in arcboot-installer_0.005.dsc. === If you don't understand why your files were rejected, or if the override file requires editing, reply to this email. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Slow redraws in the debootstrap stage
On Tue, Nov 11, 2003 at 09:38:14PM +, [EMAIL PROTECTED] wrote: Denis Barbier wrote: [...] I still do not know what to do with resized boxes. I've sponsored an NMU of debootstrap by Steinar that should make the resizing much less frequent. Thanks, this is certainly the best solution. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
FWD: Re: Bug#215469: don't include unnecessary udebs on the cd
I'll bet Goswin has a pretty good handle on this. - Forwarded message from Raphael Hertzog [EMAIL PROTECTED] - From: Raphael Hertzog [EMAIL PROTECTED] Date: Tue, 11 Nov 2003 22:06:53 +0100 To: Joey Hess [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#215469: don't include unnecessary udebs on the cd X-Spam-Status: No, hits=-4.9 required=10.0 tests=BAYES_00 autolearn=ham version=2.60 Le Sun, Oct 12, 2003 at 07:48:01PM -0400, Joey Hess écrivait: Etc. I'm sure you could save a *lot* of space by working with the d-i team to whittle down the udebs on the cd images to a set that is appropriate for the purpose of the CD. As it is these images are getting too big to be useful. Agreed, can the d-i team provide us a list of udeb to include (in the same way that you intend to provide us boot images) ? Or can someone of you manage such a list in debian-cd's CVS ? I think we should have several list for each use : - normal CD set - netinst CD - business card CD (maybe the same as netinst CD) Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org - End forwarded message - -- see shy jo signature.asc Description: Digital signature
Re: Slow redraws in the debootstrap stage
Denis Barbier wrote: Here is another patch. I managed to get hw-detect to work directly under cdebconf and so could test it, but I prefer anyway to have it reviewed. As the previous one, it only addresses the flashing boxes problem, I still do not know what to do with resized boxes. Oh hmm, I am not really sure what flashing boxes problem that is, I thought this was to fix the resizing progress bar problem. Someone else who knows the problem ought to test it. -- see shy jo signature.asc Description: Digital signature
Re: My experience with d-i
Sebastian Ley wrote: Am Di, den 11.11.2003 schrieb Joey Hess um 20:17: As for the normal boot: Initial boot worked:[X] Configure network HW: [X] Config network: [ ] I have no DHCP server Detect CD: [ ] Load installer modules: [X] Detect hard drives: [X] When I try 'Detect CD' it run 'Config network via DHCP' instead and lock for two minutes. Doesn't make sense to me, there is no dependency there. I know it, I know it ;-) Took me a good deal of thinking what this is: - DHCP fails - prio set to medium - user selects Detect CD, which works instantly and without feedback - prio is set to high again - DHCP has not yet been configured and hence runs again For the user it looks like that cdrom-detect has not run but netcfg-dhcp ran again. Ah, in other words, this is another one that could be fixed by making main-menu smart enough to skip over steps that the user explicitly skipped over. -- see shy jo signature.asc Description: Digital signature
Re: Issue mounting partitions
Michael Opdenacker wrote: I'm trying to install the testing version by making a net install with http://gluck.debian.org/cdimage/testing/netinst/i386/sarge-i386-netinst.iso (Nov 9, 2003). Booting starts fine, but I can't find any place to bind mount points to my partitions. Here's what I did: 1. Selected the hard drive to partition: see http://michaelo.free.fr/issues/nov11_2003/1.jpg 2. My existing partitions were recognized with no issue, but I didn't find any way to attach a label/mount point to any of them! See http://michaelo.free.fr/issues/nov11_2003/2.jpg 3. I selected Quit (because I didn't have to make any change) and selected Finish in the next dialog. See http://michaelo.free.fr/issues/nov11_2003/3.jpg 4. The installer complains that no partitions were found: http://michaelo.free.fr/issues/nov11_2003/4.jpg Thanks for going to the trouble to take photos of it and put them up on the web. It seems to me that the part of the installer known as partconf is not seeing your partitions, while an earlier part is. Since these parts use different underlying technologies, this is at least possible, though it's not a common problem. I think you need to get a dump of your partition table in the appropriate form and submit it as a bug against the partconf package. Not knowing much about partitions myself I'll leave the details to someone else. -- see shy jo signature.asc Description: Digital signature
Bug#220230: Debian Installer II: sr_mod continued
James Bromberger wrote: So its not looking for /dev/cdrom as the device, but for the (devfs style name) /dev/cdroms/0? That's right. I see that the /dev dump you attached does include a /dev/cdroms/cdrom0. If the cdrom detect step is still failing it's because of some other problem. Seems to me that since this is a USB cdrom, it all comes back to the installer not knowing to load usb-ohci for your usb controller, and not loading usb-storage. I expect the cd detect step should work once the appropriate usb modules are loaded. BTW, sr_mod will be available on the CD's in a couple of days. The tg3 network interface I have is detected, but running udhcpc fails. Can I ask for tg3 NIC driver as well? (These machines have dual tg3 gigabit NICs in them) The tg3 module is on the CD, but not on the initrd. The installer needs to find the cdrom or a floppy before that module will be available. However, without lspci available, I can't see whats on the system. I get the glibc error message as shown when I try and use a current unstable binary for it. How canI get around this? What is the exact version of glibc I need to use here? Do I need to use a uDeb from somewhere? The contents of /proc/pci are just as good for the purpose of trying to figure out what the PCI ID of your usb controller is. Bus 0, device 15, function 2: USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 5). IRQ 7. Master Capable. Latency=64. Max Lat=80. Non-prefetchable 32 bit memory at 0xfebfe000 [0xfebfefff]. Here we go! Please send the contents of /proc/bus/pci/devices from this system. -- see shy jo signature.asc Description: Digital signature
Bug#219765: Languagechooser 1.03 dies on mipsel
On Tue, Nov 11, 2003 at 10:25:31PM +0100, Karsten Merker wrote: They have no real function, in fact they are logically wrong here, but they cause the shell to take an additional redirection which does not trigger the shell crash that happens without them. It's not a crash or a segfault or anything like that; the shell is 'set -e' and therefore exits at the first command which returns a non-zero exit status. The old code was certainly wrong, but the new code ought to work, as the shell is not supposed to exit under -e when the command returning non-zero is guarded by an 'if'. It would seem that the shell doesn't handle pipelines in if statements properly under -e. Pending a fix to the shell, I would suggest surrounding the 'if' block with 'set +e' and 'set -e', which ought to fix the problem but makes it more obvious that it's there exactly and only to work around a shell bug. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-kernel-di_0.13_source+i386+alpha+m68k.changes ACCEPTED
Accepted: brltty-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/brltty-modules-2.4.22-1-386-di_0.13_i386.udeb brltty-modules-2.4.22-1-generic-di_0.13_alpha.udeb to pool/main/l/linux-kernel-di/brltty-modules-2.4.22-1-generic-di_0.13_alpha.udeb cdrom-core-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/cdrom-core-modules-2.4.22-1-386-di_0.13_i386.udeb cdrom-core-modules-2.4.22-1-generic-di_0.13_alpha.udeb to pool/main/l/linux-kernel-di/cdrom-core-modules-2.4.22-1-generic-di_0.13_alpha.udeb cdrom-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/cdrom-modules-2.4.22-1-386-di_0.13_i386.udeb cdrom-modules-2.4.22-1-generic-di_0.13_alpha.udeb to pool/main/l/linux-kernel-di/cdrom-modules-2.4.22-1-generic-di_0.13_alpha.udeb ext3-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/ext3-modules-2.4.22-1-386-di_0.13_i386.udeb ext3-modules-2.4.22-1-generic-di_0.13_alpha.udeb to pool/main/l/linux-kernel-di/ext3-modules-2.4.22-1-generic-di_0.13_alpha.udeb fat-modules-2.4.20-amiga-di_0.13_m68k.udeb to pool/main/l/linux-kernel-di/fat-modules-2.4.20-amiga-di_0.13_m68k.udeb fat-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/fat-modules-2.4.22-1-386-di_0.13_i386.udeb fb-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/fb-modules-2.4.22-1-386-di_0.13_i386.udeb fb-modules-2.4.22-1-generic-di_0.13_alpha.udeb to pool/main/l/linux-kernel-di/fb-modules-2.4.22-1-generic-di_0.13_alpha.udeb firewire-core-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/firewire-core-modules-2.4.22-1-386-di_0.13_i386.udeb floppy-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/floppy-modules-2.4.22-1-386-di_0.13_i386.udeb ide-core-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/ide-core-modules-2.4.22-1-386-di_0.13_i386.udeb ide-core-modules-2.4.22-1-generic-di_0.13_alpha.udeb to pool/main/l/linux-kernel-di/ide-core-modules-2.4.22-1-generic-di_0.13_alpha.udeb ide-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/ide-modules-2.4.22-1-386-di_0.13_i386.udeb ide-modules-2.4.22-1-generic-di_0.13_alpha.udeb to pool/main/l/linux-kernel-di/ide-modules-2.4.22-1-generic-di_0.13_alpha.udeb input-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/input-modules-2.4.22-1-386-di_0.13_i386.udeb ipv6-modules-2.4.20-amiga-di_0.13_m68k.udeb to pool/main/l/linux-kernel-di/ipv6-modules-2.4.20-amiga-di_0.13_m68k.udeb ipv6-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/ipv6-modules-2.4.22-1-386-di_0.13_i386.udeb ipv6-modules-2.4.22-1-generic-di_0.13_alpha.udeb to pool/main/l/linux-kernel-di/ipv6-modules-2.4.22-1-generic-di_0.13_alpha.udeb irda-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/irda-modules-2.4.22-1-386-di_0.13_i386.udeb isa-pnp-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/isa-pnp-modules-2.4.22-1-386-di_0.13_i386.udeb isa-pnp-modules-2.4.22-1-generic-di_0.13_alpha.udeb to pool/main/l/linux-kernel-di/isa-pnp-modules-2.4.22-1-generic-di_0.13_alpha.udeb kernel-image-2.4.20-amiga-di_0.13_m68k.udeb to pool/main/l/linux-kernel-di/kernel-image-2.4.20-amiga-di_0.13_m68k.udeb kernel-image-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/kernel-image-2.4.22-1-386-di_0.13_i386.udeb kernel-image-2.4.22-1-generic-di_0.13_alpha.udeb to pool/main/l/linux-kernel-di/kernel-image-2.4.22-1-generic-di_0.13_alpha.udeb linux-kernel-di_0.13.dsc to pool/main/l/linux-kernel-di/linux-kernel-di_0.13.dsc linux-kernel-di_0.13.tar.gz to pool/main/l/linux-kernel-di/linux-kernel-di_0.13.tar.gz loop-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/loop-modules-2.4.22-1-386-di_0.13_i386.udeb md-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/md-modules-2.4.22-1-386-di_0.13_i386.udeb md-modules-2.4.22-1-generic-di_0.13_alpha.udeb to pool/main/l/linux-kernel-di/md-modules-2.4.22-1-generic-di_0.13_alpha.udeb nic-extra-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/nic-extra-modules-2.4.22-1-386-di_0.13_i386.udeb nic-extra-modules-2.4.22-1-generic-di_0.13_alpha.udeb to pool/main/l/linux-kernel-di/nic-extra-modules-2.4.22-1-generic-di_0.13_alpha.udeb nic-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/nic-modules-2.4.22-1-386-di_0.13_i386.udeb nic-modules-2.4.22-1-generic-di_0.13_alpha.udeb to pool/main/l/linux-kernel-di/nic-modules-2.4.22-1-generic-di_0.13_alpha.udeb nic-pcmcia-modules-2.4.22-1-386-di_0.13_i386.udeb to pool/main/l/linux-kernel-di/nic-pcmcia-modules-2.4.22-1-386-di_0.13_i386.udeb nic-shared-modules-2.4.20-amiga-di_0.13_m68k.udeb to pool/main/l/linux-kernel-di/nic-shared-modules-2.4.20-amiga-di_0.13_m68k.udeb nic-shared-modules-2.4.22-1-386-di_0.13_i386.udeb to
Re: My experience with d-i
On Tue, Nov 11, 2003 at 02:17:07PM -0500, Joey Hess wrote: Bill Allombert wrote: The help screen [F3] says that 'net' is good for a network install, and I wanted to test network install. IIRC, The help screens are from the boot-floppies and basically useless. I suppose it is a bug worth reporting. When I try 'Detect CD' it run 'Config network via DHCP' instead and lock for two minutes. Doesn't make sense to me, there is no dependency there. Sebastian explanation of the problem seems correct. I suppose d-i should not retry a filed operation by itself, especially one that is not mandatory. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220306: cannot find usb floppy drives, etc
Package: bugreporter-udeb Severity: normal This package uses /dev/floppy/0, so there is no way it can work with USB floppy drives or other strange stuff. There is some more robust code for picking a floppy device in floppy-retreiver. It could be factored out into a separate program, or just copied. I think this package could also offer to drop its bug report files on other disks, besides just a floppy. -- see shy jo signature.asc Description: Digital signature
Re: Bug#220135: netcfg fails with two via-rhine cards and dhcp server on eth1
On Tue, 11 Nov 2003, Philip Martin wrote: I just tried the new beta ISO images and the problem still occurs. The appropriate ethernet module gets loaded (via-rhine) but Configure the network using dhcp fails. Looking in syslog I see Have the same problem, as a work around used tty2 shell to configure network manually. (the lack of ping was disappointing) e it work. running dhclient eth0 manually resulted in an error message something like Socket type is not supported //will bring (full accurate) error quote as soon as i will be able to regards Boris Ratner. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 220281 to partconf
Processing commands for [EMAIL PROTECTED]: reassign 220281 partconf Bug#220281: Installer Configure and Mount Partitions bug with 10 or more partitions Warning: Unknown package 'installer' Warning: Unknown package 'sarge-i386-netinst.iso' Bug reassigned from package `installer (sarge-i386-netinst.iso)' to `partconf'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#192305: q to end, b for begin ambiguous
tag 192305 pending thanks On Wed, May 07, 2003 at 10:05:42AM -0500, Drew Scott Daniels wrote: Package: cdebconf Severity: minor This could almost be a wishlist item, re-prioritize if desired. I hope you don't feel this is too much of a nitpicking issue. q to end, b for begin I feel is ambiguous and may mislead people. E.g.'s, someone wants to go to the end of the list hitting q, someone finished selecting wanting to begin the action on their selected items... [...] I carefully read this thread, but of course cannot make everyone happy. Here is what I just implemented in cdebconf text frontend: * 'b' key now acts as with more/less/lynx, it goes back * Prompt is: q to quit select, b for back, n for next page This is a bit long, but I believe that this is not an issue because irrelevant options are not displayed, thus the full list will only be printed in the middle of the list. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
d-i install media disklabels
I suggest we come up with a simple way to label d-i install media. I looked at using eg, the FAT disk label stuff for this, but it is very limited and has various issues. Besides, it's so 1983 and so i386. I'm thinking about a simple file like the example below, just dropped into the disk as a disk.lbl file: System: debian-installer Label: CD drivers floppy Date: 20031109 I really kinda need this so the bootfloppy knows when it has found the root floppy or hd-media, and not something else. The floppy retreiver could also display information from it (but translations?). More fields could be added as needed. I know that our CD's have their own .disk/info file, but this does not seem flexible enough. -- see shy jo signature.asc Description: Digital signature
Re: FWD: Re: Bug#215469: don't include unnecessary udebs on the cd
Joey Hess [EMAIL PROTECTED] writes: I'll bet Goswin has a pretty good handle on this. - Forwarded message from Raphael Hertzog [EMAIL PROTECTED] - From: Raphael Hertzog [EMAIL PROTECTED] Date: Tue, 11 Nov 2003 22:06:53 +0100 To: Joey Hess [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#215469: don't include unnecessary udebs on the cd X-Spam-Status: No, hits=-4.9 required=10.0 tests=BAYES_00 autolearn=ham version=2.60 Le Sun, Oct 12, 2003 at 07:48:01PM -0400, Joey Hess écrivait: Etc. I'm sure you could save a *lot* of space by working with the d-i team to whittle down the udebs on the cd images to a set that is appropriate for the purpose of the CD. As it is these images are getting too big to be useful. Agreed, can the d-i team provide us a list of udeb to include (in the same way that you intend to provide us boot images) ? Or can someone of you manage such a list in debian-cd's CVS ? I think we should have several list for each use : - normal CD set - netinst CD - business card CD (maybe the same as netinst CD) Cheers, My branch has lists of udebs to be included on CDs. At the moment thats pretty much just a list of all udebs with some minor changes and special cases for archs. My goal is to make those lists just include the major udebs and pull in dependencies that are not already on previous mediums. Not quite sure how to do it esspecially with floppies but thats my goal. The list of udebs for the 20MB (just d-i) and 50MB (d-i + base) images I used are at: http://cvs.debian.org/debian-installer/build/pkg-lists/udeb-all/?only_with_tag=mrvn They are basically all udebs that are installable. You can remove any udeb thats already on the initrd (or the common packages from all relevant initrds). For my branch (might be one or two packages different from main branch) its initrd-base and initrd-udeb: http://cvs.debian.org/debian-installer/build/pkg-lists/initrd-base/?only_with_tag=mrvn http://cvs.debian.org/debian-installer/build/pkg-lists/initrd-udebs/?only_with_tag=mrvn The main branch has just one initrd: http://cvs.debian.org/debian-installer/build/pkg-lists/cdrom/ MfG Goswin PS: If you include floppy images check against the floppy initrd too. PPS: file-retriver and pcmcia-udeb udebs are removed from archive, scratch them. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Slow redraws in the debootstrap stage
On Tue, Nov 11, 2003 at 05:11:26PM -0500, Joey Hess wrote: Denis Barbier wrote: Here is another patch. I managed to get hw-detect to work directly under cdebconf and so could test it, but I prefer anyway to have it reviewed. As the previous one, it only addresses the flashing boxes problem, I still do not know what to do with resized boxes. Oh hmm, I am not really sure what flashing boxes problem that is, I thought this was to fix the resizing progress bar problem. Someone else who knows the problem ought to test it. I am mainly interested to know whether it breaks anything. If not, I want to apply this patch even if it does not fix any obvious problem, because it makes it very easy to add a Working, please wait text on the root window which will become visible when no windows are displayed. To do so, add newtDrawRootText(width/2-11, height/2, Working, please wait...); at the end of newt_initialize(). Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
On Tue, Nov 11, 2003 at 01:00:22PM -0500, Joe Nahmias wrote: 1) Install boots into the main menu. Interface looks alot snazzier than the old text interface, however the line-drawing characters are all messed up on my terminal (corners are displayed as '', c.) Known bug? not know bug, please file one. Sorry I don't know which package to blame for that. Any takers on where I should file the bug? slang? Uh, no. It's build/pkg-lists/netboot/* that doesn't include bterm (see Joey Hess' message to debian-boot one week ago.) I don't know if there's any package for the build system. I'd go for debian-installer, in doubt. For the netboot images, why don't we include nic-extra-modules?? Wouldn't this make sense to do since we know that a network install is being attempted? It's not like we're trying to cram stuff onto a floppy here, so why not put all the network modules we have into this image? I agree, please include this in your bug report. Choosing the netboot image and having to use floppies anyway sucks. FWIW, i'm using bterm and nic-extra-modules on homemade netboot images and they work perfectly. -- Jeremie Koenig [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
floppy-retriever_0.12_i386.changes ACCEPTED
Accepted: floppy-retriever_0.12.dsc to pool/main/f/floppy-retriever/floppy-retriever_0.12.dsc floppy-retriever_0.12.tar.gz to pool/main/f/floppy-retriever/floppy-retriever_0.12.tar.gz floppy-retriever_0.12_all.udeb to pool/main/f/floppy-retriever/floppy-retriever_0.12_all.udeb load-floppy_0.12_all.udeb to pool/main/f/floppy-retriever/load-floppy_0.12_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp idea
Goswin von Brederlow wrote: Why not merge dhcp and static? Try dhcp for some time or until the user hits abort. If dhcp finds any data seed it into debconf and jump to the final summary/acknowldege request in dhcp-static. Buttons there would be retry dhcp edit manual continue. I realy don't like two programs configuring the same in two ways. Well if I were on a network with dhcp but did not want to use dhcp, I might want to boot at medium priority and pick static config. Of course a combined dhcp+manual configurator could simply ask at medium priority before using dhcp with the same effect. I have no strong preferences, I just know the current dhcp stuff is annoying to a lot of users based on install reports. -- see shy jo signature.asc Description: Digital signature
Bug#219928: debian-installer: build failures on sparc
On Tue, Nov 11, 2003 at 08:52:01PM +0100, Goswin von Brederlow wrote: Joey Hess [EMAIL PROTECTED] writes: Goswin von Brederlow wrote: Then how do you know it is a bug in mklibs and it is not actually a missing symbol? Which was the real reason it failed in every testcase I got my hand on so far. All of those suposedly mklibs weak symbols bugs disapeared when recompiling the faulty binaries against the proper versions of libraries so far. If I read between the lines right, this time it was breakage in brltty on sparc, and I've removed it from the pkg-lists for sparc now. Is any arch still using brltty? Do we care about it? Yes, Mario Lang invested effort on getting it to work with debian-installer; without it blind users cannot install. Does brltty break on i386, m68k or alpha too? Don't know. -- Debian GNU/Linux Operating System By the People, For the People Chris Tillman (a people instance) toff one at cox dot net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Slow redraws in the debootstrap stage
Denis Barbier wrote: I am mainly interested to know whether it breaks anything. If not, I want to apply this patch even if it does not fix any obvious problem, because it makes it very easy to add a Working, please wait text on the root window which will become visible when no windows are displayed. To do so, add newtDrawRootText(width/2-11, height/2, Working, please wait...); at the end of newt_initialize(). In that case, I tested the patch with a 3 floppy + CD install in. I suspended that session after it started to retreive debs from the CD. There is one weird thing I do not understand. Remember the black character at the bottom-right corner? Well, it is now one line higher than it used to be. I made sure to refresh the screen, this is not a transient glitch. Strange. Later on in the install it moved to the bottom where I expect it. After cfdisk runs, the screen is corrupted. Looks like cdebconf draws the next dialog box on top of what cdebconf left on the screen, without clearing it. I don't know if it's related, but I then ran a shell from the menu, and the terminal was in stair-step mode. Never seen that before. I was interested to see if what I had done in the shell would remain on the screen when I got back to the menu, but it jumped into high priority mode and ran something that immediatly displayed a red error, which redrew the screen, so I don't know. The progress bar dialog does of course resize a few times, even with debootstrap fixes, since the descriptions of some kernel modules are rather long. I wish it would only grow bigger, not smaller.. -- see shy jo signature.asc Description: Digital signature
Re: Slow redraws in the debootstrap stage
On Tue, Nov 11, 2003 at 08:17:07PM -0500, Joey Hess wrote: The progress bar dialog does of course resize a few times, even with debootstrap fixes, since the descriptions of some kernel modules are rather long. I wish it would only grow bigger, not smaller.. This is already the case, isn't it? It gets reset when a new progress bar starts, though. Should we fix hw-detect to cut the names with ... in the middle? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Translation testing
On Tue, Nov 11, 2003 at 05:48:04PM +0200, [EMAIL PROTECTED] wrote: Can you tell me please(or redirect to RTFM) how to test an ongoing translation? Hello, I'm not an i18n wizard, but i think you will have to grab a copy of the CVS repository, and rebuild the packages you've translated from source, after having dropped your po files for each package in their debian/po directory. Then cd to the build directory, drop the freshly compiled udebs into localudebs, and run make demo TYPE=demo as root. At least that's what I do for patches. Maybe the poeple who know what they're speaking about will give you a simpler way, if there's one.. -- Jeremie Koenig [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
On Tue, Nov 11, 2003 at 12:33:59PM -0500, Joey Hess wrote: We're missing bogl-bterm and a lot of other utf-8 and terminal stuff on the netboot initrd. I will add it. Could you please s/nano/nano-udeb/ in pkg-lists/netboot/common ? Netboot images don't build any more. -- Jeremie Koenig [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp idea
Sebastian Ley wrote: Hm, another idea: Start netcfg, with dhcp probing in the background while in the foreground presenting a select question with: Trying to automatically configure the network... Abort network configuration Configure network manually We would need then a means to interrupt this question if DHCP probing is successful. The advantage: The user has full control if and how long he wants to probe for DHCP. If you're going to change cdebconf -- which this would require -- it would be more general to add a 'cancel' button to progress bars, and arrange for it to somehow do something useful. There are a few other things in the installer I'd like the ability to cancel.. -- see shy jo signature.asc Description: Digital signature
