Bug#684283: marked as done (the Hyper-V kernel modules ( as minimum, hv_vmbus hv_utils hv_storvsc hv_netvsc ) are missing in the current installer image of Debian Wheezy)
Your message dated Sun, 02 Dec 2012 10:24:39 + with message-id 50bb2c67.8000...@debianpt.org and subject line has caused the Debian Bug report #684283, regarding the Hyper-V kernel modules ( as minimum, hv_vmbus hv_utils hv_storvsc hv_netvsc ) are missing in the current installer image of Debian Wheezy 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 ow...@bugs.debian.org immediately.) -- 684283: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/wheezy_d-i/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso Date: 2012-08-08 Machine: virtual computer ( guest ) on Hyper-V Processor: Memory: Partitions: Base System Installation Checklist: [O] = OK, [E] = error, [ ] = not testing Initial boot: [O ] Detect network card:[ E] Configure network: [E] Detect CD: [ ] Load installer modules: [E] Detect hard drives: [ E] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Hi! and on Image version: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-kde-CD-1.iso and on Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso the Hyper-V kernel modules ( as minimum, hv_vmbus hv_utils hv_storvsc hv_netvsc ) are missing in the current installer image of Debian Wheezy Best regards, Victor Miasnikov Blog: http://vvm.blog.tut.by/ P.S. And see: http://lists.debian.org/debian-boot/2012/06/msg00485.html == To: debian-boot@lists.debian.org Subject: Wheezy nightly build (netinst / businesscard) can't find disk drive on Hyper-V VMs From: Oskar Senft debian(at)senft-net(dot)com Date: Tue, 19 Jun 2012 18:27:22 +0200 Message-id: 4fe0a86a.8020...@senft-net.com Hi I just tried to use the nightly build of netinst and businesscard of Wheezy on a virtual machine running on Hyper-V. The problem is that the the driver for the (virtual) hard disks is not loaded. As far as I can tell this is due to the fix for bug #661318, which now causes the ata_piix to no longer load on Hyper-V because the hv_storvsc should be used instead. However, the Hyper-V kernel modules (hv_storvsc et al) are missing in the current netinst and businesscard installer image for AMD64 - I did not check on x86 or any other installer type. From what I can tell the following kernel module should be part of the installer to support installation on Hyper-V virtual machines: /lib/modules/3.2.0-2-amd64/kernel/drivers/net/hyperv/hv_netvsc.ko /lib/modules/3.2.0-2-amd64/kernel/drivers/scsi/hv_storvsc.ko /lib/modules/3.2.0-2-amd64/kernel/drivers/hv /lib/modules/3.2.0-2-amd64/kernel/drivers/hv/hv_vmbus.ko /lib/modules/3.2.0-2-amd64/kernel/drivers/hv/hv_utils.ko I'd be happy to raise a bug on this, but I wanted to check first if this is a know problem. Google and the debian-boot archives don't know anything about it. What's the correct procedure to raise bugs on the installer? Thanks Oskar. == ---End Message--- ---BeginMessage--- Closing as the bug submitter tested with the image: 2012-11-30 debian-testing-amd64-netinst.iso SHA1 b544066bbdd40c4a561007064dafc359a750e4e4 and reports that it's fixed. -- Melhores cumprimentos/Best regards, Miguel Figueiredo---End Message---
Re: Launchpad: Merge of Accounts Requested
On Sun, Dec 02, 2012 at 05:24:49AM -, Launchpad Account Merge wrote: Launchpad: request to merge accounts Someone has asked us to merge one of your Launchpad accounts with another. If you go ahead, this will merge the account called 'Debian Install System Team (debian-boot)' into the account 'alan-ar06'. To confirm you want to do this, please follow this link: https://launchpad.net/token/sglK1tJNkPZzZHhHdpfn If you didn't ask to merge these accounts, please either ignore this email or report it to the Launchpad team: feedb...@launchpad.net You can read more about merging accounts in our help wiki: https://help.launchpad.net/YourAccount/Merging So this request went into the public mailing list records, which is a tad insane… Kind regards Philipp Kern signature.asc Description: Digital signature
Re: Bug#694803: Wheezy beta4 installation report
Hi all, tl;dr: CRT monitor working freqs we're not correctly auto-detected and screen went black. Which component is responsible for screen auto-detection? -- Melhores cumprimentos/Best regards, Miguel Figueiredo -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50bb2fba.3050...@debianpt.org
Bug#694803: Wheezy beta4 installation report
On Fri, Nov 30, 2012 at 13:46:00 +, Barry Tennison wrote: Install went fine (grub installed) until first reboot (at end of installation process) Then had two problems which I've seen before, and I think people should be given workarounds for them if the installer can't cope with them. Please send the output of 'dmesg' after booting with the drm.debug=6 kernel parameter. Cheers, Julien signature.asc Description: Digital signature
Bug#694777: Wheezy Beta4 installs but X server unusable
Em 01-12-2012 07:23, Christian PERRIER escreveu: Quoting Brian Potkin (claremont...@gmail.com): Perhaps the installer could warn the user if her video card is among those listed in AtiHowTo and the installer doesn't see the firmware supplied somewhere by the user. Perhaps just a referral to the wiki page ? Didn't the installer ask for RV610_pfp.bin to be supplied? Logically, no. Firmware for video cards is none of the installer's business. Of coure, from the user point of view, all this is related, but from the logical organisation of packages, it is not. Unless I missed something somewhere (which is possible), we focus out firmware-related attention on network cards. Although not mandatory for installation IMHO this could fit in hw-detect. -- Melhores cumprimentos/Best regards, Miguel Figueiredo -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50bb4294.8020...@debianpt.org
Bug#694582: marked as done (installation report Beta-4)
Your message dated Sun, 02 Dec 2012 12:23:43 + with message-id 50bb484f.4020...@debianpt.org and subject line has caused the Debian Bug report #694582, regarding installation report Beta-4 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 ow...@bugs.debian.org immediately.) -- 694582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: netinstall, dd'ed to USB stick, text mode Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta4/i386/iso-cd/debian-wheezy-DI-b4-i386-netinst.iso Date: 25-NOV-2012 20:00 GMT Machine: Toshiba Satellite A100 Processor: Intel Core2 duo Memory: 3GByte Partitions: for Windows XP, Xubuntu and swap Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [0] Detect network card:[E/O] (see below) Configure network: [0] Detect CD: [0] Load installer modules: [0] Detect hard drives: [0] Partition hard drives: [0] Install base system:[0] Clock/timezone setup: [0] User/password setup:[0] Install tasks: [0] Install boot loader:[O] Overall install:[O] Comments/Problems: This time, I tried to install through WLAN, which requires iwlwifi-3945 firmware. I tried to provide it in a second partition of the USB stick used for the installation, or on a second USB stick, but the installer did not find it. Only after I manually mounted the stick,the firmware was found and loaded, and the rest of the installation, like the WLAN configuration and the XFCE desktop, went like a charm. Great! Googling for debian installation firmware turned up lots of pages with mostly contradicting information how to provide the firmware, so I tied archives: deb, tar, and zip, and the unpacked firmware files iwlwifi-3945-1.ucode and iwlwifi-3945-2.ucode, on a vfat or ext2 file system, in the root directory of the stick or in a subdirectory named firmware. In the log, there were warnings about utf-8 not being an appropriate mount option for vfat, when the installer tried to mount various partitions (sdb1, sdb2) and the device sdb itself, but did not find the firmware. Thanks for the good work Herbert -- ---End Message--- ---BeginMessage--- Fixed in #694082. -- Melhores cumprimentos/Best regards, Miguel Figueiredo---End Message---
Bug#694934: Installer hangs at detect network hardware
Package: installation-reports Boot method: From DVD image Image version: debian-wheezy-DI-b4-amd64-DVD-1.iso Date: 2012-12-01 Machine: Self-build around Asrock X58 motherboard Processor: Intel i7-920 Memory: 6GB DDR3 Partitions: see attachment df_Tl.out Output of lspci: see attachment lspci_knn.out Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] 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:[E] Comments/Problems: I chose: Advanced options Alternative desktop environments Xfce Advanced options Expert install and answered questions about language, keyboard, locale (default), modules to load (default), extra installer components (none). At the next stage Detect network hardware the installation stalled indefinitely (more than ten minutes) with a blue screen having a single white line at the bottom and a black cursor. Keyboard input was echoed to this bottom line, but I was unable to get any other response from the system and was obliged to use the machine's power on/off switch. On a second attempt, the installation progressed to completion when I skipped the steps Detect network hardware Configure the network Configure the clock although I was then left with an unusable system owing to the absence of the necessary Radeon firmware (see bug #692001 for example). Using a live rescue CD and accessing the internal hard disk via chroot it was possible to achieve network connectivity by manually setting up files /etc/network/interfaces and /etc/resolv.conf, whereupon I could install the package firmware-linux-nonfree and finally obtain a working graphical display. Mike Thomas Filesystem Type 1K-blocks Used Available Use% Mounted on rootfs rootfs 949052564 2748460 898094952 1% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 554628 724553904 1% /run /dev/disk/by-uuid/2ffea0c7-27f0-42f4-b5ab-a46796122a63 ext4 949052564 2748460 898094952 1% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 3624600 0 3624600 0% /run/shm 00:00.0 Host bridge [0600]: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port [8086:3405] (rev 12) Subsystem: ASRock Incorporation Device [1849:3405] 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 12) Kernel driver in use: pcieport 00:05.0 PCI bridge [0604]: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 5 [8086:340c] (rev 12) Kernel driver in use: pcieport 00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 [8086:340e] (rev 12) Kernel driver in use: pcieport 00:09.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 9 [8086:3410] (rev 12) Kernel driver in use: pcieport 00:10.0 PIC [0800]: Intel Corporation 5520/5500/X58 Physical and Link Layer Registers Port 0 [8086:3425] (rev 12) 00:10.1 PIC [0800]: Intel Corporation 5520/5500/X58 Routing and Protocol Layer Registers Port 0 [8086:3426] (rev 12) 00:14.0 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers [8086:342e] (rev 12) Kernel driver in use: i7core_edac 00:14.1 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers [8086:3422] (rev 12) 00:14.2 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers [8086:3423] (rev 12) 00:14.3 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers [8086:3438] (rev 12) 00:1a.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a37] Subsystem: ASRock Incorporation Device [1849:3a37] Kernel driver in use: uhci_hcd 00:1a.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a38] Subsystem: ASRock Incorporation Device [1849:3a38] Kernel driver in use: uhci_hcd 00:1a.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a39] Subsystem: ASRock Incorporation Device [1849:3a39] Kernel driver in use: uhci_hcd 00:1a.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 [8086:3a3c] Subsystem: ASRock Incorporation Device
Bug#694771: installation-reports: s390x installer creates invalid /etc/network/interfaces
On Fri, Nov 30, 2012 at 03:09:43PM +0100, Philipp Kern wrote: Could you please send us /var/log/installer/syslog (probably needs to be compressed with gzip before sending)? To be precise: From the installed system. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#694934: Installer hangs at detect network hardware
On Sun 02 Dec 2012 at 12:22:50 +, R.M. Thomas wrote: Comments/Problems: I chose: Advanced options Alternative desktop environments Xfce Advanced options Expert install and answered questions about language, keyboard, locale (default), modules to load (default), extra installer components (none). At the next stage Detect network hardware the installation stalled indefinitely (more than ten minutes) with a blue screen having a single white line at the bottom and a black cursor. Keyboard input was echoed to this bottom line, but I was unable to get any other response from the system and was obliged to use the machine's power on/off switch. Ctrl-C should get you back to the main menu. Please look at #694582 and see if it helps. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121202153043.GA5828@desktop
Bug#694722: eMachines eM355, encrypted boots off pendrive, preseeding fails
Hello Brian,
thanks for responding.
On 2012-Nov-30 18:54 (+), Brian Potkin wrote with possible deletions:
[gunzip boot.img.gz /dev/sdb = failed]
This works for me.
[gunzip boot.img.gz /dev/sdb1 = GRUB error]
This would not work because the MBR is not written to. There is nothing
in it to say how to boot.
I think you may have your comments on the two techniques the wrong way
round. Also, it is SYSLINUX which does the booting, not GRUB. Did you
really get a screen with GRUB displayed at the top?
Ok, I'm retrying this right now:
# gunzip boot.img.gz /dev/sdb
# mount /dev/sdb /media/sdb
# cp debian-wheezy-DI-b4-amd64-netinst.iso /media/sdb
# umount /media/sdb
When I plug the pendrive into the target machine, it hangs. No
boot-menu, just a blinking cursor. Now let me retry the other version:
# dd if=/dev/zero of=/dev/sdb
# fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF
disklabel
Building a new DOS disklabel with disk identifier 0x1b9f17d2.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.
Warning: invalid flag 0x of partition table 4 will be corrected by
w(rite)
Command (m for help): p
Disk /dev/sdb: 4025 MB, 4025810432 bytes
124 heads, 62 sectors/track, 1022 cylinders, total 7862911 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1b9f17d2
Device Boot Start End Blocks Id System
Command (m for help): n
Partition type:
p primary (0 primary, 0 extended, 4 free)
e extended
Select (default p): p
Partition number (1-4, default 1):
Using default value 1
First sector (2048-7862910, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-7862910, default 7862910):
Using default value 7862910
Command (m for help): p
Disk /dev/sdb: 4025 MB, 4025810432 bytes
124 heads, 62 sectors/track, 1022 cylinders, total 7862911 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1b9f17d2
Device Boot Start End Blocks Id System
/dev/sdb12048 7862910 3930431+ 83 Linux
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
# gunzip boot.img.gz /dev/sdb1
# mount /dev/sdb1 /media/sdb1
# cp debian-wheezy-DI-b4-amd64-netinst.iso /media/sdb1
# umount /media/sdb1
Ok, pendrive goes to target machine again. Nothing happens this time,
just a blinking cursor in the top left corner, just as above. No boot
menu, no GRUB. So you were right:
This would not work because the MBR is not written to. There is nothing
in it to say how to boot.
It is hard for me now to figure out what happened last time, when I've
seen the GRUB error message. I'm sure it was GRUB, because I ended up
in it's rescue mode. Would it be possible that a GRUB survived
somewhere else on the target machine's harddisk from a previous install,
and the BIOS fell back to launch that one, since nothing was found on
the pendrive's MBR? Anyways, since I cannot reproduce it, it's not a
bug.
So I try the preseeding as you told me, using a new partition on the
pendrive I've set up with
# dd if=debian-wheezy-DI-b4-amd64-netinst.iso of=/dev/sdb
Pretty awesome! The installer seems to ignore the ESSID I've set
for wifi, but that's the only issue I can put my finger on. I'm pretty
happy.
Is there a definitive documentation of the syntax, semantics, and
possible values I can put in my `preseed.cfg`?
Thank you!
Stefan
--
Stefan Klinger o/klettern
/\/ bis zum
send plaintext only - max size 32kB - no spam \ Abfallen
http://stefan-klinger.de
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121202160635.GC7117@bellbird
Bug#694934: Installer hangs at detect network hardware
On 02/12/12 15:30, Brian Potkin wrote: On Sun 02 Dec 2012 at 12:22:50 +, R.M. Thomas wrote: Comments/Problems: I chose: Advanced options Alternative desktop environments Xfce Advanced options Expert install and answered questions about language, keyboard, locale (default), modules to load (default), extra installer components (none). At the next stage Detect network hardware the installation stalled indefinitely (more than ten minutes) with a blue screen having a single white line at the bottom and a black cursor. Keyboard input was echoed to this bottom line, but I was unable to get any other response from the system and was obliged to use the machine's power on/off switch. Ctrl-C should get you back to the main menu. I did thump some random keys, but probably didn't try Ctrl-C. Thanks for the tip, I'll remember that for next time. Please look at #694582 and see if it helps. In my case, the stall at Detect network hardware may not to be a firmware issue. After I had set up the configuration files /etc/network/interfaces and /etc/resolv.conf the commands ifdown and ifup successfully controlled the eth0 port with no need for me to install manually any packages (drivers or firmware). I did need the package firmware-linux-nonfree in order to get the video card working, but I assume that was a unrelated problem. Mike -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50bb8938.9070...@sciolus.org
Bug#694965: netcfg: Allow setup of pointopoint routes to reach gateway
Package: netcfg Severity: wishlist Please add the possibility to specify pointopoint routes when setting up the networking in the Debian Installer. The result would look like something like this: iface eth0 inet static address a.b.c.d netmask 255.255.255.255 gateway e.f.g.h pointopoint e.f.g.h Afterwards this routing would look like: root@alpha:~# ip route default via e.f.g.h dev eth0 e.f.g.h dev eth0 proto kernel scope link src a.b.c.d root@alpha:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 e.f.g.h 0.0.0.0 UG0 00 eth0 e.f.g.h 0.0.0.0 255.255.255.255 UH0 00 eth0 At the moment I don't know of any other way to configure this besides skipping the network confguration at installation time and then doing a manual network configuration afterwards. Or is there some other option that I'm just not aware of? With the growing shortage of IPv4 adress space this will probably become more and more common. At least for one large hoster in Germany this is already the standard mode of operation if you want to have more then one IP address (for virtual machines for example). Cheers Mike -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50bba162.3020...@neuffer.com
Processed: Re: Bug#694928: config-file change on /etc/default/rcS
Processing control commands: reassign -1 flash-kernel Bug #694928 [initscripts] asks for confirmation on config-file change on /etc/default/rcS, while file didn't change Bug reassigned from package 'initscripts' to 'flash-kernel'. No longer marked as found in versions sysvinit/2.88dsf-34. Ignoring request to alter fixed versions of bug #694928 to the same values previously set -- 694928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b694928.135447510624835.transcr...@bugs.debian.org
Processed: 694928: flash-kernel: postinst modifies /etc/default/rcS
Processing commands for cont...@bugs.debian.org: retitle 694928 flash-kernel: postinst modifies /etc/default/rcS Bug #694928 [flash-kernel] asks for confirmation on config-file change on /etc/default/rcS, while file didn't change Changed Bug title to 'flash-kernel: postinst modifies /etc/default/rcS' from 'asks for confirmation on config-file change on /etc/default/rcS, while file didn't change' found 694928 3.3 Bug #694928 [flash-kernel] flash-kernel: postinst modifies /etc/default/rcS Marked as found in versions flash-kernel/3.3. thanks Stopping processing here. Please contact me if you need assistance. -- 694928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.135447564829004.transcr...@bugs.debian.org
Bug#694928: [Pkg-sysvinit-devel] Bug#694928: config-file change on /etc/default/rcS
[Ivo De Decker] The postinst from flash-kernel contains this: # Stop fsck from prompting the user for input since most users don't # have a serial console. sed -i s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/rcS || true So this bug should be reassigned. Of course, this bug was introduced when sysvinit changed /etc/default/rcS from a non-conffile to a conffile. Before this change, /etc/default/rcS was copied into place on first time installation, and never updated using dpkg. This was done like this to avoid any conffile questions during upgrades. At the moment with /etc/default/rcS as a conffile, there is no way for flash-kernel to do what it want in a policy compliant way. :( The only way to make that happen is for sysvinit to provide a mechanism to edit the file, or to convert the file back to being a non-conffile. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121202192253.gc27...@ulrik.uio.no
Bug#694965: netcfg: Allow setup of pointopoint routes to reach gateway
There already seems to be some code in static.c like the code below, but
it doesn't seem to be working
Manual configuration always only cycles through the following requests:
IP Address
Mask
Gateway
then it seems to try to configure the network and complains about an
unreachable gateway.
Instead I'd expect it to pop up the query for the pointopoint link.
Sometimes you can even trigger netcfg tp pop up a dialog box which shows
the network config overview and there it is obvious that there is a
unfilled pointopoint variable.
So this is rather a bug to be fixed then a wishlist item.
Please fix.
Thank you.
Cheers
Mike
static int netcfg_get_pointopoint(struct debconfclient *client, struct
netcfg_interface *interface)
{
int ret, ok = 0;
union inX_addr addr;
while (!ok) {
debconf_input(client, critical, netcfg/get_pointopoint);
ret = debconf_go(client);
if (ret)
return ret;
debconf_get(client, netcfg/get_pointopoint);
if (empty_str(client-value)) { /* No P-P is ok */
interface-pointopoint[0] = '\0';
return 0;
}
ok = inet_pton (interface-address_family, client-value, addr);
if (!ok) {
debconf_capb(client);
debconf_input (client, critical, netcfg/bad_ipaddress);
debconf_go (client);
debconf_capb(client, backup);
}
}
inet_ntop(interface-address_family, addr, interface-pointopoint,
NETCFG_ADDRSTRLEN);
return 0;
}
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50bbb1d9.3020...@neuffer.com
Bug#694928: asks for confirmation on config-file change on /etc/default/rcS, while file didn't change
clone 694928 -1 reassign -1 initscripts thanks On Sun, Dec 02, 2012 at 12:23:07PM +0100, Martin Zobel-Helas wrote: Please find attached an example patch for flash-kernel to support old and new (rcS and fsck) locations for FSCKFIX as discussed on #debian-devel earlier. Please don't apply it just yet--we'll presumably need to get approval from the release team to change this in initscripts at the same time. I'll have a patch for initscripts shortly; might be a bit later in the week to allow for comprehensive testing. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121202234737.gt14...@codelibre.net
Bug#694928: asks for confirmation on config-file change on /etc/default/rcS, while file didn't change
On Sun, Dec 02, 2012 at 11:47:37PM +, Roger Leigh wrote: clone 694928 -1 reassign -1 initscripts thanks On Sun, Dec 02, 2012 at 12:23:07PM +0100, Martin Zobel-Helas wrote: Please find attached an example patch for flash-kernel to support old and new (rcS and fsck) locations for FSCKFIX as discussed on #debian-devel earlier. Hmm, actually attached now. -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 From 300eb0dcd6abc4ced0596f87a33d3165d46779e5 Mon Sep 17 00:00:00 2001 From: Roger Leigh rle...@debian.org Date: Sun, 2 Dec 2012 23:34:57 + Subject: [PATCH] debian: Update /etc/default/fsck in flash-kernel-installer postinst --- debian/changelog | 10 ++ debian/flash-kernel-installer.postinst |7 ++- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index 68c673b..526f1ec 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,13 @@ +flash-kernel (3.4) UNRELEASED; urgency=low + + [ Roger Leigh ] + * flash-kernel-installer postinst: Update FSCKFIX in +/etc/default/fsck as well as /etc/default/rcS for backward +compatibility. The purpose is to use /etc/default/fsck for +new installations. + + -- Roger Leigh rle...@debian.org Sun, 02 Dec 2012 23:33:24 + + flash-kernel (3.3) unstable; urgency=low * Replace XC-Package-Type by Package-Type diff --git a/debian/flash-kernel-installer.postinst b/debian/flash-kernel-installer.postinst index c07dee5..311615d 100755 --- a/debian/flash-kernel-installer.postinst +++ b/debian/flash-kernel-installer.postinst @@ -35,7 +35,12 @@ db_progress INFO flash-kernel-installer/prepare # Stop fsck from prompting the user for input since most users don't # have a serial console. -sed -i s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/rcS || true +if [ -e /target/etc/default/rcS ]; then + sed -i -e s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/rcS || true +fi +if [ -e /target/etc/default/fsck ]; then + sed -i -e s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/fsck || true +fi if ! apt-install flash-kernel; then error apt-install flash-kernel failed -- 1.7.10.4
Processed: Re: Bug#694928: asks for confirmation on config-file change on /etc/default/rcS, while file didn't change
Processing commands for cont...@bugs.debian.org: clone 694928 -1 Bug #694928 [flash-kernel] flash-kernel: postinst modifies /etc/default/rcS Bug 694928 cloned as bug 694986 reassign -1 initscripts Bug #694986 [flash-kernel] flash-kernel: postinst modifies /etc/default/rcS Bug reassigned from package 'flash-kernel' to 'initscripts'. No longer marked as found in versions flash-kernel/3.3. Ignoring request to alter fixed versions of bug #694986 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 694928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694928 694986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694986 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13544920594988.transcr...@bugs.debian.org
Bug#694928: asks for confirmation on config-file change on /etc/default/rcS, while file didn't change
On Sun, Dec 02, 2012 at 11:49:44PM +, Roger Leigh wrote: On Sun, Dec 02, 2012 at 11:47:37PM +, Roger Leigh wrote: clone 694928 -1 reassign -1 initscripts thanks On Sun, Dec 02, 2012 at 12:23:07PM +0100, Martin Zobel-Helas wrote: Please find attached an example patch for flash-kernel to support old and new (rcS and fsck) locations for FSCKFIX as discussed on #debian-devel earlier. Hmm, actually attached now. Slight update to cope with commented-out lines (as provided by default). -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 From 4db3a50a7bd6b11f3a4fa425e5e2c9b7cf1c9673 Mon Sep 17 00:00:00 2001 From: Roger Leigh rle...@debian.org Date: Sun, 2 Dec 2012 23:34:57 + Subject: [PATCH] debian: Update /etc/default/fsck in flash-kernel-installer postinst --- debian/changelog | 10 ++ debian/flash-kernel-installer.postinst |7 ++- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index 68c673b..526f1ec 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,13 @@ +flash-kernel (3.4) UNRELEASED; urgency=low + + [ Roger Leigh ] + * flash-kernel-installer postinst: Update FSCKFIX in +/etc/default/fsck as well as /etc/default/rcS for backward +compatibility. The purpose is to use /etc/default/fsck for +new installations. + + -- Roger Leigh rle...@debian.org Sun, 02 Dec 2012 23:33:24 + + flash-kernel (3.3) unstable; urgency=low * Replace XC-Package-Type by Package-Type diff --git a/debian/flash-kernel-installer.postinst b/debian/flash-kernel-installer.postinst index c07dee5..e9b88c7 100755 --- a/debian/flash-kernel-installer.postinst +++ b/debian/flash-kernel-installer.postinst @@ -35,7 +35,12 @@ db_progress INFO flash-kernel-installer/prepare # Stop fsck from prompting the user for input since most users don't # have a serial console. -sed -i s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/rcS || true +if [ -e /target/etc/default/rcS ]; then + sed -i -e s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/rcS || true +fi +if [ -e /target/etc/default/fsck ]; then + sed -i -e s/^#FSCKFIX=no$/FSCKFIX=yes/ -e s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/fsck || true +fi if ! apt-install flash-kernel; then error apt-install flash-kernel failed -- 1.7.10.4
