File: Readme.debian

package info (click to toggle)
yard 1.17.patch1-5
  • links: PTS
  • area: main
  • in suites: potato
  • size: 600 kB
  • ctags: 74
  • sloc: perl: 1,729; sh: 250; makefile: 176; asm: 32
file content (78 lines) | stat: -rw-r--r-- 3,215 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
Short Readme for debian users:
==============================

For the fast ones: do /usr/share/yard/conf_yard 
                      make_root_fs 
											check_root_fs 
									and write_rescue_disk.

Okay,
here some further explantions you might need when the upper programs revealed
some problems.


0. Test your rescue system !!!before!!! you really need it.


1. As mentioned before the programs are perl scripts. They have been dynamically
configured especially for your system when they were installed. The makefile and
all the other sources lie under /usr/share/yard. If you upgrade the kernel at 
the same time you install yard, yard cannot determine which kernel is the actual 
one and which modules does it have to use etc. The final configuration has then
to wait until the next reboot. 
It can then be started with /usr/share/yard/conf_yard. If it was once configured
it doesn't hurt to rerun it. It just says that yard is already configured.


2. You had configured yard for your machine before and we destroyed your
configuration? Don't worry. We moved your old /etc/yard to something like
/etc/yardYYMMDDHHMMSS (YYMMDDHHMMSS stands for the timestamp - if you haven't
recognized before). If you haven't been too fast and installed it twice a
second it should be fine. Just remove our new /etc/yard and replace it with the
oldest /etc/yardYYMMDDHHMMSS and there you go.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!         Caution: when you purge yard you will purge all of       !!!!!!!!
!!!!!!                    your configuration too.                       !!!!!!!! 
!!!!!!            (works as desired, or at least as designed)           !!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


3. Due to security reasons the output of our installation script and also the
output of yard itself will go to /var/log/yard.


4. There were reports about problems when using the nss mechanisms 
(the problem should be gone now - but who knows?).

If you experience a 
    bad login 
    (login[xx]: invalid passowrd for "UNKNOWN" on 'xxx')
or 
    shutdown CTRL-ALT-DEL 
    (You don't exist. Go away.) 
		 ((OT: nice to know btw. how do I go away if I don't exist?))
when you use your rescue system there might is some bad influence from NSS. 

You can get some proposals when you do (no need to reboot):
> 1. Add line strace in /etc/yard/Bootdisk_Contents
> 2. make_root_fs
> 3. chroot /floppy ash
> 4. strace whoami


5. Problems after upgrading/installing yard together with new kernel
The installation script tries to guess the path to the modules by getting the
version of the running kernel. If you do an upgrade yard will probably use the
already installed new kernel together with the old modules. To prevent making 
such a false configuration the installer simply refuses to run. Yard seems to be
installed but is not finally configured.

If you see this message now because you called make_root_fs it's a very strong 
hint that you hit the upper situation.

Please run /usr/share/yard/conf_yard manually at least once before make_root_fs 
to do this.



This document is /usr/share/doc/yard/README.debian.