Linux PARISC architecture development
 help / color / mirror / Atom feed
From: bame@hp.com
To: Mihails Nikitins <nikitins@latnet.lv>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] PALO questions
Date: Thu, 14 Aug 2003 10:48:12 -0600	[thread overview]
Message-ID: <20030814164813.281BD733C4@fc.hp.com> (raw)
In-Reply-To: Message from Mihails Nikitins <nikitins@latnet.lv> of "Thu, 14 Aug 2003 19:36:08 +0300." <1060878968.3f3bba7807eb5@clients.latnet.lv>

> Hi all,
> 
> 1. PALO docs tell "recoverykernel" in palo.conf is the path to the kernel that
> you want to boot within a failsafe session, it will be stored in the 'f0'
> partition. Do I undertstand correctly that command like 
> palo &#8211;I /dev/sda
> copies file specified by paloc.conf line
> --recoverykernel=/boot/vmlinux   ?

Yes, that kernel is copied to the f0 partition (or wherever you designate)

> 2. Is it possible to see f0 partition contents? In HP-UX, there are commands
> working with LIF files like lifls and lifcp. How can I check if there is a
> recovery kernel in PALO area?

Palo shows the contents in a very crude form during booting.  There is
no file system as such, like LIF, in the f0 partition, thus no convenient
tools for that.  Thought about doing something like that but the
payoff doesn't seem worth it especially since we usually boot kernels
from the file system anyway.  Feel free to send me a patch for "palo --ls"
or something :-)

> 3. I noticed palo warns about bad DOS magic. Is it normal?

Harmless if annoying.  From the source:

            /* we're currently using 32-bit file seeks which is ok since
             * the IPL is also limited to 2G right now.  So on big disks
             * this next read may fail, and we need to let that happen
             * gracefully.
             */
            if (seekread(bootdev, (char *)&fb, sizeof fb, 512 * offset) == -1)
                break;
            if (fb.dosmagic[0] != 0x55 || fb.dosmagic[1] != 0xaa)
            {
                printf("Bad DOS magic in extended partition\n\r");
                break;
            }

Either the disk is improperly formatted or (more likely) the seekread()
call isn't returning the -1 error like it should.  Since we can't
boot from anything past the 2G limit anyway it doesn't matter.

      reply	other threads:[~2003-08-14 16:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-14 16:36 [parisc-linux] PALO questions Mihails Nikitins
2003-08-14 16:48 ` bame [this message]

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=20030814164813.281BD733C4@fc.hp.com \
    --to=bame@hp.com \
    --cc=nikitins@latnet.lv \
    --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