From: Eric Kimminau <eak@detroit.sgi.com>
To: Miguel de Icaza <miguel@nuclecu.unam.mx>
Cc: adevries@engsoc.carleton.ca, ariel@sgi.com, linux@cthulhu.engr.sgi.com
Subject: Re: boot linux - wish
Date: Sat, 16 Aug 1997 01:08:48 -0400 [thread overview]
Message-ID: <33F535E0.7336423F@detroit.sgi.com> (raw)
In-Reply-To: 199708152146.QAA30833@athena.nuclecu.unam.mx
Miguel de Icaza wrote:
>
> > > Could someone rise to the challenge of writing a utility
> > > that will install Linux on an IRIX machine?
> >
> > I don't mind rising to that challenge, but one huge obstacle is how do we
> > get the utility to partition the Linux drive?
>
> the fx command is used to partition disks on IRIX. It took me a while
> to work around the user friendlyness of it, but then, I wanted to keep
> a part of my disk with XFS (because I just LOVE that file system) and
> the rest for my ext2fs.
>
> > I'm guessing the solution is to write a utility that from within Irix
> > talks directly to the raw SCSI disk to setup the partitions. I have NO
> > idea how to do this as I doubt the raw disk interface is anything like
> > that in Linux. Clues accepted.
>
> The only thing you need to do is access the first sector in the disk.
> this one holds the disk label with the current partition definitions.
> Oliver at .at was working on getting Linux FDISK up and running, you
> can probably talk with him.
>
> > > And give hints like:
> > > Sorry you don't have the e2fs tools installed on IRIX yet
> > > should I download them from ftp.linux.sgi.com [y/n]?
> >
> > Er, does such a tool in fact exist?
>
> Yes. get the e2fsprogs suite, it is the only thing you need to
> populate a file system.
>
> Miguel.
Is there ever ANY chance of seeing XFS in Linux? Or a flavor of a really
fast journaled file system?
--
Eric Kimminau System Engineer
eak@detroit.sgi.com Silicon Graphics, Inc
Vox:(810) 848-4455 39001 West 12mile Road
Fax:(810)848-5600 Farmington, MI 48331-2903
"I speak my mind and no one else's."
http://www.dcs.ex.ac.uk/~aba/rsa/perl-rsa-sig.html
-----END PGP PUBLIC KEY BLOCK-----
http://bs.mit.edu:11371/pks/lookup?op=vindex&search=Eric+A.+Kimminau&fingerprint=on
next prev parent reply other threads:[~1997-08-16 5:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-15 20:17 boot linux - wish Ariel Faigon
1997-08-15 20:17 ` Ariel Faigon
1997-08-15 20:23 ` Mike Shaver
1997-08-15 21:47 ` Miguel de Icaza
1997-08-15 22:03 ` Alex deVries
1997-08-16 1:05 ` Mike Shaver
1997-08-16 1:05 ` Mike Shaver
1997-08-16 12:08 ` Alan Cox
1997-08-16 12:08 ` Alan Cox
1997-08-16 14:15 ` Mike Shaver
1997-08-16 14:15 ` Mike Shaver
1997-08-16 20:33 ` Ralf Baechle
1997-08-16 20:33 ` Ralf Baechle
1997-08-15 20:38 ` Alex deVries
1997-08-15 20:53 ` Mike Shaver
1997-08-15 20:53 ` Mike Shaver
1997-08-15 20:59 ` Alex deVries
1997-08-19 10:38 ` Oliver Frommel
1997-08-15 21:46 ` Miguel de Icaza
1997-08-16 5:08 ` Eric Kimminau [this message]
1997-08-16 6:18 ` Ralf Baechle
1997-08-16 6:18 ` Ralf Baechle
1997-08-16 20:25 ` Miguel de Icaza
1997-08-16 21:54 ` Vincent Renardias
1997-08-16 22:07 ` Ralf Baechle
1997-08-16 22:07 ` Ralf Baechle
1997-08-17 12:33 ` Alan Cox
1997-08-17 12:33 ` Alan Cox
1997-08-18 4:25 ` Kernel with working initrd? Alex deVries
1997-08-19 1:37 ` Current problems Alex deVries
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=33F535E0.7336423F@detroit.sgi.com \
--to=eak@detroit.sgi.com \
--cc=adevries@engsoc.carleton.ca \
--cc=ariel@sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=miguel@nuclecu.unam.mx \
/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