[Cooker] nice cron scripts

2001-11-30 Thread Werth (hrzpub)

Hy,
I'm up late and my compi just turned unusable for viewing movies. I
think that all cron scripts should use nice -19 to be nice to the user.
If he does work on the system he won't be disturbed. If he doesn't work
there is no problem at all. Some problems may occure if the system is
used for calculations and the scripts don't get enough time in 24h to
gzip all files. Would this be a problem?
Alexander Werth

-- 
The right to read is a battle being fought today...
http://www.gnu.org/philosophy/right-to-read.html





Re: [Cooker] Kernel Panic: VFS unable to mount root on 3:01

2001-08-06 Thread Werth (hrzpub)

Hy,
We just need more info to solve this. Let's see:
First of all we need to know if the root file system is working at  all.
Boot the rescue system from Your Mandrake CD and try to mount root. Try
fsck /dev/[your root dev here].
Am 05 Aug 2001 05:55:51 + schrieb StrogKILR:
> 
> I get this error when I reboot the machine and go from win98
> to mandrake.
Describe the process You used. I suppose You used loadlin somehow.
Do You have a driver for large drive support installed like ezDrive? But
then I think this wouldn't be a problem. Can You apply loadlin from
MS-DOS before You start Microsoft Windows 98? 
> but I believe I also get it just simply during a cold
> boot to mandrake.
What? You hadn't tested this? Or is this an irregular happening problem?
> At first it was happening in GRUB (most people seem
> to have the problem in lilo, so I switched to lilo and I'm still
> having the problem.
What about posting the /etc/lilo.conf file to this list?
a list of the partition tables with fdisk /dev/hda would be nice.
>   Does anyone have a good solution for this other than
> reinstalling MDK 8 ?
Reinstalling would be a good choice if the root file system is damaged
and can't be repaired. You don't need to reformat Your /home partition.
Otherwise I would prefer to repair the system.

> lilo boots from the first hard drive, which is the linux one.
So You are booting lilo first? Are You sure You didn't start lilo from
Your master boot record and change the lilo configuration on a
partition?

After all setting up a boot environment isn't as simple as it should be.
Is there a way to restore the MBR? I mean a way to make the MBR listen
to the active flag again other than starting fdisk /mbr from MS DOS?

Alexander Werth