Back in the day, these additional (potentially optional) computation units
(e.g., FPU, GPU, vector engine(s)) were generically referred to as
“co-processors” as a class. The debate over interface/interaction with them was
hot … until their access & context became a matter of additional
Time to virtualize console, and let an appropriately authorized (root
credentialed) daemon let an ssh or LAT or some other network thing attach to it
and converse with it?
Erik f...@netbsd.org
On Mar 27, 2014, at 11:29 , matthew green m...@eterna.com.au wrote:
it certainly can be improved for this situation, but i've
got an SS10 with mis-matched cpus (2x100mhz, 1x150mhz,
the latter with a bigger cache and thus significantly
faster than the other cpus) and it works pretty fine.
Generally speaking, SCA SCSI drives are hot-swap capable.
I'm not interested in fiddling with 50-pin or 68-pin with a paused machine -
that's (as you note) a recipe for errors and filesystem corruption.
The key thing in documentation is not just how, but why.
For example, why scsictl dev
What is the specific sequence of NetBSD commands to execute in order to
successfully hot swap an SCA SCSI drive? Obviously, umount(8), maybe scsictl(8)
for stopping the disk ...
Please specifically discuss issues relating to differing disklabels, both
on-disk and in-kernel.
Our documentation
On Jul 25, 2013, at 07:37, Michael Lorenz macal...@netbsd.org wrote:
Easy mistake to make and hard to catch since it rarely ever causes trouble
(unless you're running some weird video mode where width height)
I believe that's called portrait mode and these days it's not so much weird
as
NetBSD has a problem with NTP time keeping on x86 systems which have TSC: if
those systems have variable CPU clock frequency support for power consumption
efficiency (e.g. SpeedStep, PowerNow), if or when the CPU frequency changes,
the relationship between TSC and the ticking of real time
Ah, Matt, now you've stepped in it: UNIX kernel notifications, and a model for
that. A topic that I glossed over in my previous note.
There are three basic modes of UNIX use:
1. traditional multi-user timesharing system. We in NetBSD land still use our
systems this way sometimes; cf.
On Sep 8, 2011, at 14:45, Thor Lancelot Simon wrote:
On Thu, Sep 08, 2011 at 11:26:29AM -0400, Matthew Mondor wrote:
It would be nice to for instance be able to use an MTU of 3000 so that
there are less context switches, but unfortunately tracing the
processes show that 1024 bytes are read
Can you please expand PUD and explain what blktap2 does and is used for?
can't tell the actors without a playbill,
Erik f...@netbsd.org
On Jun 27, 2011, at 10:59 , David Holland wrote:
On Sat, Jun 25, 2011 at 08:57:30PM +0200, Johnny Billquist wrote:
I might be confused here. I thought that if you accessed the block
device, you were restricted to blocks. So you can in fact not seek
to an arbitrary byte, nor read an arbitrary
We're all dancing around a very fundamental question here: what interface
abstraction should the raw interface to a disk controller (and attached
disks) present?
We're not going to allow userland to directly write device registers as a
general practice (X11 notwithstanding, and that's a
On Jun 25, 2011, at 11:57 , Johnny Billquist wrote:
True. However, Unix have never really gracefully handled file systems or
devices that comes and goes. :-)
As Robert Elz wrote (and I'll echo): UNIX has always handled removable devices
- you just have to tell UNIX that you're going to
On Jun 23, 2011, at 23:19 , Michael van Elst wrote:
s...@cs.columbia.edu (Steven Bellovin) writes:
The point is that when dealing with raw devices, you take what the hardware
gives you. 6th Edition could have detected this and copied the user data
into a properly-aligned buffer, with the
On Jun 22, 2011, at 08:28 , der Mouse wrote:
The issue for me is not that the hardware does or doesn't have
alignment restrictions. It's that they show through to userland (and
in a very peculiar way). As someone mentioned upthread, it's possible
what's going on is that this hardware has
15 matches
Mail list logo
