Re: trying to understand/purge linux-image-2.6.32-trunk-686
H.S. wrote: There was a slight screw-up with my mount points of /boot earlier today, when I was doing a bit of house cleaning. I purged some old kernels and installed a new one while /boot was mounted on a different partition (another story, sigh!). I noticed the problems and fixed that and rebooted with proper mounting. This, of course, resulted in the kernel files still in (correct) /boot that were supposed to have been purged. To fix that, with /boot correctly mounted, I reinstalled the kernel packages that I had purged and then purged them. Now, after doing this, I still have this kernel in /boot: $ ls -1 /boot/*trunk* /boot/config-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686.bak /boot/System.map-2.6.32-trunk-686 /boot/vmlinuz-2.6.32-trunk-686 However, I am not sure to which package this belongs: $ dpkg -l linux-image-2\.6\.32* | grep trunk un linux-image-2.6.32-trunk-686 none (no description available) If that is its package, apt can't find it: $ apt-cache show linux-image-2.6.32-trunk-686 W: Unable to locate package linux-image-2.6.32-trunk-686 E: No packages found Anybody know what is the deal with this kernel image? What am I missing here? What about 'dpkg -P 2.6.32-trunk-686'? Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hu5ndi$bu...@dough.gmane.org
Re: trying to understand/purge linux-image-2.6.32-trunk-686
On 02/06/10 09:47 AM, Hugo Vanwoerkom wrote: H.S. wrote: Now, after doing this, I still have this kernel in /boot: $ ls -1 /boot/*trunk* /boot/config-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686.bak /boot/System.map-2.6.32-trunk-686 /boot/vmlinuz-2.6.32-trunk-686 However, I am not sure to which package this belongs: $ dpkg -l linux-image-2\.6\.32* | grep trunk un linux-image-2.6.32-trunk-686 none (no description available) If that is its package, apt can't find it: $ apt-cache show linux-image-2.6.32-trunk-686 W: Unable to locate package linux-image-2.6.32-trunk-686 E: No packages found Anybody know what is the deal with this kernel image? What am I missing here? What about 'dpkg -P 2.6.32-trunk-686'? It is already being shown as not installed. In fact, I am trying to install it. The problem with this kernel is that I purged it when /boot was mistakenly mounted on some other device. So apt worked as far as its database is concerned, but the package's files remained on the original /boot. Now that I have the correct boot, I would like to install the package again and then follow by purging it so that aptitude now removes all the files from the correct /boot. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hu5s8i$k...@dough.gmane.org
Re: trying to understand/purge linux-image-2.6.32-trunk-686
On Wed, Jun 02, 2010 at 11:10:09AM -0400, H.S. wrote: H.S. wrote: Now, after doing this, I still have this kernel in /boot: $ ls -1 /boot/*trunk* /boot/config-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686.bak /boot/System.map-2.6.32-trunk-686 /boot/vmlinuz-2.6.32-trunk-686 The problem with this kernel is that I purged it when /boot was mistakenly mounted on some other device. So apt worked as far as its database is concerned, but the package's files remained on the original /boot. Now that I have the correct boot, I would like to install the package again and then follow by purging it so that aptitude now removes all the files from the correct /boot. Since they are stale files, not associated with any installed package, why not simply delete the files? Cheers, Tom -- What you don't know won't help you much either. -- D. Bennett signature.asc Description: Digital signature
Re: trying to understand/purge linux-image-2.6.32-trunk-686
On 02/06/10 11:19 AM, Tom Furie wrote: On Wed, Jun 02, 2010 at 11:10:09AM -0400, H.S. wrote: H.S. wrote: Now, after doing this, I still have this kernel in /boot: $ ls -1 /boot/*trunk* /boot/config-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686.bak /boot/System.map-2.6.32-trunk-686 /boot/vmlinuz-2.6.32-trunk-686 Since they are stale files, not associated with any installed package, why not simply delete the files? Yes, that is one option. But how do I make sure I got all the stale files? If a package is known by apt, I can use dpkg -L package name to see which files are installed and where. In this case, however, dpkg cannot tell me that. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hu5uee$94...@dough.gmane.org
Re: trying to understand/purge linux-image-2.6.32-trunk-686
On Wednesday 02 June 2010 10:47:26 H.S. wrote: On 02/06/10 11:19 AM, Tom Furie wrote: On Wed, Jun 02, 2010 at 11:10:09AM -0400, H.S. wrote: H.S. wrote: Now, after doing this, I still have this kernel in /boot: $ ls -1 /boot/*trunk* /boot/config-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686.bak /boot/System.map-2.6.32-trunk-686 /boot/vmlinuz-2.6.32-trunk-686 Since they are stale files, not associated with any installed package, why not simply delete the files? Yes, that is one option. But how do I make sure I got all the stale files? If a package is known by apt, I can use dpkg -L package name to see which files are installed and where. In this case, however, dpkg cannot tell me that. cruft can. Package: cruft State: not installed Version: 0.9.12 Priority: optional Section: admin Maintainer: Marcin Owsiany porri...@debian.org Uncompressed Size: 1,348k Depends: libc6 (= 2.7-1), file Description: Find any cruft built up on your system cruft is a program to look over your system for anything that shouldn't be there, but is; or for anything that should be there, but isn't. It bases most of its results on dpkg's database, as well as a list of `extra files' that can appear during the lifetime of various packages. cruft is still in pre-release; your assistance in improving its accuracy and performance is appreciated. Homepage: http://alioth.debian.org/projects/cruft/ -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: trying to understand/purge linux-image-2.6.32-trunk-686
On Wed, Jun 02, 2010 at 11:47:26AM -0400, H.S. wrote: On 02/06/10 11:19 AM, Tom Furie wrote: Since they are stale files, not associated with any installed package, why not simply delete the files? Yes, that is one option. But how do I make sure I got all the stale files? If a package is known by apt, I can use dpkg -L package name to see which files are installed and where. In this case, however, dpkg cannot tell me that. As far as I can tell, generally linux-image* puts files in /lib/modules, /boot, /usr/share/doc, and /usr/share/bug. Now given that -trunk should never have made it to the repo's there may or may not be other files to find, but that should be a good start, and as mentioned in another reply, cruft might be able to help with any others. Cheers, Tom -- Frankfort, Kentucky, makes it against the law to shoot off a policeman's tie. signature.asc Description: Digital signature
Re: trying to understand/purge linux-image-2.6.32-trunk-686
On 02/06/10 11:50 AM, Boyd Stephen Smith Jr. wrote:
On Wednesday 02 June 2010 10:47:26 H.S. wrote:
On 02/06/10 11:19 AM, Tom Furie wrote:
On Wed, Jun 02, 2010 at 11:10:09AM -0400, H.S. wrote:
H.S. wrote:
Now, after doing this, I still have this kernel in /boot:
$ ls -1 /boot/*trunk*
/boot/vmlinuz-2.6.32-trunk-686
Since they are stale files, not associated with any installed package,
why not simply delete the files?
Yes, that is one option. But how do I make sure I got all the stale
files? If a package is known by apt, I can use dpkg -L package name
to see which files are installed and where. In this case, however, dpkg
cannot tell me that.
cruft can.
I tried cruft on my /boot partition and got more than I bargained for.
It listed the files related to the package in question and some others
too. They are:
/boot/System.map-2.6.32-trunk-686
/boot/config-2.6.32-trunk-686
/boot/initrd.img-2.6.17-2-486.bak
/boot/initrd.img-2.6.26-2-686
/boot/initrd.img-2.6.26-2-686.bak
/boot/initrd.img-2.6.32-3-686
/boot/initrd.img-2.6.32-trunk-686
/boot/initrd.img-2.6.32-trunk-686.bak
/boot/vmlinuz-2.6.32-trunk-686
I understand the files with 'trunk' in them, but the rest I am not why
they are there since I have the following kernels installed:
$ dpkg -l linux-image* | grep ^i | awk '{print $2}'
linux-image-2.6-686
linux-image-2.6.26-2-686
linux-image-2.6.32-3-686
linux-image-686
And besides these, cruft also listed tons of /boot/grub files as
unexplained.
--
Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/hu62es$pa...@dough.gmane.org
Re: trying to understand/purge linux-image-2.6.32-trunk-686
Boyd Stephen Smith Jr. wrote: On Wednesday 02 June 2010 10:47:26 H.S. wrote: On 02/06/10 11:19 AM, Tom Furie wrote: On Wed, Jun 02, 2010 at 11:10:09AM -0400, H.S. wrote: H.S. wrote: Now, after doing this, I still have this kernel in /boot: $ ls -1 /boot/*trunk* /boot/config-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686.bak /boot/System.map-2.6.32-trunk-686 /boot/vmlinuz-2.6.32-trunk-686 Since they are stale files, not associated with any installed package, why not simply delete the files? Yes, that is one option. But how do I make sure I got all the stale files? If a package is known by apt, I can use dpkg -L package name to see which files are installed and where. In this case, however, dpkg cannot tell me that. cruft can. Package: cruft State: not installed Version: 0.9.12 Priority: optional Section: admin Maintainer: Marcin Owsiany porri...@debian.org Uncompressed Size: 1,348k Depends: libc6 (= 2.7-1), file Description: Find any cruft built up on your system cruft is a program to look over your system for anything that shouldn't be there, but is; or for anything that should be there, but isn't. It bases most of its results on dpkg's database, as well as a list of `extra files' that can appear during the lifetime of various packages. cruft is still in pre-release; your assistance in improving its accuracy and performance is appreciated. Homepage: http://alioth.debian.org/projects/cruft/ So I installed cruft and it produced a 24MB report. I don't even know how to look at that. And what means ' missing USERS '? Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hu635g$rn...@dough.gmane.org
Re: trying to understand/purge linux-image-2.6.32-trunk-686
On 02/06/10 12:36 PM, Tom Furie wrote: On Wed, Jun 02, 2010 at 11:47:26AM -0400, H.S. wrote: On 02/06/10 11:19 AM, Tom Furie wrote: Since they are stale files, not associated with any installed package, why not simply delete the files? Yes, that is one option. But how do I make sure I got all the stale files? If a package is known by apt, I can use dpkg -L package name to see which files are installed and where. In this case, however, dpkg cannot tell me that. As far as I can tell, generally linux-image* puts files in /lib/modules, /boot, /usr/share/doc, and /usr/share/bug. Now given that -trunk should I have tried dpkg -L with installed kernels to see where they usually install files. So if push comes to shove, I can manually delete trunk kernel related files. I would be great to do this dpkg-way, however. Thanks. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hu638u$sa...@dough.gmane.org
Re: trying to understand/purge linux-image-2.6.32-trunk-686
On Wed, Jun 02, 2010 at 01:09:48PM -0400, H.S. wrote: On 02/06/10 12:36 PM, Tom Furie wrote: As far as I can tell, generally linux-image* puts files in /lib/modules, /boot, /usr/share/doc, and /usr/share/bug. Now given that -trunk should I have tried dpkg -L with installed kernels to see where they usually install files. So if push comes to shove, I can manually delete trunk kernel related files. I would be great to do this dpkg-way, however. Unfortanately, without access to the relevant package (maybe it's still lying around on somebody's system), I really don't think there's a dpkg-way to solve this. Cheers, Tom -- Democracy is the worst form of government except all those other forms that have been tried from time to time. -- Winston Churchill signature.asc Description: Digital signature
Re: trying to understand/purge linux-image-2.6.32-trunk-686
On Wednesday 02 June 2010 11:55:55 H.S. wrote:
I tried cruft on my /boot partition and got more than I bargained for.
It listed the files related to the package in question and some others
too. They are:
/boot/System.map-2.6.32-trunk-686
/boot/config-2.6.32-trunk-686
/boot/initrd.img-2.6.17-2-486.bak
/boot/initrd.img-2.6.26-2-686
/boot/initrd.img-2.6.26-2-686.bak
/boot/initrd.img-2.6.32-3-686
/boot/initrd.img-2.6.32-trunk-686
/boot/initrd.img-2.6.32-trunk-686.bak
/boot/vmlinuz-2.6.32-trunk-686
I understand the files with 'trunk' in them, but the rest I am not why
they are there since I have the following kernels installed:
$ dpkg -l linux-image* | grep ^i | awk '{print $2}'
linux-image-2.6-686
linux-image-2.6.26-2-686
linux-image-2.6.32-3-686
linux-image-686
Then you can (or at least should be able to) confirm that the files listed are
not owned by those packages.
They may still be important files for your system, and the {pre,post}inst
routines may have created them. However, they are unknown to the dpkg
database, which is why cruft identifies them.
I'm sure the cruft maintainer / upstream would like your assistance in making
cruft better.
And besides these, cruft also listed tons of /boot/grub files as
unexplained.
Are they owned by a package?
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
b...@iguanasuicide.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/
signature.asc
Description: This is a digitally signed message part.
can somebody list contents of linux-image-2.6.32-trunk-686? [was: Re: trying to understand/purge linux-image-2.6.32-trunk-686]
On 02/06/10 01:36 PM, Tom Furie wrote: On Wed, Jun 02, 2010 at 01:09:48PM -0400, H.S. wrote: On 02/06/10 12:36 PM, Tom Furie wrote: As far as I can tell, generally linux-image* puts files in /lib/modules, /boot, /usr/share/doc, and /usr/share/bug. Now given that -trunk should I have tried dpkg -L with installed kernels to see where they usually install files. So if push comes to shove, I can manually delete trunk kernel related files. I would be great to do this dpkg-way, however. Unfortanately, without access to the relevant package (maybe it's still lying around on somebody's system), I really don't think there's a dpkg-way to solve this. If somebody has the package linux-image-2.6.32-trunk-686 on their system someplace (may be even in /var/cache/apt/archives/) or installed, I would like to know its contents. If the package is installed, the following output will be great: $ dpkg -L linux-image-2.6.32-trunk-686 Thanks in advance. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hu65e8$53...@dough.gmane.org
Re: trying to understand/purge linux-image-2.6.32-trunk-686
On 02/06/10 01:46 PM, Boyd Stephen Smith Jr. wrote:
On Wednesday 02 June 2010 11:55:55 H.S. wrote:
I understand the files with 'trunk' in them, but the rest I am not why
they are there since I have the following kernels installed:
$ dpkg -l linux-image* | grep ^i | awk '{print $2}'
linux-image-2.6-686
linux-image-2.6.26-2-686
linux-image-2.6.32-3-686
linux-image-686
Then you can (or at least should be able to) confirm that the files listed
are
not owned by those packages.
Yes, I agree. But the tons of grub files didn't make me very confident
about the capability of curft (on a related note, I am quite confident
about deborphan though).
They may still be important files for your system, and the {pre,post}inst
routines may have created them. However, they are unknown to the dpkg
database, which is why cruft identifies them.
I'm sure the cruft maintainer / upstream would like your assistance in making
cruft better.
Sure, won't mind giving feedback based on my experiences. How? On the
dev mailing list?
And besides these, cruft also listed tons of /boot/grub files as
unexplained.
Are they owned by a package?
No idea. I never fiddled with grub (except when dpkg did its pre and
post kernel installation/purge stuff) during the short during of /boot
mounting problem. The only command I used one was update-grub.
Thanks.
--
Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/hu65l8$5t...@dough.gmane.org
Re: can somebody list contents of linux-image-2.6.32-trunk-686? [was: Re: trying to understand/purge linux-image-2.6.32-trunk-686]
On Mi, 02 iun 10, 13:46:47, H.S. wrote: If somebody has the package linux-image-2.6.32-trunk-686 on their system someplace (may be even in /var/cache/apt/archives/) or installed, I would like to know its contents. If the package is installed, the following output will be great: $ dpkg -L linux-image-2.6.32-trunk-686 $ ls /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-* /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-1_amd64.deb /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-2_amd64.deb /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-3_amd64.deb /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-4_amd64.deb /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-5_amd64.deb I only have these, does it help? Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: can somebody list contents of linux-image-2.6.32-trunk-686? [was: Re: trying to understand/purge linux-image-2.6.32-trunk-686]
On 02/06/10 03:02 PM, Andrei Popescu wrote: On Mi, 02 iun 10, 13:46:47, H.S. wrote: If somebody has the package linux-image-2.6.32-trunk-686 on their system someplace (may be even in /var/cache/apt/archives/) or installed, I would like to know its contents. If the package is installed, the following output will be great: $ dpkg -L linux-image-2.6.32-trunk-686 $ ls /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-* /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-1_amd64.deb /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-2_amd64.deb /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-3_amd64.deb /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-4_amd64.deb /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-5_amd64.deb I only have these, does it help? A bit, yes. If you can give the output of the following command, it will be better (list contents of the specified package, you can use any from the list you gave above): $ dpkg -L linux-image-2.6.32-trunk-amd64_2.6.32-1_amd64.deb Thanks. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hu6a4t$r8...@dough.gmane.org
Re: can somebody list contents of linux-image-2.6.32-trunk-686? [was: Re: trying to understand/purge linux-image-2.6.32-trunk-686]
On 02/06/10 03:07 PM, H.S. wrote: On 02/06/10 03:02 PM, Andrei Popescu wrote: On Mi, 02 iun 10, 13:46:47, H.S. wrote: If somebody has the package linux-image-2.6.32-trunk-686 on their system someplace (may be even in /var/cache/apt/archives/) or installed, I would like to know its contents. If the package is installed, the following output will be great: $ dpkg -L linux-image-2.6.32-trunk-686 $ ls /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-* /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-1_amd64.deb /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-2_amd64.deb /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-3_amd64.deb /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-4_amd64.deb /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-5_amd64.deb I only have these, does it help? A bit, yes. If you can give the output of the following command, it will be better (list contents of the specified package, you can use any from the list you gave above): $ dpkg -L linux-image-2.6.32-trunk-amd64_2.6.32-1_amd64.deb Sorry, my bad. The command should be: $ dpkg -L name of package installed | grep -v 'lib.modules' or, if you want to list the contents of a deb file (instead of an installed package), the following will give the same info (might need to be root or use sudo for apt's cache files): # sudo dpkg -c /path/to/foo.deb | grep -v 'lib.modules' The grep command effectively filters out all the lines with lib/modules in them. Thanks. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hu6b58$vq...@dough.gmane.org
Re: can somebody list contents of linux-image-2.6.32-trunk-686? [was: Re: trying to understand/purge linux-image-2.6.32-trunk-686]
On Mi, 02 iun 10, 15:24:23, H.S. wrote: or, if you want to list the contents of a deb file (instead of an installed package), the following will give the same info (might need to be root or use sudo for apt's cache files): No, root is not needed, since the debs in apt's cacher are world readable. # sudo dpkg -c /path/to/foo.deb | grep -v 'lib.modules' From within vim: :r !dpkg -c /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-1_amd64.deb | grep -v 'lib.modules' drwxr-xr-x root/root 0 2009-12-06 20:13 ./ drwxr-xr-x root/root 0 2009-12-06 20:13 ./boot/ -rw-r--r-- root/root 1608485 2009-12-06 20:13 ./boot/System.map-2.6.32-trunk-amd64 -rw-r--r-- root/root 2331488 2009-12-06 20:13 ./boot/vmlinuz-2.6.32-trunk-amd64 -rw-r--r-- root/root105244 2009-12-06 20:13 ./boot/config-2.6.32-trunk-amd64 drwxr-xr-x root/root 0 2009-12-06 20:13 ./usr/ drwxr-xr-x root/root 0 2009-12-06 20:13 ./usr/share/ drwxr-xr-x root/root 0 2009-12-06 20:13 ./usr/share/doc/ drwxr-xr-x root/root 0 2009-12-06 20:13 ./usr/share/doc/linux-image-2.6.32-trunk-amd64/ -rw-r--r-- root/root114736 2009-12-06 19:18 ./usr/share/doc/linux-image-2.6.32-trunk-amd64/changelog.Debian.gz -rw-r--r-- root/root 2167 2009-07-18 00:10 ./usr/share/doc/linux-image-2.6.32-trunk-amd64/copyright drwxr-xr-x root/root 0 2009-12-06 20:13 ./usr/share/bug/ drwxr-xr-x root/root 0 2009-12-06 20:13 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/ -rw-r--r-- root/root 111 2008-01-25 10:51 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/include-1cmdline -rw-r--r-- root/root 184 2009-10-04 21:55 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/control -rw-r--r-- root/root29 2009-12-06 20:13 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/info -rw-r--r-- root/root 363 2009-10-04 19:55 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/presubj -rwxr-xr-x root/root 451 2009-10-04 22:19 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/script -rw-r--r-- root/root 1369 2009-11-17 03:18 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/include-1tainted -rw-r--r-- root/root 162 2008-05-20 23:30 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/include-sound -rw-r--r-- root/root 293 2009-10-04 23:01 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/include-usb -rw-r--r-- root/root 106 2007-05-21 23:54 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/include-0version -rw-r--r-- root/root 1180 2009-11-21 20:22 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/include-network -rw-r--r-- root/root 100 2007-03-11 15:25 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/include-modules -rw-r--r-- root/root 308 2009-10-04 19:55 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/include-dmesg -rw-r--r-- root/root 1173 2009-10-04 22:07 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/include-model -rw-r--r-- root/root 300 2009-10-04 22:07 ./usr/share/bug/linux-image-2.6.32-trunk-amd64/include-pci drwxr-xr-x root/root 0 2009-12-06 20:13 ./lib/ Hope this helps ;) Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: can somebody list contents of linux-image-2.6.32-trunk-686? [was: Re: trying to understand/purge linux-image-2.6.32-trunk-686]
On 02/06/10 03:50 PM, Andrei Popescu wrote: On Mi, 02 iun 10, 15:24:23, H.S. wrote: or, if you want to list the contents of a deb file (instead of an installed package), the following will give the same info (might need to be root or use sudo for apt's cache files): No, root is not needed, since the debs in apt's cacher are world readable. Yes, you are right. I had to use sudo because I have linked /var/cache/arpt/archives to another partition (long story :( ) and there the debs are not world readable. # sudo dpkg -c /path/to/foo.deb | grep -v 'lib.modules' From within vim: :r !dpkg -c /var/cache/apt/archives/linux-image-2.6.32-trunk-amd64_2.6.32-1_amd64.deb | grep -v 'lib.modules' Yes, it does. Thanks a ton. Regards. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hu6d5s$7o...@dough.gmane.org
Re: can somebody list contents of linux-image-2.6.32-trunk-686? [was: Re: trying to understand/purge linux-image-2.6.32-trunk-686]
On Wed, 2010-06-02 at 13:46 -0400, H.S. wrote: snip If somebody has the package linux-image-2.6.32-trunk-686 on their system someplace (may be even in /var/cache/apt/archives/) or installed, I would like to know its contents. snip snapshot.debian.org might be useful, it archives all debian packages that have been produced. You have a choice of the five different releases of the package you mention at: http://snapshot.debian.org/package/linux-2.6/2.6.32-5/#linux-image-2.6.32-trunk-686_2.6.32-5 -- Tixy () The ASCII Ribbon Campaign (www.asciiribbon.org) /\ Against HTML e-mail and proprietary attachments -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1275517535.2078.3.ca...@computer2.home
Re: can somebody list contents of linux-image-2.6.32-trunk-686? [was: Re: trying to understand/purge linux-image-2.6.32-trunk-686]
Correction... On Wed, 2010-06-02 at 23:25 +0100, Tixy wrote: snapshot.debian.org might be useful, it archives all debian packages that have been produced. You have a choice of the five different releases of the package you mention at: http://snapshot.debian.org/package/linux-2.6/2.6.32-5/#linux-image-2.6.32-trunk-686_2.6.32-5 That URL should have been http://snapshot.debian.org/binary/linux-headers-2.6.32-trunk-686/ -- Tixy () The ASCII Ribbon Campaign (www.asciiribbon.org) /\ Against HTML e-mail and proprietary attachments -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1275517975.2078.5.ca...@computer2.home
