[I sent the same message to [EMAIL PROTECTED], but since that list
seems not very active, I am asking here too]
Hi all,
the subject says it all.
I am considering using FreeBSD for a robotics project, and I am
thinking of using 4.x for stability. But, since we will probably use
USB a lot, I am
I'm trying to write pam module, which uses libs from /usr/local/lib (lber
and lsap). What should i put in Makefile in order to link module with this
libs?
LIBLDAP= /usr/local/lib/ldap.a
LDADD+= -L/usr/local/lib -lldap
LDFLAGS += -L/usr/local/lib -lldap
DPADD= ${LIBCRYPT} ${LIBLDAP}
doesn't
On Wed, Jul 16, 2003 at 05:57:44AM -0700, Avleen Vig wrote:
I have been experiencing several ffs_clusteralloc: map mismatch
kernel panics (always while heavy r/w activity on ad0). PC in question
has SuperMicro P3TDL3 motherboard,
2 ide + 1 scsi HDD and 4 nics (full dmesg kernel config
On Mon, Jul 21, 2003 at 04:42:12AM -0400, Ilmar S. Habibulin wrote:
I'm trying to write pam module, which uses libs from /usr/local/lib (lber
and lsap). What should i put in Makefile in order to link module with this
libs?
LIBLDAP= /usr/local/lib/ldap.a
LDADD+= -L/usr/local/lib -lldap
On Mon, Jul 21, 2003 at 09:18:42AM +0200, Marco Molteni wrote:
[I sent the same message to [EMAIL PROTECTED], but since that list
seems not very active, I am asking here too]
Hi all,
the subject says it all.
I am considering using FreeBSD for a robotics project, and I am
thinking of
On Sat, 19 Jul 2003, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Marc Ramirez [EMAIL PROTECTED] writes:
: I have a device driver that needs to make requests for data from a
: userland daemon. What's the preferred method for doing this in 4.8R and
: 5.1R? I'm assuming
On Fri, 18 Jul 2003, Terry Lambert wrote:
Marc Ramirez wrote:
I asked this in -questions, but got no response; sorry for the repost.
I have a device driver that needs to make requests for data from a
userland daemon. What's the preferred method for doing this in 4.8R and
5.1R? I'm
I should be most grateful if someone reviews the attached code fragment
and let me know how to do the right thing for PAE whilst remaining
machine-independent.
My previous version of this code was written after reading the pre-busdma'd
bktr(4) driver, which used pmap_kenter() - bad puppy!
Should
On Sat, 19 Jul 2003, Pawel Jakub Dawidek wrote:
On Fri, Jul 18, 2003 at 03:47:05PM -0400, Marc Ramirez wrote:
+ I have a remote datastore that I want to present as a filesystem. There
+ are two parts to this: fetching raw data over the network, and doing some
+ processing on the data. For
Cool. Thanks, everyone! Messrs. Watson and Lambert have convinced me to
go the pseudo-device route. I think that's really going to clean up a lot
of the code.
I'm so excited!
Thanks!
Marc.
On Sun, 20 Jul 2003, Robert Watson wrote:
On Sat, 19 Jul 2003, Pawel Jakub Dawidek wrote:
Your
:It turns out that the kernel's internal ELF loader is misinterpreting
:an ABS symbol (i.e. set with .SET in assembly) whos value is 0 as being
:'not found', and once that is fixed it was also confusing the absolute
:symbol with a COMMON symbol.
:
:Thanks for the pointer. FWIW, We
In message: [EMAIL PROTECTED]
Marco Molteni [EMAIL PROTECTED] writes:
: Any ideas, besides the compare the USB source between 4.x and 5.x
: suggestion? ;-)
USB hot plugging in 4.x sucks really bad. it is tolerably ok in 5.x
for non-weird devices.
Warner
In a message written on Mon, Jul 21, 2003 at 08:53:53AM -0700, Tim Kientzle wrote:
Actually, this example passes -Wall if you declare
execargv as simply char *[]. However, I'm looking
for something that passes gcc -Wwrite-strings, which this
example does not.
% cat exec.c
#include unistd.h
On Mon, Jul 21, 2003 at 12:57:35PM -0400, Leo Bicknell wrote:
In a message written on Mon, Jul 21, 2003 at 08:53:53AM -0700, Tim Kientzle wrote:
Actually, this example passes -Wall if you declare
execargv as simply char *[]. However, I'm looking
for something that passes gcc
In a message written on Mon, Jul 21, 2003 at 11:15:38AM -0600, Chad David wrote:
Try cc -Wwrite-strings -Wcast-qual exec.c.
You cannot simply cast away a const.
Grumble, will someone give me all the warnings you want turned on so I
can work around all of them? :)
% cat exec.c
#include
On Mon, Jul 21, 2003 at 01:23:21PM -0400, Leo Bicknell wrote:
In a message written on Mon, Jul 21, 2003 at 11:15:38AM -0600, Chad David wrote:
Try cc -Wwrite-strings -Wcast-qual exec.c.
You cannot simply cast away a const.
Grumble, will someone give me all the warnings you want turned
Robert Watson wrote:
Of these approaches, my favorite are writing directly to a file, and using
a psuedo-device, depending on the requirements. They have fairly
well-defined security semantics (especially if you properly cache the
open-time credentials in the file case). I don't really like
In article [EMAIL PROTECTED] you wrote:
In message: [EMAIL PROTECTED]
Marco Molteni [EMAIL PROTECTED] writes:
: Any ideas, besides the compare the USB source between 4.x and 5.x
: suggestion? ;-)
USB hot plugging in 4.x sucks really bad. it is tolerably ok in 5.x
for non-weird
On Mon, Jul 21, 2003 at 01:57:59AM +0200, Pawel Jakub Dawidek wrote:
+ So as you can see I'm listing every entry that isn't writable.
+ This function is called when process is killed by kernel with SIGBUS.
+ It shows me that only this region isn't writable:
+
+ ENTRY:PID: 0-0xbfc0 (0:0)
On Mon, 21 Jul 2003, Terry Lambert wrote:
Robert Watson wrote:
Of these approaches, my favorite are writing directly to a file, and using
a psuedo-device, depending on the requirements. They have fairly
well-defined security semantics (especially if you properly cache the
open-time
Chad David wrote:
I assumed it was obvious that you could copy the data, but I believe
the intent of the original question was to find an alternative. As
far as I know there isn't one. A const is a const, except in C++.
Yes, the intent was to find a way to avoid copying the data.
I was hoping
In a message written on Mon, Jul 21, 2003 at 11:24:43AM -0700, Tim Kientzle wrote:
I was hoping that someone knew a standard way to
say yes, I really do mean to cast away that const,
akin to C++ const_cast.
I'm missing something here. You can do that, but you can't do that
with say
You know, my own thinking made me figure this one out:
% cat exec.c
#include unistd.h
#include paths.h
#include string.h
int main(int argc, char *const argv[], char *const envp[]) {
char *const execargv[] = { _PATH_BSHELL, NULL };
execve(_PATH_BSHELL,execargv,NULL);
return 0;
}
% cc
On Mon, Jul 21, 2003 at 02:20:40PM -0400, Robert Watson wrote:
+ For one of our research projects, here at NAI, we did a fair amount of
+ userland network code prototyping. We started out with IPDIVERT, then
+ pushed down to BPF using a partial network stack in userspace. We've
+ found it's a
Hmm. Is the VM object properly sized? Any attempt to fault-in data
beyond a VM object's EOF, regardless of how you set the map_entry
permissions, will seg fault or bus fault.
-Matt
Matthew Dillon
On Mon, Jul 21, 2003 at 12:03:59PM -0700, Matthew Dillon wrote:
+ Hmm. Is the VM object properly sized? Any attempt to fault-in data
+ beyond a VM object's EOF, regardless of how you set the map_entry
+ permissions, will seg fault or bus fault.
I'm allocationg memory with obreak()
: end =3D vm-vm_daddr + ctob(vm-vm_dsize);
: obreak(vm, end + size);
: vm_map_protect(vm-vm_map, end, end + size, VM_PROT_READ);
:
:And vm_map_protect() will create new map entry (it should, right?)
:with entry-start =3D end and entry-end =3D end + size.
:
:But what happend with
Hi Pawel,
On Mon, Jul 21, 2003 at 09:16:22PM +0200, Pawel Jakub Dawidek wrote:
I'm allocationg memory with obreak() function (so vm_map_find() function
is used to find space). But if I try to allocate size (and size is small),
obreak() will allocate more memory.
You may find the vm_map and
On Mon, 21 Jul 2003, Pawel Jakub Dawidek wrote:
For example syscall is marking some range with mark() function. For now
on this range isn't accessable from userland. If process will try to
write to this page, page is copied (copy-on-write). If this page will
be modified by kernel it will
On Mon, Jul 21, 2003 at 12:32:19PM -0700, Matthew Dillon wrote:
+ Hmm. Well, when a process forks the vm_map_entry's fork along with
+ it. The underlying VM objects remain shared but become copy-on-write.
Yes, but I mean while execve(), not fork().
Before execve() is called map got for
Valentin Nechayev [EMAIL PROTECTED] writes:
I need to downgrade a remote FreeBSD system from 5.1-release to 4.8-release
remotely without any local help (except possible hitting Reset).
Maybe if you tell us why you need to do this we can figure out a way
for you to avoid doing it?
DES
--
On Monday 21 July 2003 15:00, Bernd Walter wrote:
On Mon, Jul 21, 2003 at 09:18:42AM +0200, Marco Molteni wrote:
[I sent the same message to [EMAIL PROTECTED], but since that list
seems not very active, I am asking here too]
Hi all,
the subject says it all.
I am considering using
5.x seems to have much better support for USB 2.0 as well. I have
a SanDisk 2.0 USB compact flash reader that just works with 5.1 release.
So far no amount of kernel hacking has made it work with 4.8.
Unfortunetly for me I need it to work under 4.8. )-:
As a follow up to this problem
On Mon, Jul 21, 2003 at 08:51:19PM +0100, Bruce M Simpson wrote:
Matt, Bruce, thanks!
I've track it down.
Yes, those read-only pages was reused. So now I'm putting them on list
before syscall is called, and after syscall is executed I free memory
for non-execve syscalls and mark entries from
I've recently setup and started using Free-BSD 5.1 as my desktop at home
and was looking to find more information about getting started in
contributing to the Free-BSD project.
What piqued my interest is the well organised clean Free-BSD kernel, and
the vast wealth of documentation on using the
On 21 Jul 2003 22:30:39 -0500, Shawn [EMAIL PROTECTED] wrote:
I've recently setup and started using Free-BSD 5.1 as my desktop at home
and was looking to find more information about getting started in
contributing to the Free-BSD project.
What piqued my interest is the well organised clean
On Mon, 2003-07-21 at 22:46, Jeremy Messenger wrote:
Is this http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-
handbook/ what you are looking for? Also, you can try to check
http://www.freebsd.org/docs.html ..
Thank you! I can't believe I missed that. I swear I looked all around
37 matches
Mail list logo
