| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
extracted and recreating device files.
Without this, you'll see following messages when 'MAKEDEV all':
[: : out of range
[: : out of range
acd0t is invalid -- can't have more than 32 devices or 169 tracks
Reported by: David Syphers <dsyphers@uchicago.edu> (at current@FreeBSD.org)
|
|
|
|
|
| |
PR: 29971
Submitted by: Joseph Mallett <jmallett@xMach.org>
|
| |
|
|
|
|
|
|
| |
utility will work, and document it in the manpage.
MFC after: 3 days
|
|
|
|
|
| |
PR: 21394
Submitted by: Craig Leres <leres@ee.lbl.gov>
|
| |
|
|
|
|
|
| |
PR: 18836
Submitted by: ben
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
recurse. Rather recurse on ourself (as we know our own name).
|
|
|
|
|
|
| |
mornings.
Pointy hat again Obtained from: roam@orbitel.org
|
|
|
|
| |
Pointy hat Obtained from: roam@orbitel.bg
|
| |
|
|
|
|
| |
Noted by: nyan
|
|
|
|
|
|
| |
they so desire it.
Suggested by: rwatson
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Pointed out by: bde
|
| |
|
| |
|
|
|
|
| |
Suggested by: Kaltashkin Eugene <zhecka@klondike.ru>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In a few days I will commit a patch which changes vn(4) to use the
disk-minilayer. This will make vn(4) fully DEVFS friendly but have
the side effect that vnconfig needs the vn%d.ctl devices to be able
to configure vn(4).
Please remake your /dev/vn entries with this revision of MAKEDEV if
you don't rung DEVFS already.
|
|
|
|
| |
committed shortly.
|
| |
|
|
|
|
|
|
|
| |
with these in the normal case.
Set MAKEDEVPATH in sysinstall to include the /mnt2 stuff before starting
the fixit shell.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
overwriting $PATH, and find mknod $PATH instead of hardcoding /sbin so
that the copy of MAKEDEV on the fixit floppy is usable, since mknod and
expr live in /mnt2/stand when the fixit floppy is running.
Get rid of the sed invokation in release/Makefile that attempts to
delete the PATH setting stuff from MAKEDEV on the fixit floppy. This
hasn't worked since a long ago change to MAKEDEV caused the sed
expression to no longer match.
PR: misc/21241
|
|
|
|
|
|
| |
for the 'twe' driver. This is an expedient solution for an
actually-manifesting symptom of a major problem with MAKEDEV. Roll on
DEVFS.
|
| |
|
| |
|
|
|
|
| |
install on these...
|
| |
|
|
|
|
|
|
|
|
|
| |
make_dev() call.
At the moment, it is an error for anyone but root to write to this
device (EPERM), and the permissions don't suggest that. Soon, however,
anyone will be able to write here, but only root will cause an implicit
reseed.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
X field is treated the same as the unit number for acdX. The optional
Y parameter specifies the number of track devices to create starting at
track 1. If Y is not specified, it defaults to 100.
- Add the acd0t target to the all target to preserve previous behavior.
- Don't add the acd0t target to the fixit target, thus keeping the fixit
floppy from running out of i-nodes.
|
|
|
|
| |
Problem pointed out by: markm
|
|
|
|
|
|
| |
units > 255 properly.
Fix usio while I'm there
|
| |
|
| |
|
|
|
|
|
| |
both soon...), create urandom instead of the link to random. It's
also what makes sense according to the make_dev(9)'s in random(4).
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The tap driver is used to present a virtual Ethernet interface to the
system. Packets presented by the network stack to the interface are
made available to a character device in /dev. With tap and the bridge
code, you can make remote bridge configurations where both sides of
the bridge are separated by userland daemons.
This driver also has a special naming hack to allow it to serve a similar
purpose to the vmware port.
Submitted by: myevmenkin@att.com, vsilyaev@mindspring.com
|
|
|
|
| |
Reviewed by: dfr
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(I had been busy for my own research activity until the last weekend)
Supported devices:
SB Midi Port (sbc + midi)
SB OPL3 (sbc + midi)
16550 UART (midi, needs a trick in your hint)
CS461x Midi Port (csa + midi)
OSS-compatible sequencer (seq)
Supported playing software:
playmidi (We definitely need more)
Notes:
/dev/midistat now reports installed midi drivers. /dev/sndstat reports
only pcm drivers. We need the new name(pcmstat?).
EMU8000(SB AWE) does not sound yet but does get probed so that the OPL3
synth on an AWE card works.
TODO:
MSS/PCI bridge drivers
Midi-tty interface to support general serial devices
Modules
|
|
|
|
| |
exists"
|
|
|
|
| |
revisited when the new /dev/random is done.
|
| |
|