• From: Oceanside, CA
  • Registered: 2008-04-17
  • Posts: 650

Topic: Ship "passwd" in c1 rootfs

Since the c1's rootfs can optionally be rw, I'd like to see passwd shipped on the stock rootfs.  Size isn't really a concern on the rootfs like it was with the CC, so it shouldn't be a problem, right?

Linux Guy - Occasional Chumby Hacker

Materdaddy's Website

  • Registered: 2008-06-27
  • Posts: 518

Re: Ship "passwd" in c1 rootfs

Sure, I'll flip support for that on in busybox.

  • From: Oceanside, CA
  • Registered: 2008-04-17
  • Posts: 650

Re: Ship "passwd" in c1 rootfs

Just out of curiousity, what do you guys use for packaging up the rootfs?  Is it 100% manual?  Buildroot with glibc instead of uClibc? Buildroot-ng?  Some "home brew" solution??

Linux Guy - Occasional Chumby Hacker

Materdaddy's Website

  • Registered: 2008-06-27
  • Posts: 518

Re: Ship "passwd" in c1 rootfs

We use a home-grown solution.  It relies heavily on clever Makefiles that are passed arguments like ARCH, CROSS_COMPILE, TARGET, CNPLATFORM, and CONFIGNAME.  These last two vary depending on the product, and are what differentiates between an Ironforge (cc) and Falconwing (c1) build.

It all gets packaged and then fed to genext2fs (for c1) or mkfs.cramfs (for cc), which then uses a series of scripts that generates the update files and a ROM image like the one I posted earlier.