summaryrefslogtreecommitdiff
path: root/system/utmps
AgeCommit message (Collapse)AuthorFilesLines
2020-03-02system/utmps: bump to 0.0.3.2Max Rees1-2/+2
2019-12-21system/the rest: modernise, fix metadataA. Wilcox1-3/+2
2019-10-23system/skalibs et al.: update skaware to latest versionsLaurent Bercot1-3/+3
2019-09-30system/skalibs: bump to 2.9.0.0 + related skaware bumpsLaurent Bercot1-4/+4
contains upgrades to: system/skalibs system/utmps system/execline system/s6 user/s6-dns user/s6-networking
2019-07-31system/utmps: upgrade to 0.0.2.2Laurent Bercot1-2/+2
2019-05-28 system/s6-linux-init: new package = new init systemLaurent Bercot3-13/+11
This commit touches lots of things at once: it is necessary in order to maintain consistency. The impacted packages are: - s6-linux-init: new package. s6-linux-init mechanism plus booting policy. s6-linux-init conflicts with sysvinit; you can have one or the other, depending on what init you want to boot on. * s6-linux-init-common: subpackage of s6-linux-init, containing files used in the s6 supervision tree in both init cases. Both s6-linux-init and sysvinit depend on s6-linux-init-common. - s6: removed s6-svscanboot, which is policy, and only used in the sysvinit case. The s6 package is pure mechanism now. - utmps: adapted to the new location of the supervision tree, and reliable files provided by s6-linux-init-common. It works as is with both init systems. - gettys-openrc: had to move its invocation from "openrc sysinit" to "openrc default", because you can't make early gettys with s6-linux-init (no control over stage 1), and you can't have a supervision tree before sysinit with sysvinit (because /run is mounted very late, in boot), so the only solution that works with both is to make gettys late services. - sysvinit: now has s6-svscanboot (starting the s6 supervision tree from inittab), and a carefully crafted inittab that should work in all cases. Getting the right order of inittab lines was NOT easy, and I now hate sysvinit even more than I did before. Note that with the current version of apk, you cannot switch from sysvinit to s6-linux-init, or vice-versa, without an error. apk says files conflict. Because it adds the new files before removing the old ones. It should still work with apk -f, because the .apk-new mechanism makes it so that there's no real collision while you're switching, but it's still ugly as fuck and needs to be fixed in apk before we make the switch available to users.
2019-03-06 system/utmps: upgrade to 0.0.2.1Laurent Bercot1-10/+38
2019-01-06 system/utmps: upgrade to 0.0.2.0Laurent Bercot1-2/+2
2018-08-18 system/utmps: the utmp user and group are already hardcoded inLaurent Bercot3-12/+2
2018-08-16 system/utmps: upgrade to 0.0.1.3Laurent Bercot1-6/+6
2018-08-15 Move s6 higher in the supervision chainLaurent Bercot7-53/+18
- Better s6 layout, with a place for early services and a place for packages to add their services later on. - s6-svscan is now supervised by sysvinit (instead of being run once by openrc) - s6-svscan is now the only process supervised by sysvinit. All the other "respawn" lines are delegated to s6. - utmpd and wtmpd are now early services instead of being added by openrc. These changes implement a full supervision architecture and make init more flexible. Later on, it will be easier to - add conditional gettys (for /dev/hvc0...) - remove sysvinit entirely - decouple the init process from the service manager.
2018-06-27system/utmps: bump to 0.0.1.2A. Wilcox1-5/+4
2018-06-26system/utmps: fix checksumA. Wilcox1-1/+1
2018-06-16system/utmps: bump to 0.0.1.1A. Wilcox1-3/+3
2018-06-15system/utmps: new packageA. Wilcox6-0/+120