README (i.e. for the server: exportfs, mountd, statd, nfsd,
sm-notify; for the client: statd / sm-notify before mountall). This
is important to allow locking to work correctly.
svn path=/nixos/branches/boot-order/; revision=22196
When starting multiple VMs, some will have perfectly synchronised
clocks, while others will have their clocks run much slower (say, a
factor of 5).
svn path=/nixos/branches/boot-order/; revision=22195
a daemon (it just starts some kernel threads). In the post-stop
script, stop the kernel threads.
* exportfs: fix the createMountPoints option.
* Mount the nfsd filesystem on /proc/fs/nfsd because mountd prefers
this.
svn path=/nixos/branches/boot-order/; revision=22187
swapfiles cannot be unmounted or even remounted read-only.
* In the remount, pass `-t none' to get a more informative error
message if the filesystem is in use.
svn path=/nixos/branches/boot-order/; revision=22179
it allows the `mountall' task to start mounting filesystems as soon
as udev is running and devices become available (i.e. it doesn't
have to wait for all devices). This means that some jobs should
depend on "stopped udevtrigger" instead of "started udev".
svn path=/nixos/branches/boot-order/; revision=22167
I also updated the get-go-src expression to get also the heavy upstream openoffice packages.
By now it tries to take also a package for 'sdk', which it is not needed in fact; manual rework
after running the get-go-src result script is enough.
svn path=/nixpkgs/trunk/; revision=22154
during boot. Mountall ensures that these are done in the right
order. It's informed by udev about devices becoming available. It
emits some Upstart events upon reaching certain states, in
particular ‘local-filesystems’ after all local filesystems have been
mounted successfully, ‘remote-filesystems’ after all network
filesystems have been mounted, and ‘filesystem’ (sic) when all
filesystems have been mounted.
Currently, if a filesystem fails to mount or doesn't exist, then the
mingettys won't start and the boot will appear to hang. This is
because mountall doesn't emit an event for failing filesystems and
waits indefinitely for the filesystems to become available.
* The ‘filesystems’ and ‘swap’ Upstart jobs are gone. (Support for
encrypted swap devices is temporarily gone.)
* Generate a proper /etc/fstab from the ‘fileSystems’ and
‘swapDevices’ options.
svn path=/nixos/branches/boot-order/; revision=22148
as they become available (as determined by monitoring udev) and
emits Upstart events to inform other jobs that the filesystems are
mounted. This is very useful for NixOS (which currently ignores
filesystems in the job dependency chain - very bad).
Unfortunately, mountall depends on Plymouth (a boot splash
implementation). The patch allows mountall to build without
Plymouth. Since Plymouth is also used to inform users about failing
mounts and get responses, some more changes will be needed.
Probably mountall should emit a "mount-failed" event to trigger a
root shell on the console to allow the user to repair the problem.
svn path=/nixpkgs/trunk/; revision=22143
Eelco Dolstra