[Buildroot] Editing filesystem files

[Buildroot] Editing filesystem files

[Guillaume Dargaud]

Hello all,
thanks to the support I got here, I now have a nice boot on my ml405 and I 
get to the login with no error. Which brings me to the question:

- how do I login ?
If I type 'root' it refuses without even asking for a password, so I guess 
ttyUL0 is not allowed by /etc/securetty

- how do I edit the various target files (/etc/securetty, /etc/passwd, 
/etc/shadow...) _before_ creating the ramdisk ?

I mean, I could unzip rootfs.powerpc.ext2.gz, mount it, edit it, rezip it 
and then proceed with the kernel 'make ARCH=ppc 
CROSS_COMPILE=powerpc-linux-uclibc- zImage.initrd' and genace, but if I ever 
do 'make' in buildroot again, I'll loose all my changes.

I see target/generic/target_skeleton/etc/shadow and 
target/generic/target_busybox_skeleton/etc/shadow but if I modify files in 
there and do 'make' again, the new project_build_powerpc/genepy/root/ or 
ramdisk file don't reflect the changes. Do I need to make clean or something 
?

Thanks
-- 
Guillaume Dargaud
http://www.gdargaud.net/

[Buildroot] Editing filesystem files

[Guillaume Dargaud]

Following up on this, when do the files in target/generic/target_skeleton 
get copied in project_build_powerpc/genepy/root  ?

It seems to happen the very first time in run make and then never again, no 
matter what I try (even after make clean).

The documentation says:
"So simply rebuilding the image by running make should propagate any new 
changes to the image."
but I just don't see that happening, even if I "rm -rf 
project_build_powerpc/genepy/root" (only dynamically created files get 
rebuilt there then).
-- 
Guillaume Dargaud
http://www.gdargaud.net/


----- Original Message ----- 
From: "Guillaume Dargaud" <dargaud@lpsc.in2p3.fr>
To: <buildroot@uclibc.org>
Sent: Tuesday, April 08, 2008 16:29
Subject: [Buildroot] Editing filesystem files


> Hello all,
> thanks to the support I got here, I now have a nice boot on my ml405 and I
> get to the login with no error. Which brings me to the question:
>
> - how do I login ?
> If I type 'root' it refuses without even asking for a password, so I guess
> ttyUL0 is not allowed by /etc/securetty
>
> - how do I edit the various target files (/etc/securetty, /etc/passwd,
> /etc/shadow...) _before_ creating the ramdisk ?
>
> I mean, I could unzip rootfs.powerpc.ext2.gz, mount it, edit it, rezip it
> and then proceed with the kernel 'make ARCH=ppc
> CROSS_COMPILE=powerpc-linux-uclibc- zImage.initrd' and genace, but if I 
> ever
> do 'make' in buildroot again, I'll loose all my changes.
>
> I see target/generic/target_skeleton/etc/shadow and
> target/generic/target_busybox_skeleton/etc/shadow but if I modify files in
> there and do 'make' again, the new project_build_powerpc/genepy/root/ or
> ramdisk file don't reflect the changes. Do I need to make clean or 
> something
> ?
>
> Thanks
> -- 
> Guillaume Dargaud
> http://www.gdargaud.net/
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
> 

[Buildroot] Editing filesystem files

[Hamish Moffatt]

On Wed, Apr 09, 2008 at 01:47:41PM +0200, Guillaume Dargaud wrote:
> Following up on this, when do the files in target/generic/target_skeleton 
> get copied in project_build_powerpc/genepy/root  ?
> 
> It seems to happen the very first time in run make and then never again, no 
> matter what I try (even after make clean).

Yes that's my experience.

> The documentation says:
> "So simply rebuilding the image by running make should propagate any new 
> changes to the image."
> but I just don't see that happening, even if I "rm -rf 
> project_build_powerpc/genepy/root" (only dynamically created files get 
> rebuilt there then).

If you delete the root it should re-copy the target_skeleton, but you
may find that lots of other files don't get reinstalled (particularly
some of the toolchain libraries).

Unfortunately some of the packages don't use files in the root as their
test, but stamp files elsewhere in the build tree. Or they don't depend
on enough files in the root...

With an external toolchain it's safe to delete most of the root I've
found.

Dependencies between files in the root and the target_skeleton would be
preferable. This would detect everything other than file deletions.

Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

[Buildroot] Editing filesystem files

[Guillaume Dargaud]

> Dependencies between files in the root and the target_skeleton would be
> preferable. This would detect everything other than file deletions.

Yes, but it would be quite heavy to put it all in a make file, with the risk 
of forgetting something. I'm okay with the idea of the root being rebuilt 
from scratch, but how do you trigger that ? As you say, even deleting it 
completely won't copy some of the skeleton back. What can we 'touch' to make 
this happen ?
-- 
Guillaume Dargaud
http://www.gdargaud.net/

[Buildroot] Editing filesystem files

[Hamish Moffatt]

On Thu, Apr 10, 2008 at 01:43:20PM +0200, Guillaume Dargaud wrote:
> 
> > Dependencies between files in the root and the target_skeleton would be
> > preferable. This would detect everything other than file deletions.
> 
> Yes, but it would be quite heavy to put it all in a make file, with the risk 
> of forgetting something. I'm okay with the idea of the root being rebuilt 

There's no need to list all the files in the Makefile; you can use
$(wildcard ...) to generate the list dynamically. Although I haven't
tried to do this for a whole tree.

> from scratch, but how do you trigger that ? As you say, even deleting it 
> completely won't copy some of the skeleton back. What can we 'touch' to make 
> this happen ?

With external toolchain it seems to be safe to delete most (if not all)
of the project_build_xyz/abc/root directory. I don't have a good answer
to your question though. Personally I would like to have proper
dependencies so that I don't need to do an explicit re-copy operation.


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>