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/
On Wed, 2010-06-02 at 13:46 -0400, 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.
snapshot.debian.org might be useful, it archives all debian package
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
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 re
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
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
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
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}'
>> l
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 h
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
>
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
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 mak
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
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
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 pack
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
> >
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.
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/Syste
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
>>
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
reboo
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 prop
21 matches
Mail list logo
