| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
gratutious changes in the latest SSH
Reviewed by: obrien
Approved by: obrien
|
|
|
|
|
| |
Submitted by: dinoex
MFC after: 7 days
|
|
|
|
|
|
|
|
|
| |
is not set. This allows admins to create a per-machine configuration file
while leaving the freebsd.mc template pristine. Provide a rule to create
`hostname`.mc from freebsd.mc if it doesn't exist.
PR: misc/26299
MFC after: 8 days
|
|
|
|
|
|
|
|
| |
plus documentation.
Submitted by: Alexander Leidinger <Alexander@Leidinger.net>
Not objected to by: hm
MFC after: 1 week
|
|
|
|
|
| |
the 'svr4' module already. This was a 4.x-only problem and should not
have been MFS'ed.
|
|
|
|
|
|
|
|
| |
PR:
Submitted by:
Reviewed by:
Approved by:
Obtained from:
|
|
|
|
| |
<roam@orbitel.bg>
|
|
|
|
| |
Reminded by: gshapiro
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fsck checking. Applying these changes (typically via mergemaster)
will cause your system to start running background checks on all
your soft update enabled filesystems (provided that you have
a kernel with the required functionality, e.g., one built since
the end of April). Please report any and all problems to
mckusick@mckusick.com (not mckusick@freebsd.org which I read
infrequently). See the comment above the fsck command in /etc/rc
for instructions on how to disable background checking should it
cause you too much trouble.
Several FAQs:
1) Can I reboot before the background checks are done?
Ans) Yes, when the system restarts the checks will pick up
where they left off.
2) Can a crash during checking corrupt my filesystem?
Ans) No, recovered resources are returned to the system using soft
updates which ensure that the freeing is done in a safe order.
3) How will I know if any background checks are being done?
Ans) Filesystems that are to be checked in background will be listed
as `DEFER FOR BACKGROUND CHECKING' at the usual fsck check time
during system startup.
4) What happens to the output of the background checks?
Ans) It is sent to syslog `daemon' facility log level `notice'.
5) When will this feature be available in the 4.X kernel?
Ans) Never. It is much too radical and extensive a change to be
MFC'ed. Besides, it needs many months of experience and
tuning before it is ready for widespread use.
6) What happens if a background fsck fails (i.e., fsck finds
errors that would normally require a manual fsck)?
Ans) The filesystem will be marked as needing a manual fsck.
At the next system reboot, the check will be done in
foreground and the usual actions taken (usually a failure
to go multi-user until fsck has been run by hand on the
affected filesystem).
|
|
|
|
|
|
| |
at boot time.
MFC after: 3 weeks
|
|
|
|
| |
routes for IPv6 as well as IPv4 routes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the null mount, we currently create a temporary mfs on /tmp, copy
/etc to /tmp, then mount /etc as mfs and copy everything back from
/tmp, then delete the /tmp mfs.
The patch eliminates the temporary /tmp mfs and the subsequent
copying and simply populates the /etc mfs by copying from
/conf/default/etc. This requires that /conf/default/etc contain a
complete copy of all the /etc stuff instead of just overrides. I
don't think that is too much of an extra step in setting up a
diskless environment.
* Provide the ability to make /tmp a memory filesystem independent
of /var. This removes the requirement that /tmp be a symlink to
/var/tmp and this makes the diskless code work with the default
filesystem layout. If a seperate /tmp memory filesystem is
created, the 'tmpsize' environment variable is used to determine
its size (default to 10 Meg).
* Reduce diffs between the -current and -stable versions of these
files to a bare minimum. Only the definition of the shell
function 'mount_md' is different.
Not Objected to by: -arch@, -small@
MFC after: 2 days
|
|
|
|
| |
after a mergemaster.
|
|
|
|
|
| |
doesn't solve the problem of root being allowed to log in, but that sort
of thing is something PAM should be doing anyway.
|
|
|
|
| |
so zsh can parse this file as well.
|
|
|
|
| |
Submitted by: Mark Knight <markk@knigma.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This driver supports PCI Xr-based and ISA Xem Digiboard cards.
dgm will go away soon if there are no problems reported. For now,
configuring dgm into your kernel warns that you should be using
digi. This driver is probably close to supporting Xi, Xe and Xeve
cards, but I wouldn't expect them to work properly (hardware
donations welcome).
The digi_* pseudo-drivers are not drivers themselves but contain
the BIOS and FEP/OS binaries for various digiboard cards and are
auto-loaded and auto-unloaded by the digi driver at initialisation
time. They *may* be configured into the kernel, but waste a lot
of space if they are. They're intended to be left as modules.
The digictl program is (mainly) used to re-initialise cards that
have external port modules attached such as the PC/Xem.
|
| |
|
|
|
|
|
|
| |
but runs kbdcontrol instead of vidcontrol.
Reviewed by: ru
|
|
|
|
| |
to perl5 modules installed by hand.
|
| |
|
|
|
|
| |
PR: conf/26633
|
| |
|
| |
|
|
|
|
|
| |
PR: bin/26836
Submitted by: Matthew Seaman <matthew.seaman@tornadogroup.com>
|
|
|
|
|
|
|
|
|
| |
o create a simple wrapper function mount_md that makes it easy to
move from mount_mfs.
# NOTE: you will need to MAKEDEV md[0123] in order for this to work.
Reviewed by: bsd, keichii
|
|
|
|
|
|
| |
PR: conf/24865
Submitted by: schweikh
Reviewed by: hm
|
|
|
|
|
|
| |
PR: conf/24865
Submitted by: schweikh
Reviewed by: hm
|
|
|
|
|
| |
rc.diskless2 to use mdconfig rather than mount_mfs. These changes are
still relevant to -current.
|
| |
|
|
|
|
| |
periodic/daily/470.status-named.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
place where default sysctl value have to be tweaked if we ever would want
to switch kernel default to 1.
Submitted by: dillon
|
|
|
|
| |
Reviewed by: Nick Hibma <n_hibma@qubesoft.com>
|
|
|
|
|
|
| |
o put a note into sysctl.conf describing vfs.vmiodirenable knob.
OK'ed by: alfred
|
|
|
|
| |
Submitted by: Akihiro Kosakada <pdp@cyber-fleet.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
/dev/log like this: if [ ! -h /dev/log ];
The man page for test(1) says that the -h switch is depracated and that
users should NOT rely on it being available. It suggest the -L switch instead.
They both do the same thing: check for the existence of the symbolic link.
PR: 26596
Submitted by: mikem <mike_makonnen@yahoo.com>
|
| |
|
|
|
|
| |
MFC canidate.
|
|
|
|
|
|
|
|
|
| |
'denied AXFR', not 'unapproved AXFR'.
This is an MFC candidate.
PR: misc/26529
Submitted by: duwde@duwde.com.br
|
|
|
|
|
| |
: These files use 4 space indentation, and other than in the header
: comments, should not contain any tabs.
|
|
|
|
| |
which may include the -q flag.
|
| |
|
|
|
|
| |
Reviewed by: phk
|
| |
|