, mask);
mask = 1;
}
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail
, if the drivers are not fixed by may 1st
the HARP ATM stack will be put in the attic.
If anybody is interested in actively maintaining this code, I may be
able to find a donor for some ATM cards.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC
(something), onemore)) {
chugchugchug(argthisa;
}
is just a tiny bit more readable than
if ((somerandomfunction(argthis, functionthat(something), onemore)
!= 0) {
chugchugchug(argthisa;
}
for instance.
--
Poul-Henning Kamp
In message [EMAIL PROTECTED], Mike Meyer writes:
Poul-Henning Kamp [EMAIL PROTECTED] types:
In message [EMAIL PROTECTED], Mike Meyer writes:
David O'Brien [EMAIL PROTECTED] types:
On Wed, Mar 06, 2002 at 02:08:07AM +0200, Giorgos Keramidas wrote:
Now, IFF the C language had a type called
In message [EMAIL PROTECTED], Mike Meyer writes:
Poul-Henning Kamp [EMAIL PROTECTED] types:
In message [EMAIL PROTECTED], Mike Meyer writes:
I'm advocating that the rule focus on readability rather than trying
to enforce a type which doesn't exist.
Excellent idea. Can you provide verbiage
be explicitly compared
to zero
if (float_t == 0.0)
3. Integers need not be explicitly compared to zero:
if (foo MASK)
not
if ((foo MASK) != 0)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
what is the problem ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED
of the the logic of the expression does. Which is
if string compare a with b is equal then do X. [if (strcmp(a,b) == 0)]
Well, we're clearly into IMO land here, so lets ignore that :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
should mean are the same but
really means are different and likewise for the second one.
Guys, strcmp() has been defined that way for almost 30 years, get
used to it, and don't demand obfuscation of every other if() in
the kernel to try to hide the fact...
--
Poul-Henning Kamp | UNIX since Zilog
stuff out of the
dumpon(8) manual and proceed to remove the program itself as described
above.
Thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
a divert ipfw rule for incoming trafic from the
attackers IP# to capture all the tricks he is trying to
do.
Log the received packets in detail in pcap format files.
Report the packets to Dshield.org
etc.
Any takers ?
--
Poul-Henning Kamp | UNIX since
someone
who understands the pcb functions can point out exactly what the error is
in here -- this is the first time i've ever looked at them...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
--
Poul-Henning Kamp | UNIX since
or indirectly, provide feedback to DARPA.
I hope this answers the FAQ on UFS2, GEOM and all that.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
and Unixware.
We are working very hard to make procfs optional in FreeBSD for a
number of reasons.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
is to use an ioctl to download the data from
userland.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe
practically rules out any high-level.
You might consider putting a PIC out there for the actual timing,
and having a control interface to it along the lines of pulse this
line move ignition earlier, pulse that one and move ignition later.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
as timecounter?
Unlikely.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL
in miibus_attach() or miibus_probe()
instead?
I just had reason to mess around with a PHY GigE related problem
as well, and I can only say that the MII code might have sounded
like a good idea at the time but the implementation sucks as far
as I can tell.
--
Poul-Henning Kamp | UNIX since Zilog
of simple
classes in GEOM.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL
In message [EMAIL PROTECTED], Miguel Mendez writes:
Well, if you've used recent versions of the veritas volume manager
fronted you'll notice that they give the cli command output in a window,
that's what I intend to do.
They did that in 1994...
--
Poul-Henning Kamp | UNIX since Zilog
, because
I couldn't find one already in existance. fdisk and disklabel only seem
to work on one disk at a time, and I wanted to see everything.
Yes :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Montana State University,Bozeman MT 59717 [EMAIL PROTECTED]
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
hacks
to the compiler and the passwd program when the compiler itself
was being compiled.
Sigh.
Wrong reference.
That was from Brians ACM Turning award thankyou-presentation.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
In message [EMAIL PROTECTED], David Schultz writes:
Thus spake Poul-Henning Kamp [EMAIL PROTECTED]:
That was from Brians ACM Turning award thankyou-presentation.
http://www.acm.org/classics/sep95/
Ahh, at least I got one more parameter right than Terry :-)
--
Poul-Henning Kamp | UNIX
, not the basics, correct? Other than SMP, of
course.
It is the intent that GEOM will be standard (or basics if you like).
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
In message [EMAIL PROTECTED], j mckitrick writes:
On Fri, Jun 07, 2002 at 02:44:27PM +0200, Poul-Henning Kamp wrote:
| In message [EMAIL PROTECTED], j mckitrick writes:
| | On the other hand, there are numerous new features (GEOM, TrustedBSD,
| | OpenPAM, Snapshots + background fsck, etc) being
mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
I have a bunch of 8 floppies I need to try to recover contents
from, is there anybody out there who has a 8 drive they'd be willing
to part with for $$ ?
If it comes with the magic SA800-PC cable it would be just perfect.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
In message [EMAIL PROTECTED], Hellmuth Michaelis writes:
Poul-Henning Kamp wrote:
I have a bunch of 8 floppies I need to try to recover contents
from, is there anybody out there who has a 8 drive they'd be willing
to part with for $$ ?
Sorry, but i'm in the same boat. I have an old Hewlett
(1) over a wavelan is a very
good test-bed for this issue.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
In message [EMAIL PROTECTED], Michael Sierchio writes:
Poul-Henning Kamp wrote:
Yes, I can attest to this an I belive it is actually the case on both
-current and -releng4 that disabling newreno improves TCP performance.
I belive running an X11 application or scp(1) over a wavelan is a very
that. :(
Luigi, get in touch with W Gerald Hicks [EMAIL PROTECTED],
he has patches which does this by objcopy'ing the binary file to
an elf-object and then linking that with the kernel.
This is far superior to overwrite the binary kernel approach.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
to get passage of time (I don't need date/time, just
the passage of it) for different internal operations in the program.
Use UTC time, it has no daylight savings problems.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
In message [EMAIL PROTECTED], M. Warner Losh writes:
In message: [EMAIL PROTECTED]
Poul-Henning Kamp [EMAIL PROTECTED] writes:
: In message 005f01c22dd1$7be7d180$0300a8c0@fivehundred, Andrei Cojocaru writ
: es:
: I am already synchronizing using xntp, that's not the problem
for an MFC. Suggest you provide a -stable friendly patchfile
until we have this issue settled in -current.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
to not
access subsectors.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
and use the 512 byte units, so I guess it would be:
offset = dbtob(blkno);
KASSERT(!(offset (bsize - 1)), (suitable diagnostic));
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
it should be MFCed before release.
I agree, but I'm ENOTIME.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
In message 49874ca8.5090...@gmx.de, Christoph Mallon writes:
I compiled a list of all local variables in src/sys/ (r188000), which
are only written to, but never read.
Bravo!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD
things happen.
You will want to study carefully Dave Mills work to tame the alpha
chips wandering SAW clocks.
Poul-Henning
[1] In my mind, reworking the callout system in the kernel would
be a much better more neded and much more worthwhile project.
--
Poul-Henning Kamp | UNIX since Zilog
notice
in reaction to temperature and battery power.
Let me repeat:
[1] In my mind, reworking the callout system in the kernel would
be a much better more neded and much more worthwhile project.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP
like getpid/getgid.
Agreed, that is a good place to start.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
to a per-CPU page.
Rule #3:
The only thing worse than generalizing from one example is
generalizing from no examples at all.
We can add those mappings when we know why we would want them.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP
In message alpine.bsf.2.00.0903272303040.12...@fledge.watson.org, Robert Wats
on writes:
In which case user application threads will need to
know their CPU [...]
Didn't jemalloc solve that problem once already ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org
be interesting.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
(1) or similar (multiline)
# Example:
# 9 2.91 real 0.03 user 0.05 sys
9 ___
*END UFSTUNE FORM*
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long time before progress
am building the infrastructure
it should be based on in the kernel.
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail
off from. Basically all that is needed for a DEVFS
to do, is to hook into the dev_t maintenance code and construct
the directory tree.
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long
with the interrupts, the overflow heuristics in
i8254_get_timecount() may break down). Other systems may have even
more limitations on the timecounters.
Bruce
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
--
Poul-Henning Kamp
But shouldn't you still be able to use the timer in the local apic ?
In message 86k8sajlmz@not.demophon.com, Ville-Pertti Keinonen writes:
p...@critter.freebsd.dk (Poul-Henning Kamp) writes:
Somebody should study the abilities of the on-cpu APIC for this
for pentium ff. machines
In message 19990714185101.09...@goatsucker.org, Scott Mitchell writes:
Ugh. In that case, can someone back out Poul-Henning's changes to the
if_xe.c in the -STABLE tree?
Uhm my change has not been applied to STABLE, but the 3.2-PAO import
references current rather than stable.
--
Poul-Henning
The point was who the heck sends the SIGHUP and why ?
Poul-Henning
In message 23428.932574...@axl.noc.iafrica.com, Sheldon Hearn writes:
[Hi-jacked from cvs-committers and cvs-all]
On Wed, 21 Jul 1999 18:15:09 +0200, Poul-Henning Kamp wrote:
There is another one you may want to look at, I
this fact.
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers
pre-collapsed.
You are talking gibberish here. Please show code where this is
a problem.
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long time before progress goes too far
will cover from before the big bang to way past
any time we'll be caring about. :-)
But we cannot do time in seconds resolution, we need to resolve at least
the cpu clock frequency, which right now is approaching 1GHz (30bit!)
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org
it some
day.
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers
) on
a blinding fast machine...
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe
In message pine.bsf.3.95.990818105716.12306a-100...@current1.whistle.com,
Julian Elischer writes:
On Wed, 18 Aug 1999, Poul-Henning Kamp wrote:
Matt doesn't represent the FreeBSD project, and even if he rewrites
the VFS subsystem so he can understand it, his rewrite would face
considerable
-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body
that does know about it, to the vfs producer on
machine 3 that also knows about it?
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send
a little surprised that there's any objection to the concept of
mandatory locking.
Too many of us have had wedged systems because of it I guess...
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take
it appropriately.
'rm' can be a lethal tool :-)
Well, maybe you were more lucky, I've had my share of troubles, and
I think the very concept stinks...
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD
) on
a blinding fast machine...
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe
In message pine.bsf.3.95.990818105716.12306a-100...@current1.whistle.com,
Julian Elischer writes:
On Wed, 18 Aug 1999, Poul-Henning Kamp wrote:
Matt doesn't represent the FreeBSD project, and even if he rewrites
the VFS subsystem so he can understand it, his rewrite would face
considerable
-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body
it some
day.
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers
) and
ask for another review after testing, before committing it.
Erez.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-fs in the body of the message
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run
In message pine.bsf.4.05.9908282023450.6392-100...@fw.wintelcom.net, Alfred P
erlstein writes:
On Fri, 27 Aug 1999, Poul-Henning Kamp wrote:
Uhm, have any of you actually ever looked at src/sys/kern/vnode_if.src ?
I can't really tell if you are commenting on the diffs I provided or
if you
have a sensible meaning ? (and for
all the other reasons which made us move src/contrib/sys to
src/sys/contrib)
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long time before progress goes
wins over ITAR in this case. :)
That's certainly an improvement in that particular battle :-)
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long time before progress goes too far
But, unfortunately, putting the console on a serial port creates
vulnerabilities when DDB is enabled. You are, essentially, creating
an unintentional backdoor into the system. Hence the problem.
ports/*/conserver is your friend!
--
Poul-Henning Kamp FreeBSD coreteam
to me. Perhaps ask p...@?
My only worry is that if people start to use this indiscriminantly to
store random collections of numbers, then it is far from the optimal
data structure for it.
Other than that: go for it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org
There are various hooks into this product which allows it to be
controlled by programs, I have not used those (yet?)
Recommended,
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
, (intmax_t)t, buf);
If some system introduces int512_t that may not be optimal, but
since printf is a pretty slow operation anyway, I doubt it will
hurt even half as much as the alternative.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD
In message 4debe469.5060...@links.org, Ben Laurie writes:
On 05/06/2011 19:21, Poul-Henning Kamp wrote:
In message 4debc741.1020...@links.org, Ben Laurie writes:
I have therefore resorted to printf'ing any typedefed integer type using
%jd and an explicit cast to (intmax_t):
printf
cast anything that that's typedef'ed to intmax_t and
move on.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
systems without bmake.
I am not sure if that is a concern we should care about.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
like hardware that you can reliably share
a disk between different mutually competitive operating systems.
Most unix-machines don't have a concept of what you call partitions,
and neither did BSD unix until 386BSD introduced it.
Until then: One OS, one disk(-pack|-drive).
--
Poul-Henning Kamp
, it is global rather than per-thread.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
also support in pthread for thread specific storage, which
should be your first choice.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
are implemented ? That
might allow you to.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
in md(4) disk, rm, remount r/o
rm -rf $jdir/*
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
UID/GID spaces.
Filesystems mounted or visible in multiple jails act as shared UID/GID
(sub-)spaces for those jails, but there is now way to avoid that, it's
a direct consequence of the sharing of the filesystems.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org
-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
freebsd-hackers@freebsd.org
In message alpine.bsf.2.00.1206031022360.55...@wojtek.tensor.gdynia.pl, Wojci
ech Puchar writes:
is it the same possible with USB?
i mean if i can make my laptop to simulate say USB CDROM.
No, the hardware is not up to it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p
In message alpine.bsf.2.00.1206130909310.73...@wojtek.tensor.gdynia.pl, Wojci
ech Puchar writes:
One of the major slowdowns is that we do all the device drivers
serially synchronously.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
I would like to point out that all other operating system which has
had this precise problem, have solved it by adding a bootfs partition
to hold the kernel+modules required to truly understand the disk-layout ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org
in their manual.
TL;DR: Which part of compatible doesn't Intel get ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
In message 201208102249.q7amn8gf066...@fire.js.berklix.net, Julian H. Stacey
writes:
I dont see 1.1.5:
It is not in our VCS because of the USL-BSD lawsuit.
You can find the bits here: http://phk.freebsd.dk/FreeBSD/
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org
-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
freebsd-hackers@freebsd.org
In message 20120816081336.gb27...@e-new.0x20.net, Lars Engels writes:
386BSD was even better, and I have a machine that boots it in less
than 15 seconds from power-on...
Me too, it's running Linux. ;-)
You should upgrade the OS then... :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus
In message blu0-smtp510b16745b704c714268e2d5...@phx.gbl, Lorenzo Cogotti writ
es:
Hi,
I was wondering about the possibility of FreeBSD to provide an official
supported graphical environment.
We already do: It's called X11 :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p
In message CAGsORuAnDs_E=l747+tp95nxjxdonnsqfvfco+xd2hjsj-u...@mail.gmail.com
, Zhihao Yuan writes:
On Mon, Sep 17, 2012 at 10:42 AM, Poul-Henning Kamp p...@phk.freebsd.dk
wrote:
In message blu0-smtp510b16745b704c714268e2d5...@phx.gbl, Lorenzo Cogotti
writ
es:
Hi,
I was wondering about
In message cagsorub4yd8rknlrwmctx16idohwjkd1rnyarb98nwn+pwv...@mail.gmail.com
, Zhihao Yuan writes:
On Mon, Sep 17, 2012 at 11:20 AM, Poul-Henning Kamp p...@freebsd.org wrote:
My suggest was 100% serious: Assume X11 _is_ the graphical
environment, pick a toolkit which is written to work
be nice to have as an option, but I would hate
to have to deal with it, when I squeeze FreeBSD into embedded systems
which have neither graphics outputs nor keyboard or mouse inputs.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD
you have at least 75% of the user population of FreeBSD agreeing
on which window manager we should offer as the default, we can talk
about this.
Until such a consensus exists, this discussion is just a waste of time.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org
about this.
so if 76% would decide that FreeBSD should have KDE included in system -
it means that it should?
Just to clarify: when I write offer by default I do not mean cram
down peoples throat.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC
In message cagh67wqty4krgwspa5jaht-4hqd4veykley-r3c6k9f5xaf...@mail.gmail.com
, Garrett Cooper writes:
No difference proven at 95.0% confidence
This is the important bit of information...
Thanks for the tip :)!
You're welcome :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p
not a good idea.
Given that /dev is really just a view into GEOMs namespace, one could
argue for GEOM:ada0p3 that that may be going overboard in sematic
correctness.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer
501 - 600 of 606 matches
Mail list logo
