Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Editing filesystem files
Date: Wed, 9 Apr 2008 13:47:41 +0200	[thread overview]
Message-ID: <11ea01c89a37$87cb1010$f52f9e86@LPSC0173W> (raw)
In-Reply-To: 111801c89984$f480be70$f52f9e86@LPSC0173W

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
>
> 

  reply	other threads:[~2008-04-09 11:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08 14:29 [Buildroot] Editing filesystem files Guillaume Dargaud
2008-04-09 11:47 ` Guillaume Dargaud [this message]
2008-04-09 22:31   ` Hamish Moffatt
2008-04-10 11:43     ` Guillaume Dargaud
2008-04-12  9:22       ` Hamish Moffatt

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='11ea01c89a37$87cb1010$f52f9e86@LPSC0173W' \
    --to=dargaud@lpsc.in2p3.fr \
    --cc=buildroot@busybox.net \
    /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