On Mon, Dec 13, 2010 at 11:48 AM, Todd T. Fries wrote:
> I echo Mark's sentiments, though for a different reason.
>
And hot-pluggable serial devices, like GPS receivers. Some of them do
have usb serial numbers I can key on.
On Tue, Nov 30, 2010 at 12:51 AM, Joachim Schipper
wrote:
> In short, what's the use?
Network unlocks. I don't want to have to wander over to my colo
facility after every reboot, and plug in a disk every time, and I also
don't want to have to log in and run bioctl by hand for every volume.
--
Currently bioctl invokes readpassphrase(3) with RPP_REQUIRE_TTY, which
means that there must be a controlling tty to read the password from.
This diff adds an option (-s) to force bioctl to read the passphrase
from stdin. Without this option existing behavior is maintained.
Index: bioctl.8
===
Hi all,
here's a diff to fsck to accept pass numbers greater than 2 so that one
can avoid slaughtering IO-limited deviced. This is useful for people who
have stacked softraids, all backed by the same disk, as might be found
on a laptop with encrypted home:
/dev/wd0a / ... 1
/dev/w
On Wed, Jul 22, 2009 at 10:36 AM, Jean Rebiffe wrote:
> > Open Source projects are of course particularly welcome to use the
> > pool in their default setup, but we ask that you get a vendor zone
> > when using the pool as a default configuration.
they obviously don't mean that if it's taken them
On Fri, May 15, 2009 at 4:20 AM, Adam Jakubowski wrote:
> usbdevs allows me to assign a uftdi device to a physical
> FTDI device by its iSerialNumber, i.e.:
no it doesn't. usbdevs prints what it can about usb devices including
things like the attached driver and device serial number. if you can
s
