All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Leippe <nick@byu.edu>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] New to list (just got a B132L)...
Date: Wed, 07 Mar 2001 19:19:06 -0700	[thread overview]
Message-ID: <01030719190606.00237@nick> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

I just got myself a B132L, and am eventually gonna get
Linux on there.

I've already installed LFS (www.linuxfromscratch.org)
on a few x86 boxes, and was wondering how involved
the build process was.  (I've not yet built an xc or
attempted a cross-install, but I've been thinking on
how I'd do it...)

I'd really rather not use Debian or anything 
pre-packaged...

I'd really rather figure out how to do a complete
cross-install, since my dual x86 box can compile much
faster than any of my other arch. boxes.  Still not
sure if this is really possible.

Nick

ps, I've got an alpha, a mips, and an _old_ m68k machine
as well, so I'm hoping there will be a lot of carry-over
for all of them... (luckily all models I own are well
supported by their respective Linux port)

- -- 
Nobody will ever need more than 640 kB RAM.
                 -- Bill Gates, 1983
Windows 98 requires 16 MB RAM.
                 -- Bill Gates, 1999
Nobody will ever need Windows 98.
                 -- logical conclusion
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6puwbGinZK3ajqyURAuttAKCIoMuvVmti0+XIsC2REaBTS3z+xwCeIZZ1
+LGwL5SWRtoNjknNATyYX34=
=dQWM
-----END PGP SIGNATURE-----

                 reply	other threads:[~2001-03-08  2:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=01030719190606.00237@nick \
    --to=nick@byu.edu \
    --cc=parisc-linux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.