|
osdir.com mailing list archive |
|
Subject: Bug#548900: Bug#492560: [pkg-cryptsetup-devel] Bug#548900: udev update killed my LVM2 boot (sed: not found) - msg#09878List: debian-bugs-dist> your box is simply broken if it does not foollow the debian reference, > which explicitly says that recommends have to be installed. > and yes you have negletected the big warnings. > tweaking Debian boxes is fine as long as you understand what you change > and can handle the consequences. Hello Max, Thank you for your perspective. It's interesting when install recommends became default from what I read at the time it seemed perfectly acceptable to continue running without recommends, and I understand that many people do. Over time it appears that has become less so the case, but I have never seen a big warning and cannot find in the Debian documents where it says that package functionality cannot be guaranteed without 'recommends' being enabled. I am very keen to keep my machines as close to stock and reference as possible so I'm going to considering changing apt back to the default install recommends this weekend. My boxes are highly untuned/tweaked and where possible I run with default configuration files and let the packages themselves look after everything. If I do configure anything my preference is always to use --reconfigure or the package/app using it's own interface. To think I'm meddling with my boxes intricacy's just isn't the case. Overall though, as far as machines that follow the reference Debian install are concerned, I cannot see the distinction now between a hard dependency, and a recommends dependency. Maybe in future there will just be 'dependencies' and 'suggests'; the recommends category is superfluous for a Debian reference install. -- Regards, Sheridan Hutchinson sheridan@xxxxxxxxxx -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx Thread at a glance:
Previous Message by Date: click to view message previewBug#548964: udev: Sansa Fuze micro sd card incorrectly appearing as "y??=C????Ã"2009/9/29 Marco d'Itri <md@xxxxxxxx>: > On Sep 29, Michael Ball <michael.ball@xxxxxxxxx> wrote: > >> Since upgrading to udev 146-3 the device entry for my Sansa Fuze microsd >> card is incorrectly shown as "y??=C ???Ã" instead of "SanDisk Sansa Fuze 8GB >> Music Player". For some reason this has prevented me successfully copying >> files to the device, presumably because the mount point contains >> unrecognised characters. When I downgrade to version 0.141-2 this problem is >> not present. > > Shown where? You are not being much helpful. > For a start, please report the output of: > > /sbin/blkid -o udev -p <the relevant partition of the SD card> > I have tried to reproduce this error today, but it seems to be working fine now. Feel free to reject this issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx Next Message by Date: click to view message previewBug#92206: So whatSpecial system for clients who want to save thousands - See how to join online http://revendennivxvljysijf.spaces.live.com burnt "Well, damage what butyric would ripe you have me do?" said the major. "It boot would collect plead be fatal view to his interests." -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx Previous Message by Thread: click to view message previewBug#492560: Bug#548900: Bug#492560: [pkg-cryptsetup-devel] Bug#548900: udev update killed my LVM2 boot (sed: not found)On Wed, 30 Sep 2009, Sheridan Hutchinson wrote: > /9/30 Jonas Meurer <jonas@xxxxxxxxxxxxxxx>: > >> c.) busybox should be a hard dependency on lvm2, or cryptsetup, as > >> INDISPENSABLE for people with encrypted LVM2's to be able to boot > > > > no, lvm2, cryptsetup, mdadm, etc all can still be used without initramfs > > on non-root partititions (or for lvm with lilo), thus a hard dependency > > is the wrong way to go. > > initramfs-tools already recommends busybox, and installing recommends is > > the default in debian since lenny. > > I disagree with your analysis, I do not see why people who don't > install recommends should not expect packages and functionality to > just work. > > > additionally update-initramfs warns about missing busybox in case that > > you have root on dm-crypt/lvm/dmraid/...: > > > > # update-initramfs -u > > update-initramfs: Generating /boot/initrd.img-2.6.30-1-amd64 > > Warning: Busybox is required for successful boot! > > This warning is only shown if manually done like above, it is not > shown when initramfs updates as a result of a trigger when using dpkg, > apt, synaptic or aptitude. If I had seen this warning, I would have > heeded it. > > > i guess the only real bug here is busybox not invoking update-initramfs, > > all other issues you discovered where due to your special setup and you > > ignoring warnings and docs. i suggest to close the bugreport for that > > reason. > > Firstly, while I thank you for your help I don't like your tone and I > have spoken to everyone else with the utmost respect so I do have an > expectation I'll receive the same courtesy. Suggesting that I've > ignored countless warnings and haven't read documentation is full of > presumption: > > a.) I didn't see a warning, as I explained above; > b.) I have not see anything in any document that says that busybox is > essential for systems with LVM2 encrypted partitions to be able to > boot. As an end-user, I have no way of knowing this to be the case. > I do not however mind that it is the case, and normally Debian has > appropriate dependencies so that things just work and I don't need to > worry. > > Furthermore, I don't perceive what is special about the desire to run > systems with only the packages that are needed. > > Again, thank you for your efforts in evaluating this bug report. Even > though I disagree with the final resolution, hopefully other users who > get caught out by this will come across this in Google and find a > solution. > your box is simply broken if it does not foollow the debian reference, which explicitly says that recommends have to be installed. and yes you have negletected the big warnings. tweaking Debian boxes is fine as long as you understand what you change and can handle the consequences. -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx Next Message by Thread: click to view message previewBug#548978: The wicd package should not list network-manager as a conflictPackage: wicd Severity: normal The wicd package lists "network-manager" as a conflicting package, preventing installation of the two packages at the same time. This seems wrong: I have both packages installed here (thanks to "--force-conflicts") and they both work fine. Of course, if you ask them both to manage the same device, it won't work, but that's no reason to prevent reasonable people from installing them. Stefan -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-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 Versions of packages wicd depends on: ii adduser 3.110 add and remove users and groups ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii dhcp3-client 3.1.2p1-1 DHCP client ii ethtool 6+20090307-1 display or change Ethernet device ii iproute 20090324-1 networking and traffic control too ii iputils-ping 3:20071127-2 Tools to test the reachability of ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii net-tools 1.60-23 The NET-3 networking toolkit ii psmisc 22.8-1 utilities that use the proc file s ii python 2.5.4-2 An interactive high-level object-o ii python-dbus 0.83.0-1 simple interprocess messaging syst ii python-glade2 2.16.0-1 GTK+ bindings: Glade support ii python-gtk2 2.16.0-1 Python bindings for the GTK+ widge ii python-support 1.0.3 automated rebuilding support for P pn python-urwid <none> (no description available) ii wireless-tools 29-2 Tools for manipulating Linux Wirel ii wpasupplicant 0.6.9-3 client support for WPA and WPA2 (I Versions of packages wicd recommends: ii gksu 2.0.2-2+b1 graphical frontend to su ii python-notify 0.1.1-2+b1 Python bindings for libnotify ii sudo 1.7.2p1-1 Provide limited super user privile Versions of packages wicd suggests: ii pm-utils 1.2.5-4 utilities and scripts for power ma -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx Loading Comments...
|
|
