Hi,
I've build succesfully an androgynous libusb. This is a libusb in
linux binary format with freebsd-like usb-access. (I use it to
run a jtag-debugging utility which is supplied as a linux
binary only.)
Unfortunately I had to patch the linux.ko module to support the
ioctl calls out of the linux
Hi,
On Fri, 24 Oct 2008 19:51:31 +0200, Hans Petter Selasky <[EMAIL PROTECTED]>
wrote:
>
> No, you cannot use the linux libusb on FreeBSD. You need to use the FreeBSD
> compiled libusb. The USB kernel interfaces are quite different.
OK - I see. I'm just trying to build a "hermaphrodite" library
Hi,
I'd like to run a program in linux-emulation (closed source ...)
which uses the libusb. Is the structure (ioctls on devices and so on)
sufficient compatible to use a linux libusb?
Or is there any way to build a simple wrapper library to use the
nativ libusb? (IMHO this is not possible.)
Do yo
Hi,
I solved the dump problem in a not very
clean way.
First I changed dumps behaviour to ignore
the SIGPIPE signal when the -P and -a option
is given. The problem with occured than was
the loss of data because of the race condition
between "write date to pipe" and "receive SIGPIPE".
I solved th
Hello,
as you probably know I want to expand dump in such
a way it enableds multivolume dumps also when the
output data is written to stdout/a pipe.
Now I ran into a serious problem.
Dump counts the written bytes to remember where
it has to proceede after the volumen change.
Now the SIGPIPE signa
Hi,
Maybe someone could implement a memory section
that is overwritten by the bios after reboot.
Then all the sensitive keys could be stored there.
This would prevent an attack that just boots from
another media and dump the whole memory out of i.e.
an USB-stick.
Preventing the physical access
Hi,
On Tue, 26 Feb 2008 08:51:02 +0100, Peter Jeremy
<[EMAIL PROTECTED]> wrote:
[...] But it also has some gotchas. The
biggest one is that dump needs to be able to write past EOM (so it can
record an end-of-volume block).
Just even I tried the following:
-create a 50MB filesystem (with md)
Hi,
I'm not sure wheher Martin is trying to create a dump that is a single
logical volume split over multiple physical volumes or a multi-volume
dump.
I want to make a real multi-volume dump over multiple media. Because
if I had only one big volume I'd - in the worst case - have to insert
all
Hi,
Yes, gzip or bzip2 compress better, but they also:
* Are a lot slower.
Yesterday I made a comparison regarding the speed
of compress, bzip2 and gzip.
And actually compress is much slower than gzip:
$ dd if=/dev/random |compress -c > /dev/null
3883204 bytes/sec
$ dd if=/dev/random |gzip
Hi,
On Mon, 25 Feb 2008 20:34:31 +0100, wrote:
You might want to play with the -P option to dump. Your above could be
written as:
dump -aL0 -P 'compress -c' /MYFILESYSTEM | cdrecord dev=... -
Unfornunately this does not work as you expect. Dump just takes
its data an pass it to the script s
Hi,
I'll write a script that back up my data on dvd-r and dvd-rams.
(And some incremental backups also at some internet storage
services.)
Therefore I'd like to use dump. It is not too hard to create
dump-volumes with fixed size through the -B option. But now
I'd like to use some sort of compres
Hi,
I ask the same question some day on -questions before but got
no usefull answer. Since it is also more technical
related I try it here again.
I created a dvd with two slices a and b. (Don't ask for the
reason - it is a test for my backup system)
This slices are ufs formated and gbde encrypte
12 matches
Mail list logo
