Custom Query (4810 matches)
Results (43 - 45 of 4810)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #264 | fixed | Bootscripts: creating new /var/run/utmp doesn't work | ||
| Description |
Hello I've been testing the 1.1 bootscripts. So far so good! Except for a couple of typos "Clearning -> Clearing" :-) One thing that puzzled me slightly was this part of cleanfs echo -n "Creating new /var/run/utmp..." touch /var/run/utmp && chmod 644 /var/run/utmp evaluate_retval That won't achieve anything will it? I don't see the point. Was the intention to start a fresh utmp file every reboot? If so then methinks it is missing a "rm -f /var/run/utmp". Greg This only updates the "modified" time of /var/run/utmp. It's better to use echo -n "" >/ver/run/utmp instead |
|||
| #268 | fixed | few bootscript cleanups | ||
| Description |
reboot ones. This will ensure $PATH is set properly and doesn't include 'bad dirs' where other binaries could live called reboot but don't do what we expect it to do. |
|||
| #269 | fixed | redundant (or needs rephrasing) text in chapter5/proc.xml | ||
| Description |
In chapter5/proc.xml "It's not a problem to mount the proc file system twice or even more than that, since it's a virtual file system maintained by the kernel itself." These days any filesystem can be mounted more than once. Maybe replace with something like: "It's not a problem to mount the proc (or indeed any other) file system twice or even more than that as required." |
|||
