From: James Smith <james@compusmithllc.com>
To: Frank Cornelis <Frank.Cornelis@rug.ac.be>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] firmware update using BOOTP
Date: 30 Sep 2002 15:56:19 -0500 [thread overview]
Message-ID: <1033419379.4785.33.camel@seventy> (raw)
In-Reply-To: <Pine.GSO.4.31.0209302241060.16124-100000@eduserv.rug.ac.be>
i installed all my 712's from bootp without upgrading & they went fine -
even the ones with the 1.9 firmwares
have you got a pointer to the firmware update info so i can check it out
the pros/cons myself ?
James S
On Mon, 2002-09-30 at 15:50, Frank Cornelis wrote:
>
> > most of my 712's are ver 1.9 or 2.1 & they all work fine as far as i can
> > see with linux - is there any advantage to updating to 2.3 ?
> >
> > or is this a case of 'if its not broken....'
>
> The text file that comes with the 2.3 patch mentions
> More reliable LAN operation
> as one of the improvements. I wanted to be sure for my BOOTP lifimage
> loading.
> Anyway, it's really easy to do.
> Create an /etc/bootptab on your server containing:
> .default:\
> :sm=255.255.255.224:\
> :gw=192.168.1.62:\
> :ds=195.130.131.2:\
> :ht=ethernet:\
> :bf=C7120023.frm:
>
> hp712:hn:ha=0800099D56DA:ip=192.168.1.34:tc=.default
>
> Of course, adjust with your network settings (man bootptab).
> Run the bootpd daemon (and tftp daemon) on your server and reboot your HP.
> Then goto the BOOT_ADMIN menu using ESC and type:
> search lan
> You should see your BOOTP server listed.
> Then simply do:
> boot lan
>
> That's it.
>
> Frank.
>
next prev parent reply other threads:[~2002-09-30 20:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 21:17 [parisc-linux] firmware update using BOOTP Frank Cornelis
2002-09-29 22:54 ` Matthew Wilcox
2002-09-30 14:10 ` James Smith
2002-09-30 20:50 ` Frank Cornelis
2002-09-30 20:56 ` James Smith [this message]
2002-10-01 7:31 ` Frank Cornelis
2002-10-02 5:00 ` Grant Grundler
2002-10-02 6:59 ` Derek Engelhaupt
2002-10-01 0:53 ` Grant Grundler
2002-10-02 4:48 ` Chuck Slivkoff
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=1033419379.4785.33.camel@seventy \
--to=james@compusmithllc.com \
--cc=Frank.Cornelis@rug.ac.be \
--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