Re: [PATCH V2] d-i hd-media support for armhf
Unless console=ttyS0,115200,115200 happens to be safe, but I don't know that I would suggest relying on that. What about console=tty0,115200? I think adding ,115200 is a bad idea trying to paper over a mis-configured u-boot env. Better say no and let people fix their config. Stefan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/jwvk33cuecf.fsf-monnier+gmane.linux.debian.ports@gnu.org
Bug#730059: busybox-syslogd conflicts with systemd
Package: busybox-syslogd Severity: normal Dear Maintainer, As stated in the subject, systemd and busybox-syslogd are in conflict (via klogd, IIUC). I'm not completely uptodate on systemd, but AFAIK it does not provide syslogd functionality, so I'd like to keep running busybox-syslogd alongside systemd. Stefan -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.10-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages busybox-syslogd depends on: ii busybox 1:1.20.0-9 busybox-syslogd recommends no packages. busybox-syslogd suggests no packages. -- 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/20131120201007.8215.46791.report...@faina.iro.umontreal.ca
Bug#606280: busybox-syslogd: /etc/init.d/busybox-klogd spews garbage on stderr
Package: busybox-syslogd Severity: minor The `running' shell function in this script (also used in /etc/init.d/busybox-syslogd) suffers from a minor race-condition that causes it to emit irrelevant messages on stderr: the /proc/[1-9]*/stat glob is expanded first and then passed to `cut' which then has to open those files, but some of them will have disappeared in the mean time. A simple fix is to redirect stderr to /dev/null. Maybe a better fix is to juunk this `running' function and use one of the standard thingies like start-stop-daemon instead. Stefan -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (10, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.36-rc6-686 (SMP w/2 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20101207201742.9218.1064.report...@bichito.home
Re: lilo removal in squeeze (or, please test grub2)
for much. But I am opposed to the removal of lilo. Both grub-legacy and grub-pc use sectors on the hard disk outside of the master boot record (cylinder 0, head 0, sector 1). In other words they use cylinder 0, head 0, sector 2 and possibly subsequent sectors on cylinder 0 head 0. Really? Never heard of it, and it sounds very odd: why would they do that when they can (and do, AFAICT) use sectors on specified partitions? Is that documented/discussed somewhere? Stefan -- 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/jwvvdaa7cev.fsf-monnier+gmane.linux.debian.u...@gnu.org
Re: lilo removal in squeeze (or, please test grub2)
for much. But I am opposed to the removal of lilo. Both grub-legacy and grub-pc use sectors on the hard disk outside of the master boot record (cylinder 0, head 0, sector 1). In other words they use cylinder 0, head 0, sector 2 and possibly subsequent sectors on cylinder 0 head 0. Really? Yes. That sucks. and it sounds very odd: why would they do that when they can use sectors on specified partitions? Because the question is where?. Inside a file, like LILO does. The lilo approach is inside the filesystem, which can break. The grub approach is right after MBR, which needs room there. But you can install Grub in a partition (rather than the MBR), so how does it work then? grub (legacy) can be installed in any partition. IIUC grub2 is limited to being installed in the MBR. Due to the differing sizes, yes. Why does the size make any difference? At least for the Lilo-like technique, size is not an issue. Stefan -- 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/jwvsk5e3pwx.fsf-monnier+gmane.linux.debian.u...@gnu.org
Bug#518399: installation-reports: / on LVM incorrectly accepted without a /boot
Package: installation-reports Severity: normal [ Sorry to report this so late, but I was just reminded of this problem and noticed I had failed to report it at the time. ] When I installed Debian testing on my PowerBook G4 12, I was a bit too optimistic about yaboot and thought that the kernel and initrd would be copied to the Apple_bootstrap partition, so I setup everything on LVM volumes, without a separate partition for /boot. I set this all directly within debian-installer. Debian happily accepted this setup and then proceeded to create an Apple_bootstrap partition with a yaboot.conf that referred to /dev/mapper/foo-bar even though yaboot cannot access this volume. So the next boot failed miserably, and I had to manually fix things up to restart the install, add a /boot partition, etc... Other than that, the install went very smoothly: congratulations! -- Package-specific info: Boot method: hd Image version: Lenny, early january 2009 Date: Date and time of the install Machine: PowerBook G4 12 Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] 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:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=3.1 (installer build 20060304) == Installer hardware-summary: == umame -a: Linux pastel 2.6.15-1-486 #1 Tue Feb 21 20:16:13 UTC 2006 i686 unknown lspci -v -t: -[00]-+-00.0 nVidia Corporation CK804 Memory Controller lspci -v -t: +-01.0 nVidia Corporation CK804 ISA Bridge lspci -v -t: +-01.1 nVidia Corporation CK804 SMBus lspci -v -t: +-02.0 nVidia Corporation CK804 USB Controller lspci -v -t: +-02.1 nVidia Corporation CK804 USB Controller lspci -v -t: +-04.0 nVidia Corporation CK804 AC'97 Audio Controller lspci -v -t: +-06.0 nVidia Corporation CK804 IDE lspci -v -t: +-07.0 nVidia Corporation CK804 Serial ATA Controller lspci -v -t: +-08.0 nVidia Corporation CK804 Serial ATA Controller lspci -v -t: +-09.0-[05]--+-0b.0 Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) lspci -v -t: |\-0c.0 Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller lspci -v -t: +-0a.0 nVidia Corporation CK804 Ethernet Controller lspci -v -t: +-0b.0-[04]-- lspci -v -t: +-0c.0-[03]-- lspci -v -t: +-0d.0-[02]-- lspci -v -t: +-0e.0-[01]00.0 nVidia Corporation GeForce 6200 TurboCache(TM) lspci -v -t: +-18.0 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration lspci -v -t: +-18.1 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map lspci -v -t: +-18.2 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller lspci -v -t: \-18.3 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control lspci -n: :00:00.0 0580: 10de:005e (rev a3) lspci -n: :00:01.0 0601: 10de:0050 (rev a3) lspci -n: :00:01.1 0c05: 10de:0052 (rev a2) lspci -n: :00:02.0 0c03: 10de:005a (rev a2) lspci -n: :00:02.1 0c03: 10de:005b (rev a3) lspci -n: :00:04.0 0401: 10de:0059 (rev a2) lspci -n: :00:06.0 0101: 10de:0053 (rev f2) lspci -n: :00:07.0 0101: 10de:0054 (rev f3) lspci -n: :00:08.0 0101: 10de:0055 (rev f3) lspci -n: :00:09.0 0604: 10de:005c (rev a2) lspci -n: :00:0a.0 0680: 10de:0057 (rev a3) lspci -n: :00:0b.0 0604: 10de:005d (rev a3) lspci -n: :00:0c.0 0604: 10de:005d (rev a3) lspci -n: :00:0d.0 0604: 10de:005d (rev a3) lspci -n: :00:0e.0 0604: 10de:005d (rev a3) lspci -n: :00:18.0 0600: 1022:1100 lspci -n: :00:18.1 0600: 1022:1101 lspci -n: :00:18.2 0600: 1022:1102 lspci -n: :00:18.3 0600: 1022:1103 lspci -n: :01:00.0 0300: 10de:0161 (rev a1) lspci -n: :05:0b.0 0c00: 104c:8023 lspci -n: :05:0c.0 0200: 11ab:4320 (rev 13) lspci -v: :00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) lspci -v:
Bug#413718: closed by Frans Pop [EMAIL PROTECTED] (reply to [EMAIL PROTECTED]) (Re: Bug#413718: debian-installer: netinst cannot authenticate to a public hotspot)
It's very unlikely that we'll support that anytime soon. Why not? All it requires is the addition of `lynx' on the netinst images. Of course, space is relevant, so maybe the answer is use another image. Still, I think lynx would make for a very pleasant addition, since it could also be used to get online help/info while doing the install. I also question if it is advisable to install a system over such a public network. It's my university's free access network, and it's definitely worth using when doing an install: I got 5MB/s as compared to the 300kB/s I'd get at home. And it's not 100% public (which is why it requires an authentication step). Tere might be security issues, but it's not like those issues are completely absent when using a different access method. Looks like you found the correct solution to finish the installation. I did. But it was rather inconvenient. Basically take it as a plea to include lynx in the netinst image (while understanding that other priorities may keep lynx out of it in the foreseeable future). Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413718: debian-installer: netinst cannot authenticate to a public hotspot
Package: debian-installer Severity: normal I recently installed Debian from a netinst CD onto a laptop. The installation overall went fairly smoothly, except that I was not initially able to access the network: the ethernet card was correctly recognized and configured, but my network connection requires an authentication step via a web browser, and netinst does not include any. So I've had to do a minimal install from netinst, then use an USB flash drive to copy lynx (and a couple auxiliary libraries), then authenticate, then finally do the rest of the install manually (via apt-get). Stefan -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686-bigmem Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
