Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <joel.soete@tiscali.be>
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Cc: Helge Deller <deller@gmx.de>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] palo II
Date: Sun, 01 Jun 2003 17:51:29 +0000	[thread overview]
Message-ID: <3EDA3D21.8070400@tiscali.be> (raw)
In-Reply-To: <Pine.BSF.4.53.0306011402580.1237@e0-0.zab2.int.zabbadoz.net>

Bjoern A. Zeeb wrote:

>On Sun, 1 Jun 2003, Helge Deller wrote:
>
>  
>
>>>is there a chance that one can recover from s.t.h like this ?
>>>
>>>Command line for kernel: 'root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0
>>>palo_kernel=3/boot/vmlinux-2.5.60-pa1' Selected kernel:
>>>/boot/vmlinux-2.5.60-pa1 from partition 3
>>>ERROR: open /boot/vmlinux-2.5.60-pa1 from partition 3 failed
>>>      
>>>
>>You could boot a good kernel via tftp. That's how I test different kernels...
>>    
>>
>
>not a too bad idea but that's not the problem here.
>
>When palo cannot open the kernel and errors out shouldn't it fall back
>to the dialog and ask one to which fields to change instead of simply
>running into a dead end where I think I can only recover from with
>physical access to the machine ?
>
>  
>
Afaik no way right now and I think it would be a good idea to open a bug 
report about this subject.
The current palo status of is specialy anoying when you reboot a server 
as a N (selftest of about 1/4h) and you made some stupid typo (as you 
do: 60 in place of 69) .

Hmm if I still have some time to have a look on this (as well as for 
booting a compressed kernel), which is the best 'model' (the nearest of 
palo) that I would have to analyse?

Cheers,
    Joel

  reply	other threads:[~2003-06-01 17:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-01 13:04 [parisc-linux] palo II Bjoern A. Zeeb
2003-06-01 13:44 ` Helge Deller
2003-06-01 14:05   ` Bjoern A. Zeeb
2003-06-01 17:51     ` Joel Soete [this message]
2003-06-02 18:14     ` Grant Grundler
2003-06-02 18:29       ` Bjoern A. Zeeb
2003-06-02 19:40         ` Bjoern A. Zeeb
2003-06-04 10:42           ` Bjoern A. Zeeb
  -- strict thread matches above, loose matches on Subject: below --
2003-06-05 11:59 Joel Soete
2003-06-05 14:14 ` Bjoern A. Zeeb
2003-06-05 14:32   ` Matthew Wilcox
2003-06-05 15:15 Joel Soete
2003-06-05 15:23 ` Bjoern A. Zeeb
2003-06-05 18:44 ` Bjoern A. Zeeb
2003-06-05 18:53   ` Bjoern A. Zeeb
2003-06-11 17:46 Joel Soete
2003-06-11 17:51 ` Matthew Wilcox
2003-06-11 20:31   ` Stian Søiland
2003-06-11 20:32     ` Alan Cox
2003-06-12  6:13       ` Grant Grundler
2003-06-12  8:45       ` Joel Soete
2003-06-11 19:52 ` Bjoern A. Zeeb
2003-06-12  9:16   ` Joel Soete

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EDA3D21.8070400@tiscali.be \
    --to=joel.soete@tiscali.be \
    --cc=bzeeb-lists@lists.zabbadoz.net \
    --cc=deller@gmx.de \
    --cc=parisc-linux@lists.parisc-linux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox