summaryrefslogtreecommitdiffstats
path: root/system/skeleton/dev
Commit message (Collapse)AuthorAgeFilesLines
* skeleton: add /dev/fd, /dev/std{in, out, err} symlinks for static /dev on ↵Peter Korsgaard2018-05-014-0/+4
| | | | | | | | | | | | | | | | | | readonly rootfs Some applications, e.g. bashs process subsitution feature, rely on the convention of `/dev/fd` being a symbolic link to `/proc/self/fd`. When a static /dev is used on a readonly rootfs then the runtime ln invocations in the inittab will fail, so we need to add the symlinks at build time. Makedevs doesn't support creating symlinks, so instead add the symlinks to the default skeleton. For non-static /dev setups, the kernel will mount devtmpfs which shadows the /dev of the rootfs, but then the runtime ln invocations in inittab will create the symlinks. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* system: separate sysv and systemd parts of the skeletonYann E. MORIN2017-08-023-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | For systemd, we create a simple /etc/fstab with only an entry for /, as systemd otherwise automatically mounts what it needs where it needs it. systemd does not like that the content of /var be symlinks to /tmp, especially journald that starts before /tmp is mounted, and thus the journal files are hidden from view, which causes quite a bit of fuss... Instead, move the current /var to a sysv-only skeleton. systemd at install time will create the /var content it needs, so we just create an empty /var for systemd. systemd would create /home and /srv at runtime if they are missing, but it is better to create them right now, to simplify supporting systemd on a RO filesystem in the (near) future. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Maxime Hadjinlian <maxime.hadjinlian@gmail.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* skeleton: fix absence of /dev/shm on static, read-only systemsLuca Ceresoli2015-10-031-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | /dev/shm is needed for systems using shared memory. On init-based systems this directory is usually created in the inittab along with /dev/pts, by the lines: package/busybox/inittab: ::sysinit:/bin/mkdir -p /dev/pts ::sysinit:/bin/mkdir -p /dev/shm package/sysvinit/inittab: si2::sysinit:/bin/mkdir -p /dev/pts si3::sysinit:/bin/mkdir -p /dev/shm However this is broken when static /dev management is selected and the root filesystem is read-only, showing during boot the error: mkdir: can't create directory '/dev/shm': Read-only file system Fix it by creating the empty /dev/shm directory, just like /dev/pts. Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* New top-level directory: systemThomas Petazzoni2012-11-042-0/+1
This directory groups the following elements: * the default root filesystem skeleton * the default device tables * the Config.in options for system configuration (UART port for getty, system hostname, etc.) * the make rules to apply the system configuration options Even though the skeleton and device tables could have lived in fs/, it would have been strange to have the UART, system hostname and other related options into fs/. A new system/ directory makes more sense. As a consequence, this patch also removes target/Makefile.in, which has become useless in the process. [Peter: fixup TARGET_SKELETON settings / documentation to match] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Yann E. MORIN <yann.morin.1998@free.fr> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
OpenPOWER on IntegriCloud