I would like to setup a cow filesystem in the host before the UML boots.
Doing so when starting the UML works, but I would like to load some files into the COW before I start the uml. Can this be done? What would I do to go about doing this?
thanks,
-UML is really working great -thanks to
On lunedì 6 agosto 2007, Blaisorblade wrote:
> On giovedì 2 agosto 2007, Peter Chant wrote:
> > Chaps,
> >
> > I'm creating a script to generate a Slackware 12.0 based root file system
> > and also a script to run the uml machine. I'm running into a spot of
> > bother - it seems to mount the files
On Tuesday 07 August 2007, Blaisorblade wrote:
>
> I just realized the real problem - that "disk is full" message is given on
> a tmpfs mount (with udev, /dev stays normally on tmpfs); the size limit of
> a tmpfs mount is by default the half of the available RAM.
>
> Uml by default picks 32M of RAM
On Tuesday 07 August 2007 7:46 pm Peter Chant wrote:
> Cheers, making real progress now, thanks to you and also Dave Houlden's web
> page http://homepage.ntlworld.com/dave.houlden/root_fs_slack12.0.readme.
> (not sure if he reads / posts here).
>
> A bit of comparison between Dave's notes and my go
First thanks a lot for doing this work, it's been long needed.
Second please don't send out that many patches. We encourage people
to split things into small patches when the changes are logially
separated. Which these are not - it's a flag day change (which btw
is fine despite the rants soe peo
> +void attr_kill_to_mode(struct inode *inode, struct iattr *attr)
This function badly needs a kerneldoc description. Also I can't say
I like the name a lot, but without a clearly better idea I should
probably not complain :)
We should at least add a generic_ prefix to indicate it's a generic
he
On Tue, 7 Aug 2007 21:49:09 +0100
Christoph Hellwig <[EMAIL PROTECTED]> wrote:
> First thanks a lot for doing this work, it's been long needed.
>
> Second please don't send out that many patches. We encourage people
> to split things into small patches when the changes are logially
> separated.
On Tue, 7 Aug 2007 21:51:49 +0100
Christoph Hellwig <[EMAIL PROTECTED]> wrote:
> > +void attr_kill_to_mode(struct inode *inode, struct iattr *attr)
>
> This function badly needs a kerneldoc description. Also I can't say
> I like the name a lot, but without a clearly better idea I should
> probab
On Tuesday 07 August 2007, David Houlden wrote:
> Pleased to hear my notes were helpful. I've not yet found udev useful for
> my use of UML hence I don't bother to install it. However, I have been
> following your problem with interest.
I think I'll probally follow your lead. My thoughts were to
On Mon, 6 Aug 2007 09:54:03 -0400
Jeff Layton <[EMAIL PROTECTED]> wrote:
> Apologies for the resend, but the original sending had the date in the
> email header and it caused some of these to bounce...
>
> ( Please consider trimming the Cc list if discussing some aspect of this
> that doesn't con
On Tue, 07 Aug 2007 20:45:34 -0400
Trond Myklebust <[EMAIL PROTECTED]> wrote:
> > - rename something so that unconverted filesystems will reliably fail to
> > compile?
> >
> > - leave existing filesystems alone, but add a new
> > inode_operations.setattr_jeff, which the networked filesytems c
On Tue, 2007-08-07 at 17:15 -0700, Andrew Morton wrote:
> Is there any way in which we can prevent these problems? Say
The problem here is that we occasionally DO need to add new flags, and
yes, they MAY be security related. The whole reason why we're now having
to change the semantics of setatt
12 matches
Mail list logo
