directory; the ramdisk build also relies on the termcap entry here, so this
isn't totally useless. All based on work by Scott Taylor (sgimips at
mrynet.com), with bugs most likely added by me.
including checks for "backups that exist when actual file is deleted", a la
the existing mechanism used for "/etc/ifconfig.*" ... "/etc/rc.d/*" checks.
This resolves [security/15798] from Bob Kemp <bob@allegory.demon.co.uk>.
in and setting -kb, check it out again, since the initial check in
trashes any RCSIDs (because -kb wasn't set at that time).
This stops the annoying situation where you add a new file (e.g, "foo")
which contains an RCSID and you get *two* notifications of differences
in two successives runs of /etc/security; the first when the file is
initially checked in and a second when diff finds the RCSID is different
(contains "foo.conf,v 1.1" instead of "foo,v 1.66").
intvid didn't find the frame buffer on his PB 170 in NetBSD 1.5. This is
because the PowerBook 140/145+145B/170 entries in intvid_info[] were
entered into the table directly from the corresponding hardware tech
notes. Unfortunately, the actual frame buffer is mapped at an offset
of 32 KB from the base of the region (at least when in 32-bit mode).
Since all 4 of these systems have identical video configurations, I'm
updating the rest to match.
PowerPC and provides a PCI-host bridge, interrupt controller, two com ports,
two IIC ports, a timer, and a DRAM controller.
The driver supports PCI, interrupts and com ports.
bbinfo.c module; news* boot blocks occupy all of the first 16 sectors,
with a jump instruction to skip the label at bytes 64..511.
Replace news_clearboot() and news_setboot() callbacks with common
news_copydisklable() callback, and set bbinfo_params->offset to
NEWS_BOOT_BLOCK_OFFSET (which is now 0), and ->headeroffset to 0.
(Thanks to Izumi for picking this up; the perils of working on code at 2am)
on spldma), and rest of driver/network code (which runs on splnet) in way
if->if_snd queue is accessed. Solve by using intermediate queue.
Problem found, and fix provided by Christian Limpach in port-next68k/16798
*-sushi-* packages.
Suggested by Allen Barret in PR misc/16900:
>$ grep base-sysutil distrib/sets/lists/base/mi | grep sushi | wc -l
> 288
>$ grep base-sysutil distrib/sets/lists/base/mi | grep -v sushi | wc -l
> 136
>
>In a future where syspkgs are useful, it seems likely that some
>people will want to avoid installing sushi, while others will want to
>be able to upgrade sushi without upgrading the entire system. Several
>small subsystems, including cron and lpr, have their own syspkg sets,
>and it seems reasonable to do the same for the sushi subsystem.
rafal