new mtree options.
I will be updating these shortly to remove some old stuff and add some
new stuff. These currently produce the exact same trees as they did.
arrange for that directory to get created by mtree. Also, process secure
directory after all the others, because the programs there may overlay
ones installed from the main part of the tree.
2. Make this say it is 2.0.0 (Development).
3. Update the stty commands to say ^H for erase.
4. Update the disklabel commands to use the new 4.4 syntax.
2. Update the COPYRIGHT= to be just the COPYRIGHT file for now.
3. Fully parameterize the floppy device being used. This is needed right
now so I can at least build these on 1.44 until it all is working, then
I will have to find a way to get them back down to size.
4. Remove mount_pcfs from the filesystem floppy, we don't have that yet.
5. Update the shared libraries t obe copied. This should now work for
this and all future releases.
6. Reduce the CRYPT_SRCS down to the few static binaries that have crypt
in them.
7. Change all references for the kernel from /386bsd to /kernel.
8. For some reason umount is returning 1, use a - until I can find out why.
9. Update the disklabel commands to be 4.4 syntax.
10. Remove the ugly elvis wart, we don't have elvis anymore.
11. Use the -d (directories only) option on the mtree commands. This
greatly reduces the noise from distrib-dirs:.
12. Note the fact that the mtree commands need a wrapper around them as they
return a status of 2 if the tree was modified and the make should not
exit on that condition.
13. Add a trailing slash on the chflags command as ${RELEASEDIR} may be
a symbolic link.
Changed the everlenghtening list of "if [ -f /etc/hostname.foo ].." to a
loop which will do them all, and look for init-scripts for them as well.
perfect place to put your calls to slattach and such: /etc/start_if.sl0
for instance.
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.
