On Tue, Feb 27, 2001 at 03:51:03PM -0800, Paul Saab wrote:
Oops.
make that
vfs.root.mountrootfrom="ufs:/dev/ad0s1a"
Thanks Paul
Joe
PGP signature
Matt Dillon wrote:
Allowing a program to run the OS itself out of VM, with or without
overcommit, is (being generous) just plain dumb.
I'm not a fan of either (overcommit or non-), I can see advantages with both
(seeing that Solaris, which I happen to work with, has one and FreeBSD
On Tue, Feb 27, 2001 at 02:44:04PM -0800, John Baldwin wrote:
On 27-Feb-01 Josef Karthauser wrote:
I've got a bootable filesystem that although it's installed in the first
slice on a disk the kernel/bootloader tries to mount /dev/ad0s2a as the
root filesystem. I'm scratching my head as
On Wed, Feb 28, 2001 at 11:32:02AM +, Josef Karthauser wrote:
What does 'lsdev' show.
Here's what lsdev shows:
disk @ 0xf3e4
disk0: BIOS drive A:
disk1: BIOS drive C:
disk1s1a: FFS
So why is it trying to book disk1s2a at mount time. /me's confused.
Ahha!
Tony Finch [EMAIL PROTECTED] writes:
What about setrlimit(RLIMIMT_DATA)?
Yep, I'd forgotten about that. Malloc() will return NULL if you hit
your data size limit.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers"
Hi,
I am doing the following, on the partition with softupdates turned on:
1. fd = open("a file", O_CREAT)
2. mmap(fd)
3. sequencial write to mmapped region
4. some other processing
5. munmap
6. unlink
7. close
Since this is a supposedly high-perfomance application, I am interested
that data
Why is the mlock(2) call restricted to the super user instead
of enforcing it through per-user or per-login class limits?
I was checking to see if most of the pieces were in place for
"mlockall(MCL_FUTURE)" and noticed the "memorylocked infinity"
setting in limits (I didn't know about
I am doing the following, on the partition with softupdates turned on:
1. fd = open("a file", O_CREAT)
2. mmap(fd)
3. sequencial write to mmapped region
4. some other processing
5. munmap
6. unlink
7. close
Since this is a supposedly high-perfomance application, I am interested
that
On Wed, Feb 28, 2001 at 08:57:31AM -0500, Peter Dufault wrote:
I am doing the following, on the partition with softupdates turned on:
1. fd = open("a file", O_CREAT)
2. mmap(fd)
3. sequencial write to mmapped region
4. some other processing
5. munmap
6. unlink
7. close
[ putting hackers- back here]
On Wed, Feb 28, 2001 at 06:07:50AM -0800, Mike Smith wrote:
I am doing the following, on the partition with softupdates turned on:
1. fd = open("a file", O_CREAT)
2. mmap(fd)
3. sequencial write to mmapped region
4. some other processing
5.
Do an msync with MS_SYNC someplace. Also, use MAP_NOSYNC in
mmap until 4.3 when Matt Dillon plans to make that the default behavior.
Ahh, no. That's the other way around - I do not *want* it to hit the
disk, but would like to *know* when it nevertheless does.
OK, doing a stat and
On Mon, Feb 26, 2001 at 02:31:33PM -0800, John Wilson wrote:
On Sun, 25 Feb 2001 22:00:31 -0600, Michael C . Wu wrote:
On Sun, Feb 25, 2001 at 09:17:38AM -0800, John Wilson scribbled:
If you still have the Perforce-CVS conversion script, I would be
very grateful if you could e-mail it to
On Tue, Feb 27, 2001 at 10:39:13PM -0800, Julian Elischer wrote:
no, something specifically designed around kernel type of actions.
declarations of "physical pointer", "kvm pointer" "User Pointer"
for example, and being able to declare a structure (not 'struct')
and say "this list is 'per
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On 28-Feb-01 Marc W wrote:
I'm trying to ensure robust shutdown on my machine. Thus, I've
installed signal handlers for a bunch of nasty looking signals. In my
new handler, after all critical state is saved, I then call abort(3),
and all seems to work well.
EXCEPT --
: is it possible to actually find out whether data hit the disk or not for
: a particular run of 1-7?
:
:Answer to your question:
:
:Do an msync with MS_SYNC someplace. Also, use MAP_NOSYNC in
:mmap until 4.3 when Matt Dillon plans to make that the default behavior.
I plan on making it the
Hi,
Can you please tell me when did the MGET function change it
implementation from using MALLOC to using pool_get to allocate a mbuf. I
am having a trouble finding out how does the memstats keep track of the
mbufs allocated through pool_get.
Thanks
Regards
Shankar
To Unsubscribe: send mail to
Hmm. Well, mlock() is one of those system calls that virtually
nobody has worked on since inception. The most I've done with it
has been to fix bugs. The resource issues for mlock() aren't
really good enough to prevent misuse in a general multiuser system.
The resource is
::Along the same lines (matt probably knows the answer) is it
::easy to force paging in and locking down of any memory associated
::with a process so that mlockall(MCL_FUTURE) together with
::an appropriate memorylocked limit gives the requested
::memory semantics? I'd have to check through the
Shankar Agarwal wrote:
Hi,
Can you please tell me when did the MGET function change it
implementation from using MALLOC to using pool_get to allocate a
mbuf. I
Never. We don't use pool_get(). That's a NetBSD-ism. :-)
The mbuf subsystem uses its own allocator and stats are kept in
Attached below is a port of NetBSD's patch to FreeBSD's dump(8).
dump's tree walker is a little weird, so the patch is a little more
complicated than calling fts_set with FTS_SKIP. For the technical
details of what it does, see:
http://lists.openresources.com/NetBSD/tech-kern/msg00453.html.
For your collective amusement, here's a post that talks about how OS/2 handles
memory allocation. DosAllocMem() has a flags argument, and one of the flags
requests the OS to actually commit the memory.
http://w3.hethmon.com/os2isp/1998/Apr/Msgs/l2w96957.html
Long shot, probably, but I've got a bunch of virtual machines on an IBM
S/390 mainframe, and while we're running SuSE Linux on most of them, on a
whim I tossed out the idea of running FreeBSD on one of them, and to my
surprise, it was taken seriously.
So, has anyone done any work with getting
hello,
can ipchains / iptables be ported to
FreeBSD...
this is a suggestion if u dont
mind.
jett
Attached below is a port of NetBSD's patch to FreeBSD's dump(8).
dump's tree walker is a little weird, so the patch is a little more
complicated than calling fts_set with FTS_SKIP. For the technical
details of what it does, see:
In the last episode (Mar 01), jett tayer said:
can ipchains / iptables be ported to FreeBSD... this is a suggestion
if u dont mind.
We've already got ipfw and ipfilter; why in the world would we need a
third packet-filtering systam? :)
--
Dan Nelson
[EMAIL PROTECTED]
To
In message [EMAIL PROTECTED],
Ken Bolingbroke writes:
Long shot, probably, but I've got a bunch of virtual machines on an IBM
S/390 mainframe, and while we're running SuSE Linux on most of them, on a
whim I tossed out the idea of running FreeBSD on one of them, and to my
surprise, it was taken
Long shot, probably, but I've got a bunch of virtual machines on an IBM
S/390 mainframe, and while we're running SuSE Linux on most of them, on a
whim I tossed out the idea of running FreeBSD on one of them, and to my
surprise, it was taken seriously.
So, has anyone done any work with
28 matches
Mail list logo
