you MUST add the directory name and the .. entry to close the directory.
If you do not understand mtree files, do not modify them, it is very
easy to trash someones box with a mistake in here. Especially with
regards to .. entries.
some file names.
2. Add MAKEDEVS= that does all the /dev population so that this is not
duplicated in 2 or 3 places. Helps to keep it in sync too. Cleaned
up and fixed to not overflow inode tables.
3. Fix paths to the 2 crypt versions.
4. Init is sbin/init now instead of sbin/init.bsdi.
5. bdes is now in secure/usr.bin, will need to do something about telnet.
6. Incorporate 1.1.5.1 patches for EXTRACT.sh files.
7. Correct calls to make kcopy-flooppy to work with or without obj/.
8. Reorder src-clean: target so that it does not destroy the real obj
tree, but does rip out junk and obj links.
9. Incorporate 1.1.5.1 patche for srcbin tarball name.
10. Add chflags command to release-dirs target so the rm -rf can have a
chance to work.
With this and a few more commits I will have 2.0 bin tarballs.
be installed on, so they should be in /dev as well.
Removed the smoking remains of dcf*. I didn't realize that it had made it
into MAKEDEV. Gone from cdevsw long time ago, gone from /dev now.
the choice of building with the password scrambler or the DES
libraries. Folks outside the US can simply drop in the other
DES libraries. (stupid laws...)
Everything still keys off of the old NOCRYPT variable so building
a portable distribution remains the same.
Submitted by: pst
actually have a printer connected or online:
- MAKEDEV: remove all signs of lpa
add lpctl? devices (minor # = unit + 128)
- usr.sbin/Makefile add lptcontrol
- sys/i386/isa/lpt.c implement the LP_BYPASS flag: when a unit is
opened with this flag set, the printer is
not primed, and no check is made to see that
the printer is online. This can only be used
to pass ioctls. (giving us /dev/lpctl?)
- lptcontrol.c use /dev/lpctl? (LP_BYPASS)
-f flag removed, -u flag added
- lptcontrol.8 document changes in lptcontrol
rewrite using mandoc macros
Submitted by: Geoff.
1. Use ${MAKE} everywhere again. Whoops.
2. Replace multiple invocations of gzip ... split ... with one variable.
3. Add src-clean target for making the src tree presentable before
making a src tarball out of it.
upon disk type. In far more cases than not this is the optimal setting
for any disk drive made after 1990.
This now means all installs will have the disks newfs'ed with either:
newfs -b 8192 -f 1024 -d 0 -n 1
or
newfs -n 4096 -f 512 -d 0 -n 1
depending on what the user chooses for the blocking factor.
date!!) and rename them to something more eye-catching so people will read them
again (considering the previous state of affairs, I'm actually rather glad they didn't!).
1. Add to secr and bindists to possibly save the occasional fool who
doesn't RTFM and uses the wrong command to extract this (or even someone
who's legitimately using this to extract on top of a bindist somewhere
*else*).
2. Do the right thing with any symlinks in the src tree. Right now, we're
free of the buggers, but just in case.
2. Get kcopy and filesystem images from current directory since we
now build them here; a clean rule is now all that's needed to make
the crunch stuff complete.
The kernel configs already support this, so with a boot floppy or a utility
like booteasy, the user should be able to install and boot off the second drive.
Hurrah.
way I'm going to allow this to be set to secure. People blow their
password files away all the time, and I am not at all keen to lose the
ability to get them recovered with the simple expedient of a single-user
boot.
Without this entry init.bsdi don't ask root password when it goes
to sigle-user. This entry must present here in any case,
subject of arguing can be only default mode, I mean
"secure" or "insecure" here. Please consider this entry
like template and change "insecure" to "secure" if you
are _shure_, but not back out whole line.
# This entry needed for asking password when init goes to single-user mode
console none unknown off insecure
1. Properly use ${.CURDIR} now instead of hardcoded relative dirs.
2. Use ${BINOWN} and ${BINGRP} everywhere instead of root/wheel
3. Add target for copying over EXTRACT scripts (and add them here).
4. Start thinking about crunched floppy target (not in yet, next commit).
Deleted commented-out line which would start mountd; that's not
the right pplace to do it (don't confuse the users).
Should probablyhave uncommented rpc.rstatd, but didn't.
The configure function now tells the user to type "man 5 resolver"
for more info on resolv.conf, but mentions that the bindist must
be fully installed before this can be done (actually a user won't
have reached this stage if he doesn't have an installed bindist ;-)
2. Added notes that tell the user a little bit about how to use syscons
since they'll be running it from the outset now and would probably like
to know how to switch terminals.
2 Added optional excessive login logging.
3) Added login acces control on a per host/tty base.
4) See skey(1) for skey descriptions and src/usr.bin/login/README
for the logging and access control features.
-Guido
2 Added optional excessive login logging.
3) Added login acces control on a per host/tty base.
4) See skey(1) for skey descriptions and src/usr.bin/login/README
for the logging and access control features.
-Guido
----------------------------
revision 1.13.2.1
date: 1994/05/05 03:58:27; author: rgrimes; state: Exp; lines: +15 -25
Upgrade some things that are now different in 1.1.
----------------------------
FreeBSD release still nukes everything on scratch using a big-hammer
method, even if it is nfs-mounted (and, when it is, the expiration policy
may be different). Daily script should by default do nothing to remote
filesystems?
----------------------------
revision 1.8.2.1
date: 1994/04/18 06:37:29; author: rgrimes; state: Exp; lines: +10 -4
Use the hostname.* files created by the installation to reduce the
amount of work one has to do when setting up a system.
----------------------------
----------------------------
revision 1.1.2.1
date: 1994/04/10 20:20:26; author: rgrimes; state: Exp; lines: +11 -5
Use /dev/fd0 instead of /dev/fd0a. Add mounting of mcd1 if mcd0
fails when searching for a cdrom drive.
----------------------------
revision 1.1.2.1
date: 1994/04/10 20:20:25; author: rgrimes; state: Exp; lines: +3 -3
Use /dev/fd0 instead of /dev/fd0a. Add mounting of mcd1 if mcd0
fails when searching for a cdrom drive.
----------------------------
revision 1.53.2.3
date: 1994/04/10 20:19:37; author: rgrimes; state: Exp; lines: +12 -3
Must have etc and usr directories on the cdinstall floppies.
Need to have device files for mcd1.
Create links for usr/libexec and usr/lib on cdinstall floppies so that
shared library code is loaded from cdrom.
----------------------------
revision 1.2.2.3
date: 1994/04/17 19:45:24; author: rgrimes; state: Exp; lines: +13 -2
Eliminate warning messages about /sbin/sh /sbin/init and /etc/termcap
when extracting the bin or des archives. Note this is also the
place I fixed the libc.so.1.0 problem a long time ago by adding
a --exclude libc.so.1.0 to the tar command.
only once an hour instead of every five minutes. This was due to a minute
specification of 0/5 -- which should have been */5. This has been fixed.
Expect your /var/cron/log to grow much faster now.
Used the canonical non-existent file (/nonexistent) instead This should
probably be documented somewhere, but it's unclear where the right
place is (passwd(5)? login(8)? hier(7)? all three?).
installed by default, because then everybody would suddenly start
trying to authenticate themselves in the CS.BERKELEY.EDU realm, which
is really not a very good idea. Maybe the README could get installed.
pair of crunched binaries that are not built by this, but other than
that it is back to an automated procedure. So many changes it is
hard to describe.
>From: chmr@edvz.tu-graz.ac.at (Christoph Robitschko)
Date: Fri, 21 Feb 1992 09:40:35 +0100 (MET)
The last version expected elvis* files in /var/tmp, while elvis puts
elv* files there.
back editor!
Add nvi recovery precedure from man page.
Fix ntpdate echo lines so that it looks pretty (ntpdate spits out 1 line
of output that makes the system boot up look real ugly if you do it
echo -n, so I chaged it to echo, and then added a
echo -n 'starting more network daemons:' so any addition daemon starts
look normal.
>From: "Chris G. Demetriou" <cgd@sun-lamp.cs.berkeley.edu>
Update of /b/source/CVS/src/etc
In directory sun-lamp.cs.berkeley.edu:/usr/src/etc
Modified Files:
master.passwd
Log Message:
disable toor by default
Use freefall.cf as sendmail prototype file, it is more realistic than the
tcpproto.cf file for a FreBSD system. Fix so that obj dir is created in
sendmail/cf/cf as to not polute the source tree and to have the Makefile
in there do the right things.
Remove all the extra /dev/fd0?* entries on the floppies, they where using
up all the inodes and are not needed at this time.
Temporarily remove the floppy target from release: untilit is
fixed.
This file has lots more work coming, but to get the 1.1 BETA out I am
going to hand craft the floppies :-(.
Further it implements crontab -e.
I moved cron from /usr/libexec to /usr/sbin where most daemons are
that are run from rc. That also gets rid of the ugly path crond
used to have in ps(1) outputs. Further I renamed it to cron, as
Paul Vixie likes it and is done by NetBSD.
NOTE VERY WELL THE FOLLOWING:
1) Systems crontab changed. Every users crontab resides in /var/cron
*EXCEPT* root's. This is a special crontab as it resides in
/etc. Further it is the *ONLY* crontab file in which you specify
usernames. See /usr/src/etc/crontab. This is also done by BSDI's
BSD/386 as far as I know (they provided the patches for it anyway)
2) So you *must* delete root's crontab and reinstall the copy
in /etc from /usr/src/etc.
'Must' is to much: the old installed crontab will work but cron
will also try to 'run' /etc/crontab.
3) Last but not least: cron's logging is now done via syslog. Note
that logging by cron is done lowercase when it logs about itsself
and uppercase when it logs user events, like installing a new crontab.
The default logfile file is the same as before:
syslog.conf:cron.* /var/cron/log
-Guido
Subject: Re: daily insecurity output (fwd)
|From: rgrimes@agora.rain.com (Rodney Grimes)
|
|This is from the new /etc/security script. I no longer get the segmentation
|violation, but now the arg list is too long, some /bin/sh program want to
|fix the current /etc/security ls command so that it is a pipe insteal of
|a back quoted arg?
|
|> checking setuid files and devices:
|> /etc/security: ls: argument list too long
This uses xargs instead. My slip line's down so I can't check it in
at the moment. Rich
added a note that you must decide what is appropriate for your system.
>From: borsburn@mcs.kent.edu (Bret Orsburn)
Date: Wed, 12 Jan 94 01:09:43 -0500
I've finally figured out (one of the reasons) why I can't run MS-Windows
after running FreeBSD 1.0...*sometimes*.
Here's your first clue. This is what your MS-Windows video drivers are called
if you run a Number 9 GXE video card:
/dos/windows/system/#9gxetc.drv
/dos/windows/system/#9gxe.drv
