"Michael M." <[EMAIL PROTECTED]> writes:
> But I think you did not hear from most of the legions of Sid users for
> whom the Xorg upgrade proceeded without a single issue.
As far as I could tell, the most annoying problems happened only if you had
customized xorg.conf, which I suppose the bulk of
Michael M. wrote:
Sumo Wrestler (or just ate too much) wrote:
Yes, I know this is not Sid, but I read with interest the many posts
covering the Xorg upgrade. I could practically hear the yelping.
But I think you did not hear from most of the legions of Sid users for
whom the Xorg upgrade
Sumo Wrestler (or just ate too much) wrote:
Yes, I know this is not Sid, but I read with interest the many posts
covering the Xorg upgrade. I could practically hear the yelping.
But I think you did not hear from most of the legions of Sid users for
whom the Xorg upgrade proceeded without a
On Tue, Apr 25, 2006 at 09:40:48AM -0700, Andrew Sackville-West wrote:
> On Tue, Apr 25, 2006 at 11:06:42AM -0400, [EMAIL PROTECTED] wrote:
> > On Mon, Apr 24, 2006 at 09:41:09PM +0300, Andrei Popescu wrote:
> > >
> > > If the filename doesn't change (of the kernel image) i think neither
> > > gru
On Tue, Apr 25, 2006 at 04:33:51PM -0400, Matthias Julius wrote:
> Andrew Sackville-West <[EMAIL PROTECTED]> writes:
>
> > Isn't that the purpose of symlinks to kernel images? so you don't have
> > to rerun for new kernels with same name?
>
> This is so that the lilo.conf doesn't need to be chang
Andrew Sackville-West <[EMAIL PROTECTED]> writes:
> Isn't that the purpose of symlinks to kernel images? so you don't have
> to rerun for new kernels with same name?
This is so that the lilo.conf doesn't need to be changed. The lilo
bootloader doesn't know anything about filesystems. And it doe
On Tue, Apr 25, 2006 at 11:06:42AM -0400, [EMAIL PROTECTED] wrote:
> On Mon, Apr 24, 2006 at 09:41:09PM +0300, Andrei Popescu wrote:
> >
> > If the filename doesn't change (of the kernel image) i think neither
> > grub nor lilo need the update. But it doesn't hurt. Unless you changed
> > menu.lst
On Mon, Apr 24, 2006 at 09:41:09PM +0300, Andrei Popescu wrote:
>
> If the filename doesn't change (of the kernel image) i think neither
> grub nor lilo need the update. But it doesn't hurt. Unless you changed
> menu.lst without reading/understanding the instructions inside.
lilo has to be called
Andreas Rippl wrote:
On Sun, Apr 23, 2006 at 04:46:56PM -0500, Sumo Wrestler (or just ate too much)
wrote:
[...]
Hi Sumo,
Hi Andreas,
I have gone through the update (without giving much thought I have to
admit) and there was no trouble here. I guess I didn't give a second
thought because
Andreas Rippl wrote:
On Sun, Apr 23, 2006 at 04:46:56PM -0500, Sumo Wrestler (or just ate too much)
wrote:
Joris Huizer wrote:
I don't know exactly why libc6 is upgraded, but the upgrade seems to be
part of the 3.1r2 update (see http://release.debian.org/stable/3.1/3.1r2/)
I got it too, just
Andrei Popescu wrote:
Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote:
John Hasler wrote:
Sumo Wrestler writes:
As Joris Huizer says, it's the new point release. I'll get it sometime,
but not now :)
There is no reason not to get it now. Point releases always go smoothly.
If you have been doing sec
Andrei writes:
> If the filename doesn't change (of the kernel image) i think neither grub
> nor lilo need the update.
Lilo does.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sun, Apr 23, 2006 at 04:46:56PM -0500, Sumo Wrestler (or just ate too much)
wrote:
> Joris Huizer wrote:
> >
> >I don't know exactly why libc6 is upgraded, but the upgrade seems to be
> >part of the 3.1r2 update (see http://release.debian.org/stable/3.1/3.1r2/)
> >I got it too, just tracking s
[EMAIL PROTECTED] wrote:
> On Mon, Apr 24, 2006 at 07:26:38PM +0300, Andrei Popescu wrote:
> > Joris Huizer <[EMAIL PROTECTED]> wrote:
> >
> > > Andrei Popescu wrote:
> > > >
> > > > Do you need to reboot after this upgrade? I'm asking because I did the
> > > > upgrade on a remote machine with s
On Mon, Apr 24, 2006 at 01:14:41PM -0400, [EMAIL PROTECTED] wrote:
> And if you use lilo to set up bootablility, you'd better run it *before*
> you reboot; otherwise it will not be able to find the new kernel. And
> the old one will have been replaced, if it's really just a bugfix of the
>
On Mon, Apr 24, 2006 at 07:26:38PM +0300, Andrei Popescu wrote:
> Joris Huizer <[EMAIL PROTECTED]> wrote:
>
> > Andrei Popescu wrote:
> > >
> > > Do you need to reboot after this upgrade? I'm asking because I did the
> > > upgrade on a remote machine with some hardware troubles and I am afraid
>
Joris Huizer <[EMAIL PROTECTED]> wrote:
> Andrei Popescu wrote:
> >
> > Do you need to reboot after this upgrade? I'm asking because I did the
> > upgrade on a remote machine with some hardware troubles and I am afraid
> > to reboot it.
> >
>
> Hmm... if you got a new kernel image you need to r
Andrei Popescu wrote:
Do you need to reboot after this upgrade? I'm asking because I did the
upgrade on a remote machine with some hardware troubles and I am afraid
to reboot it.
Hmm... if you got a new kernel image you need to restart the machine to
use it (untill then it's running with the
Andrei Popescu wrote:
Do you need to reboot after this upgrade? I'm asking because I did the
upgrade on a remote machine with some hardware troubles and I am afraid
to reboot it.
There shouldn't be a need to do so; if some service needs to be
restarted, just do the `/etc/init.d/ restart`, th
Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote:
> John Hasler wrote:
> > Sumo Wrestler writes:
> >> As Joris Huizer says, it's the new point release. I'll get it sometime,
> >> but not now :)
> >
> > There is no reason not to get it now. Point releases always go smoothly.
> > If you have been doing se
John Hasler wrote:
Sumo Wrestler writes:
As Joris Huizer says, it's the new point release. I'll get it sometime,
but not now :)
There is no reason not to get it now. Point releases always go smoothly.
If you have been doing security updates you already have most of it.
I got it without any p
Sumo Wrestler writes:
> As Joris Huizer says, it's the new point release. I'll get it sometime,
> but not now :)
There is no reason not to get it now. Point releases always go smoothly.
If you have been doing security updates you already have most of it.
--
John Hasler
--
To UNSUBSCRIBE, email
Christopher Nelson wrote:
On Sun, Apr 23, 2006 at 10:31:23AM -0500, Sumo Wrestler (or just ate too much)
wrote:
I just did an "aptitude update," and now when I attempt to upgrade,
aptitude says that it wants to upgrade libc6 and libc6-dev.
[...]
Again if it's the stable version, it should be g
Joris Huizer wrote:
I don't know exactly why libc6 is upgraded, but the upgrade seems to be
part of the 3.1r2 update (see http://release.debian.org/stable/3.1/3.1r2/)
I got it too, just tracking sarge too
HTH,
Thanks Joris, it does help.
Wow, we're going to get another point release. This
Florian Kulzer wrote:
You can use
aptitude changelog libc6 libc6-dev
Thanks, this'll be useful to me. I know it's in the man-page, but I
didn't think about it.
to see the changelogs for the new packages. Maybe that will tell you
what is up. If that does not work (I often have problems wi
Joris Huizer wrote:
>
> I don't know exactly why libc6 is upgraded, but the upgrade seems to be
> part of the 3.1r2 update (see http://release.debian.org/stable/3.1/3.1r2/)
> I got it too, just tracking sarge too
>
It has to do with the recent changes in daylight savings time in certain
parts of
Sumo Wrestler wrote:
> My question is "why are libc6 and libc6-dev being upgraded?"
IIRC, because of time zone changes.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
libc6 is updated in the point release to update timezone information and
fix a bug on the amd64 architecture. This is documented in the release
announcement under "Miscellaneous Bugfixes".
If you install apt-listchanges, it will show you the changelogs
before upgrading the packages, which is usefu
Sumo Wrestler (or just ate too much) wrote:
I'm using Sarge.
I just did an "aptitude update," and now when I attempt to upgrade,
aptitude says that it wants to upgrade libc6 and libc6-dev.
I know that those are pretty critical to the functioning of the system,
so I've temporarily put them on ho
On Sun, Apr 23, 2006 at 10:31:23 -0500, Sumo Wrestler (or just ate too much)
wrote:
> I'm using Sarge.
>
> I just did an "aptitude update," and now when I attempt to upgrade,
> aptitude says that it wants to upgrade libc6 and libc6-dev.
>
> I know that those are pretty critical to the functionin
On Sun, Apr 23, 2006 at 10:31:23AM -0500, Sumo Wrestler (or just ate too much)
wrote:
> I'm using Sarge.
>
> I just did an "aptitude update," and now when I attempt to upgrade,
> aptitude says that it wants to upgrade libc6 and libc6-dev.
>
> I know that those are pretty critical to the function
31 matches
Mail list logo