All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Nasrat <pauln@truemesh.com>
To: elks <Linux-8086@vger.kernel.org>
Subject: Re: root disk!
Date: Mon, 14 Oct 2002 20:10:49 +0100	[thread overview]
Message-ID: <20021014191049.GC12349@raq465.uk2net.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0210141137120.1738-100000@mail.costarica.net>

On Mon, Oct 14, 2002 at 11:49:15AM -0600, Miguel Bolanos wrote:
> Hi all!
> 
> i have been trying to create an elks root disk, but when i run 'make root'
> on the elkscmd dir, it mounts the minixfs to /mnt/elks/ it runs the script
> /mnt/elks/dev/MAKEDEV, but it gets executed i get the folling error:

Umm, yes elkscmd is a bit b0rked atm - keep meaning to look at it.

It's halfway between being runnable on elks itself - hence /bin/test and
calls to MAKESET, etc.  

I've haven't been using elkscmd, rather I've make a minix filesystem
using 

dd if=/dev/zero of=myroot bs=1024 count=1440
/sbin/mkfs.minix -n14 myroot 1440
mount -t minix -o loop myroot /mnt/elks

Then I take harry's prebuilt image (link on elks.sf.net) and mount that.

mount -t minix -o loop root /mnt/elksroot

Use rsync/cp to replicate the filesystem and add my own binaries on as
necessary.

 
> 2 additional things that i would like to mention is that i have realized
> is that the current documentation on how to create root disks for elks is
> not good enought i have found some issues that are not documented, such
> as... /mnt/elks must exist because it is needed to mount the minixfs

Umm, there are two other ways of making elkscmd images other than via
loopback - ramdisk and floppy.  I haven't tried either but they're in
the Make.defs file for elkscmd.

> there, the error is very obvious but still i belive it should be on the
> papers, as well i found that it runs /bin/test, but test is actually a is
> a shell builtin so of course it cant be found under that path, solved this
> by creating a dummy script under /bin/test:

Test isn't built in for ash/sash the shells that elks use, MAKESET is an
elks shell based script rather than a bash script.  I guess just using
test would work as elks will have /bin in the PATH and bash will do the
right thing.

If I have time I'll have a poke around elkscmd tomorrow.

If you want a root disk - grab the images from Harry's site, if you want
to customise one, you can do so by following my instructions.

Paul

  reply	other threads:[~2002-10-14 19:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-14 17:49 root disk! Miguel Bolanos
2002-10-14 19:10 ` Paul Nasrat [this message]
2002-10-16  8:39   ` jb1

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=20021014191049.GC12349@raq465.uk2net.com \
    --to=pauln@truemesh.com \
    --cc=Linux-8086@vger.kernel.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.