From: Bdale Garbee <bdale@gag.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: PA/Linux CD Image
Date: Wed, 9 Aug 2000 12:28:12 -0600 (MDT) [thread overview]
Message-ID: <20000809182812.78B76363F3@rover.gag.com> (raw)
In-Reply-To: <39917C97.4DC81F31@gmx.de>
In article <39917C97.4DC81F31@gmx.de> you wrote:
> if i put
> some effort into installing it then I'll like to use it as a basis for
> further updates, e.g. when there will be eventually a stable kernel I
> want to install it over this distribution. I'll have to install probably
> some further programs, too. Will this be possible with a "reasonable"
> effort?
That depends on your definition of "reasonable". :-) I don't think anyone
expects you to "install" the bits on this CD. The image is bootable, and it
should be possible to play around quite a bit running from the CDROM root.
My personal spin on this is that if it's not hard for you to burn a CR-R, or
if you were to acquire a physical disk at LWCE, then it's probably worth
dropping it in a CDROM drive and booting it to see what's there and what does
and doesn't work. It may not be worth trying to install this onto your hard
disk for any reason other than intellectual curiosity unless you intend to
dive in and help the team complete the porting work. Even then, I find it
desireable to work over an nfsroot and not a local disk installation.
We're getting close (a couple of months, maybe) from being able to offer
a relatively normal Debian installation/upgrade process. If you want to
*use* parisc-linux (as opposed to helping get the port finished), that is
probably a better trigger event to wait for.
Bdale
next prev parent reply other threads:[~2000-08-10 0:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-09 15:45 PA/Linux CD Image schaecsn
2000-08-09 18:28 ` Bdale Garbee [this message]
2000-08-09 18:52 ` Grant Grundler
2000-08-09 20:25 ` Andrew Shugg
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=20000809182812.78B76363F3@rover.gag.com \
--to=bdale@gag.com \
--cc=parisc-linux@thepuffingroup.com \
/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