On Wed, Nov 13, 2002 at 12:01:08PM -0800, Matthew Dillon wrote:
+ Would people be interested if I added such a feature? Limit the
+ highest allocatable pty to 90% when operating within a jail? e.g.
+ if you have 256 ptys both jail and normal tend to allocate ptys
+ from the
The files in this directory provide pkgsrc functionality on FreeBSD.
http://pigseye.kennesaw.edu/~dyeske/netbsd/
I used the RedHat 5.0 zoularis binaries under FreeBSD current to get digest and bmake
going
natively. This is not well tested, and I know very little about pkgsrc. I had some
After some advocacy effort, I convinced a friend to try
FreeBSD and I handed him some old 3.4 CDs I had. He
attempted to install it on a 600M HD with the surprise that
the auto settings in sysinstall didn't leave him sufficient
space on the /usr partition. He was somewhat surprised as
the CD
--- Terry Lambert [EMAIL PROTECTED] wrote:
Chuck Tuffli wrote:
On Fri, Nov 15, 2002 at 11:03:44AM -0600, mark tinguely wrote:
[snip]
The memory is avaliable to the kernel/drivers when
bus_dmamem_free() is
called. The problem for you is that someone else does allocate a
page within
I'm at my Witt's End trying to fix an unterminated quoted string problem
in a shell script. Do any of you have any debugging tools tucked away
that might help with this? (sh -[xv] have already been tried.) Something
that printed a parse tree of the script would do the trick, but I can't
find
Hi,
I successfully build a RELENG_4_7_0_RELEASE distributions except for the
packages.
from release(7)
cd /usr
cvs co -rRELENG_4_5_0_RELEASE src
cd src
make buildworld
cd release
make release CHROOTDIR=/local3/release BUILDNAME=4.5-RELEASE \
I hope I'm completely misunderstanding the docs for exports(5) and
kin, but here goes:
The short form:
I have two filesystems I want to export. They're both listed in
/etc/exports. The first will be exported just fine, the second
yields complaints from mountd about the device being busy.
On Saturday 16 November 2002 19:52, Lyndon Nerenberg wrote:
I'm at my Witt's End trying to fix an unterminated quoted string problem
in a shell script. Do any of you have any debugging tools tucked away
that might help with this?
Try using an editor with syntax highlighting, e.g., Vim or
Gary Thorpe wrote:
Really, there's a lot of the kernel which could be pageable,
which would help this. But for this to work, all the code
in the paging path has to be marked non-pageable.
The way Windows handles this is to have seperate ELF sections
for pageable vs. unpageable vs.
In message: [EMAIL PROTECTED]
Matthew Dillon [EMAIL PROTECTED] writes:
: I think that should be a goal. I think something like this:
:
: USE_MINIC=YES Link against the mini-C library.
I don't like this so much, but not enough to object to it be allowed,
but not default.
Hello,
I have seen two instances of this problem in the
last 4 months and it is not reproducible, so I was
wondering if somebody could point me to some potential
causes. The problem appears to be that there are 2 extra
stack pops while executing in the kernel in a routine.
This function looks
I've tried a number of syntax-colouring editors, to no avail. The quotes
(single, double, and back) *are* balanced, according to everything I've
thrown the script at. That's why I'm more interested in something that
can actually parse Bourne shell syntax (quiet Terry - I *know* what
you're going
In message: [EMAIL PROTECTED]
Matthew Dillon [EMAIL PROTECTED] writes:
: Take /bin/csh (aka tcsh) for example.
:
: Startup overhead if static: 144 pages faults, 113 zero fill, 64 COW
: Startup overhead if dynamic: 310 page faults, 131 zero fill, 84 COW
:
: So
--- Matthew Dillon [EMAIL PROTECTED] wrote:
:I personally thing that we should have a shared /{s,}bin in 5.0 and
:that it should be the dafult and that it should work with / and /usr
:being on different partitions. Preliminary indications are that
we'd
:save on the order of 25M-30M on /,
Lyndon Nerenberg wrote:
I've tried a number of syntax-colouring editors, to no avail. The quotes
(single, double, and back) *are* balanced, according to everything I've
thrown the script at. That's why I'm more interested in something that
can actually parse Bourne shell syntax (quiet Terry -
:
: So the difference is 38 pages of memory = 152KB per instance.
: That's fairly significant on a multi-user system that might have
: several hundred csh's running. I specifically compile certain
: non-forked binaries on my system static precisely to reduce their
: memory
:I just ran a quick test on my systems here. It looks like two
:identical systems give results that are approximately:
:
: VSZ RSS
:dynamic:
:root 79054 1.3 2.5 1952 1524 pa S 2:56AM 0:00.13 tcsh
:static:
:root 38788 0.0 0.1 1324 908 pi S 7:53PM
Thus spake Gary Thorpe [EMAIL PROTECTED]:
Take /bin/csh (aka tcsh) for example.
Startup overhead if static: 144 pages faults, 113 zero fill, 64
COW
Startup overhead if dynamic: 310 page faults, 131 zero fill, 84
COW
So the difference is 38 pages of memory =
RedHat systems have only two statically linked binaries in their systems
and it is one of the things that I viscerally hate about RedHat. You have
to look on another system or lookup on the net which shell to use instead
of /sbin/init and then play around with a massively minimal set of things
19 matches
Mail list logo
