Re: My zypper dissapeared

On 2008-08-27, houghi <houghi@xxxxxxxxxxxxxxxxxx> wrote:
Vahis wrote:
OK, so instead of directly putting `zypper` at boot time, you use `at
zypper` at boot time. OK, cool. Nice to know.
Obviously you should still let the shutdown still do the `zypper`
directly (and let it finish) because otherwise it might never happen.


Then maybe just:
zypper --quiet up -y -t patch

Otherwise you never get the kernel updates.

No, because when you get the kernel, you need to reboot. Not something
you want to do.

But this was done at shutdown, so there's gonna be a boot?

So again what I propose is:
1) Machines that seldom are durned off
a) just use cron

I do. +email tells me when to do interactive things, I will choose time.

2) Machines that are often turned off
a) With the boot do the update without the kernel. That way you
always have the latest version. Use the `at` to do it when
the PC is idle
b) With the shutdown do the update with the kernel. That way
if there is something, you need to reboot and that is what
you are doing anyway.

This should be made available in YaST to choose. Just like the current
"Automatic Updates"

Make a request, I'll vote.


Obviously if you have a LOT of PC's, like in an offic, you will also
have a server, so use that to do get the updates and download from
there. No need to bother the servers on the internet with 15.000
downloads at 09:00 and 17:00

The server would do it at night time on an odd minute.

Very good practice. Also the 50 or whatever PC:s should be cloned with
the aid of a disk image to start with. Or at least with AutoYaST which
I've never tried.


OTOH it could be wise to install the new kernel first next to the old
one and test it for a while before making it default and removing the
old one.

I had once (ages ago) a non booting kernel and did that for a while.
I gave it up when there was no trouble ever after.

There was an incident once and that lasted for a few hours. So people
doing the updates then AND did not pass the interactive omnes where
affected.

I was even more newbie then than now, I was in shit. I don't remember
how I solved it. Now I would know, of course :)


Maybe I'll do that again next time.

Once for I believe a 3 hour window in 10 years for something you won't
be affected by if you not install the kernels automagically is not a
real issue. I am sure I (and you)) will make more errors by overwriting
the wrong kernel.

This is because I've just changed to 64 bit (and more ram + a four cores)
and a lot is new to me, I'm suspicious :)

Then don't do automagick kernel updates.

We'll see. Right now I'm about to compile and install a module for the
onboard nic. Unless there's a better solution.

I'll start another thread about that.


--
Vahis
http://waxborg.servepics.com
Congressman Wilson has an expression:
"You can teach them to type, but you can't teach them to grow tits."
.

Relevant Pages

  • Re: FC5, And FC6 wont shutdown completely
    ... The last 7 entries from the shutdown messages are. ... Shutdown with the 2.6.15 kernel runs to completion, ... that this problem has started since some update on FC5. ... Neither had the updates which seem to have caused this problem, ...
    (Fedora)
  • Re: FC5, And FC6 wont shutdown completely
    ... and since some updates to ... FC5, kernels later than the original kernel installed from the CDROM ... refuse to shutdown cmpletely. ...
    (Fedora)
  • Re: grubby details of grub2
    ... Somewhat to my amazement I got it working. I even dual boot to ... custom kernel parameters, for example.). ... You might also want to suppress the linux rescue mode entries. ... You will have to manually make any updates to the custom ...
    (Ubuntu)
  • Re: grubby details of grub2
    ... Somewhat to my amazement I got it working. I even dual boot to ... custom kernel parameters, for example.). ... You might also want to suppress the linux rescue mode entries. ... You will have to manually make any updates to the custom ...
    (Ubuntu)
  • Re: Grub Question after updates ????
    ... comment out or remove the section with the old kernel. ... > boot with Grub. ... Things were fine until I installed the updates. ... > boot grub I have 2 versions of Kernel. ...
    (alt.os.linux.redhat)