Re: lug-bg: Kernel panic timeout (LILO)

[danchev@email.domain.hidden (George Danchev)]

On 17 05 2003 15:19, Plamen Tonev wrote:
<em class="quotelev1">> On Sat, 17 May 2003 14:35:52 +0300 (EEST)
<em class="quotelev1">> "Marian Popov" <mano_at_pazardjik.com> wrote:
<em class="quotelev1">> 
<em class="quotelev1">>
<em class="quotelev2">> > Po princip kato kompilirash nov kernel e dobre da ne mu
<em class="quotelev2">> > davash make install a da si kopirash kernela rychno
<em class="quotelev2">> > v /boot ili kydeto iskash ot source direktoriata koato
<em class="quotelev2">> > beshe mai /arch/i386/... neshto si. Sled koeto si opisvash
<em class="quotelev2">> > v lilo.conf novia kernel no da si sedi i staria.
<em class="quotelev2">> > Pri tova povojenie pri boot ako crashne neshto
<em class="quotelev2">> > mojesh da resetnesh mashinata i s natiskane na ALT
<em class="quotelev2">> > pri boot sha ti izlezne menu za izbor na kernel.

:-) Mano bre .. podcenqvash horata ;-) toj pita za po-debeli raboti;-)

<em class="quotelev1">> Ne..ne..ne..
<em class="quotelev1">> Ok, treti opit za formulirane na vyprosa ;-)
<em class="quotelev1">> Razbira se che kato govorja za tova che mi trjabva takyv variant stava
<em class="quotelev1">> vypros che njamam  fizicheski dostyp do masihnata - inache zashto mi e
<em class="quotelev1">> takova chanchene kato moga da si puskam ot lilo prompt-a kakvoto iskam.
<em class="quotelev1">> Nikoi osven Alexandyr li ne razbra kakvo iskam...
<em class="quotelev1">> Btw..tova pitah za reboot-vaneto avtomatichnoto...pri kernel panic...sega
<em class="quotelev1">> ostava i momenta kak tova (i dali) moje da se navyrje s lilo,grub,whatever
<em class="quotelev1">> za da se osiguri fault safe reboot. 
<em class="quotelev1">> Plamen

Prodylzhavam ot tam deto stigna Velin ... i /proc/sys/kernel/panic =/= 0
kernel-a ste reboot-ne, sled koeto ste e neobhodimo nqkak si da e ukazno na 
machine-a BIOS da booti ot hard-a tam ... sled koeto ide OS loader-a... 
Ako da kazhem riskoviq kernel image NE e default-nat v lili.conf (see default 
<image>), to sled delay <sec/10> bi trqbvalo boot-ne default kernel image-a, 
kojto da kazhem e po-robust ;-) ... eventualni stops biha bili pri incidentno 
spirane na sistemata, fsck na / ... Ako si e ext3fs  v jounnal mode ORDERED, 
to mozhesh spokojno da skip-nesh check-a stoto ext3 ORDERED vinagi e v 
consistent state:

A feature of e2fsck is that it will regularly force a check of a 
        filesystem even if the filesystem is marked clean. Typically, this
        happens on every twentieth mount or every 180 days, whichever comes
        first.

        This still happens with ext3, and is quite possibly not what you want
        to happen - one of the reasons you chose ext3 was to avoid the 
downtime
        which is caused by a long fsck.

        So it is a good idea to turn this feature off for ext3. 
        To distable use the command

                   tune2fs -i 0 /dev/hdxx

<p>Sled kato se log-nesh posle vse pak ste napravish edin fsck zastoto, dori i v 
consistent state fs-a mozhe da sydyrzha inodes na ve4e nesystestvuvasti 
files, koeto ne e opasno, no e izlishen bokluk ... Obratnoto e opasno data 
t.e. files bez asociirani inodes ... (ask foldoc.org for fs inode, cqlata 
info za file-a se pazi tam;-)

<p>Preosmisli tazi posledovatelnost i testvaj lokalno na nqkoq machine i sled 
tova remote ... dont forget remote machine BIOS boot configuration ;-) 


-- 
pub  4096R/0E4BD0AB 2003-03-18
1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB <keyserver.bu.edu>
============================================================================
A mail-list of Linux Users Group - Bulgaria (bulgarian linuxers).
http://www.linux-bulgaria.org - Hosted by Internet Group Ltd. - Stara Zagora
To unsubscribe: http://www.linux-bulgaria.org/public/mail_list.html
============================================================================