[Pkg-uml-pkgs] [rootstrap] how to proceed?

[Stefano Melchior]

On Fri, May 19, 2006 at 07:48:52PM +0200, Mattia Dongili wrote:
Dear all,
> > > I already have udev on all my UML filesystems.
> > report of the yesterday night test: I succeeded!
> 
> Great!
> 
> > What do I need to say:
> > - you need ubd on the host too in order to make 'mkfs', 'mount' rootstrap
> >   module working;
> 
> right.
> 
> > - you may provide in /etc/udev/links.conf the record suggested in
> >   http://uml.harlowhill.com/index.php/DevfsUdev, but it is still not
> >   enough;
> > - you succeed when you use a mounted cdrom as mirror, because 'debian'
> >   rootstrap module still fails [1].
> 
> maybe because of unconfigured network?
no absolutely not, in the sense that I set up some preconfigured tapX and
I always use them in order to interface host and guest.
> 
> > At this point, I was wondering if:
> > 
> > - it is possible and reasonable to ask to Marco D'Itri to provide udb
> >   devices creation for udev on host; I checked there are no mention in the
> >   its(udev) bug list
> 
> we can provide our own rules (see the output of apt-file search
> /etc/udev)
it don't returned any result: I tried, even if my implementation resulted
unsuccessful, to remove and create ubdn devices:

if [ ! -d /dev/ubd ]; then 
	for i in 0 1 2 3 4 5 6 7; 
		do sudo rm -rf /dev/ubd* ;
		sudo mknod /dev/ubd$i b 98 $[$i * 16]; 
		cd /dev/ && ./MAKEDEV /dev/udb ; 
	done; 
fi

but on my system the output error is:

.udevdb or .udev presence implies active udev.  Aborting MAKEDEV invocation.

and using a script to be invoked by running rootstrap:

Using rootstrap module filesystem from:
        /usr/lib/rootstrap/modules/filesystem
		rm: cannot remove `/dev/ubd0': Read-only file system
		rm: cannot remove `/dev/ubd1': Read-only file system
		rm: cannot remove `/dev/ubd2': Read-only file system
		rm: cannot remove `/dev/ubd3': Read-only file system
		rm: cannot remove `/dev/ubd4': Read-only file system
		rm: cannot remove `/dev/ubd5': Read-only file system
		rm: cannot remove `/dev/ubd6': Read-only file system
		rm: cannot remove `/dev/ubd7': Read-only file system

It is due to the fact that when rootstrap tries to create the device it
uses hostfs with read-only right. That's is tricky.
I am going to investigate how to provide a patch to Marco D'Itri for udev.
> 
> > - it is reasonable that rootstrap provides for their (ubds) creation;
> > - it is reasonable to add new mirror choises (apart from debootstrap and
> >   cdrom);
> > I planned to test other thing during the day
> 
> Can you please start committing changes in SVN (if any) so that I can
> test things too without reinventing the wheel?
done, unfortunately with some error... :(
> Or do I only need to "MAKEDEV ubd" in the host to make roostrap happy?
more or less
Cheers

SteX
-- 
Stefano Melchior, GPG key = D52DF829 - <stefano.melchior at openlabs.it>
http://etinarcadiaego.dyndns.org    --     http://www.stex.name
Skype ID "stefanomelchior"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 307 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-uml-pkgs/attachments/20060522/eccff35b/attachment.pgp