Re: getting the initial setup working



On Sun, 2012-05-06 at 11:29 -0400, Matthias Clasen wrote:
> Yeah, no problem... I was just trying to see how well your
> instructions on the wiki work.
> I've pushed an easy-fixes branch with some more trivial things. 

Thanks!

> I came
> across a few more issues that should perhaps be mentioned on the wiki:
> 
> - I had to add the minimal content to /ostree/var/passwd and
> /ostree/var/groups and edit the fstab in the image to get my home
> directory mounted, before I could successfully log in.

Ok, right; so what I've been trying to do is dynamically initialize
/var (e.g. when gdm starts up, if /var/lib/gdm doesn't exist, it's
created), but I forgot to do a build of the latest "ginitscripts" on
ostree.gnome.org.  I've updated the build, but I need to do more work
on /var.

> ostbuild tree-to-bin wouldn't work until I figured out that I had to
> pass --tree=/ostree/gnomeos-3.4-i686-devel - the gnomeos instructions
> didn't mention the /ostree/current symlink, so I didn' t have one at
> this point.

Right.

> Next, bin-to-src would't work, because there are no components in my
> repo. I looked around and discovered the pull-components command. I
> had to fix it to make it work, see the easy-fixes branch. After
> pulling all the components, bin-to-src did work.

Yeah, pull-components is kind of a hack.  I have some ideas for
how to improve it though.

> Then, I ran into problems with ostbuild build-components, but it had
> gotten too late to investigate those further...

I've only been testing things locally, but I hadn't done the
full clean run-through; e.g. I still had an old /var lying around
which hid problems.  I'm trying a full clean install today myself.

I've pushed your easy-fixes branch, with one minor adjustment to the
pull-components fix.  Thanks!





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]