From: Mark Hatle <fray@mvista.com>
To: Grant Erickson <grant@borg.umn.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Linux/PPC Installer Source Code
Date: Fri, 02 Jun 2000 09:54:15 -0700 [thread overview]
Message-ID: <3937E6B7.1BFCD6B8@mvista.com> (raw)
In-Reply-To: Pine.SGI.4.21.0006021058070.183027-100000@tigris.borg.umn.edu
Grant Erickson wrote:
>
> Is the source code available for the Linux/PPC 1999 installer (based on
> the Red Hat installer)? I've scoured the Linux/PPC 1999 CD and can't seem
> to locate it among the other source code and SRPMs.
>
> I'm particularly interested in looking at loading software onto "virgin"
> embedded boards and/or field upgrade strategies for embedded boards with
> semi-frequent software upgrade requirements.
>
> Thanks,
>
> Grant Erickson
>
If you can find the source CD for the LinuxPPC Reference Release 1.0 it
should be the same source code.
ftp://mirror.linuxppc.org/linuxppc-dev-rel/1.0/
(look in the misc/src directory)
Also, if that fails, it's almost identical to the RedHat 6.0 installer
source. (The majority of the changes delt with the MacOS partition
scheme.)
The scheme is to compile a list of packages that are to be installed,
parse the dependency information so that you (hopefully) can install
things in order of whats needed, and then perform the install.
You may want to hop onto #mklinux on your local efnet IRC server and ask
for some suggestions if you are planning on writing an installer. I
would stay away from the RedHat type installers for an embedded
application, there are better tools out there.
--Mark
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-02 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-02 16:01 Linux/PPC Installer Source Code Grant Erickson
2000-06-02 16:54 ` Mark Hatle [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-02 18:16 Thomas J. Merritt
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=3937E6B7.1BFCD6B8@mvista.com \
--to=fray@mvista.com \
--cc=grant@borg.umn.edu \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).