system is
one of the reasons UNIX received support from BTL management"
translate into "UNIX was created to run a word processor"?
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
can't provide useful info on *why* it
doesn't work. I wish I could stop what I was doing every time someone
had a problem, but I don't have that kind of time."
Neat.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with &
tories installed them unstripped,
> as they should be.
Do you perchance have something like
INSTALL=install -s
in your /etc/make.conf?
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
erial
console in single-user mode, and could neither interrupt nor
background it, I had no shell). Upon reboot, fsck -p produced a
shitload of busy_count < 0 messages.
(newfs still gets wedged, btw)
DES
--
Dag-Erling Smorgrav - d...@ifi.uio.no
To Unsubscribe: send mail to majord...@freebsd.
Dag-Erling Smorgrav writes:
> I'm getting tons of these in an IDE-only box. They started appearing
> after I put in an IBM DTTA371010 to replace the old (and dying)
> Quantum Fireball ST.
Following up on myself, the box just panicked (softdep_write_complete:
lock held).
DES
Dag-Erling Smorgrav writes:
> Dag-Erling Smorgrav writes:
> > I'm getting tons of these in an IDE-only box. They started appearing
> > after I put in an IBM DTTA371010 to replace the old (and dying)
> > Quantum Fireball ST.
> Following up on myself, the box just pan
Dag-Erling Smorgrav writes:
> Dag-Erling Smorgrav writes:
> > Dag-Erling Smorgrav writes:
> > > I'm getting tons of these in an IDE-only box. They started appearing
> > > after I put in an IBM DTTA371010 to replace the old (and dying)
> > > Quantum Fir
Dag-Erling Smorgrav writes:
> Dag-Erling Smorgrav writes:
> > Dag-Erling Smorgrav writes:
> > > Dag-Erling Smorgrav writes:
> > > > I'm getting tons of these in an IDE-only box. They started appearing
> > > > after I put in an IBM DTTA371010
e the the #freebsd IRC channel about this. The name
> slips my mind right now.
Almost certainly EE (Eivind Eklund).
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
1
>
> Stop.
> *** Error code 1
>
The build is running in a chroot tree which does not have a valid
/etc/resolv.conf.
> yedi#ls /usr/ports/distfiles
> docbk241.tar.Z isoENTS.zip linuxdoc-1.1.tar.gz
> docbk30.tar.Z jade-1.2.1.tar.gz
/usr/src?
VM86 is no longer an option. Remove it, and everything will be fine.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
ears before
them. I haven't seen that many ignorants in my short encounter with
FreeBSD."
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
e. Try the following:
# sysctl -w net.inet.ip.portrange.last=4
and see if it solves the EAGAIN problem.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Brian Feldman writes:
> On 13 Jun 1999, Dag-Erling Smorgrav wrote:
> > connect() normally uses the 1024-5000 range. Try the following:
> >
> > # sysctl -w net.inet.ip.portrange.last=4
> >
> > and see if it solves the EAGAIN problem.
>
> Actually, t
Dag-Erling Smorgrav writes:
> This still doesn't explain select()'s failure to time out
Found it! If you change:
printf("no select() action");
to:
fprintf(stderr, "no select() action\n");
you'll see that select() does time out.
The m
Brian Feldman writes:
> On 13 Jun 1999, Dag-Erling Smorgrav wrote:
> > BTW, you should check for errno == EINTR when select() returns -1.
> The perror() is the status report for select() when -1.
Yeah, but EINTR is a normal condition, so I'd ignore it silently
instead of logg
can't be unconfigured if it's still referenced?
Is there any possibility of implementing a compulsory (as opposed to
advisory) file locking system, so vn swapfiles can't be truncated or
written to by any other process while it's in use?
DES
--
Dag-Erling Smorgrav - d...@flood.ping.
me; I seem to recall that he had managed to get the kernel
to boot and was working on panics (from violated invariants) which
occurred during fsck.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
s of
work to correct.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
f vnodes if I'm not mistaken.
That's the whole point with it.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
echo "apachectl not found"
exit 1
fi
case $1 in
start|stop|restart)
/usr/local/sbin/apachectl $1
;;
*)
echo "Usage: $(basename $0) start|stop|restart"
exit 1
;;
esac
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.
David Scheidt writes:
> # cd /; (cd /cdrom; tar cvf - usr/share/examples/drivers ) | tar xvf -
> should work.
# cd /cdrom && tar cvf - usr/share/examples/drivers | tar xvf - -C /
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@fr
t breaking binary compatibility. We've had too much of that for
no good reason (at least once between 2.2.7 and 2.2.8, and once
between 3.1 and 3.2).
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
o
want kan keep using the old syntax still can, then I for one have no
objections.
Rewriting ipfw rules to ipfilter rules on the fly should be trivial; a
simple Perl script should be sufficient.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.o
"Brian F. Feldman" writes:
> On 19 Jun 1999, Dag-Erling Smorgrav wrote:
> > Rewriting ipfw rules to ipfilter rules on the fly should be trivial; a
> > simple Perl script should be sufficient.
> Not quite as trivial as you think. ipfw and ipf are completely backward
Thomas Good writes:
> Many conf tasks remain non-trivial as compared to BSD or Linux due
> to inexpertise on SCO's end...as the red Sytem Admin Handbook once
> stated (Neveth, Snyder et al.) SCO Unix* is `perverse'.
Nemeth, Snyder, Seebass, Hein.
DES
--
Dag-
ot that one right :)
> and her `Essential System Administration'
> from Tim O'Reilly but the red sysadm guide is my favourite.
Actually, I didn't like it very much. It's been a long time though; I
was 17 when I read it.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.u
mem:kmem /usr/local/sbin/identd identd
-w -t120
d...@des ~% grep ident /usr/src/usr.sbin/inetd/inetd.c
voidident_stream __P((int, struct servtab *));
{ "ident", SOCK_STREAM,1, -1, ident_stream },
ident_stream(s, sep)/* Ident serv
canonical name is.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
the 'internal' keyword, so you
could change /etc/services to read:
fooglorb113/tcp
and inetd.conf to read:
fooglorbstream tcp nowait rootinternal ident
and inetd would know what service to provide on port 113, even if
/etc/services doesn't call it 'iden
Alex Charalabidis writes:
> On 21 Jun 1999, Dag-Erling Smorgrav wrote:
> > The PR is wrong. Sheldon is right. It *does* work the way it ships. If
> > he experienced problems, I bet the real bug was that he edited
> > inetd.conf, HUPed inetd, and hit the "HUP clobbers
ial release of tcpdump? Can we
afford to wait until then, and simply merge in the next release when
it comes?
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
ad an
external LaCie disk hooked up to his Mac until I threatened to pour
Coca Cola into the PSU (this was after I'd hinted several times that
the handles on his G3 would serve very well for chucking it out the
window)
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe:
crypt0genic writes:
> * Dag-Erling Smorgrav (d...@flood.ping.uio.no) [990701 11:47]:
> > LaCie don't make drives, they just package them in ugly boxes with
> > noisy fans.
> Im not sure what model you are refering too, but the drive I have is
> in a stylish external
x27;t hesitate to contact
the Oslo FreeBSD User Group (http://www.ofug.org/).
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
though. Also, although I caught and corrected a few spacing
nits caused by chopping off five letters, there may be some I didn't
catch.
If no-one objects, I'll commit this to -CURRENT in a few days.
DES
--
Dag-Erling Smorgrav - d...@yes.no
Index: src/
RRENT in a few days if no-one objects.
The patches are by Ruslan Ermilov, with a few adjustment by yours
truly.
DES
--
Dag-Erling Smorgrav - d...@yes.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Dag-Erling Smorgrav writes:
> Attached are patches [...]
...and here are the patches.
Noticed by: Peter Wemm
DES
--
Dag-Erling Smorgrav - d...@yes.no
Index: src/usr.bin/netstat/inet.c
===
RCS file: /home/ncvs/src/usr.
ing into this matter I found
another problem :) new patches will be available soon.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Dag-Erling Smorgrav writes:
> That said, thanks for asking - while looking into this matter I found
> another problem :) new patches will be available soon.
Nothing serious; a corrected patch is available on my freefall web
page (http://www.freebsd.org/~des/software/)
DES
--
Dag-
> Not to let this become a passage of right or anything.
ITYM "rite of passage". HTH, HAND!
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
ut a : at the start of your getopt()
string and examine every argument getopt() complains about.
Hope this helps... keep up the good work!
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
It complains about
files with my name at the top (e.g. /usr/include/fetch.h in FreeBSD
3.x and 4.x) in non-ISO8859 locales.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
th of Ski, but I work in Ski). If you can find the right
coordinates for Oslo, put me there instead :) I think tegge also lives
in Oslo now, but I'm not sure.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
s), I will place this file in two locations:
>
> ftp://dragon.ham.muohio.edu/pub/howardjp/grep-0.3.tar.gz
> ftp://ftp.wam.umd.edu/pub/howardjp/grep-0.3.tar.gz
Mirror site: ftp://ftp.ofug.org/pub/grep/
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mai
lots of ports, since the ports framework uses
grep a lot.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Jamie Howard writes:
> I incorporated a huge patch from Dag-Erling Smorgrav [...]
Here's more :)
BTW, I assume you've read this:
http://www.opengroup.org/onlinepubs/007908799/xcu/grep.html>
I see you switched to using extended regexps by default, and made -E a
no-op; this
[accidentally b0rked the cc: line; apologies to those who get this twice]
Jason Thorpe writes:
> On 07 Jul 1999 20:57:16 +0200
> Dag-Erling Smorgrav wrote:
> > Don't use err() indiscriminately after a malloc() failure; malloc()
> > doesn't set errno.
> This i
Dag-Erling Smorgrav writes:
> Jamie Howard writes:
> > I incorporated a huge patch from Dag-Erling Smorgrav [...]
> Here's more :)
Following up on myself, I introduced a bug in the previous round of
patches; here's a corrected patch against 0.3.
(the bug was that grep wo
rep does)
As for full-line matches (-x), simply check that
(pmatch[0].rm_so == 0 && pmatch[0].rm_eo == len)
This should save you from playing games with back-references.
(both code snippets assume that line points to a line of text from the
input and that len is the length of that li
Jamie Howard writes:
> On 7 Jul 1999, Dag-Erling Smorgrav wrote:
> > I see you switched to using extended regexps by default, and made -E a
> > no-op; this breaks the ports collection, so I changed it back.
>
> The FreeBSD, NetBSD, and OpenBSD manpage for grep says
only match whitespace boundaries IIRC.
Anyway, I already posted a solution which does not involve screwing
around with the pattern.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
BTW, the end-of-line handling is wrong; grep will fail to select a
line where the pattern appears at the end and the line is not
terminated by a newline. I'm working on a fix (and on implementing my
solution for -w and -x).
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubs
Assar Westerlund writes:
> Dag-Erling Smorgrav writes:
> > + realpat = grep_malloc(strlen(pattern) + sizeof("^(")
> > + + sizeof(")$") + 1);
> Why not just use asprintf?
Doesn't matter, thsis code is gone in the late
how much RAM / swap you have. You
won't run into trouble unless you actually try to use too much of it.
> What happens if the process hits its resource limits?
Malloc() fails with ENOMEM.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.
r kern.maxfiles.
> Someone told me to store these limits (above) in
> a etc/sysctl.conf file but when I went to etc that
> file wasn't in there .. do I have to newly create the
> file or should it already be there?
'man sysctl.conf'
DES
--
Dag-Erling Smorgrav - [EMAIL PROTEC
"Julian Stacey [EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Penguin mascot has enough advantages over Chuck already !
Then why do I get this urge to go bowling every time I see Tux?
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EM
Jamie Heckford <[EMAIL PROTECTED]> writes:
> In all honesty, I am just looking for something to play
> with and see how fast FreeBSD can go.
I'd say about 2.8 m/s/s, given sufficient height.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAI
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> Jamie Heckford <[EMAIL PROTECTED]> writes:
> > In all honesty, I am just looking for something to play
> > with and see how fast FreeBSD can go.
> I'd say about 2.8 m/s/s, given sufficient height.
Doh! I mean
.. "if you do it quickly, nobody will notice"
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
oes not set
resource limits; nor does it chroot as far as I recall.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
;ll only screw it up"... I'm
tempted to reply "not much more than it already is". Eivind and I
rewrote it for our previous employer, but the mod is part of a large
chunk of proprietary code, unfortunately.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mai
before; we managed to
chroot the scripts so we're reasonably confident that they can't do
much harm except to themselves.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Chris Stenton <[EMAIL PROTECTED]> writes:
> Fatal server error:
> xf86OpenConsole: Server must be suid root
This is your clue.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "un
"Crist J. Clark" <[EMAIL PROTECTED]> writes:
> On Sat, Jan 20, 2001 at 01:51:43AM +0100, Dag-Erling Smorgrav wrote:
> > Chris Stenton <[EMAIL PROTECTED]> writes:
> > > Fatal server error:
> > > xf86OpenConsole: Server must be suid root
> >
return (value); what happens ?
If the value you return is non-zero, see above. If it's zero, the
userland syscall code returns p->p_retval[0] to the caller.
> * Does this logic also apply to the Linux syscall stuff in the kernel?
I think so. Marcel would be better placed to answer
could
> only be changed setting some option in the kernel and compiling a new
> one.
Congratulations, you just invented capabilities! :)
http://www.trustedbsd.org/
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Jos Backus <[EMAIL PROTECTED]> writes:
> This patch gets rid of the Broken pipe messages.
No need to name the loop...
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
[EMAIL PROTECTED] (Alexander Langer) writes:
> There recently (last week or something) was a thread here or on
> another mailinglist on how to debug kernel moduls, which is a little
> bit tricky.
It's also documented in the handbook.
DES
--
Dag-Erling Smorgrav - [EMAIL P
Alexander Langer <[EMAIL PROTECTED]> writes:
> Thus spake Dag-Erling Smorgrav ([EMAIL PROTECTED]):
> > Alexander Langer <[EMAIL PROTECTED]> writes:
> > > There recently (last week or something) was a thread here or on
> > > another mailinglist on how to
Zhiui Zhang <[EMAIL PROTECTED]> writes:
> Is there a way to specify a kernel other than /kernel to boot from? I do
> not want to do this manually, I want to put it into some configuration
> file. Thanks,
'man loader'
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
ost of it really isn't
deep voodoo and you can understand it if you try. In my experience,
this psychological block is a much bigger obstacle to overcome than
actual technical complexity.
(hmm, I must remember to drop by Mustang Jack next time I'm in NYC)
DES
--
Dag-Erling Smorgrav - [EMAIL P
vijay <[EMAIL PROTECTED]> writes:
> Hi, I am new to FreeBSD. I wanted to know if I can play audio
> CDs on "my" system.
'man cdcontrol'
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Chet Ramey <[EMAIL PROTECTED]> writes:
> Bash uses the presence of SSH_CLIENT to decide whether or not to run the
> shell startup files for a non-interactive shell (like it attempts to do
> for rsh). [...]
Feh. Here's a nickel, kid, get yourself a real shell.
DES
--
bugs (except for some, but not all, known security holes) about half a
year ago. If you absolutely must run RELENG_3, don't run anything but
the very latest 3.5-STABLE (cvsup and cvs are your friends).
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PR
t available at the time.
Well, it was a stupid decision at that time, and the decision not to
upgrade or replace these machines now is even stupider.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
slowdown to try to
narrow down the day (or even the week) on which it occurred?
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
grade. When you're sure
you've got it down pat, take the production box down for however long
you need to upgrade it (somewhere between half an hour and two hours
depending on disk speeds and how much tinkering is needed).
DES (been there, done that)
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
ot; RAM, then touches every page during startup.
Unless some form of clustering is done, this causes 16384 write
operations for a 64 MB virtual machine...
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ying I-told-you-so when it eventually
> breaks.)
Get a better job. Skilled IT workers are rare enough that they
shouldn't need to put up with such crap, and shouldn't have any
trouble getting a new job when the crap starts flying.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To U
tc. becomes insignificant next to the time spent doing I/O,
and if you're already doing I/O as fast as you can there's no room for
improvement. On a machine with a slower CPU or a faster I/O system,
you'd see improvement.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsu
box,
probably with a 100 MHz or 133 MHz FSB, not the old 486DX33 you have
lying in a corner.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Jordan Hubbard <[EMAIL PROTECTED]> writes:
> [...] That implies to me, at least, that after a certain
> point the CPU is going to be the bottleneck.
More likely RAM bandwidth. Those 133 Mhz FSBs ought to help, though.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To
on disk.
Don't be so sure. Stuff on disk has to be read into memory, and this
is generally done by DMAing it off the disk, which locks the memroy
bus, then copying it out into userland. With an MFS you skip the first
part, unless MFS is stupider than I thought.
DES
--
Dag-Erling Smorgra
of jobs boosts performance to a certain point;
past this point, performance starts decreasing again.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
#x27;t trigger it to be
> recompiled by the kernel make process.
Of course not. It's not part of the kernel. There's a duplicate of
this file in /usr/src/sys/netinet which need to be kept in synch.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTE
Robin Cutshaw <[EMAIL PROTECTED]> writes:
> Any ideas as to why it would take almost three times longer to build
> on FreeBSD?
Yup: 4.x sucks at SMP. Try the comparison again with uniprocessor
kernels - I expect you'll see a much smaller difference.
DES
--
Dag-Erling
ility to correctly
detect if a dependency is out of date is irrelevant.
Also, my experience is that unless you're paying Sun significant
amounts of $$, their reaction to bug reports is to close their eyes,
hum real loud and hope they go away.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsub
oject that directly or indirectly
depends on every other, you can also just specify that one file on the
command line.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
e the old 'config & make' method uses a
compile directory in /usr/src.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
thank you very much, but it takes some
hand-holding.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
thing until you dirty one
page too many and segfault.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ll give
you a chunk of memory that's already mapped and you'll be fine, but
sometimes (when allocating beyond what was previously used) it won't.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> if (sigsetjmp(env) == -1) {
Blah, this should be
if (sigsetjmp(env, 1) == -1) {
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers"
[EMAIL PROTECTED] (Peter Seebach) writes:
> In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes:
> >Malloc() does not overcommit - the kernel does. Malloc() doesn't know
> >and doesn't care.
> But it could still probably force the behavior.
Barring kernel
ilable before you actually get
to dirty the pages that were allocated.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Kenneth Wayne Culver <[EMAIL PROTECTED]> writes:
> On 24 Feb 2001, Dag-Erling Smorgrav wrote:
> > Kenneth Wayne Culver <[EMAIL PROTECTED]> writes:
> > > FreeBSD supports cardbus in -CURRENT, but I wouldn't expect it to ever
> > > support cardbus in 4.x.
"Daniel C. Sobral" <[EMAIL PROTECTED]> writes:
> It doesn't work. The application killed by reason of insufficient
> resources is not (necessarily) the one that causes the page fault
> leading to that.
This is arguably a bug which needs to be fixed.
DES
--
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 "
e
> > disk, but would like to *know* when it nevertheless does.
> OK, doing a stat and checking the mtime should give you
> the info at the expense of polling, I can't think of another way.
Won't help. You'll get the same mtime no matter whether the file is
actually
101 - 200 of 489 matches
Mail list logo
