FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=upstream%2F10.1.0 2013-08-13T18:51:26Z 2013-08-13T18:51:26Z Jilles Tjoelker jilles@FreeBSD.org 2013-08-13T18:51:26Z urn:sha1:595ab5638b1c5db0973608d8c8eda712ed0802ca In particular, this makes the kernel login class on processes started from /etc/rc "daemon" instead of "default". Reviewed by: trasz 2012-05-25T19:45:01Z Jilles Tjoelker jilles@FreeBSD.org 2012-05-25T19:45:01Z urn:sha1:3c52150e70ebc3e264786918f0414edfa243a7d2 2012-04-06T13:06:01Z Ed Schouten ed@FreeBSD.org 2012-04-06T13:06:01Z urn:sha1:6ee5808be791510ee549529218ebd9e61853a5ef Though we should open the TTY with O_NONBLOCK to prevent rc(8) execution from potentially stalling, we must not forget to clear the flag later on, to prevent read(2) calls from failing later on. This prevented the shell pathname prompt from working properly. Reported by: kib 2012-03-14T16:22:09Z Ed Schouten ed@FreeBSD.org 2012-03-14T16:22:09Z urn:sha1:4c2c7b2c9461801cdc2b12fb342d39207e92c445 If the environment doesn't offer a working /dev/console, the existing version of init(8) will simply refuse running rc(8) scripts. This means you'll only have a system running init(8) and nothing else. Change the code to do the following: - Open /dev/console like we used to do, but make it more robust to use O_NONBLOCK to prevent blocking on a carrier. - If this fails, use /dev/null as stdin and /var/log/init.log as stdout and stderr. - If even this fails, use /dev/null as stdin, stdout and stderr. So why us this useful? Well, if you remove the `getpid() == 1' check in main(), you can now use init(8) inside jails to properly execute rc(8). It still requires some polishing, as existing tools assume init(8) has PID 1. Also it is now possible to use use init(8) on `headless' devices that don't even have a serial boot console. 2012-03-11T22:30:06Z Ed Schouten ed@FreeBSD.org 2012-03-11T22:30:06Z urn:sha1:7a11d7d883255a4396392a33a04672610ac7c02e MFC after: 1 week 2012-02-22T06:27:20Z Kevin Lo kevlo@FreeBSD.org 2012-02-22T06:27:20Z urn:sha1:29dcf726d233505532b89c31f8ba31eb69fa26df 2012-02-11T20:47:16Z Ed Schouten ed@FreeBSD.org 2012-02-11T20:47:16Z urn:sha1:c21ae3a403b8fbf817d4e11ccaf4a67ad8495450 This has the following advantages: - During boot, the BOOT_TIME record is now written right after the file systems become writable, but before users are allowed to log in. This means that they can't cause `hidden logins' by logging in right before init(8) kicks in. - The pututxline(3) function may potentially block on file locking, though this is very rare to occur. By placing it in an rc script, the user can still kill it with ^C if needed. - Most importantly: jails don't use init(8). This means that a force reboot of a system running jails will leave stale entries in the accounting database of the jails individually. 2011-11-04T13:36:02Z Ed Schouten ed@FreeBSD.org 2011-11-04T13:36:02Z urn:sha1:1efe3c6b58ea5d0e5a0d49039d84d00f2370c7de These tools declare global variables without using the static keyword, even though their use is limited to a single C-file, or without placing an extern declaration of them in the proper header file. 2011-01-23T14:22:26Z Jilles Tjoelker jilles@FreeBSD.org 2011-01-23T14:22:26Z urn:sha1:acf0ab0669861bdcef9c49f5ed87ff6c82bd1d1b It does not make sense to shut down daemons that were not started. In particular, this fixes loss of mixer settings when shutting down using shutdown(8), init(8) or ctrl+alt+del from single-user mode. If /etc/rc reboots, /etc/rc.shutdown is not run. Also fix segfaults and other erratic behaviour if init receives SIGHUP or SIGTSTP while in single-user mode. This commit does not attempt to fix any badness with signal handlers (assumption that pointers can be read and written atomically, EINTR race condition). I believe it does not make this badness any worse. Silence on: -arch@ 2010-01-27T20:32:58Z Ed Schouten ed@FreeBSD.org 2010-01-27T20:32:58Z urn:sha1:a21dd5e9dd63fb9fd47254a7622271caa2acaee4 This tool doesn't require libulog anymore.