mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6: future of UMSDOS?
Date: Fri, 28 May 2004 11:19:07 +0200	[thread overview]
Message-ID: <20040528091907.GQ1912@lug-owl.de> (raw)
In-Reply-To: <20040528090345.6C6913F04@latitude.mynet.no-ip.org>

[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]

On Fri, 2004-05-28 11:03:44 +0200, aeriksson@fastmail.fm <aeriksson@fastmail.fm>
wrote in message <20040528090345.6C6913F04@latitude.mynet.no-ip.org>:
> Adrian Bunk wrote:
> > On Mon, May 24, 2004 at 10:19:09AM -0700, Mark Beyer - Contractor wrote:
> UMSDOS as-is, no not really, but I would like to see it ported to run
> on top of smb. Being able to have an smb equivalent to nfsroot would
> be really cool for disk space limited laptops and the like where you
> want to run e.g. colinux. All you'd need is a vmlinuz file, a small
> initrd file, and you're set to go. No need for
> filesystems-on-big-files and such workarounds...

Well, I've done something like that in userspace. For mass installations
(hundreds to thousands of machines with no interaction, while only a
Windows machine is available in each location ...), I boot off with
kernel + ramdisk (containing needed device nodes and the minimal set of
smbfs binaries to mount the server), then symlinking everything from the
servers into my ramdisk.

This approach is somewhat limited (eg. it needs to fit on a single
floppy for re-installing a totally crashed box) because smbfs binaries
are somewhat large (if you don't cut them down manually:), but it works,
at least for installation.

I guess that UMSDOS' approach *could* in theory be made to work with any
filesystem capable of storing plain files, but that'll need some work,
though:)

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-05-28  9:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19 18:43 Adrian Bunk
2004-05-24 14:51 ` Jan-Benedict Glaw
2004-05-24 17:19   ` Mark Beyer - Contractor
2004-05-27 20:28     ` Adrian Bunk
2004-05-28  9:03       ` aeriksson
2004-05-28  9:19         ` Jan-Benedict Glaw [this message]

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=20040528091907.GQ1912@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®