Thus spake Matthew Dillon <[EMAIL PROTECTED]>:
> Implementing swapoff is a bunch of grunt-work but not too hard in
> concept. Basically the work involved is this:
Sounds like a plan, and not too tricky. Perhaps I'll see if I can
figure it out when I have some free time.
> * Make
:BTW, NetBSD's new UVM code has the ability to do this. Perhaps
:it's worth looking in to how difficult it would really be in FreeBSD...
:
:To Unsubscribe: send mail to [EMAIL PROTECTED]
:with "unsubscribe freebsd-hackers" in the body of the message
Someone got it mostly working a year or t
BTW, NetBSD's new UVM code has the ability to do this. Perhaps
it's worth looking in to how difficult it would really be in FreeBSD...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Thus spake Sean Kelly <[EMAIL PROTECTED]>:
> My familiarity with the "workings" of FreeBSD is still pretty minimal. Are
> there certain reasons that there currently is no way to stop paging to a
> device/file?
I imagine the implementation of this would be complicated, as it
is in Linux. You'd ha
Not sure if this is offtopic here or not, so apologies ahead of time if so.
It has been many years since I used Linux, but one thing I recall is that
there was a `swapoff` command in Linux to complement the `swapon` command.
Are there any patches or plans to implement such a thing in FreeBSD?
My
Bernd Walter wrote:
> On Fri, Jul 12, 2002 at 10:23:35PM +0100, void wrote:
> > On Wed, Jul 10, 2002 at 02:30:19PM +0200, Bogdan TARU wrote:
> > >
> > > Hi guys,
> > >
> > > I have just rebooted my machine, and immediately after boot I have run
> > > 'sysctl -a' as an usual user. Well, in 'ke
On Fri, Jul 12, 2002 at 10:23:35PM +0100, void wrote:
> On Wed, Jul 10, 2002 at 02:30:19PM +0200, Bogdan TARU wrote:
> >
> > Hi guys,
> >
> > I have just rebooted my machine, and immediately after boot I have run
> > 'sysctl -a' as an usual user. Well, in 'kern.msgbuf' I have found the
> >
> In general, it's bad to use stack if the only reason you are using
> it is to seperate context, which is the point I was trying to make.
>
> OpenSSL takes this one level worse, and uses stack to avoid the
> allocation and deallocation of context structures that are copies
> of context structure
Peter Wemm wrote:
> > Note that this assumes none of the stack is used elsewhere; in the
> > kernel example, ther is slightly over 3K used, on average, by the
> > time you get to run.
>
> FWIW; This isn't correct for -current anymore. We have about 7.6K
> of kernel stack now, and a guard page be
Terry Lambert wrote:
> Yar Tikhiy wrote:
> > As I see, there are many spots in the FreeBSD userland sources where
> > multi-kilobyte automatic variables (e.g., string buffers) are used.
> > I've been taught that such variables would better be static or
> > allocated on heap.
> >
> > So the follow
Yar Tikhiy wrote:
> As I see, there are many spots in the FreeBSD userland sources where
> multi-kilobyte automatic variables (e.g., string buffers) are used.
> I've been taught that such variables would better be static or
> allocated on heap.
>
> So the following question comes to my mind: To
On Wed, Jul 10, 2002 at 02:30:19PM +0200, Bogdan TARU wrote:
>
> Hi guys,
>
> I have just rebooted my machine, and immediately after boot I have run
> 'sysctl -a' as an usual user. Well, in 'kern.msgbuf' I have found the
> whole master.passwd file, with combinations of usernames/passwords
On Fri, Jul 12, 2002 at 01:36:22PM -0700, Julian Elischer wrote:
+> did you get answers to this?
+>
Here You got example how to use SLIST_* macros, sysctls, etc.:
http://garage.freebsd.pl/slist.tgz
more examples on http://garage.freebsd.pl
--
Pawel Jakub Dawidek
UNIX Systems Administrator
http:
did you get answers to this?
On Wed, 10 Jul 2002, [unknown-8bit] Aurélien Nephtali wrote:
> Hi,
>
> I'm new in kernel coding (i'm making a kernel module) so i had to learn how
> to use MALLOC*() macros to get memory, not very difficult in fact. But when
> the moment of making a chained list ca
I think it's slightly more complex then that. Sure, all modern
UNIX systems can handle huge stack-based structures, but porting
to other architectures is not the only concern one should have.
Porting from a non-threaded to a threaded environment, for example,
is a major conce
Your mail to 'phrackstaff' with the subject
Hi,phrack,please try again
Is being held until the list moderator can review it for approval.
The reason it is being held:
Posting to a restricted list by sender requires approval
Either the message will get posted to the list, or you will r
In the last episode (Jul 12), Yar Tikhiy said:
> Hi there,
>
> As I see, there are many spots in the FreeBSD userland sources where
> multi-kilobyte automatic variables (e.g., string buffers) are used.
> I've been taught that such variables would better be static or
> allocated on heap.
>
> So t
Good Morning,
I would suggest that since we have an VM implementation that works,
that the answer to your question is "it doesn't really matter." Now,
the information you received about making these items static or
heap allocated can be really beneficial when you are coding for
an embedded system
On Friday 12 July 2002 11:48 am, Yar Tikhiy wrote:
| Hi there,
|
| As I see, there are many spots in the FreeBSD userland sources where
| multi-kilobyte automatic variables (e.g., string buffers) are used.
| I've been taught that such variables would better be static or
| allocated on heap.
|
| So
Hi there,
As I see, there are many spots in the FreeBSD userland sources where
multi-kilobyte automatic variables (e.g., string buffers) are used.
I've been taught that such variables would better be static or
allocated on heap.
So the following question comes to my mind: To stay portable to a
I meant to ask whether we simply need to add a check for (!dev) before the
for loop in vop_revoke() in sys/kern/vfs_subr.c. That would clearly
prevent the crash here. What I don't know is whether there is some larger
bug.
-Michael
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
21 matches
Mail list logo
