Add 'make dist' target to get a tarball to test in addition to the upload target.
[sysvinit.git] / obsolete / README.RIGHT.NOW
CommitLineData
a74aeac6
PR
1WARNING:
2
3 This version of sysvinit is really different from the 2.50 and
4 earlier version.
5
6 Shutdown now puts the system into runlevel 6 (reboot), 0 (halt)
7 or 1 (single user). This can cause unexpected results if you
8 install the binaries from this release into Slackware distributions
9 older than Slackware 3.0.
10
11SUPPORTED DISTRIBUTIONS:
12
13 The binaries from this package can be installed in:
14
15 o Debian 1.3 and later
16 o RedHat 3.x and later
17 o Slackware 3.0 (UNTESTED but it might work - no complaints yet).
18 Also read the INIT.README in the slackware/ directory.
19 o Slackware 2.x: see the slackware/ directory
20
21 Do not install any of the scripts from the debian/ directory unless
22 you know what you are doing.
23
24UNSUPPORTED DISTRIBUTIONS:
25
26 o The rest :)
27
28 If you have a non-supported system, please upgrade to the latest version
29 of your distribution that supports the Linux 2.0.x kernel (probably
30 the reason why you are installing this newer sysvinit).
31
32 You might get away by installing *just* the "init" binary, and nothing
33 else. Do _not_ replace your existing halt, reboot or shutdown programs.
34
35HOW TO NON DESTRUCTIVELY TEST THE NEW INIT:
36
37 Install *just* the init binary as /sbin/init.new. Now reboot the system,
38 and stop your bootloader so you can give arguments on the command line.
39 With LILO you can usually achieve this by keeping the SHIFT key
40 pressed during boot up. Enter the name of the kernel image (for LILO,
41 TAB shows a list) followed by the argument "init=/sbin/init.new".
42 The name "init.new" is special, do not use something like "init.test".
43
44 For example:
45
46 boot: linux init=/sbin/init.new
47
48 YOU CANNOT SHUTDOWN IN A CLEAN WAY AFTER THIS. Your best bet is to use
49 the "-n" flag to shutdown. This is because init is not running as process #1
50 if you use this method. Anyway, if this works, you can remove the old init
51 and copy the new init into place.
52
53DISCLAIMER:
54
55 If it breaks you get to keep both pieces. If you want to run the latest
56 Linux 2.0.x kernel and you can't get init to work just upgrade your entire
57 distribution to a newer version that supports the 2.0.x kernel properly.
58