Hello!

I think I broke something on my Debian while installing a Kernel image
(amd64) and ran out of disk space (it didn't tell me that and I was AFK
during the installation to ctrl-c/abort). Here's the log (also on
http://pastebin.ca/469432 ):

# apt-get install linux-image-2.6.18-4-amd64
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
linux-image-2.6.18-4-amd64
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 16.8MB of archives.
After unpacking 65.3MB of additional disk space will be used.
Get:1 http://security.debian.org etch/updates/main
linux-image-2.6.18-4-amd64 2.6.18.dfsg.1-12etch1 [16.8MB]
Fetched 16.8MB in 27s (614kB/s)
Preconfiguring packages ...
Selecting previously deselected package linux-image-2.6.18-4-amd64.
(Reading database ... 159029 files and directories currently installed.)
Unpacking linux-image-2.6.18-4-amd64 (from
..../linux-image-2.6.18-4-amd64_2.6.18.dfsg.1-12etch1_i386.deb) ...
Done.
Setting up linux-image-2.6.18-4-amd64 (2.6.18.dfsg.1-12etch1) ...

Hmm. The package shipped with a symbolic link
/lib/modules/2.6.18-4-amd64/source
However, I can not read the target: No such file or directory
Therefore, I am deleting /lib/modules/2.6.18-4-amd64/source

Running depmod.
Finding valid ramdisk creators.
Using mkinitrd.yaird to build the ramdisk.
Running postinst hook script /usr/sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found:
/boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.18-4-amd64
Found kernel: /boot/vmlinuz-2.6.18-4-k7
Found kernel: /boot/vmlinuz-2.6.18-3-k7
Updating /boot/grub/menu.lst ... done


# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda1 270969 268661 0 100% /
tmpfs 517936 0 517936 0% /lib/init/rw
udev 10240 92 10148 1% /dev
tmpfs 517936 0 517936 0% /dev/shm
/dev/hda5 14421344 5813276 7875508 43% /home
/dev/hda6 4807056 2934696 1628176 65% /usr
/dev/hda7 918322 498744 370582 58% /var
/dev/hda8 918322 16487 852839 2% /tmp
/dev/hda9 4807056 200528 4362344 5% /usr/local
/dev/hda11 47383396 2431172 42545288 6% /extra
/dev/hda12 918322 16452 852874 2% /others
/dev/hdb1 861728 16416 801540 3% /stuff
/dev/hdb5 5336664 1113552 3952020 22% /storage
# apt-get clean
# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda1 270969 268661 0 100% /
tmpfs 517936 0 517936 0% /lib/init/rw
udev 10240 92 10148 1% /dev
tmpfs 517936 0 517936 0% /dev/shm
/dev/hda5 14421344 5813284 7875500 43% /home
/dev/hda6 4807056 2934696 1628176 65% /usr
/dev/hda7 918322 482255 387071 56% /var
/dev/hda8 918322 16487 852839 2% /tmp
/dev/hda9 4807056 200528 4362344 5% /usr/local
/dev/hda11 47383396 2431172 42545288 6% /extra
/dev/hda12 918322 16452 852874 2% /others
/dev/hdb1 861728 16416 801540 3% /stuff
/dev/hdb5 5336664 1113552 3952020 22% /storage
# apt-get remove linux-image-2.6.18-4-amd64
Reading package lists... Done
Building dependency tree... Done
The following packages will be REMOVED:
linux-image-2.6.18-4-amd64
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives.
After unpacking 65.3MB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 160927 files and directories currently installed.)
Removing linux-image-2.6.18-4-amd64 ...
Running postrm hook script /usr/sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found:
/boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.18-4-k7
Found kernel: /boot/vmlinuz-2.6.18-3-k7
Updating /boot/grub/menu.lst ... done

The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
Unless you used the optional flag in lilo,
you may need to re-run your boot loader[lilo]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
Unless you used the optional flag in lilo,
you may need to re-run your boot loader[lilo]
# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda1 270969 204863 51650 80% /
tmpfs 517936 0 517936 0% /lib/init/rw
udev 10240 92 10148 1% /dev
tmpfs 517936 0 517936 0% /dev/shm
/dev/hda5 14421344 5813292 7875492 43% /home
/dev/hda6 4807056 2934604 1628268 65% /usr
/dev/hda7 918322 481879 387447 56% /var
/dev/hda8 918322 16487 852839 2% /tmp
/dev/hda9 4807056 200528 4362344 5% /usr/local
/dev/hda11 47383396 2431172 42545288 6% /extra
/dev/hda12 918322 16452 852874 2% /others
/dev/hdb1 861728 16416 801540 3% /stuff
/dev/hdb5 5336664 1113552 3952020 22% /storage
# cd /boot
# ls
System.map-2.6.18-3-k7 config-2.6.18-4-k7 initrd.img-2.6.18-4-k7
System.map-2.6.18-4-k7 grub vmlinuz-2.6.18-3-k7
config-2.6.18-3-k7 initrd.img-2.6.18-3-k7 vmlinuz-2.6.18-4-k7
# ls -all
total 6334
drwxr-xr-x 3 root root 1024 May 3 11:52 .
drwxr-xr-x 26 root root 1024 May 3 11:52 ..
-rw-r--r-- 1 root root 720490 Dec 10 17:36 System.map-2.6.18-3-k7
-rw-r--r-- 1 root root 722453 Apr 18 08:38 System.map-2.6.18-4-k7
-rw-r--r-- 1 root root 71347 Dec 10 10:50 config-2.6.18-3-k7
-rw-r--r-- 1 root root 70797 Apr 18 02:04 config-2.6.18-4-k7
drwxr-xr-x 2 root root 1024 May 3 11:52 grub
-rw------- 1 root root 1137172 Dec 21 13:22 initrd.img-2.6.18-3-k7
-rw------- 1 root root 1186592 May 2 15:35 initrd.img-2.6.18-4-k7
-rw-r--r-- 1 root root 1267064 Dec 10 17:36 vmlinuz-2.6.18-3-k7
-rw-r--r-- 1 root root 1268572 Apr 18 08:38 vmlinuz-2.6.18-4-k7
# ls -all /initrd.img
ls: /initrd.img: No such file or directory


Do I need to worry about those errors? If so, then what do I need to
fix this? I am afraid to reboot my computer and find Debian not able to
boot up. :(

Thank you in advance.
--
"In every enemy that is an ant, behold an elephant." --Turkish
/\___/\
/ /\ /\ \ Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

I demand that Ant may or may not have written...

> I think I broke something on my Debian while installing a Kernel image
> (amd64) and ran out of disk space (it didn't tell me that and I was AFK
> during the installation to ctrl-c/abort). Here's the log [...]:

> # apt-get install linux-image-2.6.18-4-amd64
> Reading package lists... Done
> Building dependency tree... Done
> The following NEW packages will be installed:
> linux-image-2.6.18-4-amd64
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 16.8MB of archives.
[snip]
> Testing for an existing GRUB menu.lst file ... found:
> /boot/grub/menu.lst
> Searching for splash image ... none found, skipping ...
> Found kernel: /boot/vmlinuz-2.6.18-4-amd64
> Found kernel: /boot/vmlinuz-2.6.18-4-k7
> Found kernel: /boot/vmlinuz-2.6.18-3-k7
> Updating /boot/grub/menu.lst ... done
>
>
> # df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/hda1 270969 268661 0 100% /
[snip; no /boot]
> # apt-get clean
> # df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/hda1 270969 268661 0 100% /
[snip; a small usage reduction in /var]
> # apt-get remove linux-image-2.6.18-4-amd64
> Reading package lists... Done
> Building dependency tree... Done
> The following packages will be REMOVED:
> linux-image-2.6.18-4-amd64
> 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> Need to get 0B of archives.
> After unpacking 65.3MB disk space will be freed.

Big hint there - maybe you want to remove a kernel image which you know that
you won't be using again first. (Obviously not the one currently in use!)

[snip]
> The link /vmlinuz is a damaged link
> Removing symbolic link vmlinuz
> Unless you used the optional flag in lilo,
> you may need to re-run your boot loader[lilo]

Hmm, problem...

[snip]
> # df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/hda1 270969 204863 51650 80% /

Well, there you go. 15MB short.

[snip]
> Do I need to worry about those errors? If so, then what do I need to fix
> this? I am afraid to reboot my computer and find Debian not able to boot
> up. :(

Probably the best thing to do is to start building your own stripped-down
kernels. Or shrink another partition by 64MB or so and create a /boot
partition from it - mount it elsewhere, move files to it from your existing
/boot, add a suitable fstab entry, unmount it and remount it over your old
/boot, re-run lilo.

--
| Darren Salt | linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Generate power using sun, wind, water, nuclear. FORGET COAL AND OIL.

Descartes of Borg: "I assimilate, therefore I am."

ÈÓã Çááå ÇáÑÍãä ÇáÑÍíã
ÈäÇÊ æÔÈÇÈá ÚÇíÒå ÊÊÔÑÝ ÈãÚÑÝÊß ÊÚÇÑÝ ãä ßá Ïæá ÇáÚÇáã ÇÏÎá Çáí ÚÇáã
ãä ÇáãÊÚÉ æÇáÒæÇÌ æÇáÍÈ

ÇÝÖá ãæÞÚ ááÊÚÇÑÝ Èíä ÇáÌäÓ íä ÇáÔÈÇÈ æÇáÈäÇÊ ãä ßá Ïæá ÇáÚÇáã
www.arabzwaj.com
ÊÚÇÑÝ ãä ßá Ïæá ÇáÚÇáã ÈäÇÊ æÔÈÇÈ äÝÓåã íÍÈæÇ æíÊÌæÒæÇ ÈÌÏ ÊÚÇÑÝ ÍÞíÞí
æÒæÇÌ ÔÑÚí
ÚÇíÒ ÊßÓÈ 5000 ÏæáÇÑ ÇÏÎá æÇÚÑÝ ÇÐÇí æÔæÝ ÇáÊÝÇÕíá ÈäÝÓß ÇÖÛØ Úáí
ÇáÑÇÈØ ÇÏäÇå

http://www.arabzwaj.com/welcome/view...5f65eb723025a2

ÇÝÖá ãæÞÚ ááÊÚÇÑÝ Èíä ÇáÌäÓ íä ÇáÔÈÇÈ æÇáÈäÇÊ ãä ßá Ïæá ÇáÚÇáã
www.arabzwaj.com

ÈäÇÊ æÔÈÇÈ ÚÇíÒííä íÊÚÑÝæÇ Úáíßã


ÕæÑ ÚÇÑíÉ ÍÞíÞíÉ


ÊÚÇÑÝ ãÌÇäí ãä ßá Ïæá ÇáÚÇáã www.arabzwaj.com
for marrige and friend shipÇÝÖá ÊÚÇÑÝ Èíä ÇáÔÈÇÈ æÇáÈäÇÊ ãæÞÚ ÒæÇÌ
ãÌÇäí www.arabzwaj.com

www.arabzwaj.com ÇÝÖá ãæÞÚ ãÌÇäí ááÊÚÇÑÝ æ ááÒæÇÌ ÇáÔÑÚí

www.arabzwaj.com ÈäÇÊ æÔÈÇÈ ÚÇíÒå ÊÊÚÑÝ Úáíßã





the best web site formarrige and frindship www.arabzwaj.comÇÝÖá ãæÞÚ
ãÌÇäí ááÊÚÇÑÝ æ ááÒæÇÌ

In alt.os.linux.debian Darren Salt <news@youmustbejoking.demon.cu.invalid> wrote:
> I demand that Ant may or may not have written...

Eh?


> > I think I broke something on my Debian while installing a Kernel image
> > (amd64) and ran out of disk space (it didn't tell me that and I was AFK
> > during the installation to ctrl-c/abort). Here's the log [...]:

> > # apt-get install linux-image-2.6.18-4-amd64
> > Reading package lists... Done
> > Building dependency tree... Done
> > The following NEW packages will be installed:
> > linux-image-2.6.18-4-amd64
> > 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> > Need to get 16.8MB of archives.
> [snip]
> > Testing for an existing GRUB menu.lst file ... found:
> > /boot/grub/menu.lst
> > Searching for splash image ... none found, skipping ...
> > Found kernel: /boot/vmlinuz-2.6.18-4-amd64
> > Found kernel: /boot/vmlinuz-2.6.18-4-k7
> > Found kernel: /boot/vmlinuz-2.6.18-3-k7
> > Updating /boot/grub/menu.lst ... done
> >
> >
> > # df
> > Filesystem 1K-blocks Used Available Use% Mounted on
> > /dev/hda1 270969 268661 0 100% /
> [snip; no /boot]
> > # apt-get clean
> > # df
> > Filesystem 1K-blocks Used Available Use% Mounted on
> > /dev/hda1 270969 268661 0 100% /
> [snip; a small usage reduction in /var]
> > # apt-get remove linux-image-2.6.18-4-amd64
> > Reading package lists... Done
> > Building dependency tree... Done
> > The following packages will be REMOVED:
> > linux-image-2.6.18-4-amd64
> > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> > Need to get 0B of archives.
> > After unpacking 65.3MB disk space will be freed.

> Big hint there - maybe you want to remove a kernel image which you know that
> you won't be using again first. (Obviously not the one currently in use!)

Yeah, but it was too late. I thought install said it only needed 16.8MB
to install (not download). DOH! Installer should had caught the lack of
free disk space though. Weird.


> [snip]
> > The link /vmlinuz is a damaged link
> > Removing symbolic link vmlinuz
> > Unless you used the optional flag in lilo,
> > you may need to re-run your boot loader[lilo]

> Hmm, problem...

> [snip]
> > # df
> > Filesystem 1K-blocks Used Available Use% Mounted on
> > /dev/hda1 270969 204863 51650 80% /

> Well, there you go. 15MB short.

Yeah. In the past, I actually had ran out of disk space and the install
failed and refused due to lack of disk space. Not this time. :(


> [snip]
> > Do I need to worry about those errors? If so, then what do I need to fix
> > this? I am afraid to reboot my computer and find Debian not able to boot
> > up. :(

> Probably the best thing to do is to start building your own stripped-down
> kernels. Or shrink another partition by 64MB or so and create a /boot
> partition from it - mount it elsewhere, move files to it from your existing
> /boot, add a suitable fstab entry, unmount it and remount it over your old
> /boot, re-run lilo.

Um, I don't have lilo. I use Grub on this box.

According to my Debian friend, he doesn't think I will have problem. He
asked for my grub setup and files. You can see them at
http://pastebin.ca/469711 .... They appear to be OK? What do you think?
--
"In every enemy that is an ant, behold an elephant." --Turkish
/\___/\
/ /\ /\ \ Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

I demand that Ant may or may not have written...

> In alt.os.linux.debian Darren Salt <news@youmustbejoking.demon.cu.invalid>
> wrote:
>> I demand that Ant may or may not have written...

> Eh?

Towel Day on the 25th... ;-)

>>> I think I broke something on my Debian while installing a Kernel image
>>> (amd64) and ran out of disk space (it didn't tell me that and I was AFK
>>> during the installation to ctrl-c/abort). Here's the log [...]:
[snip]
>>> After unpacking 65.3MB disk space will be freed.

>> Big hint there - maybe you want to remove a kernel image which you know
>> that you won't be using again first. (Obviously not the one currently in
>> use!)

(Hmm, just noticed - "freed". OTOH, that'd be across all affected partitions,
and there could still be more used space on some of them...)

> Yeah, but it was too late. I thought install said it only needed 16.8MB to
> install (not download). DOH! Installer should had caught the lack of free
> disk space though. Weird.

Not really, at least at that point - it has only the total size of the
package, both compressed and installed. It doesn't have any knowledge of
what's where until installation occurs, and even then it'd have to look at
the actual filesystem(s).

>> [snip]
>>> The link /vmlinuz is a damaged link
>>> Removing symbolic link vmlinuz
>>> Unless you used the optional flag in lilo,
>>> you may need to re-run your boot loader[lilo]
>> Hmm, problem...
[snip]
>> Probably the best thing to do is to start building your own stripped-down
>> kernels. Or shrink another partition by 64MB or so and create a /boot
>> partition from it - mount it elsewhere, move files to it from your
>> existing /boot, add a suitable fstab entry, unmount it and remount it
>> over your old /boot, re-run lilo.

> Um, I don't have lilo. I use Grub on this box.

Then the package installation script output which you reported is misleading.

> According to my Debian friend, he doesn't think I will have problem. He
> asked for my grub setup and files. You can see them at
> http://pastebin.ca/469711 .... They appear to be OK? What do you think?

You've not taken /lib/modules/$VERSION into account, and some of the files
there are generated by depmod.

--
| Darren Salt | linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Buy local produce. Try to walk or cycle. TRANSPORT CAUSES GLOBAL WARMING.

I am Locutus of Borg. Earl Grey for ten thousand.

In alt.os.linux.debian Darren Salt <news@youmustbejoking.demon.cu.invalid> wrote:
> I demand that Ant may or may not have written...

> > In alt.os.linux.debian Darren Salt <news@youmustbejoking.demon.cu.invalid>
> > wrote:
> >> I demand that Ant may or may not have written...

> > Eh?

> Towel Day on the 25th... ;-)

Uhh, OK. I don't know what that is about but whatever.


> >>> I think I broke something on my Debian while installing a Kernel image
> >>> (amd64) and ran out of disk space (it didn't tell me that and I was AFK
> >>> during the installation to ctrl-c/abort). Here's the log [...]:
> [snip]
> >>> After unpacking 65.3MB disk space will be freed.

> >> Big hint there - maybe you want to remove a kernel image which you know
> >> that you won't be using again first. (Obviously not the one currently in
> >> use!)

> (Hmm, just noticed - "freed". OTOH, that'd be across all affected partitions,
> and there could still be more used space on some of them...)

Hm.


> > Yeah, but it was too late. I thought install said it only needed 16.8MB to
> > install (not download). DOH! Installer should had caught the lack of free
> > disk space though. Weird.

> Not really, at least at that point - it has only the total size of the
> package, both compressed and installed. It doesn't have any knowledge of
> what's where until installation occurs, and even then it'd have to look at
> the actual filesystem(s).

OK.


> >> [snip]
> >>> The link /vmlinuz is a damaged link
> >>> Removing symbolic link vmlinuz
> >>> Unless you used the optional flag in lilo,
> >>> you may need to re-run your boot loader[lilo]
> >> Hmm, problem...
> [snip]
> >> Probably the best thing to do is to start building your own stripped-down
> >> kernels. Or shrink another partition by 64MB or so and create a /boot
> >> partition from it - mount it elsewhere, move files to it from your
> >> existing /boot, add a suitable fstab entry, unmount it and remount it
> >> over your old /boot, re-run lilo.
>
> > Um, I don't have lilo. I use Grub on this box.

> Then the package installation script output which you reported is misleading.

Yeah, or something made it confused.


> > According to my Debian friend, he doesn't think I will have problem. He
> > asked for my grub setup and files. You can see them at
> > http://pastebin.ca/469711 .... They appear to be OK? What do you think?

> You've not taken /lib/modules/$VERSION into account, and some of the files
> there are generated by depmod.

$ ls -all /lib/modules/
total 9
drwxr-xr-x 5 root root 1024 May 3 11:52 .
drwxr-xr-x 15 root root 5120 May 3 14:44 ..
drwxr-xr-x 3 root root 1024 May 3 07:26 2.6.18-3-k7
drwxr-xr-x 4 root root 1024 May 3 07:30 2.6.18-4-k7
drwxr-xr-x 2 root root 1024 Dec 21 21:40 2.6.8-3-k7

# locate modules.dep
/lib/modules/2.6.18-3-k7/modules.dep
/lib/modules/2.6.18-4-k7/modules.dep
/usr/share/man/man5/modules.dep.5.gz

# ls /lib/modules/2.6.18-4-k7/ -all
total 1348
drwxr-xr-x 4 root root 1024 May 3 20:56 .
drwxr-xr-x 5 root root 1024 May 3 11:52 ..
lrwxrwxrwx 1 root root 34 May 2 15:32 build -> /usr/src/linux-headers-2.6.18-4-k7
drwxr-xr-x 9 root root 1024 Feb 3 16:17 kernel
drwxr-xr-x 2 root root 1024 May 3 07:30 misc
-rw-r--r-- 1 root root 298175 May 3 20:56 modules.alias
-rw-r--r-- 1 root root 69 May 3 20:56 modules.ccwmap
-rw-r--r-- 1 root root 328497 May 3 20:56 modules.dep
-rw-r--r-- 1 root root 813 May 3 20:56 modules.ieee1394map
-rw-r--r-- 1 root root 730 May 3 20:56 modules.inputmap
-rw-r--r-- 1 root root 21839 May 3 20:56 modules.isapnpmap
-rw-r--r-- 1 root root 74 May 3 20:56 modules.ofmap
-rw-r--r-- 1 root root 235243 May 3 20:56 modules.pcimap
-rw-r--r-- 1 root root 1135 May 3 20:56 modules.seriomap
-rw-r--r-- 1 root root 136719 May 3 20:56 modules.symbols
-rw-r--r-- 1 root root 334134 May 3 20:56 modules.usbmap
# ls /lib/modules/2.6.18-3-k7/ -all
total 1355
drwxr-xr-x 3 root root 1024 May 3 07:26 .
drwxr-xr-x 5 root root 1024 May 3 11:52 ..
lrwxrwxrwx 1 root root 34 Dec 21 21:40 build -> /usr/src/linux-headers-2.6.18-3-k7
drwxr-xr-x 9 root root 1024 Dec 21 13:22 kernel
-rw-r--r-- 1 root root 299849 Jan 31 01:45 modules.alias
-rw-r--r-- 1 root root 69 Jan 31 01:45 modules.ccwmap
-rw-r--r-- 1 root root 329296 Jan 31 01:45 modules.dep
-rw-r--r-- 1 root root 813 Jan 31 01:45 modules.ieee1394map
-rw-r--r-- 1 root root 730 Jan 31 01:45 modules.inputmap
-rw-r--r-- 1 root root 21839 Jan 31 01:45 modules.isapnpmap
-rw-r--r-- 1 root root 74 Jan 31 01:45 modules.ofmap
-rw-r--r-- 1 root root 235607 Jan 31 01:45 modules.pcimap
-rw-r--r-- 1 root root 1135 Jan 31 01:45 modules.seriomap
-rw-r--r-- 1 root root 136719 Jan 31 01:45 modules.symbols
-rw-r--r-- 1 root root 339383 Jan 31 01:45 modules.usbmap

/lib/modules/2.6.18-3-k7/modules.dep and
/lib/modules/2.6.18-4-k7/modules.dep can be found in a zip file at
http://www.savefile.com/files/691436 for viewing.

Running depmod -a didn't show anything errors. Anything else I should
output?
--
"In every enemy that is an ant, behold an elephant." --Turkish
/\___/\
/ /\ /\ \ Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

I demand that Ant may or may not have written...

> In alt.os.linux.debian Darren Salt <news@youmustbejoking.demon.cu.invalid>
> wrote:
>> I demand that Ant may or may not have written...
>>> In alt.os.linux.debian Darren Salt
>>> <news@youmustbejoking.demon.cu.invalid> wrote:
>>>> I demand that Ant may or may not have written...
>>> Eh?
>> Towel Day on the 25th... ;-)

> Uhh, OK. I don't know what that is about but whatever.

42!

[snip]
>>>> [snip]
>>>>> The link /vmlinuz is a damaged link
>>>>> Removing symbolic link vmlinuz
>>>>> Unless you used the optional flag in lilo,
>>>>> you may need to re-run your boot loader[lilo]
>>>> Hmm, problem...
>> [snip]
>>>> Probably the best thing to do is to start building your own
>>>> stripped-down kernels. Or shrink another partition by 64MB or so and
>>>> create a /boot partition from it [...].
>>> Um, I don't have lilo. I use Grub on this box.
>> Then the package installation script output which you reported is
>> misleading.

> Yeah, or something made it confused.

The postrm script content says that "confused" is right.

>>> According to my Debian friend, he doesn't think I will have problem. He
>>> asked for my grub setup and files. You can see them at
>>> http://pastebin.ca/469711 .... They appear to be OK? What do you think?
>> You've not taken /lib/modules/$VERSION into account, and some of the files
>> there are generated by depmod.

> $ ls -all /lib/modules/
[snip]

I would have gone straight for 'du -s /lib/modules/*', but never mind :-)

For comparison (locally-built kernel, custom configuration):
$ du -s /boot/*2.6.21 /lib/modules/2.6.21 /lib/modules/2.6.21/modules*
975 /boot/System.map-2.6.21
44 /boot/config-2.6.21
1951 /boot/vmlinuz-2.6.21
3839 /lib/modules/2.6.21
19 /lib/modules/2.6.21/modules.alias
1 /lib/modules/2.6.21/modules.ccwmap
17 /lib/modules/2.6.21/modules.dep
1 /lib/modules/2.6.21/modules.ieee1394map
1 /lib/modules/2.6.21/modules.inputmap
1 /lib/modules/2.6.21/modules.isapnpmap
1 /lib/modules/2.6.21/modules.ofmap
3 /lib/modules/2.6.21/modules.pcimap
1 /lib/modules/2.6.21/modules.seriomap
28 /lib/modules/2.6.21/modules.symbols
40 /lib/modules/2.6.21/modules.usbmap

(All sizes are in kilobytes; directory contents are included in the totals. )

> Running depmod -a didn't show anything errors. Anything else I should
> output?

Not sure, really... probably best to do something like
$ dpkg -x /var/cache/apt/archives/linux-image-2.6.18-4-k7*i386.deb foo
$ du -s foo foo/boot foo/usr

Add 200 to the first value and you have a value approximating the total
install size. Subtract the third (and the second if you've added a /boot
partition) and you'll see (more or less) how much space is required in your
root partition.

--
| Darren Salt | linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + At least 4000 million too many people. POPULATION LEVEL IS UNSUSTAINABLE.

I'd like to, but the grunion are running.

On May 4, 6:19 am, ANT...@zimage.com (Ant) wrote:
>
> $ ls -all /lib/modules/
> total 9
> drwxr-xr-x 5 root root 1024 May 3 11:52 .
> drwxr-xr-x 15 root root 5120 May 3 14:44 ..
> drwxr-xr-x 3 root root 1024 May 3 07:26 2.6.18-3-k7
> drwxr-xr-x 4 root root 1024 May 3 07:30 2.6.18-4-k7
> drwxr-xr-x 2 root root 1024 Dec 21 21:40 2.6.8-3-k7

You could remove /lib/modules/2.6.8-3-k7, becouse you don't have that
kernel installed any longer. Check so that you don't have that version
of linux-kernel package install first. If so, purge that package, and
that directory will be removed. If not, remove /lib/modules/2.6.8-3-
k7 by hand...
Should save some bytes any way.

Good luck

> >>>> I demand that Ant may or may not have written...
> >>> Eh?
> >> Towel Day on the 25th... ;-)
>
> > Uhh, OK. I don't know what that is about but whatever.

> 42!

Oh you're referring to Hitchiker to the Galaxy. I never got into that.
:/


> > $ ls -all /lib/modules/
> [snip]

> I would have gone straight for 'du -s /lib/modules/*', but never mind :-)

Oh well, I am still learning Linux. I just use it as a
workstation/backup machine. Here:
$ du -s /lib/modules/*
44764 /lib/modules/2.6.18-3-k7
51747 /lib/modules/2.6.18-4-k7
1 /lib/modules/2.6.8-3-k7


> For comparison (locally-built kernel, custom configuration):
> $ du -s /boot/*2.6.21 /lib/modules/2.6.21 /lib/modules/2.6.21/modules*
> 975 /boot/System.map-2.6.21
> 44 /boot/config-2.6.21
> 1951 /boot/vmlinuz-2.6.21
> 3839 /lib/modules/2.6.21
> 19 /lib/modules/2.6.21/modules.alias
> 1 /lib/modules/2.6.21/modules.ccwmap
> 17 /lib/modules/2.6.21/modules.dep
> 1 /lib/modules/2.6.21/modules.ieee1394map
> 1 /lib/modules/2.6.21/modules.inputmap
> 1 /lib/modules/2.6.21/modules.isapnpmap
> 1 /lib/modules/2.6.21/modules.ofmap
> 3 /lib/modules/2.6.21/modules.pcimap
> 1 /lib/modules/2.6.21/modules.seriomap
> 28 /lib/modules/2.6.21/modules.symbols
> 40 /lib/modules/2.6.21/modules.usbmap

Here's mine:
$ du -s /boot/*2.6.18-3* /lib/modules/2.6.18-3* /lib/modules/2.6.18-3*/modules*
708 /boot/System.map-2.6.18-3-k7
71 /boot/config-2.6.18-3-k7
1117 /boot/initrd.img-2.6.18-3-k7
1244 /boot/vmlinuz-2.6.18-3-k7
44764 /lib/modules/2.6.18-3-k7
296 /lib/modules/2.6.18-3-k7/modules.alias
1 /lib/modules/2.6.18-3-k7/modules.ccwmap
325 /lib/modules/2.6.18-3-k7/modules.dep
1 /lib/modules/2.6.18-3-k7/modules.ieee1394map
1 /lib/modules/2.6.18-3-k7/modules.inputmap
23 /lib/modules/2.6.18-3-k7/modules.isapnpmap
1 /lib/modules/2.6.18-3-k7/modules.ofmap
232 /lib/modules/2.6.18-3-k7/modules.pcimap
2 /lib/modules/2.6.18-3-k7/modules.seriomap
135 /lib/modules/2.6.18-3-k7/modules.symbols
335 /lib/modules/2.6.18-3-k7/modules.usbmap

$ du -s /boot/*2.6.18-4* /lib/modules/2.6.18-4* /lib/modules/2.6.18-4*/modules*
710 /boot/System.map-2.6.18-4-k7
71 /boot/config-2.6.18-4-k7
1165 /boot/initrd.img-2.6.18-4-k7
1245 /boot/vmlinuz-2.6.18-4-k7
51747 /lib/modules/2.6.18-4-k7
295 /lib/modules/2.6.18-4-k7/modules.alias
1 /lib/modules/2.6.18-4-k7/modules.ccwmap
324 /lib/modules/2.6.18-4-k7/modules.dep
1 /lib/modules/2.6.18-4-k7/modules.ieee1394map
1 /lib/modules/2.6.18-4-k7/modules.inputmap
23 /lib/modules/2.6.18-4-k7/modules.isapnpmap
1 /lib/modules/2.6.18-4-k7/modules.ofmap
231 /lib/modules/2.6.18-4-k7/modules.pcimap
2 /lib/modules/2.6.18-4-k7/modules.seriomap
135 /lib/modules/2.6.18-4-k7/modules.symbols
330 /lib/modules/2.6.18-4-k7/modules.usbmap


> (All sizes are in kilobytes; directory contents are included in the totals. )

> > Running depmod -a didn't show anything errors. Anything else I should
> > output?

> Not sure, really... probably best to do something like
> $ dpkg -x /var/cache/apt/archives/linux-image-2.6.18-4-k7*i386.deb foo

Hmm, this won't work because I ran apt-get clean yesterday after the
incident:
$ ls -all /var/cache/apt/archives/
total 32
drwxr-xr-x 3 root root 29696 May 3 14:47 .
drwxr-xr-x 3 root root 1024 May 3 14:47 ..
-rw-r----- 1 root root 0 May 3 14:47 lock
drwxr-xr-x 2 root root 1024 May 3 14:43 partial
--
"In every enemy that is an ant, behold an elephant." --Turkish
/\___/\
/ /\ /\ \ Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

> > $ ls -all /lib/modules/
> > total 9
> > drwxr-xr-x 5 root root 1024 May 3 11:52 .
> > drwxr-xr-x 15 root root 5120 May 3 14:44 ..
> > drwxr-xr-x 3 root root 1024 May 3 07:26 2.6.18-3-k7
> > drwxr-xr-x 4 root root 1024 May 3 07:30 2.6.18-4-k7
> > drwxr-xr-x 2 root root 1024 Dec 21 21:40 2.6.8-3-k7

> You could remove /lib/modules/2.6.8-3-k7, becouse you don't have that
> kernel installed any longer. Check so that you don't have that version
> of linux-kernel package install first. If so, purge that package, and
> that directory will be removed. If not, remove /lib/modules/2.6.8-3-
> k7 by hand...
> Should save some bytes any way.

$ dpkg -l | grep ^ii |grep 2.6.8
ii kernel-headers-2.6.8-3 2.6.8-16sarge6 Header files related to Linux kernel version
ii kernel-headers-2.6.8-3-k7 2.6.8-16sarge6 Linux kernel headers 2.6.8 on AMD K7
ii kernel-kbuild-2.6-3 2.6.8-2 Linux kernel 2.6 kbuild tools
ii libpqxx-2.6.8 2.6.8-1+b1 C++ library to connect to PostgreSQL

# apt-get remove kernel-headers-2.6.8-3 kernel-headers-2.6.8-3-k7
kernel-kbuild-2.6-3
Reading package lists... Done
Building dependency tree... Done
The following packages will be REMOVED:
kernel-headers-2.6-k7 kernel-headers-2.6.8-3 kernel-headers-2.6.8-3-k7
kernel-kbuild-2.6-3
0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
Need to get 0B of archives.
After unpacking 42.6MB disk space will be freed.

Is that really a good idea? Don't I neeed kernel-headers-2.6-k7 since I
use 2.6-18...-k7 for my AMD CPU? I tried removing one package at a time
but all resulted wanting to remove kernel-headers-2.6-k7 package. :( I
would love to get 42.6 MB of precious disk space back!

$ du /lib/modules/2.6.8-3-k7
1 /lib/modules/2.6.8-3-k7

It wouldn't help much for that specific location. :)
--
"In every enemy that is an ant, behold an elephant." --Turkish
/\___/\
/ /\ /\ \ Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

I demand that Ant may or may not have written...

[snip]
> # apt-get remove kernel-headers-2.6.8-3 kernel-headers-2.6.8-3-k7
> kernel-kbuild-2.6-3
> Reading package lists... Done
> Building dependency tree... Done
> The following packages will be REMOVED:
> kernel-headers-2.6-k7 kernel-headers-2.6.8-3 kernel-headers-2.6.8-3-k7
> kernel-kbuild-2.6-3
> 0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
> Need to get 0B of archives.
> After unpacking 42.6MB disk space will be freed.

> Is that really a good idea? Don't I neeed kernel-headers-2.6-k7 since I
> use 2.6-18...-k7 for my AMD CPU?

It won't matter. If you need the headers, you want linux-kernel-headers.

[snip]
--
| Darren Salt | linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Output less CO2 => avoid massive flooding. TIME IS RUNNING OUT *FAST*.

Complete and utter lie: "You'll never use all of that disk space."

In alt.os.linux.debian Darren Salt <news@youmustbejoking.demon.cu.invalid> wrote:
> I demand that Ant may or may not have written...

> [snip]
> > # apt-get remove kernel-headers-2.6.8-3 kernel-headers-2.6.8-3-k7
> > kernel-kbuild-2.6-3
> > Reading package lists... Done
> > Building dependency tree... Done
> > The following packages will be REMOVED:
> > kernel-headers-2.6-k7 kernel-headers-2.6.8-3 kernel-headers-2.6.8-3-k7
> > kernel-kbuild-2.6-3
> > 0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
> > Need to get 0B of archives.
> > After unpacking 42.6MB disk space will be freed.

> > Is that really a good idea? Don't I neeed kernel-headers-2.6-k7 since I
> > use 2.6-18...-k7 for my AMD CPU?

> It won't matter. If you need the headers, you want linux-kernel-headers.

> [snip]

Ahh, I didn't know that. $ dpkg -l | grep ^ii |grep linux-kernel-headers
ii linux-kernel-headers 2.6.18-7 Linux Kernel Headers for development

# apt-get remove kernel-headers-2.6.8-3 kernel-headers-2.6.8-3-k7
Reading package lists... Done
Building dependency tree... Done
The following packages will be REMOVED:
kernel-headers-2.6-k7 kernel-headers-2.6.8-3 kernel-headers-2.6.8-3-k7
0 upgraded, 0 newly installed, 3 to remove and 1 not upgraded.
Need to get 0B of archives.
After unpacking 40.8MB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 159345 files and directories currently installed.)
Removing kernel-headers-2.6-k7 ...
Removing kernel-headers-2.6.8-3-k7 ...
Removing kernel-headers-2.6.8-3 ...

# apt-get remove kernel-kbuild-2.6-3
Reading package lists... Done
Building dependency tree... Done
The following packages will be REMOVED:
kernel-kbuild-2.6-3
0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
Need to get 0B of archives.
After unpacking 1778kB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 150551 files and directories currently installed.)
Removing kernel-kbuild-2.6-3 ...

# pwd ; ls -all
/lib/modules
total 8
drwxr-xr-x 4 root root 1024 May 8 13:32 .
drwxr-xr-x 15 root root 5120 May 7 15:47 ..
drwxr-xr-x 3 root root 1024 May 3 07:26 2.6.18-3-k7
drwxr-xr-x 4 root root 1024 May 4 15:31 2.6.18-4-k7

I hope that was OK.


$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda1 270969 207387 49126 81% /
tmpfs 517936 0 517936 0% /lib/init/rw
udev 10240 92 10148 1% /dev
tmpfs 517936 0 517936 0% /dev/shm
/dev/hda5 14421344 5842460 7846324 43% /home
/dev/hda6 4807056 2903168 1659704 64% /usr
/dev/hda7 918322 483257 386069 56% /var
/dev/hda8 918322 16487 852839 2% /tmp
/dev/hda9 4807056 200528 4362344 5% /usr/local
/dev/hda11 47383396 2431172 42545288 6% /extra
/dev/hda12 918322 16452 852874 2% /others
/dev/hdb1 861728 16416 801540 3% /stuff
/dev/hdb5 5336664 1114876 3950696 23% /storage

Hmm. Where did 40.8MB free, I was supposed to get, go? Were they not
from /boot?
--
"What reason, like the careful ant, draws laboriously together, the wind of accident sometimes collects in a moment." --Friedrich von Schiller
/\___/\
/ /\ /\ \ Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

Ant wrote:
>
> # apt-get remove kernel-headers-2.6.8-3 kernel-headers-2.6.8-3-k7
[snip]
> Hmm. Where did 40.8MB free, I was supposed to get, go? Were they not
> from /boot?

Nope. The kernel headers can be found in /usr/include/linux and
/usr/include/asm.

(Under /boot you'll only find stuff that is essential for booting. The
kernel headers are used when compiling stuff, not for booting.)

> > # apt-get remove kernel-headers-2.6.8-3 kernel-headers-2.6.8-3-k7
> [snip]
> > Hmm. Where did 40.8MB free, I was supposed to get, go? Were they not
> > from /boot?

> Nope. The kernel headers can be found in /usr/include/linux and
> /usr/include/asm.

> (Under /boot you'll only find stuff that is essential for booting. The
> kernel headers are used when compiling stuff, not for booting.)

Thanks! I always thought headers were required for modules (not just
compiling). Heh, I am still learning Linux a lot. :)
--
"What reason, like the careful ant, draws laboriously together, the wind of accident sometimes collects in a moment." --Friedrich von Schiller
/\___/\
/ /\ /\ \ Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )