Jeff Palmer wrote:
Hello,
Let me preface the email by saying I'm not overly familiar with geli, and
it may already have the ability to do what I'm about to describe.
The scenario: A FreeBSD based appliance at a customer premise. The
customer really can't be trusted not to disasemble the b
I am experimenting with modifying a kernel module and I need
to be able to open/read/write/close a file from within the
module. Is there a preferred way to do this? Are there any
locking or buffering issues that I need to be aware of?
sys/kern/kern_alq.c:alq_open() and sys/kern/kern_ktrace.c:k
I have a Soekris 4501 (and 4521) i'm attempting to get
set up with the Atheros mini-pci cards 168c:0012 (rev 01), ie:
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath0: mem 0xa000-0xa000 irq 10 at device 16.0 on pci0
ath0: Ethernet address: 00:01:24:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've finally found time to work on my L4::BSD project again, and I'm
getting back into the building of the kernel and it's various
"friends" alongside it for the new "port" (iguana, which is the
minimalistic L4 based OS that will help bridge the
Stefan Bethke <[EMAIL PROTECTED]> schrieb am 22.08.2006 21:22:31:
>
> kenv(2) has smbios entries; they're available through getenv() and
> getenv_() in the kernel. See http://www.freebsd.org/cgi/
> cvsweb.cgi/src/sys/boot/i386/libi386/smbios.c for the history.
>
OK
I can get the "System Inform
Oliver Fromme wrote:
> Matteo Riondato wrote:
> > Just to have a try, I replaced /boot/beastie.4th with file a
> > containing only:
> >
> > ." Welcome to FreeSBIE"
> > exit
> >
> > then I deleted the line mentioning beastie-start from /boot/loader.rc
> > and rebooted my machine.
> [...
Hello,
I am experimenting with modifying a kernel module and I need to be able
to open/read/write/close a file from within the module. Is there a
preferred way to do this? Are there any locking or buffering issues
that I need to be aware of?
Thanks,
Kim
--
Kim Shrier - principal, Shrier and D
Divacky Roman wrote:
hi
I wonder what happens when proc A, create proc B using
fork1(td, RFMEM, 0, &p2);
and either A or B mmap()s something. is the mmaped memory shared
among the procs? what if it brk()s something?
the virtual memory space is totally shared.
this is how linuxthreads w
> From: Jeff Palmer
> Sent: Wednesday, August 23, 2006 2:17 PM
>
> The idea: I'd like to use geli to encrypt *everything* on
> the disk. So if someone (a competitor maybe) removes the
> disk from the machine, he can't gain any data off of it
> easily. I know nothing is 100%, but why make th
On Wed, Aug 23, 2006 at 02:17:02PM -0400, Jeff Palmer wrote:
> Hello,
>
>
> Let me preface the email by saying I'm not overly familiar with geli, and
> it may already have the ability to do what I'm about to describe.
>
> The scenario: A FreeBSD based appliance at a customer premise. The
> c
Hello,
Let me preface the email by saying I'm not overly familiar with geli, and
it may already have the ability to do what I'm about to describe.
The scenario: A FreeBSD based appliance at a customer premise. The
customer really can't be trusted not to disasemble the box, and gain
knowledg
Is this file supposed to have a license at the top?
sys/fs/udf/osta.h
Eric
--
Eric AndersonSr. Systems AdministratorCentaur Technology
Anything that works is better than anything that doesn't.
On Tue, 22 Aug 2006 12:59:07 -0500 (CDT)
Sergey Babkin <[EMAIL PROTECTED]> mentioned:
> If we get back to the question of why we need the file,
> we might not need it at all. As far as I understand,
> the problem is that the Watcom compiler works by
> sticking a set of messages into the executable
- Original Message -
From: "Oliver Fromme" <[EMAIL PROTECTED]>
To: ; <[EMAIL PROTECTED]>
Sent: Wednesday, August 23, 2006 2:40 PM
Subject: Re: Aqcuiring full path to running process from outside the
?kernel
Oliver Fromme wrote:
Another way would be to use /proc/$$/file (where $$ is
hi
I wonder what happens when proc A, create proc B using
fork1(td, RFMEM, 0, &p2);
and either A or B mmap()s something. is the mmaped memory shared
among the procs? what if it brk()s something?
thnx
roman
--
www.liberalnistrana.cz
___
Reko Turja wrote:
> But as said in earlier post of mine, I managed to achieve what I was
> trying with the following code - using the sysctl seems to achieve
> what was needed reliably enough, at least for now.
>
> int mib[4];
> size_t len;
> mib[0] = CTL_KERN;
> mib[1] = KERN_PROC;
> m
On Tue, 22 Aug 2006 12:36:40 +0200
"Attilio Rao" <[EMAIL PROTECTED]> mentioned:
>
> Mmm, I think that a better approach would be refering to different
> MSRs tables for pentium, p6 and Pentium 4 (if I remind correctly they
> are which show differences). It is more extensible, portable and
> possib
17 matches
Mail list logo
