| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
We're going to be passing it "$CHROOT/" as a writable directory by
default, so it needs to be able to tell that it means to leave
everything writable.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The issue is that the tempdir is added at the end of the list of
directories to keep writable, and entries earlier in the list are
subdirectories of tempdir.
The check encountered the subdirs first, so decided it must recurse and
make everything else read-only.
It never got as far as noticing that /tmp was requested writable.
Now, every path is checked for being equal, then checked for being
a subdirectory.
This changed style to use any and generator expressions, as it was more
concise than having an explicit loop for checking equality, then an
explicit loop for checking subdirectory.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will list all the paths generated by the walker generator function
that aren't in the specified set.
It removes directories from those returned by the walker, since with
os.walk(topdown=True) this culls the search space.
In the set of provided paths and the set of returned paths, if a directory
is given, then its contents are virtually part of the set.
This oddly specific behaviour is because invert_paths is to be used
with linux-user-chroot to mark subtrees as read-only, when it only
has a set of paths it wants to keep writable.
It takes a walker, rather than being given a path and using os.walk, so
that it is a pure function, so is easier to unit test.
|
| |
|
|
| |
This is not used elsewhere, and probably never will.
|
| |
|
|
|
|
|
|
|
| |
This was done with the aid of the pep8 script, available by running
`easy_install pep8`.
It may be worth making this part of ./check, but that will require
putting pep8 into the development tools stratum.
This should be easy, given pep8 has no external dependencies.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is an ugly, ugly way to do this, but time is pressing.
SystemBuilder checks what arch is defined in the morphology, if
it is an x86 (or None for compatibility) then it will do the syslinux
install stuff.
This hack is needed because syslinux is x86 specific and arm
often has different requirements for where the kernel must be loaded
from, sometimes it is flash, sometimes it is a different partition.
This will likely become board specific, but for a qemu-system-arm,
the kernel should be a separate file, to be passed on the command line.
Having a different 'kind' for each architecture would be a nicer way,
but would require more changes, since there are various checks for
morphology['kind'] == 'system'
|
| |
|
|
|
| |
losetup has a --show option that will print the loop device the file
was mapped to, this is better than parsing the output of losetup -j.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the tempdir of the staging area instead of the chroot directory
as the basedir for building system images.
It would be better to create it directly in the cache, then rename it
when finished, but commands need a filename and the cache provides an
open file handle.
Change the generated fstab and extlinux.conf to use systemd as the init
and expect the root filesystem to be on vda1 instead of sda1.
vda1 is slightly more efficient and is the default storage device for
libvirt.
This is safe to add before systemd is fully integrated, as if the
kernel can't find that file it run /sbin/init, which is busybox
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
sfdisk may omit a space between the partition name and the :
if the partition name is long, so splitting into tokens doesn't
always work.
This regex should work better
|
| | |
|
|
|
The system images will later need to be read, so useful commands
want to be shared
|
