We can now start SSH with optional syslogging support. Also, if a program
is not already present in the /etc/rc.d "profile" (actually, not it has become
a collection of profiles) it will be automatically added.
This sounds hackish, and it probably is, but also, it might be the best
workable solution for now...
svn path=/nixpkgs/trunk/; revision=5044
there is some difference between "install" on my FC3 machine and "install"
in coreutils in Nix:
building install_man
install -o root -g root -m 644 sysklogd.8 /nix/store/x03w5xpzcya04b4ax47lic2ahnf479nz-sysklogd-1.4.1/usr/share/man/man8/sysklogd.8
install: cannot change ownership of `/nix/store/x03w5xpzcya04b4ax47lic2ahnf479nz-sysklogd-1.4.1/usr/share/man/man8/sysklogd.8': Operation not permitted
make: *** [install_man] Error 1
svn path=/nixpkgs/trunk/; revision=5035
dependencies, such as "networking" in Nix expressions) is not entirely
right, at least, trying to start them from for example this SSH script is
not the right way. A cleaner solution is being developed :)
svn path=/nixpkgs/trunk/; revision=5034
probably be a bit tricky, due to sendmail "compatibility" (postfix makes
a symlink to "sendmail", so programs will keep on working).
svn path=/nixpkgs/trunk/; revision=5030
contains arbitrary information about a package, like this:
meta = {
homepage = "http://gcc.gnu.org/";
license = "GPL/LGPL";
description = "GNU Compiler Collection, 4.0.x";
};
The "meta" attribute is not passed to the actual derivation
operation, so it's not a dependency --- changes to "meta" attributes
don't trigger a recompilation.
Now we have to standardise some useful attributes ;-)
svn path=/nixpkgs/branches/usability/; revision=5024
maybe this should include the path to the Nix store and a sanity check
should be added to make sure that if we check the file in $STATEDIR that
it is indeed from an instance of the service that we want to start. This
adds complexity, because how should we deal with the situation of they are
not equal.
TODO: add a "status" command, or a "version" command, which displays which
service is currently registered with the system as "running"
svn path=/nixpkgs/trunk/; revision=5015
to be all the information that is non-site specific. The reason I want this
in a Nix expression is that it is easier to deploy in NixOS this way. It also
gives me a bit of a feel of what information is safe to keep inside the store
and what information isn't :)
svn path=/nixpkgs/trunk/; revision=5005
* you want to be able to deploy this sort of configuration. Various packages
will not be able to work correctly without this. The GNU C library has a
dependency on this, but we ignore it. glibc will happily build if this file
is missing, but resolving will sometimes fail if this file is not present
(syslog is one example)
* this information is fairly static and changed about once or twice a year.
It is maintained by IANA and cannot really be considered site-specific
configuration.
The package is not made a dependency for glibc, as a change here would
trigger a full recompilation, even though technically speaking it is a
runtime dependency using a fixed format (as dictated by IANA).
svn path=/nixpkgs/trunk/; revision=5004
embedded systems and installation CDs. Hopefully this will decrease the size
of things we use on the NixOS installation CD. Only tested in a cross-compile
for MIPS so far.
svn path=/nixpkgs/trunk/; revision=4968
Even though you could just inherit binutils it is conceptually cleaner (I
think) to make these tools available here.
svn path=/nixpkgs/trunk/; revision=4967
