| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
We moved .morph files out of chunk repos and into definitions.git over
a year ago.
Change-Id: I9c6646ee96aced7987e01f9f9dd6428835354c31
|
|
|
|
| |
Change-Id: I9a42032d1f9700b6bbd050123f5cbc1238efcb65
|
|\
| |
| |
| | |
Reviewed-by: Lars Wirzenius
|
| | |
|
|/
|
|
|
|
|
|
|
| |
After this change the root user will continue to be
created without password, since /etc/shadow is also
being populated.
This will work also in systems without shadow, if
busybox is installed with shadow support.
|
| |
|
| |
|
| |
|
|\ |
|
|/
|
|
|
|
|
|
|
|
| |
JSON versions are generated from .yaml versions using the edit-morph
script in the Morph source tree:
'scripts/edit-morph to-json *.morph.yaml'
The .morph files themselves should be converted to YAML after the next
Baserock release.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allowing arbitrary code to create device nodes is a bad idea, so
it is preferred to build under linux-user-chroot.
Since we need to create device nodes, a "devices" field is added to
the chunk morphology, which describes which devices nodes are to be
created, and how.
This commit will not work without the corresponding changes to morph.
Reviewed-by: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
| |
The full list is between 188 and 750KB, which is too much to be in
foundation.
The current file is what is required for nfs to work, which would ideally
go in the nfs stratum, but since we can't merge files in /etc I have put
it here in fhs-dirs to avoid confusion when we add other network services.
|
| |
|
|
|
|
| |
Reviewed-By: Richard Maw (on irc)
|
|
|
|
|
|
|
|
|
|
| |
init.d and rcS are not needed by systemd, so remove them.
Permissions should have been set correctly in the first place.
shadow is needed for busybox's sulogin to work correctly, which in
turn is needed for systemd's emergency console, which is needed when
an fstab entry is bad.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
More devices are needed during building, they won't actually be
needed in the final system image, because a devtmpfs is mounted
over /dev by the kernel.
urandom is needed by test suites and some cryptography stuff, like
python's multiprocessing module and openssl
random consumes entropy so isn't really safe to put in here
zero and full are harmless and something may use them.
console may no longer be needed, but there have been warnings that
console and null are needed before udev can fill /dev, however
this may no longer be necessary since the kernel has devtmpfs.
|
|
|
|
|
|
|
|
| |
This doesn't work when building using a staging area, since
it already has a /var/run directory, which tar won't replace with
a symlink.
dbus also creates a directory in /var/run, so it may not cope with
being ephemeral.
|
| |
|
|
|
|
|
|
|
|
| |
Given we need more than one symlink now it is appropriate to
provide a general mechanism for listing them, like with dirs
/run is usually a tmpfs and /var/run is semantically the same
anyway, so make is a symlink
|
| |
|
|
|
|
|
| |
These groups are required for systemd to make its tmpfs mounts
lock is a legacy group, but it is easy enough to add
|
|
|
|
|
| |
The shell may not be /bin/sh, so execute the script with whatever
shell is in PATH
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The kernel now has DEVTMPFS and DEVTMPFS_MOUNT, this will mount a
tmpfs on /dev and add nodes to it. mdev may only be used as hotplug
it may set permissions though, like udev does
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mdev is currently being used as it is part of busybox
This does not need all of the device nodes previously specified
as it is able to create them, so they are removed from create-dev-nodes
/dev/console and /dev/null may be needed to boot
rcS has been changed to use a tmpfs for /dev, this will be filled by
mdev. http://lwn.net/Articles/330985/ suggests that it may be faster
to use a devtmpfs as [um]dev only needs to set the permissions though.
More users and groups have been added. Many are for the standard
[um]dev device configuration. The sshd user and group are for ssh
as we do not have a good way to add groups in morph yet.
|
| |
|
|
|
|
|
|
|
| |
mtab does not clean itself on restart
/dev/pts is needed for interactive programs like ssh
mdev is busybox's subtitute for udev, this will populate /dev
this means that some stuff can be removed from create-dev-nodes
|
|
|
|
|
| |
real dirs got built somehow and they can't be replaced
with symlinks
|
|
|
|
|
| |
More of the standard devices are needed to use morph
This fixes S1012
|
| |
|
| |
|
|
|
|
|
| |
/var/run is needed for /var/run/ifstate
/etc/network/interfaces is needed to tell what to use
|
| |
|
|\
| |
| |
| | |
baserock/bootstrap
|
| |
| |
| |
| | |
Also, add /etc/ld.so.conf.d, and include *.conf from there.
|
| | |
|
| | |
|
|/
|
|
| |
'remotes/origin/baserock/bootstrap' into baserock/bootstrap
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add more nodes to /dev and passwd,group,inittab to /etc
add rcS, which mounts the contents of fstab
Make the contents of fstab mount on startup
This manually creates some device nodes that are needed for serial and
virtual terminals, as well as the user and group information so that it
is possible to log in as root.
It may be more appropriate to create a new morph, as this is not strictly
the fhs-dirs hierarchy, but at this stage that would require a new
repository and the alteration of foundation to require that morph.
|
| |
|