On Sun, Feb 27, 2011 at 1:32 PM, Boyd Stephen Smith Jr.
<bss@iguanasuicide.net> wrote:
Poor reason; I've never found an application that needed a reboot to fix
this. (Yes, you need to restart the application, but not the OS.)
lets look at this for a second. lets look at the libraries that init uses:
swilson@swilson-mbp-vdebian:~/catalyst/New/lib/New/Controller$ ldd /sbin/init
linux-vdso.so.1 => (0x00007fffe94c1000)
libsepol.so.1 => /lib/libsepol.so.1 (0x00007f9122b44000)
libselinux.so.1 => /lib/libselinux.so.1 (0x00007f9122928000)
libc.so.6 => /lib/libc.so.6 (0x00007f91225d5000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f91223d1000)
/lib64/ld-linux-x86-64.so.2 (0x00007f9122d7e000)
so, then lets see what package these are a part of:
swilson@swilson-mbp-vdebian:~/catalyst/New/lib/New/Controller$ dpkg --search /lib/libsepol.so.1
libsepol1: /lib/libsepol.so.1
swilson@swilson-mbp-vdebian:~/catalyst/New/lib/New/Controller$ dpkg --search /lib/libselinux.so.1
libselinux1: /lib/libselinux.so.1
swilson@swilson-mbp-vdebian:~/catalyst/New/lib/New/Controller$ dpkg --search /lib/libc.so.6
libc6: /lib/libc.so.6
swilson@swilson-mbp-vdebian:~/catalyst/New/lib/New/Controller$ dpkg --search /lib/libdl.so.2
libc6: /lib/libdl.so.2
ok, now how old are these packages:
swilson@swilson-mbp-vdebian:~/catalyst/New/lib/New/Controller$ ls -l /var/cache/apt/archives/libsepol1_2.0.30-2_amd64.deb
-r--r--r-- 1 root root 124930 2010-12-04 19:47 /var/cache/apt/archives/libsepol1_2.0.30-2_amd64.deb
swilson@swilson-mbp-vdebian:~/catalyst/New/lib/New/Controller$ ls -l /var/cache/apt/archives/libselinux1_2.0.65-5_amd64.deb
-r--r--r-- 1 root root 77714 2010-12-04 19:47 /var/cache/apt/archives/libselinux1_2.0.65-5_amd64.deb
swilson@swilson-mbp-vdebian:~/catalyst/New/lib/New/Controller$ ls -l /var/cache/apt/archives/libc6-i386_2.7-18lenny7_amd64.deb
-rw-r--r-- 1 root root 3653598 2011-01-11 14:38 /var/cache/apt/archives/libc6-i386_2.7-18lenny7_amd64.deb
hummm, so libc6 was updated on january 11, when did i last reboot this box?
swilson@swilson-mbp-vdebian:~/catalyst/New/lib/New/Controller$ uptime
19:28:15 up 41 days, 17:35, 6 users, load average: 1.72, 0.72, 0.26
so, i'm pretty sure that whatever got fixed in libc6 is not fixed on this box if it deals with the base library. maybe i'm wrong - i'm pretty sure it's possible to link a new library to a running process but i don't know. and i don't know whether the dpkg scripts will do this whenever a new library is installed for a running process.
>* Ensuring all hardware is still in good, working order.
Good reason.
iirc, if the device was made properly, when you reload a driver, it will reboot the device.
>* Even modifying partitions or filesystems to accommodate new storage needs.
I've done quite a bit of this live. LVM is good stuff. Sound be in most
environments.
on a default debian install, there is no extra space to resize lvm. i suppose, if you have a decent scsi / sas controller, you can hot plug a drive and get it to innitiate and add the volume. however, with default debian on consumer hardware, if you want to resize something, you're going to reboot.