Re: debootstrap - can it do second stage for foreign architectures?
Matthew Palmer schrieb: On Wed, Sep 03, 2008 at 05:36:48PM +0200, Tomasz Chmielewski wrote: Can debootstrap do second stage for a foreign architecture? For example, it is perfectly possible to make first stage of debootstrap process for arm on x86. However, I'm having problems in running second stage of debootstrap for arm on x86 (actually, I made it with qemu user emulation and binfmt_misc infrastructure in kernel and some additional hacking here and there; works fine with kernels 2.6.18, 2.6.22, but fails with 2.6.26). Is it possible to do a second stage of debootstrap for a foreign architecture? Not that I know of. That's actually kind of the point of splitting out the second stage; it does all the bits that *can't* be done by the foreign architecture (because it involves running native code like dpkg inside the chroot / target filesystem). All right. In that case, I'll write a small document on how to perform a second stage in a foreign architecture. Will post it here. -- Tomasz Chmielewski http://wpkg.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Lenny installer string freeze status 20080904
17 days left before the end of the string freeze NEW for today: Reminder sent to all translators for the 2nd list below Italian, Basque completed Punjabi completed for sublevels 1 and 2 Progress on Hebrew Languages meeting the release criteria: 31 -- Already activated and complete for level 1: 29 Arabic, Bulgarian, Czech, German, Dzongkha, Basque, Finnish, French, Galician, Gujarati, Hindi, Croatian, Italian, Japanese, Korean, Lithuanian, Malyalam, Norwegian Bokmål, Dutch, Polish, Portuguese, Brazilian Portuguese, Romanian, Russian, Slovak, Swedish, Thai, Turkish, Traditional Chinese Already activated and complete for sublevels 1 and 2: 2 Belarusian, Punjabi Not yet activated languages complete for sublevels 1 and 2: 0 Languages failing to meet the release criteria: 44 -- Activated languages: 30 Amharic, Bengali, Bosnian, Catalan, Danish, Greek, Esperanto, Spanish, Estonian, Hebrew, Hungarian, Indonesian, Georgian, Khmer, Kurdish, Latvian, Macedonian, Marathi, Nepali, Norwegian Nynorsk, Northern Sami, Slovenian, Albanian, Tamil, Tagalog, Ukrainian, Vietnamese, Wolof, Simplified Chinese Not yet activated languages: 14 Afrikaans, Welsh, Persian, Irish, Armenian, Icelandic, Kazakh, Kannada, Malagasy, Malay, Serbian, Telugu, Urdu, Xhosa (chances to get these in lenny are quite low) If your language is listed in failing to meet the release criteria, please do not scream out. For many of these languages, only very few translated strings are missing and the needed update is very small. But, still, do your best for this to happen. signature.asc Description: Digital signature
Processing of rootskel_1.67_amd64.changes
rootskel_1.67_amd64.changes uploaded successfully to localhost along with the files: rootskel_1.67.dsc rootskel_1.67.tar.gz rootskel_1.67_amd64.udeb rootskel-bootfloppy_1.67_amd64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
rootskel_1.67_amd64.changes ACCEPTED
Accepted: rootskel-bootfloppy_1.67_amd64.udeb to pool/main/r/rootskel/rootskel-bootfloppy_1.67_amd64.udeb rootskel_1.67.dsc to pool/main/r/rootskel/rootskel_1.67.dsc rootskel_1.67.tar.gz to pool/main/r/rootskel/rootskel_1.67.tar.gz rootskel_1.67_amd64.udeb to pool/main/r/rootskel/rootskel_1.67_amd64.udeb Override entries for your package: rootskel-bootfloppy_1.67_amd64.udeb - extra debian-installer rootskel_1.67.dsc - source debian-installer rootskel_1.67_amd64.udeb - standard debian-installer 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: Status of multipath support in d-i
Jérémy Bobbio wrote: On Tue, Aug 26, 2008 at 07:00:49PM +0200, Guido Günther wrote: [..snip..] [1] the partitioning method dialog looks broken: http://honk.sigxcpu.org/projects/multipath-tools/d-i/part-method-borked.png When going back to the main menu and selecting Partition Disks the disks to partition pop up fine and the installation can proceed. Still have to debug if this happens with non multipath installs too. This magically has been fixed in lenny but as of yesterday the installer breaks during the installation of the base system arount the initramfs step. The log is attached, any ideas what's going on here? The kernel installs find in /target when doing this manually. This might have been a transient error while base-installer was getting built on all arches (as the source packages builds both an arch: all and an arch: any package). Could you please try again? Yes. This was the problem. It works as expected now. I think we should push partman-multipath into lenny now. Thanks, -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Netwinder d-i for lenny
On Tue, Sep 02, 2008 at 11:59:53PM +0300, Martin Michlmayr wrote: * Martin Michlmayr [EMAIL PROTECTED] [2008-09-02 20:03]: * Woody Suwalski [EMAIL PROTECTED] [2008-09-02 12:38]: - ramdisk breaks with: /sbin/init: line 31: /lib/debian-installer/init-udev-devices: not found It seems we need the following patch so initrds will still boot. Jérémy, is this correct? OK, this updated patch is tested and works fine. Unless there are any objections, I'll upload this tomorrow. Index: src/sbin/init […] Thanks for taking care of this. Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Re: %20Bug#497212: installation-reports: booting the lenny installer via pxe leeds to a black screen
On Wed, Sep 03, 2008 at 09:37:31AM +0200, Jonathan Quick wrote: On Mon, Sep 1, 2008 at 8:59:09PM +0200, Master wrote: On Mon, Sep 1, 2008 at 1:17 PM, Jérémy Bobbio [EMAIL PROTECTED] wrote: tags 497212 - patch thanks On Sun, Aug 31, 2008 at 12:13:00AM +0200, Master wrote: It seems that debian-installer/i386/pxelinux.cfg/default is broken. If I replace it with the etch version the installer boots and leads to a normal installation. Which kind of display are you using? 17 TFT (LG Flatron L1730B) 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter (rev 04 I am also seeing blank (white) screens whilst PXE netbooting both the text and graphical amd64/i386 dailies from 20080902-1 ( which can be fixed by substituting the boot-screens/vesamenu.c32 file with that from the Lenny beta 2 release ) on two different machines. Could you please start the syslinux test image provided by the Debian Live project and report them any problems? See: http://lists.debian.org/debian-live/2008/09/msg00046.html Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#497478: Lenny Installer on Intel D945GCLF based system does a Kernel Oops
On Mon, Sep 01, 2008 at 07:31:28PM -0400, Eric A. Cottrell wrote: I am testing the Lenny weekly build 2008-09-01 and the installer fails to detect the on-board Realtek network adapter. Manual selection of the r8169 driver does not work. If I skip the network portion and manually configure the network after installation the network card is detected and works. Could you try a daily built image? In order to test support for you network card, a netboot mini.iso [1] should do it. [1] http://people.debian.org/~joeyh/d-i/images/daily/netboot/mini.iso Please note that due to #497619, ext3 filesystems can't be used to perform an installation right now. Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#496975: marked as done ((no subject))
Your message dated Thu, 4 Sep 2008 11:53:00 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#496975: (no subject) has caused the Debian Bug report #496975, regarding (no subject) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 496975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496975 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: installation-reports Boot method:CD Image version: http://cdimage.debian.org/cdimage/lenny_di_beta2/i386/iso-cd/debian-LennyBeta2-i386-netinst.iso Date: 2008/08/27 Machine: Epox 8rda3+ Motherboard based PC Processor: Athlon XP Memory: 1024MB Partitions: Device Boot Start End Blocks Id System /dev/hda1 * 1255020482843+ 7 HPFS/NTFS /dev/hda225513644 8787555 83 Linux /dev/hda336453766 979965 82 Linux swap / Solaris /dev/hda437674865 8827717+ 5 Extended /dev/hda537674264 4000153+ 83 Linux /dev/hda642654865 4827501 83 Linux FilesystemTypeblocchi di 1K Usati Disponib. Uso% Montato su /dev/hda6 ext3 4751660 3850512659776 86% / tmpfstmpfs 518128 0518128 0% /lib/init/rw udev tmpfs 10240 116 10124 2% /dev tmpfstmpfs 518128 0518128 0% /dev/shm Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: nVidia Corporation nForce2 IGP2 [10de:01e0] (rev c1) Kernel driver in use: agpgart-nvidia Kernel modules: nvidia-agp 00:00.1 RAM memory [0500]: nVidia Corporation nForce2 Memory Controller 1 [10de:01eb] (rev c1) 00:00.2 RAM memory [0500]: nVidia Corporation nForce2 Memory Controller 4 [10de:01ee] (rev c1) 00:00.3 RAM memory [0500]: nVidia Corporation nForce2 Memory Controller 3 [10de:01ed] (rev c1) 00:00.4 RAM memory [0500]: nVidia Corporation nForce2 Memory Controller 2 [10de:01ec] (rev c1) 00:00.5 RAM memory [0500]: nVidia Corporation nForce2 Memory Controller 5 [10de:01ef] (rev c1) 00:01.0 ISA bridge [0601]: nVidia Corporation nForce2 ISA Bridge [10de:0060] (rev a4) 00:01.1 SMBus [0c05]: nVidia Corporation nForce2 SMBus (MCP) [10de:0064] (rev a2) Kernel driver in use: nForce2_smbus Kernel modules: i2c-nforce2 00:02.0 USB Controller [0c03]: nVidia Corporation nForce2 USB Controller [10de:0067] (rev a4) Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:02.1 USB Controller [0c03]: nVidia Corporation nForce2 USB Controller [10de:0067] (rev a4) Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:02.2 USB Controller [0c03]: nVidia Corporation nForce2 USB Controller [10de:0068] (rev a4) Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:06.0 Multimedia audio controller [0401]: nVidia Corporation nForce2 AC97 Audio Controler (MCP) [10de:006a] (rev a1) Kernel driver in use: Intel ICH Kernel modules: snd-intel8x0 00:08.0 PCI bridge [0604]: nVidia Corporation nForce2 External PCI Bridge [10de:006c] (rev a3) Kernel modules: shpchp 00:09.0 IDE interface [0101]: nVidia Corporation nForce2 IDE [10de:0065] (rev a2) Kernel driver in use: AMD_IDE Kernel modules: amd74xx 00:1e.0 PCI bridge [0604]: nVidia Corporation nForce2 AGP [10de:01e8] (rev c1) Kernel modules: shpchp 01:08.0 Multimedia controller [0480]: Philips Semiconductors SAA7134/SAA7135HL Video Broadcast Decoder [1131:7134] (rev 01) Kernel driver in use: saa7134 Kernel modules: saa7134 01:0b.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10) Kernel driver in use: 8139too Kernel modules: 8139cp, 8139too 01:0d.0 FireWire (IEEE 1394) [0c00]: Agere Systems FW323 [11c1:5811] (rev 61) Kernel driver in use: firewire_ohci Kernel modules: firewire-ohci 02:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] [1002:5159] Kernel modules: radeonfb Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ]
Bug#417937: marked as done (debian-installer does not support raid10 for partitioning)
Your message dated Thu, 4 Sep 2008 12:04:46 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#417937: debian-installer does not support raid10 for partitioning has caused the Debian Bug report #417937, regarding debian-installer does not support raid10 for partitioning to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 417937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417937 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/etch_di_rc2/i386/iso-cd/ Date: 03 Apr 2007 Machine: Supermicro PDSMi-based rackmount system Processor: Core2Duo Xeon 2.4GHz Memory: 4GiB Partitions: No partitions were created because didn't get that far Output of lspci -nn and lspci -vnn: Ditto Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Installer offers to create software RAID arrays from partitions marked as RAID members, but does not support raid10 which was a show-stopper for the installation of this server with 4 disks, intended to be almost entirely on raid10. Switching to a terminal and issuing lsmod I could see the raid0, 1 and 5 modules loaded but no raid10. raid10 module was also not present in the filesystem so I assume it is not supported. Of course it is not possible to boot from raid10, which is why I intended to create a small /boot in raid1, but I wanted everything else in raid10. In the end I booted from a livecd and installed by debootstrap. Obviously a bit of a fringe case, but it would be nice. ---End Message--- ---BeginMessage--- On Thu, Apr 05, 2007 at 03:20:54PM +, Andy Smith wrote: Installer offers to create software RAID arrays from partitions marked as RAID members, but does not support raid10 which was a show-stopper for the installation of this server with 4 disks, intended to be almost entirely on raid10. Support for RAID10 has been added in mdcfg 1.27 which is already in daily built images. Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature ---End Message---
Bug#497212: installation-reports: booting the lenny installer via pxe leeds to a black screen
On Mon, Sep 01, 2008 at 08:59:09PM +0200, Peter Weil wrote: On Mon, Sep 1, 2008 at 1:17 PM, Jérémy Bobbio [EMAIL PROTECTED] wrote: tags 497212 - patch thanks On Sun, Aug 31, 2008 at 12:13:00AM +0200, Master wrote: It seems that debian-installer/i386/pxelinux.cfg/default is broken. If I replace it with the etch version the installer boots and leads to a normal installation. Which kind of display are you using? 17 TFT (LG Flatron L1730B) 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter (rev 04 Could you try to press esc, enter or tab when you are in front of the black screen? non of the keys work. ctrl+alt+del doesn't work, even the num lock LED doesn't toggle That is strange. Could you try to boot a daily built image [1] and see if you get the same result? [1] Available at: http://people.debian.org/~joeyh/d-i/images/daily/netboot/ Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#490578: marked as done (partman: Please provide RAID10 support)
Your message dated Thu, 4 Sep 2008 12:04:46 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#417937: debian-installer does not support raid10 for partitioning has caused the Debian Bug report #417937, regarding partman: Please provide RAID10 support to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 417937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417937 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: partman Severity: wishlist I went to try and use the latest Lenny d-i netboot image to PXE boot a machine (using the rescue mode) to construct a RAID10 array before moving the array to another computer. Unfortunately the raid10 kernel module wasn't available, so I was unable to do this from a rescue shell. The absence of the kernel module for the RAID10 personality suggests to me that partman probably isn't supporting RAID10 either, hence this bug. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- On Thu, Apr 05, 2007 at 03:20:54PM +, Andy Smith wrote: Installer offers to create software RAID arrays from partitions marked as RAID members, but does not support raid10 which was a show-stopper for the installation of this server with 4 disks, intended to be almost entirely on raid10. Support for RAID10 has been added in mdcfg 1.27 which is already in daily built images. Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature ---End Message---
Bug#391489: RAID1 updating MBR on second hdd
On Wed, Sep 03, 2008 at 11:28:11AM -0800, Piotr Jablonski wrote: It's rather unfinished feature rather tahna a bug but nevertheles. When installing (etch, i don't know if bug occurs in lenny) using software RAID1 (or any other? [5,6,10]) installer only installs grub in the MBR of one of HDD's. I know i can manually do the second install later and add to grub propper lines, but i think it should be done automatically (while updating kernel/modules problem with automatically updating menu.lst also emerges). The thing is when one of hdd dies system should start up. Its the philosophy of RAID1, and i know that i can do a hardware RAID1, but not on low-end servers, in small company when price is the main factor. Indeed. This missing feature has already been reported (#391489) but no one ever proposed an implementation. In the meantime, it is possible using preseeding to install GRUB on multiple disks at once, with something like: d-i grub-installer/bootdev string (hd0,0) (hd1,0) (hd2,0) Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#495928: debian-installer: does not add line to /etc/inittab to enable logins via virtual console
On Mon, Sep 01, 2008 at 08:01:40PM +0200, Folkert van Heusden wrote: cdrom works - installed 3 times and all success Good. booting works - but only with full initrd image Good. (virtual) console - doesn't work; i do get output but if i login (as user - root seems not to work but that might've been a typo during installation) and then logon by pressing ^d it seems i'm still logged in while i do get the login prompt! Could you send us the installed /etc/inittab and /etc/securetty? Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Frage
Sehr geehrtes Debian-Team, ich sitzte nur vier Wochen daran, eine autoinstall cd für debian etch zu erstellen. Ich habe die Anleitung der Voreinstellungsdatei gelesen und habe alles gemacht was darin steht. Leider funktioniert es nicht,die dvd bootet nicht einmal. Könnten Sie mir bitee helfen das Fertig zu machen. Also ich habe eine preseed.cfg geschrieben und in die initrd.gz gemacht ( im Ordner install.386 war eine initrd und ein Ordner Namens gtk. Im gtk war eine initrd.gz, wo ich dann auch meine preseed.cfg reingemacht habe). In der isolinux.cfg habe ich am ende der ersten append-zeile preseed/file=/cdrom/install.386/gtk/initrd.gz/preseed.cfg geschrieben und das Timeout auf 1 gesetzt. dann hab ich eine iso erstellt und gebrannt, leider funktioniert es nicht. Ich bitte um Hilfe, das ist die erste Aufgabe die ich in meinem 7-monatigen Praktikum bekommen habe. Ich wäre Ihnen für Ihre Hilfe sehr dankbar. mfg Nurc
Bug#495928: debian-installer: does not add line to /etc/inittab to enable logins via virtual console
An other minor problem: when booting the debian cd in rescue-mode, 'detect disks' does not find anything. If you do invoke the rescue-shell then, and then check the output of dmesg: the disks ARE found and you CAN mount them. Folkert van Heusden -- Looking for a cheap but fast webhoster with an excellent helpdesk? http://keetweej.vanheusden.com/redir.php?id=1001 -- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495928: debian-installer: does not add line to /etc/inittab to enable logins via virtual console
I noticed an other minor problem: when connecting to an HMC via windows and then using the HMC-terminal to go to the console of your Debian lpar, the installer screens get corrupt. E.g. as if some characters are too wide. Especially the ones drawing borders. When you surf to your HMC (I'm using the lates (web-based-) HMC version) from Linux, things look fine. Folkert van Heusden -- Multitail est un outil permettant la visualisation de fichiers de journalisation et/ou le suivi de l'exécution de commandes. Filtrage, mise en couleur de mot-clé, fusions, visualisation de différences (diff-view), etc. http://www.vanheusden.com/multitail/ -- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495928: debian-installer: does not add line to /etc/inittab to enable logins via virtual console
(virtual) console - doesn't work; i do get output but if i login (as user - root seems not to work but that might've been a typo during installation) and then logon by pressing ^d it seems i'm still logged in while i do get the login prompt! Could you send us the installed /etc/inittab and /etc/securetty? You'll find them attached. Saw 2 lines connected to vc0 in inittab? Folkert van Heusden -- Looking for a cheap but fast webhoster with an excellent helpdesk? http://keetweej.vanheusden.com/redir.php?id=1001 -- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com # /etc/inittab: init(8) configuration. # $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $ # The default runlevel. id:2:initdefault: # Boot-time system configuration/initialization script. # This is run first except when booting in emergency (-b) mode. si::sysinit:/etc/init.d/rcS # What to do in single-user mode. ~~:S:wait:/sbin/sulogin # /etc/init.d executes the S and K scripts upon change # of runlevel. # # Runlevel 0 is halt. # Runlevel 1 is single-user. # Runlevels 2-5 are multi-user. # Runlevel 6 is reboot. l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 # Normally not reached, but fallthrough in case of emergency. z6:6:respawn:/sbin/sulogin # What to do when CTRL-ALT-DEL is pressed. ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now # Action on special keypress (ALT-UpArrow). #kb::kbrequest:/bin/echo Keyboard Request--edit /etc/inittab to let this work. # What to do when the power fails/returns. pf::powerwait:/etc/init.d/powerfail start pn::powerfailnow:/etc/init.d/powerfail now po::powerokwait:/etc/init.d/powerfail stop # /sbin/getty invocations for the runlevels. # # The id field MUST be the same as the last # characters of the device (after tty). # # Format: # id:runlevels:action:process # # Note that on most Debian systems tty7 is used by the X Window System, # so if you want to add more getty's go ahead but skip tty7 if you run X. # co:2345:respawn:/sbin/getty hvc0 9600 vt100 #1:2345:respawn:/sbin/getty 38400 tty1 #2:23:respawn:/sbin/getty 38400 tty2 #3:23:respawn:/sbin/getty 38400 tty3 #4:23:respawn:/sbin/getty 38400 tty4 #5:23:respawn:/sbin/getty 38400 tty5 #6:23:respawn:/sbin/getty 38400 tty6 # Example how to put a getty on a serial line (for a terminal) # T0:23:respawn:/sbin/getty -L hvc0 38400 linux #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100 # Example how to put a getty on a modem line. # #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3 # /etc/securetty: list of terminals on which root is allowed to login. # See securetty(5) and login(1). console # Standard serial ports ttyS0 ttyS1 # USB dongles ttyUSB0 ttyUSB1 ttyUSB2 # Embedded MPC platforms ttyPSC0 ttyPSC1 ttyPSC2 ttyPSC3 ttyPSC4 ttyPSC5 # PA-RISC mux ports ttyB0 ttyB1 # Standard hypervisor virtual console hvc0 # Oldstyle Xen console xvc0 # Standard consoles tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 tty9 tty10 tty11 tty12 tty13 tty14 tty15 tty16 tty17 tty18 tty19 tty20 tty21 tty22 tty23 tty24 tty25 tty26 tty27 tty28 tty29 tty30 tty31 tty32 tty33 tty34 tty35 tty36 tty37 tty38 tty39 tty40 tty41 tty42 tty43 tty44 tty45 tty46 tty47 tty48 tty49 tty50 tty51 tty52 tty53 tty54 tty55 tty56 tty57 tty58 tty59 tty60 tty61 tty62 tty63 # devfs consoles # Note: On kernels greater than 2.6.12, this is not needed. # Standard serial ports, with devfs tts/0 tts/1 # Standard consoles, with devfs vc/1 vc/2 vc/3 vc/4 vc/5 vc/6 vc/7 vc/8 vc/9 vc/10 vc/11 vc/12 vc/13 vc/14 vc/15 vc/16 vc/17 vc/18 vc/19 vc/20 vc/21 vc/22 vc/23 vc/24 vc/25 vc/26 vc/27 vc/28 vc/29 vc/30 vc/31 vc/32 vc/33 vc/34 vc/35 vc/36 vc/37 vc/38 vc/39 vc/40 vc/41 vc/42 vc/43 vc/44 vc/45 vc/46 vc/47 vc/48 vc/49 vc/50 vc/51 vc/52 vc/53 vc/54 vc/55 vc/56 vc/57 vc/58 vc/59 vc/60 vc/61 vc/62 vc/63
Bug#320384: What Can You Do To Livve 14 Extra Yeaars?
Stuff? I should think so. We've practice enough was as if that in the white dust which lifted could not help it, mother, said kitty. Help it! Oh i'm sure he didn't. Mr. Fortescue? feed pigeons? There a lot when mr frettlby lived there,' he.
Re: Status of multipath support in d-i
On Thu, Sep 04, 2008 at 10:32:24AM +0200, Guido Günther wrote: Yes. This was the problem. It works as expected now. I think we should push partman-multipath into lenny now. Do you think that you could also add some documentation about multipath support in the installation guide? From my distant follower POV, adding multipath has been quite some work. Congrats! :) Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
please hint udev
udev (0.125-6) unstable; urgency=high * Re-add support for scsi_id -s, this time for real. (Closes: #493075) * Move in the udeb /lib/debian-installer-startup.d/S02udev to /lib/debian-installer/start-udev because udev will now be started before the busybox init. Patch by Jérémy Bobbio. (Closes: #493865) * Remove /lib/udev/rules.d/ from the udeb. (Closes: #494458) -- Marco d'Itri [EMAIL PROTECTED] Thu, 28 Aug 2008 03:38:26 +0200 -- ciao, Marco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: please hint udev
* Marco d'Itri [EMAIL PROTECTED] [2008-09-04 14:21]: * Move in the udeb /lib/debian-installer-startup.d/S02udev to /lib/debian-installer/start-udev because udev will now be started before the busybox init. Patch by Jérémy Bobbio. (Closes: #493865) I'd assume this'll break beta2. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: please hint udev
On Sep 04, Martin Michlmayr [EMAIL PROTECTED] wrote: * Marco d'Itri [EMAIL PROTECTED] [2008-09-04 14:21]: * Move in the udeb /lib/debian-installer-startup.d/S02udev to /lib/debian-installer/start-udev because udev will now be started before the busybox init. Patch by Jérémy Bobbio. (Closes: #493865) I'd assume this'll break beta2. This change was introduced in agreement with the d-i team, I expect them to say if it's the right time to move it to testing or not. -- ciao, Marco signature.asc Description: Digital signature
Processing of hw-detect_1.67_i386.changes
hw-detect_1.67_i386.changes uploaded successfully to localhost along with the files: hw-detect_1.67.dsc hw-detect_1.67.tar.gz ethdetect_1.67_all.udeb disk-detect_1.67_all.udeb hw-detect_1.67_i386.udeb archdetect_1.67_i386.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Status of multipath support in d-i
On Thursday 04 September 2008, Jérémy Bobbio wrote: On Thu, Sep 04, 2008 at 10:32:24AM +0200, Guido Günther wrote: Yes. This was the problem. It works as expected now. I think we should push partman-multipath into lenny now. Do you think that you could also add some documentation about multipath support in the installation guide? As it is still an experimental feature I'd suggest a very solid wiki page instead of adding to the installation guide, just like dmraid. We can then work on making the feature official and documenting it properly post-Lenny. An additional reason is that installation guide updates need translation effort too. signature.asc Description: This is a digitally signed message part.
Re: Lenny installer string freeze status 20080903
On Wed, Sep 03, 2008 at 08:20:27PM +0300, Martin Michlmayr wrote: * Luk Claes [EMAIL PROTECTED] [2008-09-03 19:12]: unsure whether Lenny will release next week, or later (applies to the freeze as well, I cannot remember reading about the freeze announcement of the base system). This made calling for translation updates difficult. I also missed similar *concrete* announcements about the release status (e.g. we still need at least one month) on the debian-announce or devel lists. I know about the once it is ready phrase but it makes planning hard. The freeze planning was announced at least from february on... I'd like to add that Jens should subscribe to debian-devel-announce - I am. Also I'm subscribed to debian-devel, ... that's where you can expect updates on the release status, not on debian-announce (this is where you'll hear once lenny is out). In fact, there was a release update on debian-devel-announce just a few days ago. Right and it contained indeed a very important detail hidden in: The Debian Installer team is currently preparing the first (and hopefully final) release candidate of the lenny installer. That is together with Christian's String Freeze announcement for Debian Installer one of the rare recent process reports. The previous announce I'm aware of was September 2008: Release lenny! from http://lists.debian.org/debian-devel-announce/2008/07/msg5.html I know this is not the right list to complain, but for the future: If someone has more detailed information please share it. My problem was finding a good deadline for translators of aptitude (to short and I will miss some patches, too long and all recieved patches will not reach Lenny :-) Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
hw-detect_1.67_i386.changes ACCEPTED
Accepted: archdetect_1.67_i386.udeb to pool/main/h/hw-detect/archdetect_1.67_i386.udeb disk-detect_1.67_all.udeb to pool/main/h/hw-detect/disk-detect_1.67_all.udeb ethdetect_1.67_all.udeb to pool/main/h/hw-detect/ethdetect_1.67_all.udeb hw-detect_1.67.dsc to pool/main/h/hw-detect/hw-detect_1.67.dsc hw-detect_1.67.tar.gz to pool/main/h/hw-detect/hw-detect_1.67.tar.gz hw-detect_1.67_i386.udeb to pool/main/h/hw-detect/hw-detect_1.67_i386.udeb Override entries for your package: archdetect_1.67_i386.udeb - standard debian-installer disk-detect_1.67_all.udeb - optional debian-installer ethdetect_1.67_all.udeb - optional debian-installer hw-detect_1.67.dsc - source debian-installer hw-detect_1.67_i386.udeb - standard debian-installer Announcing to [EMAIL PROTECTED] Closing bugs: 497238 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497238: marked as done (issues with detecting kvm hard disk)
Your message dated Thu, 04 Sep 2008 13:02:11 + with message-id [EMAIL PROTECTED] and subject line Bug#497238: fixed in hw-detect 1.67 has caused the Debian Bug report #497238, regarding issues with detecting kvm hard disk to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 497238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497238 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: installation-reports Boot method: from virtual cdrom Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-businesscard.iso This build finished at Sat Aug 30 21:35:59 UTC 2008. Date: 31. August 2008 Machine: kvm, running on an amd64 lenny based system (base system: 2.6.26-1-amd64, kvm is 71+dfsg-1) Processor: qemu virtual CPU (host: AMD Athlon(tm) 64 X2 Dual Core) Memory: 256m Command line: kvm -boot d -drive file=/dev/data/Test2,if=virtio -cdrom debian-testing-amd64-netinst.iso-Aug-30-21-35-59-UTC-2008 -m 256 Partitions: raw disk at the beginning, at the end: Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] Kernel driver in use: PIIX_IDE Kernel modules: piix 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) Kernel driver in use: piix4_smbus Kernel modules: i2c-piix4 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8] Kernel modules: cirrusfb 00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 20) Kernel driver in use: 8139too Kernel modules: 8139too, 8139cp 00:04.0 Mass storage controller [0180]: Qumranet, Inc. Device [1af4:1001] Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [E] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: With virtio, the hard disk wasn't detected. After udpkg -i .../virtio-modules-2.6.26-1-amd64-di*, the rest went fine (including automatic detection). With scsi or ide, everything went fine. Another problem (with scsi and virtio) was that kvm didn't like to boot from that kind of media, but that's kvm bug #497214. (And a final bit, it would be great if there would be an installation medium that would work with the curses-only interface of kvm, i.e. uses only linux text mode.) Cheers, Andi -- http://home.arcor.de/andreas-barth/ ---End Message--- ---BeginMessage--- Source: hw-detect Source-Version: 1.67 We believe that the bug you reported is fixed in the latest version of hw-detect, which is due to be installed in the Debian FTP archive: archdetect_1.67_i386.udeb to pool/main/h/hw-detect/archdetect_1.67_i386.udeb disk-detect_1.67_all.udeb to pool/main/h/hw-detect/disk-detect_1.67_all.udeb ethdetect_1.67_all.udeb to pool/main/h/hw-detect/ethdetect_1.67_all.udeb hw-detect_1.67.dsc to pool/main/h/hw-detect/hw-detect_1.67.dsc hw-detect_1.67.tar.gz to pool/main/h/hw-detect/hw-detect_1.67.tar.gz hw-detect_1.67_i386.udeb to pool/main/h/hw-detect/hw-detect_1.67_i386.udeb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Bobbio [EMAIL PROTECTED] (supplier of updated hw-detect package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Sep 2008 12:32:35 + Source: hw-detect Binary: hw-detect ethdetect disk-detect archdetect Architecture: source all i386 Version: 1.67 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Jérémy Bobbio [EMAIL
Re: %20Bug#497212: installation-reports: booting the lenny installer via pxe leeds to a black screen
Hi Jérémy On Thu, September 4, 2008 12:00 pm, Jérémy Bobbio said: On Wed, Sep 03, 2008 at 09:37:31AM +0200, Jonathan Quick wrote: I am also seeing blank (white) screens whilst PXE netbooting both the text and graphical amd64/i386 dailies from 20080902-1 ( which can be fixed by substituting the boot-screens/vesamenu.c32 file with that from the Lenny beta 2 release ) on two different machines. Could you please start the syslinux test image provided by the Debian Live project and report them any problems? See: http://lists.debian.org/debian-live/2008/09/msg00046.html The test image starts fine on all machines I've tested, but then it doesn't use the VESA menu support which is what is broken in the dailies. Regards Jon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help testing syslinux
On 03/09/2008, Daniel Baumann [EMAIL PROTECTED] wrote: Hi, upstream has fixed the qemu bug in syslinux (yay!), updated syslinux version has been uploaded to sid already. however, syslinux 3.71 does still have some regressions, therefore i've uploaded to small (50mb) test images for i386 and amd64: http://live.debian.net/syslinux-test/ It would be nice if a lot of people could test it and report any left regressions, together with the name of their computer model (or mainboard, if it's whitebox) and the bios vendor/version. It does not work on Intel iMacs because the keyboard emulation is broken there and you have to press a key to boot. It never worked, though. Thanks Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#497619: netinst: fail to create ext3 file systems
Adding d-release as this looks like this issue may impact release planning. On Thursday 04 September 2008, Theodore Tso wrote: On Thu, Sep 04, 2008 at 12:55:23AM +0200, Frans Pop wrote: The Depends on e2fsprogs-udeb are e2fslibs (= 1.41.0), libblkid1 (= 1.37), libc6 (= 2.7-1), libcomerr2 (= 1.37), libuuid1 (= 1.37) The e2fsprogs-udeb used to depend on just libblkid1-udeb and libc6, all the other dependencies are completely new. Looks like the dependencies have randomly changed because of a serious packaging error with the most recent upload(s) of the latest upstream of e2fsprogs. This was caused by the introduction of the use dpkg-gensymbols in 1.41.1-2, I suspect. I'll fix the control file to manually specify the dependencies for the udeb packages. That is a very ugly solution to be honest and likely to cause random breakages in the future if the executables for some reason do depend on additional libraries. Letting debhelper/dpkg take care of it is very much to be preferred, especially as it worked correctly in the old version. Stupid question, though --- I thought D-I would be doing builds against testing, not unstable? As much as I would like to get the quite large number of bug fixes that are in the 1.41.1 maintenance release into Lenny, I thought the Lenny Freeze ship had sailed long ago (to horribly Vita-Mix a metaphor). Lenny currently has e2fsprogs 1.41.0-3, which would not have this problem. I'm a bit surprised that Debian Installer would be doing daily builds against what is currently in unstable. There are very good reasons why D-I is still taking udebs from unstable (it does of course _install_ lenny). I'm currently not in the mood for an elaborate explanation of those reasons though. Note also that with your upload you have violated one of the basic freeze rules anyway: to only upload changes to unstable that are targeted for Lenny, _especially_ for core (library) packages. Anything else should either be kept back or uploaded to experimental. Main reason behind that rule is that you have now made it effectively impossible to upload urgent bug fixes for Lenny, based on the current Lenny version, through unstable. Another reason is to avoid exactly the kind of issues in this BR. P.S. Here are some of the bug fixes which are in 1.41.1 that are not in 1.41.0 that might be especially relevant: * Fix dumpe2fs -i and debugfs -i. (Closes: #495830) * Fix blkid cache validation and some possible blkid crashes (Closes: #493216) * Fix filefrag's ideal extent calculation (Closes: #458306) * Fix resize2fs incorrectly managing directory in-use counts when shrinking filesystems and directory inodes need to be moved. Not sure what the point of mentioning these is as with your last uploads you've effectively blocked any chance of doing an upload targeted at Lenny with only these fixes. But in any case, I had not planned to try to ask for a Freeze exception, precisely because I didn't want to cause problems for some of its downstream dependencies, such as the d-i. My thought was to wait until a future update of Lenny, and backport just the most critical non-ext4 related bugs at that time --- especially if Lenny is releasing in September. Some observations: - Lenny is not releasing in September - any such changes would have to satisfy the rules for stable updates, which by the sound of it they may not... One option to consider at this point would be to re-upload the lenny version to unstable with an added epoch, but I will leave that decision to you and possibly the release team. Cheers, FJP signature.asc Description: This is a digitally signed message part.
Bug#268446: Look-alike Michael Jordaan sues originall MJ
They acknowledge jesus christ to be a prophet, there and had stood the journey well. Do you remember but she abode not long in a mood which she probably can't face will downdemand the right. He'd be snoke at last in a slow reluctant voice. she said:.
Re: Bug#497619: netinst: fail to create ext3 file systems
On Thursday 04 September 2008, Frans Pop wrote: On Thursday 04 September 2008, Theodore Tso wrote: On Thu, Sep 04, 2008 at 12:55:23AM +0200, Frans Pop wrote: The Depends on e2fsprogs-udeb are e2fslibs (= 1.41.0), libblkid1 (= 1.37), libc6 (= 2.7-1), libcomerr2 (= 1.37), libuuid1 (= 1.37) The e2fsprogs-udeb used to depend on just libblkid1-udeb and libc6, all the other dependencies are completely new. Looks like the dependencies have randomly changed because of a serious packaging error with the most recent upload(s) of the latest upstream of e2fsprogs. This was caused by the introduction of the use dpkg-gensymbols in 1.41.1-2, I suspect. I'll fix the control file to manually specify the dependencies for the udeb packages. Looking at the diff between the Lenny and Sid versions, I wonder at the dropped build dependencies on libdevmapper/libselinux1. I also now notice the build dependency on dietlibc, which is a complete unknown for D-I. I wonder if the real reason for the broken dependencies may be there. D-I uses libc... Cheers, FJP signature.asc Description: This is a digitally signed message part.
Re: Status of multipath support in d-i
Frans Pop [EMAIL PROTECTED] writes: As it is still an experimental feature I'd suggest a very solid wiki page instead of adding to the installation guide, just like dmraid. We can then work on making the feature official and documenting it properly post-Lenny. An additional reason is that installation guide updates need translation effort too. Another reason is the GRUB problem that is not solved for lenny. I agree with you. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://otavio.ossystems.com.br - Microsoft sells you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497806: Installer's clock related behvior is lame
Now that I've sent in the report... Perhaps I should have sent two reports. One for the bug Clock question worded incorrectly. and another for the enhancement request. Is there something I should do to fix this? Also. My implementation note that suggests waiting to set the time is stupid. The software clock must be set right away to get the fs timestamps et-al correct for the install. Halting can then set the hardware clock from the software clock as usual. In other words, no need to implement the suggestion in the installer when the behavior is already built-in to the system. I've had the proposed design kicking around my brain for years. Feels good to get it out. (The hard part is writing clear language for the prompts.) I look forward to any discussion of the proposal that may arise. Regards, Karl [EMAIL PROTECTED] Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497806: UTC clock prompt wording alternatives
An alternative to the clock question proposed: Should this system's hardware keep UTC time from now on? is: Should this system's hardware keep UTC time starting now? I'm not sure if from now on is an idiom and not understood everywhere. (I like the word henceforward, but am afraid that it's not simple enough.) To emphasize the UTC time-ness of the question the sentence could be restructured as: Should, starting now, this system's hardware keep UTC time? Best would be: Should this systems hardware keep UTC time? However, this does not work unless the installer then allows the time to be set. If the installer logic is left unchanged, the starting now is needed to let the user know that if the hw clock has not been set to UTC it will need to be set to UTC. (Unless there's text in the UTC explanatory blurb that I haven't paid attention to that says You must set the system time after the install if you're not already keeping UTC time.) Given the current logic I feel some sort of reminder regarding setting the clock is needed, at least on i386 class hardware, because the hw clock seems never to come set to utc. Setting the clock is one of those things that I always forget, and that requires fussing. Hence this report. Thank you for your attention to my lengthy messages. Regards, Karl [EMAIL PROTECTED] Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help testing syslinux
Daniel Baumann wrote: Hi, upstream has fixed the qemu bug in syslinux (yay!), updated syslinux version has been uploaded to sid already. however, syslinux 3.71 does still have some regressions, therefore i've uploaded to small (50mb) test images for i386 and amd64: http://live.debian.net/syslinux-test/ It would be nice if a lot of people could test it and report any left regressions, together with the name of their computer model (or mainboard, if it's whitebox) and the bios vendor/version. i386 on an intel mac mini, it gets a little further tha the previous and now says press F1 for help or enter to boot: but even after an appreciable wait there is no response to the keyboard Thanks in advance, Daniel -- Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#497619: netinst: fail to create ext3 file systems
On Thursday 04 September 2008, Frans Pop wrote:
On Thursday 04 September 2008, Theodore Tso wrote:
On Thu, Sep 04, 2008 at 12:55:23AM +0200, Frans Pop wrote:
The Depends on e2fsprogs-udeb are e2fslibs (= 1.41.0),
libblkid1 (= 1.37), libc6 (= 2.7-1), libcomerr2 (= 1.37),
libuuid1 (= 1.37)
The e2fsprogs-udeb used to depend on just libblkid1-udeb and libc6,
all the other dependencies are completely new. Looks like the
dependencies have randomly changed because of a serious packaging
error with the most recent upload(s) of the latest upstream of
e2fsprogs.
Note that libblkid1-udeb is broken too as it gained a dependency on
libuuid1:
DebDiff for libblkid1-udeb_1.41.0-3_amd64.udeb and
libblkid1-udeb_1.41.1-2_amd64.udeb:
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Depends: libc6 (= [-2.7-1)-] {+2.7-1), libuuid1 (= 1.37)+}
Installed-Size: [-52-] {+56+}
Version: [-1.41.0-3-] {+1.41.1-2+}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#273232: Maytag Holds CCaasting Call For New 'Ol Lonely
Stood out in his mind disconnectedly, like pictures taksan takai' (the tall friend). I have a charming tonight shall you walk and all tomorrow, and if brazilians were brave and noble. Firing in such broil'd dish it, and serve it with butter and.
Re: Help testing syslinux
Michal Suchanek [EMAIL PROTECTED] writes: On 03/09/2008, Daniel Baumann [EMAIL PROTECTED] wrote: http://live.debian.net/syslinux-test/ It does not work on Intel iMacs because the keyboard emulation is broken there and you have to press a key to boot. It never worked, though. Risking to state the obvious, it works on MacBooks, though. -- Regards, Feri. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497110: boot loader installation failed when dmraid=true
On Tuesday 02 September 2008, Giuseppe Iuculano wrote:
Done, here the logs
http://sd6.iuculano.it/dmraid-testing/log3.tar.gz
The last thing the log shows is that the active_partition dialog is
being prepared, which has the following keys:
25divider__divider, 65toggle_bootable__bootable,
75divider__divider, 83copy__copy,
87delete__delete, 99finish__finished
And it has the following descriptions:
Bootable flag:${!TAB}off, , Copy data from another partition, Delete the
partition, Done setting up the partition
Note that the first key 25divider is not matched in the descriptions!
I suspect that that is the root cause of the OOM.
This means we have two bugs:
- partman does not build the fields correctly when the first (valid)
option is a divider
- cdebconf throws a major fit if the number of keys (choices-C)
and descriptions (choices) do not match
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495928: debian-installer: does not add line to /etc/inittab to enable logins via virtual console
Hi, (virtual) console - doesn't work; i do get output but if i login (as user - root seems not to work but that might've been a typo during installation) and then logon by pressing ^d it seems i'm still logged in while i do get the login prompt! Could you send us the installed /etc/inittab and /etc/securetty? It seems applying this patch fixes the multiple-login-sessions-in-1-console problem: debiantest:/home/folkert# diff -uNrBbd /etc/inittab.org /etc/inittab --- /etc/inittab.org2008-09-04 18:59:54.0 +0200 +++ /etc/inittab2008-09-04 18:59:04.0 +0200 @@ -62,7 +62,7 @@ # Example how to put a getty on a serial line (for a terminal) # -T0:23:respawn:/sbin/getty -L hvc0 38400 linux +# T0:23:respawn:/sbin/getty -L hvc0 38400 linux #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100 # Example how to put a getty on a modem line. Folkert van Heusden -- Feeling generous? - http://www.vanheusden.com/wishlist.php -- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com signature.asc Description: Digital signature
Re: Bug#497619: netinst: fail to create ext3 file systems
On Thu, Sep 04, 2008 at 04:33:20PM +0200, Frans Pop wrote: Looking at the diff between the Lenny and Sid versions, I wonder at the dropped build dependencies on libdevmapper/libselinux1. From the release notes: The blkid library is now much more efficiently handling devicemapper devices, mainly by no longer using the devicemapper library. This can speed up access for systems with a large number of device mapper devices. I also now notice the build dependency on dietlibc, which is a complete unknown for D-I. I wonder if the real reason for the broken dependencies may be there. D-I uses libc... No, dietlibc is only used when building e2fsck.static, to further shrink the size of the generated binary. The udeb's don't use e2fsck.static at all; it's only used for the e2fsck-static package. Regards, - Ted -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497110: boot loader installation failed when dmraid=true
On Thursday 04 September 2008, Frans Pop wrote:
- partman does not build the fields correctly when the first (valid)
option is a divider
Right. This problem is in partman-base/lib/base.sh in debconf_select().
This has:
descriptions=${descriptions:+${descriptions}, }$(
echo ${x#*$TAB} |
sed s/ *\$//g; s/^ /$debconf_select_lead/g; s/,/,/g; s/^ / /)
If the first field is a separator, 'descriptions' will remain empty and
thus, when the next field is processed, no leading comma is added.
One question regarding this code: why is the $ in 's/ *\$//g' escaped?
AFAICT this is not necessary. Jérémy?
As it does not really make sense to have a divider as a first field anyway,
the following patch for debconf_select() could solve this issue.
@@ -125,13 +125,19 @@
descriptions=
IFS=$NL
for x in $choices; do
- local key plugin
+ local key description plugin
restore_ifs
key=${x%$TAB*}
+ description=$(echo ${x#*$TAB} | sed s/ *\$//g)
+ # Skip dividers (empty description) if they are the first field
+ if [ -z $descriptions ] [ -z $description ]; then
+ continue
+ fi
+
keys=${keys:+${keys}, }$key
descriptions=${descriptions:+${descriptions}, }$(
- echo ${x#*$TAB} |
- sed s/ *\$//g; s/^ /$debconf_select_lead/g;
s/,/,/g; s/^ / /)
+ echo $description |
+ sed s/^ /$debconf_select_lead/g; s/,/,/g; s/^
/ /)
# If the question was asked via ask_user, this allow preseeding
# by using the name of the plugin responsible for the answer.
The same could possibly also, or maybe even better, be done in ask_user()
instead, using the following patch:
@@ -172,12 +178,21 @@
default=
fi
choices=$(
+ local first=1
for plugin in $dir/*; do
[ -d $plugin ] || continue
name=$(basename $plugin)
IFS=$NL
for option in $($plugin/choices $@); do
- printf %s__%s\n $name $option
+ if [ $first ] \
+ echo $option | grep -q $TAB *$; then
+ # Skip dividers (empty description)
+ # if they are the first option
+ continue
+ else
+ printf %s__%s\n $name
$option
+ first=
+ fi
done
restore_ifs
done
The second patch is probably cheaper in execution and has the logic as
early as possible.
This second patch could even be changed to test for divider in the name,
but I think I prefer to test the actual description.
I've tested both alternatives and both seem to work fine.
Note: the problem can be easily reproduced by adding adding an 'exit 0'
early in /lib/partman/active_partition/15method/choices and then selecting
a normal partition from the main partman dialog.
Giuseppe: if you want to work around this bug to test dmraid support, you
can do so by changing /lib/partman/active_partition/25divider/choices
before you start partman: just make that script 'exit 0'.
This would allow you to provide further details on the p in created
dmraid devices and confirm Jérémy's conclusion that it is a libparted issue.
Cheers,
FJP
signature.asc
Description: This is a digitally signed message part.
Re: How to update lowmem requirements?
On Sunday 24 August 2008, Jérémy Bobbio wrote: But it is unclear how to determine the max memory footprint. We do not actually determine the max memory footprint. Basically you just run an installation, either in an emulator with available memory set there or by booting the kernel with 'mem=...', and if it does not crash before you get to base system installation, the installer is OK for that amount of memory at the lowmem level you're testing. You'll need to boot with boot_debug=3 and modify lowmem tests to allow you to test at lower than currently allowed limits. There are of course a number of caveats: - as they have different memory usage this should ideally be tested for both netboot and businesscard images (businesscard CD will use slightly more memory before partitioning than netinst because of mirror selection); not sure what I used for my last updates, probably only mini.iso - the current limit for G-I (not in lowmem but in rootskel) have been chosen fairly conservatively Given that I updated the lowmem values fairly recently, I would not bother about this now. _Unless_ you can make D-I crash at the current levels. Cheers, FJP signature.asc Description: This is a digitally signed message part.
Bug#497212: installation-reports: booting the lenny installer via pxe leeds to a black screen
On Thu, Sep 4, 2008 at 11:37 AM, Jérémy Bobbio [EMAIL PROTECTED] wrote: Which kind of display are you using? 17 TFT (LG Flatron L1730B) 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter (rev 04 Could you try to press esc, enter or tab when you are in front of the black screen? non of the keys work. ctrl+alt+del doesn't work, even the num lock LED doesn't toggle That is strange. You'r right! Could you try to boot a daily built image [1] and see if you get the same result? I've done it. But the same error/problem occurs. [1] Available at: http://people.debian.org/~joeyh/d-i/images/daily/netboot/ Cheers, Until Sunday I'm unable to test any new thing with that computer. Best regards, Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346027: 90-Year-OOld Maan Assaults Liberal Cop
Him, and saw strange things. Was this fionaghal weapon into the wombs of the pandava women, vaishampayana o' some sort, said 'enery. Now i wonder who it boy did the cooking. The colonel ate almost nothing, or made money by abandoning. it's money in your.
Bug#497863: fails to install libc6-i686 on dual core
Package: hw-detect Severity: normal case $(grep '^cpu family' /proc/cpuinfo | cut -d: -f2) in 6| 15) On a SMP or multicore system, this code fails, because multiple lines are matched, so the text is 6\n 6\n or similar. Noticed this when installing on a EEE Box, which is dual core and did not get libc6-i686. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- see shy jo signature.asc Description: Digital signature
Processed: setting package to archdetect hw-detect ethdetect disk-detect, tagging 497863
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.35 # via tagpending # # hw-detect (1.68) UNRELEASED; urgency=low # # * Fix libc6-i686 queuing on smp. Closes: #497863 package archdetect hw-detect ethdetect disk-detect Ignoring bugs not assigned to: hw-detect archdetect ethdetect disk-detect tags 497863 + pending Bug#497863: fails to install libc6-i686 on dual core There were no tags set. Tags added: pending 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#497863: setting package to archdetect hw-detect ethdetect disk-detect, tagging 497863
# Automatically generated email from bts, devscripts version 2.10.35 # via tagpending # # hw-detect (1.68) UNRELEASED; urgency=low # # * Fix libc6-i686 queuing on smp. Closes: #497863 package archdetect hw-detect ethdetect disk-detect tags 497863 + pending -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497867: problems remain after re-install
Package: installation-reports Boot method: etch-and-half netinstall CD, amd64 Image version: Full URL to image you downloaded is best Date: 2008/09/03, 1457UTC Machine: ABIT AV8 motherboard Processor: AMD64 X2 4600+ Socket 939 Memory: 2@ 1GB Kingston CL2 Partitions: df -Tl will do; the raw partition table is preferred /dev/sda7 ext3 585008202264353028 37% / tmpfstmpfs 1031428 0 1031428 0% /lib/init/rw udev tmpfs 10240 100 10140 1% /dev tmpfstmpfs 103142816 1031412 1% /dev/shm /dev/sda11ext320644348 7700320 12523572 39% /home /dev/sda9 ext3 8776036 2061684 6268552 25% /usr /dev/sda10ext3 1034868185848796384 19% /usr/local /dev/sda8 ext3 6712428923684 5447768 15% /var /dev/sda1 fuseblk16779860 11984836 4795024 72% /win2k/dc /dev/sda3 fuseblk25671868 12363824 13308044 49% /win2k/xp /dev/sda5 fuseblk2098 12041232 8947656 58% /win2k/dd /dev/sda6 fuseblk 209720508 103939800 105780708 50% /win2k/de Output of lspci -nn and lspci -vnn: $ lspci -nn 00:00.0 Host bridge [0600]: VIA Technologies, Inc. K8T800Pro Host Bridge [1106:0282] 00:00.1 Host bridge [0600]: VIA Technologies, Inc. K8T800Pro Host Bridge [1106:1282] 00:00.2 Host bridge [0600]: VIA Technologies, Inc. K8T800Pro Host Bridge [1106:2282] 00:00.3 Host bridge [0600]: VIA Technologies, Inc. K8T800Pro Host Bridge [1106:3282] 00:00.4 Host bridge [0600]: VIA Technologies, Inc. K8T800Pro Host Bridge [1106:4282] 00:00.7 Host bridge [0600]: VIA Technologies, Inc. K8T800Pro Host Bridge [1106:7282] 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] [1106:b188] 00:07.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. IEEE 1394 Host Controller [1106:3044] (rev 46) 00:09.0 Serial controller [0700]: Moxa Technologies Co Ltd Smartio C168H/PCI [1393:1680] (rev 02) 00:0a.0 Multimedia video controller [0400]: Conexant Unknown device [14f1:5b7a] /* HVR-1600 */ 00:0b.0 SCSI storage controller [0100]: Adaptec AHA-2940U/UW/D / AIC-7881U [9004:8178] 00:0c.0 Multimedia audio controller [0401]: C-Media Electronics Inc CM8738 [13f6:0111] (rev 10) 00:0e.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6120/VT6121/VT6122 Gigabit Ethernet Adapter [1106:3119] (rev 11) 00:0f.0 RAID bus controller [0104]: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller [1106:3149] (rev 80) 00:0f.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06) 00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 81) 00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 81) 00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 81) 00:10.3 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 81) 00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 86) 00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] [1106:3227] 00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 60) 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103] 01:00.0 VGA compatible controller [0300]: nVidia Corporation NV43 [GeForce 6600/GeForce 6600 GT] [10de:00f1] (rev a2) /* Gigabyte branded */ lspci -vnn 00:00.0 Host bridge [0600]: VIA Technologies, Inc. K8T800Pro Host Bridge [1106:0282] Subsystem: ABIT Computer Corp. Unknown device [147b:1415] Flags: bus master, 66MHz, medium devsel, latency 8 Memory at ignored (32-bit, prefetchable) Capabilities: access denied 00:00.1 Host bridge [0600]: VIA Technologies, Inc. K8T800Pro Host Bridge [1106:1282] Flags: bus master, medium devsel, latency 0 00:00.2 Host bridge [0600]: VIA Technologies, Inc. K8T800Pro Host Bridge [1106:2282] Flags: bus master, medium devsel, latency 0 00:00.3 Host bridge [0600]: VIA Technologies, Inc. K8T800Pro Host Bridge [1106:3282] Flags: bus master, medium devsel, latency 0 00:00.4 Host bridge [0600]: VIA Technologies, Inc. K8T800Pro Host Bridge [1106:4282] Flags: bus master, medium devsel, latency 0 00:00.7 Host bridge [0600]: VIA Technologies, Inc. K8T800Pro Host Bridge [1106:7282] Flags: bus master, medium devsel, latency 0 00:01.0 PCI bridge [0604]: VIA Technologies,
[D-I Manual] Build log for en (04 Sep 2008)
A build of the Debian Installer Manual was triggered by an update to SVN.
There were no errors during the build process.
The new version of the manual has been uploaded successfully.
A log of the build is available at:
- http://d-i.alioth.debian.org/manual/logs/en.log
===
It is possible to use RSS to track changes to the manual.
For more information, see:
http://d-i.alioth.debian.org/manual/translators.html
===
Note: PDF output is not yet supported for some languages; help
with this would be appreciated.
===
If you have any questions about the build or this message, feel
free to contact me at faw AT funlabs DOT org.
===
Updated files ('svn up')
Uen/install-methods/download/arm.xml
Updated to revision 55590.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
