| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
Fork of sonarr (as radarr) but for music instead of series and movies.
|
|\
| |
| | |
Sickbeard/Sickgear/Sickrage: Init and module
|
| | |
|
| |
| |
| |
| | |
`documentation.nixos`
|
|/ |
|
|\
| |
| | |
Hylafaxplus
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit adds the following
* the uucp user
* options for HylaFAX server to control startup and modems
* systemd services for HylaFAX server processes
including faxgettys for modems
* systemd services to maintain the HylaFAX spool area,
including cleanup with faxcron and faxqclean
* default configuration for all server processes
for a minimal working configuration
Some notes:
* HylaFAX configuration cannot be initialized with faxsetup
(as it would be common on other Linux distributions).
The hylafaxplus package contains a template spool area.
* Modems are controlled by faxgetty.
Send-only configuration (modems controlled by faxq)
is not supported by this configuration setup.
* To enable the service, one or more modems must be defined with
config.services.hylafax.modems .
* Sending mail *should* work:
HylaFAX will use whatever is in
config.services.mail.sendmailSetuidWrapper.program
unless overridden with the sendmailPath option.
* The admin has to create a hosts.hfaxd file somewhere
(e.g. in /etc) before enabling HylaFAX.
This file controls access to the server (see hosts.hfaxd(5) ).
Sadly, HylaFAX does not permit account-based access
control as is accepts connections via TCP only.
* Active fax polling should work; I can't test it.
* Passive fax polling is not supported by HylaFAX.
* Pager transmissions (with sendpage) are disabled by default.
I have never tested or used these.
* Incoming data/voice/"extern"al calls
won't be handled by default.
I have never tested or used these.
|
|\ \
| |/
|/| |
nixpkgs module: Fix defaulting of `localSystem` and `system`
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Take two of #40708 (4fe289860888668956b7e79e24efeb101c2f51d1).
That PR attempted to bidirectionally default `config.nixpkgs.system` and
`config.nixpkgs.localSystem.system` to each be updated by the other. But
this is not possible with the way the module system works. Divergence in
certain cases in inevitable.
This PR is more conservative and just has `system` default `localSystem`
and `localSystem` make the final call as-is. This solves a number of
issues.
- `localSystem` completely overrides `system`, just like with nixpkgs
proper. There is no need to specify `localSystem.system` to clobber the
old system.
- `config.nixpkgs.localSystem` is exactly what is passed to nixpkgs. No
spooky steps.
- `config.nixpkgs.localSystem` is elaborated just as nixpkgs would so
that all attributes are available, not just the ones the user
specified.
The remaining issue is just that `config.nixpkgs.system` doesn't update
based on `config.nixpkgs.localSystem.system`. It should never be
referred to lest it is a bogus stale value because
`config.nixpkgs.localSystem` overwrites it.
Fixes #46320
|
|/ |
|
| |
|
|\
| |
| | |
freedesktop modules: init
|
| | |
|
| |
| |
| |
| | |
they need to exist according to the README of systemd
|
| | |
|
|/
|
|
|
|
| |
New option virtualisation.libvirtd.qemuRunAsRoot (default: true).
If false, qemu is run as non-privileged user qemu-libvirtd,
reducing security risk
|
|
|
|
|
| |
Adds a replacement for the previously broken
`services.database.cassandra` with tests for a multi-node setup.
|
|\
| |
| | |
nixos/cfssl: Add new module for cfssl
|
| |
| |
| |
| |
| |
| |
| | |
- based on module originally written by @srhb
- complies with available options in cfssl v1.3.2
- uid and gid 299 reserved in ids.nix
- added simple nixos test case
|
|/
|
|
|
|
|
|
|
|
|
| |
This reverts commit 095fe5b43def40279a243e663c662b02caac5318.
Pointless renames considered harmful. All they do is force people to
spend extra work updating their configs for no benefit, and hindering
the ability to switch between unstable and stable versions of NixOS.
Like, what was the value of having the "nixos." there? I mean, by
definition anything in a NixOS module has something to do with NixOS...
|
| |
|
|\
| |
| | |
hydron: init at 2018-07-11
|
| | |
|
|/
|
|
| |
Co-authored-by: Volth <volth@webmaster.ms>
|
|\
| |
| | |
tree-wide: users.extraUsers -> users.users, users.extraGroups -> users.groups
|
| | |
|
|/ |
|
|
|
|
|
|
| |
This reverts commit 4fe289860888668956b7e79e24efeb101c2f51d1.
This gives a recursion in certain nixpkgs configs.
|
|\
| |
| | |
nixpkgs module: Fix defaulting of `localSystem` and `system`
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
My c6f7d4367894047592cc412740f0c1f5b2ca2b59 made the mistake of not
having enough defaults. Now both variables are default as the *explicit*
value of the other, or a fallback. The fallback of `system` is the
default of `localSystem.system`. The fallback of `localSystem` is not
the other default (projected), as that would cause a cycle, but `{
system = builtins.currentTime; }` just as nixpkgs itself does it.
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
explicitly set
|
| |
|
|
|
|
|
|
|
| |
lib.optional returns a singleton or an empty list. Therefore the
argument does not need to be wrapped in a list.
An alternative patch could have used lib.optionals but seems like no
more elements are going to be added to the optional list.
|
|\
| |
| | |
fleet, panamax: remove
|
| |
| |
| |
| | |
deprecated and unmaintained upstream
|
| |
| |
| |
| |
| | |
was broken and depends on (deprecated) fleet
packages: panamax_api, panamax_ui
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As suggested in https://github.com/NixOS/nixpkgs/pull/39416#discussion_r183845745
the versioning attributes in `lib` should be consistent to
`nixos/version` which implicates the following changes:
* `lib.trivial.version` -> `lib.trivial.release`
* `lib.trivial.suffix` -> `lib.trivial.versionSuffix`
* `lib.nixpkgsVersion` -> `lib.version`
As `lib.nixpkgsVersion` is referenced several times in `NixOS/nixpkgs`,
`NixOS/nix` and probably several user's setups. As the rename will cause
a notable impact it's better to keep `lib.nixpkgsVersion` as alias with
a warning yielded by `builtins.trace`.
|
|
|
|
|
|
| |
The logic regarding the generated `.version-suffix` file is already
defined in `lib/trivial.nix` and shouldn't be duplicated in
`nixos/version`.
|
| |
|
|
|
|
|
| |
I know that "devinfo" output does not currently exist, but so does "devman".
It is mentioned in the nixpkgs manual, but no derivation in nixpkgs actually uses it.
|
| |
|
|\
| |
| | |
nixos: fix rename.nix bugs
|
| |
| |
| |
| | |
This reverts commit 70c6f6572dda0f2516bad812857ef814ec710a12.
|
|\ \
| | |
| | | |
nixpkgs module: Clean up platform options
|