' entry in their struct cdevsw.
--
Peter Jeremy
pgpin6CJBTge7.pgp
Description: PGP signature
scratch. In the 'FreeBSD Disklabel Editor' window, scroll
down to your partitions and either 'D'elete them all and re-create
using 'A'uto or toggle the 'N'ewfs flag and set the 'M'ount point.
--
Peter Jeremy
pgpc3RS1KM5eP.pgp
Description: PGP signature
the #line directives, compiling it and posting the exact gcc error and
source context.
It may be a gcc bug, it may be a HLA bug or it could be an interaction
between the FreeBSD headers and HLA.
--
Peter Jeremy
pgpp9mRIaGDPu.pgp
Description: PGP signature
or unexpected warnings. And, since
flex is used several times during a buildworld, any generic problems
would show up very quickly.
--
Peter Jeremy
pgpgHVxdRwirz.pgp
Description: PGP signature
to avoid the need to
allocate large contiguous memory chunks. iedowse@ had mostly finished
implementing this in mid May.
--
Peter Jeremy
pgpUwMhO0qV2o.pgp
Description: PGP signature
when it's in use).
--
Peter Jeremy
pgp0xtUxn80DA.pgp
Description: PGP signature
was looking for a way to write a small wrapper program
that disables network access and then exec()'s a given
program.
For dynamic executables, you could LD_PRELOAD a .so that replaces
all the socket-related syscalls.
--
Peter Jeremy
pgpm3GjTuUwBQ.pgp
Description: PGP signature
doubt either are true.
--
Peter Jeremy
pgpfFCcuCnb0C.pgp
Description: PGP signature
a system call - which is comparatively
expensive.
--
Peter Jeremy
pgpE8zWwKy0Fz.pgp
Description: PGP signature
To resurrect a fairly old thread...
On Mon, 2006-Mar-27 11:23:42 +1030, Greg 'groggy' Lehey wrote:
On Sunday, 26 March 2006 at 19:17:19 +1100, Peter Jeremy wrote:
My work system runs separate X servers on two heads (rather than
ximerama) and I have problems with windows occasionally refusing
.
--
Peter Jeremy
pgpeoYIvy0spc.pgp
Description: PGP signature
and (at first) a generic kernel?
I suspect plip has outlived its usefulness.
--
Peter Jeremy
pgpC6TooVlPWm.pgp
Description: PGP signature
statistics gathering and see if anything anomolous is occurring.
--
Peter Jeremy
pgppY9q1JHybY.pgp
Description: PGP signature
an issue for accesses to userland memory, where
it is solved by fetch(9) and store(9). If you need to deal with KVM
addresses that may be unmapped, then all I can suggest is looking at
the implementations of the above functions.
--
Peter Jeremy
pgprjaY0q3LGm.pgp
Description: PGP signature
market but is not true in the
embedded market and only marginally true for laptops.
--
Peter Jeremy
pgpqSDruA6YGB.pgp
Description: PGP signature
than this for optimal efficiency.
--
Peter Jeremy
pgpamKbTi5BUJ.pgp
Description: PGP signature
it sparse makes sense, if you will be
updating it, you will get better performance by making it non-sparse.
--
Peter Jeremy
pgpQeKoTW1HxK.pgp
Description: PGP signature
of interest
was a result of Compaq killing the Alpha. I suspect that a HP 9000
port would be starting from a much smaller base.
--
Peter Jeremy
pgpIIZBCpQODq.pgp
Description: PGP signature
that
does:
#define MAXNAMLEN 1024
...
#include sys/dirent.h
...
charmybuffer[MAXNAMLEN];
--
Peter Jeremy
pgp9G71sqx9ME.pgp
Description: PGP signature
) by replacing the getcwd() with the
first path and adding enough '../' to the second path to reach a
common directory (or root) from the first path.
--
Peter Jeremy
pgp9uQcLzup2U.pgp
Description: PGP signature
.
This sounds like flaky hardware. Try checking cooling, PSU, RAM,
cabling socketing etc. Run memtest86 or similar and try swapping
components.
--
Peter Jeremy
pgpDkIzeysmng.pgp
Description: PGP signature
amd64 system, with an up-to-date ports tree, I
suggest you take it up on freebsd-openoffice.
--
Peter Jeremy
pgpKnyCJmNFMg.pgp
Description: PGP signature
address for each alert. Sendmail is
rejecting the messages based on the From field.
Have you tried:
FEATURE(`accept_unresolvable_domains')
--
Peter Jeremy
pgp9vYyinaGYO.pgp
Description: PGP signature
2006SMTP response503 5.0.0 Need MAIL command
I can't reproduce this with sendmail 8.13 (though I'm not sure I'm
correctly replicating your environment). I suggest you either UTSL or
ask on a sendmail list.
--
Peter Jeremy
pgp5PXKLKnFmh.pgp
Description: PGP signature
to the file (and her only way of uniquely identifying it) whilst
leaving the remaining link to the file in Mallory's control.
--
Peter Jeremy
pgpN2P2SFT5ro.pgp
Description: PGP signature
On Mon, 2006-Oct-30 19:38:49 +1100, Peter Jeremy wrote:
the user is unaware that there are multiple links. I don't think
that just unlinking the file and issuing a warning is a good solution
because it's then virtually impossible to locate the other copy(s)
of the file, which remains viewable.
I
destroyed the content of a file they still wanted when
deleting an unwanted link to the file.
IMHO, rm.1 should explicitly state that rm -fP on a multi-linked
file will destry the file contents as seen via the remaining link(s).
This probably belongs in the NOTE section.
--
Peter Jeremy
condition and they are being cleansed as a low-priority
task by at least one committer.
--
Peter Jeremy
pgp3JNiVFPB1y.pgp
Description: PGP signature
-proof. See getprotoent(3) for the
correct way to read /etc/protocols.
--
Peter Jeremy
pgp2viCUWiyY6.pgp
Description: PGP signature
). Don't unnecessarily use [u]int64_t as it is
comparatively inefficient on 32-bit architectures.
I know Oracle (at least) avoids the problem on Tru64 by using
multiple SHM segments to allow SGA exceeding 2GB.
--
Peter Jeremy
pgpSILO7IEYU0.pgp
Description: PGP signature
the
number of groups some one is in is to call getgroups(0).
At least in RELENG_6, getgroups(2) states that passing the first
argument as 0 will return the number of groups: getgroups(0, NULL);
This matches the code in the kernel.
--
Peter Jeremy
pgpkJtHiEMmeM.pgp
Description: PGP signature
that each SWAPMETA object manages 16 pages.
And yes,
that means you are setting aside a little over 146 MB of wired, physical
RAM just to hold metadata for your swap. :)
Given a system with 16GB RAM, this probably isn't a serious issue.
--
Peter Jeremy
pgpuCmNLuoT1W.pgp
Description: PGP
your kernel driver.
- Use kqueue(), signal() or read() a token to indicate when some
amount of data is available.
--
Peter Jeremy
pgpT7s0FgYrbQ.pgp
Description: PGP signature
the 'location'
of the journal would be an inode number. The journal code would
need to verify that the given inode was internally consistent before
it accessed the data.
--
Peter Jeremy
pgpvJW05rdUBt.pgp
Description: PGP signature
smbios.system.uuid
9F345F4F-BEFC-D431-1340-61235A56DEF9
--
Peter Jeremy
pgpYtgc8mneB0.pgp
Description: PGP signature
together a patch to address this and submitting it as a PR
(this means addressing all references to shm_segsz in the base
system, not just sys/shm.h).
--
Peter Jeremy
pgp8hjEZLqbWd.pgp
Description: PGP signature
shmid_ds have
already been converted, though the ones in struct ipc_perm are
obsolete. At a quick glance, everything else is up to date.
http://www.opengroup.org/onlinepubs/009695399/ is a useful reference
in this area.
--
Peter Jeremy
pgpQdwA5x7yOc.pgp
Description: PGP signature
populated or don't report it at all.
--
Peter Jeremy
pgpmFjOmTnU2t.pgp
Description: PGP signature
your motherboard vendor decided to save a few deci-
cents by not bothering to connect up all the available interrupt
inputs and just share one. This isn't FreeBSD - it's the copper
tracks on your motherboard.
--
Peter Jeremy
pgpc7wd5PSWnP.pgp
Description: PGP signature
assigning 2 devices to the same irq to begin with?
FreeBSD does support shared interrupts on busses that support them
and is assigning interrupts based on information from the hardware.
--
Peter Jeremy
pgpr1eBARhAGz.pgp
Description: PGP signature
be close enough to count, or would it have to be C/C++?
Perl was removed in 5.x. Your options are shell, awk and C/C++.
--
Peter Jeremy
pgpgn9xqL6jDU.pgp
Description: PGP signature
support in the kernel (I ran grep -w cos on the
-CURRENT source tree, which turned nothing up).
Does anyone have an idea on how to do this?
Floating point is not allowed in the kernel. I suggest you look up
cordic in google. This is an efficient way to do fixed-point
trigonometry.
--
Peter
in
/usr/sys/dev/sio/sio.c if you want to go down this path).
With a port speed of 2400, I do not drop characters.
The FIFO is not enabled at speeds at or below 4800bps.
--
Peter Jeremy
pgp6xD58xJe5F.pgp
Description: PGP signature
-0800, Daniel Rudy [EMAIL PROTECTED] wrote:
overflows. Is there a way for force the driver to attach as fast since
it's not doing it?
sio tries to attach as fast and falls back to the default if that fails.
It should only fail if something else is already registered on that IRQ.
--
Peter Jeremy
reading it.
I believe it would be worthwhile creating a todo item to investigate
this more thoroughly.
--
Peter Jeremy
pgpK6PD6QiXC4.pgp
Description: PGP signature
serial driver and I believe it will supplant
sio(4) in time but I believe there are still some kludges that require
sio.
I'm glad you resolved your problems.
--
Peter Jeremy
pgpzJIopmzRS2.pgp
Description: PGP signature
On 2007-Feb-20 02:47:00 -0500, Zaphod Beeblebrox [EMAIL PROTECTED] wrote:
On 2/17/07, Peter Jeremy [EMAIL PROTECTED] wrote:
I've tried modelling a unified cache along the NetBSD line and there
appears to be a massive improvement in cache performance. It's unclear
how much of an improvement
. Have you tried increasing the number of
threads to see if there's any nasty knee further to the right? Also,
is there any chance of repeating this testing on one of the big Suns
(or a T2000) to see how this scales to lots of cores?
--
Peter Jeremy
pgpiC3VLBGcaT.pgp
Description: PGP signature
sequence
far more verbose.
--
Peter Jeremy
pgpNwLl9rfgvj.pgp
Description: PGP signature
kernel interfaces are defined in the section 9 man pages.
--
Peter Jeremy
pgpvLYXBRJztD.pgp
Description: PGP signature
haven't tried setting breakpoints but other kgdb functions work with KLDs.
--
Peter Jeremy
pgpwMNcpBaKp8.pgp
Description: PGP signature
foo.o -lc
This won't work because libc in intended to work in an environment
hosted on FreeBSD and needs infrastructure that is part of crt*.o
Have a look in (eg) /usr/src/sys/boot/i386 for code that is intended
to run without the kernel.
--
Peter Jeremy
pgpLbs2ZsAt0c.pgp
Description: PGP
at 16,000RPM).
--
Peter Jeremy
pgpYnogAgTv7J.pgp
Description: PGP signature
a good idea. tar
has other disadvantages (particularly the lack of random access) as a
ports archive format. ZIP was suggested as an alternative. I also
question the combination of sane, easy to parse and XML.
--
Peter Jeremy
pgpCiBmSG1qTp.pgp
Description: PGP signature
(and something
tar does anyway - you are just delaying it). This has the added
benefit that nothing else can use the package until it's completely
unpacked.
--
Peter Jeremy
pgpjQ4s6eMByT.pgp
Description: PGP signature
is that since
BDB isn't self documenting, a flat file may not be any use.
--
Peter Jeremy
pgp4DdQEuksZO.pgp
Description: PGP signature
tool for the job (assuming one can prove what is the best tool,
considering power, familiarity, etc.).
Demonstrate a better tool.
--
Peter Jeremy
pgpy0PFUTL4bF.pgp
Description: PGP signature
On 2007-May-14 09:36:52 -0400, Mike Meyer [EMAIL PROTECTED] wrote:
[Linux package systems]
As far as I know, none of them handle updates from source at all. In
fact, dealing with sources seems to be a noticable weakness for them.
This pretty much rules them out then.
--
Peter Jeremy
this is practical. Both package names and
port dependencies depend on the options that are selected as
well as what other ports are already installed. A centralised
ports server is not going to have access to this information.
--
Peter Jeremy
pgpfPtzrTbSlc.pgp
Description: PGP signature
does not really need or use the sort of
implicit dependency tracking and target transformations that make
excels at. Of course, any alternative to make needs to provide a
language for defining dependencies that is equally powerful and easy
to use.
--
Peter Jeremy
pgpPFzz4p1Mss.pgp
Description
=... and similar 'macro'-style constructs.
--
Peter Jeremy
pgpCyJ5Uh8Myq.pgp
Description: PGP signature
system 98% cpu 41.975 total
--
Peter Jeremy
pgpUpeOoZw3YV.pgp
Description: PGP signature
the disk entirely. Bad blocks have a
tendency to spread too...
Definitely - once the number of soft errors starts increasing, it's
time to replace the disk.
--
Peter Jeremy
pgpnF1TqmMnnw.pgp
Description: PGP signature
aren't running
UFS without softupdates).
I'll definitely look into strace'ing (not really a big fan of truss(1)
yet) the operation though, just to see how fast or slow stuff is.
ktrace can also provide timings.
--
Peter Jeremy
pgp0x3mMEp4nG.pgp
Description: PGP signature
On 2007-Jun-18 00:39:44 -0700, Garrett Cooper [EMAIL PROTECTED] wrote:
However, I was able to get ktrace output. The only problem is that ktrace(1)
apparently outputs only in binary, instead of plaintext output. Can I
convert it to plaintext somehow and process it?
kdump(1)
--
Peter Jeremy
the output from multiple files so this
patch gives you the ability to profile multiple executions of a single
executable. You will still need to glue together the profiling
results from each executable.
--
Peter Jeremy
pgpvYf1SIv8wB.pgp
Description: PGP signature
of (eg) rtld.
--
Peter Jeremy
pgpXQNdgsDDXY.pgp
Description: PGP signature
to be running a 9 month old -stable - have you considered
updating to either 6.2 or a more recent -stable?
--
Peter Jeremy
pgpsgXJnIDnMJ.pgp
Description: PGP signature
other benefit?
--
Peter Jeremy
pgphsTYS4NCig.pgp
Description: PGP signature
) == -1)
And the buffer argument should be char[], not struct kinfo_proc.
--
Peter Jeremy
pgp5pk4M5uA63.pgp
Description: PGP signature
at amd64 headers whilst the -m32
compiler needs i386 headers in many cases. There's a non-trivial
amount of work needed to actually get cross-building working. I
suggest you look throught the FreeBSD-amd64 archives.
--
Peter Jeremy
pgp0amIJul1Bq.pgp
Description: PGP signature
on amd64 will point to /libexec/ld-elf32.so.1, rather
than /libexec/ld-elf.so.1) so the result won't execute on a
FreeBSD/i386 box - but I don't see that as a problem with ld, rather
the configuration.
--
Peter Jeremy
pgplaH2VDcPfe.pgp
Description: PGP signature
a defined period.
--
Peter Jeremy
pgpzdutJbUl9D.pgp
Description: PGP signature
On 2007-Aug-22 12:13:48 +0400, sam [EMAIL PROTECTED] wrote:
Minimum system requirements:
...
- Kernel 2.6, configured for 1000Hz tick and other low latency settings
FreeBSD currently only emulates kernel 2.4. Kernel 2.6 is a SoC project.
--
Peter Jeremy
pgp900LFNqMKV.pgp
Description: PGP
/elf_common.h and rebuild). You would need to use brandelf to
patch executables built on other FreeBSD systems.
There's a set of patches implementing mac_chkexec floating around
see (eg) http://lists.virus.org/freebsd-security-0503/msg00042.html
This might do what you want.
--
Peter Jeremy
server.
--
Peter Jeremy
pgp8eROhMga6d.pgp
Description: PGP signature
to be calculated and the INDEX-6 file to be
built properly.
In which case, you should be able to cd /usr/ports make index
--
Peter Jeremy
pgpUHKyAI7zJb.pgp
Description: PGP signature
it doesn't make sense to read
more than you need, there still appears to be plenty of scope to
combine writes.
Between these two items, I would expect potential performance gains
of at least 20:1.
Note that I'm not suggesting that either of these items is trivial.
--
Peter Jeremy
On Sun, Oct 21, 2007 at 08:28:19PM -0700, David E. Thiel wrote:
Sounds fine to me - I'll take a closer look at this. I'd still like
to see the root CA certs merged into base so libfetch can be fixed.
So would I.
Does anyone object to just using the ones currently provided by the
ca_root_nss
On Thu, Nov 01, 2007 at 10:40:04AM +1100, James Healy wrote:
The remaining op is not easily converted to fixed point math, and we're
wondering what impact a single flop on the receipt of each ACK will
have. We don't have a strong understanding of the amount of overhead
involved in executing a flop
On Thu, Nov 01, 2007 at 01:41:10PM -0400, Michael B Allen wrote:
I need semtimedop(2). I'm thinking I can just do a semop with a SIGINT maybe.
I presume you mean SIGALRM.
Can someone suggest a good method for setting up a timer to deliver
the signal? What sort of timers does FreeBSD offer?
character output per time slice, or
something like that?
Maybe, though I don't understand why this would occur. If you time(1)
your program, what are the real/user/system time breakdown? That will
help clarify where the slowdown is located. Have you tried the dd(1)
command suggested.
--
Peter Jeremy
your code or time(1)d it as
suggested?
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an RFC2821-compliant MTA.
pgptNezorRMJ0.pgp
Description: PGP signature
. This is an inherent part of the
Unix approach to files.
You could look at ports/sysutils/lsof or fstat(1).
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an RFC2821-compliant MTA.
pgpQPdPjDBoxX.pgp
Description: PGP signature
, but I don't know where, or how. Any tips would be very welcome.
I presume that the exact rate is not critical. My suggestion would be
to create a kernel thread (see kthread(9)) that uses a callout (see
timeout(9)) to wake it every tick.
--
Peter Jeremy
Please excuse any delays as the result
/freebsd-current/2006-April/062261.html
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgp5VSsD43uRw.pgp
Description: PGP signature
Wes Peters [EMAIL PROTECTED] wrote:
Time for a main() man page? Where would it go? Section 2, 3, or 9?
Hmm...
I'd support that. I believe the page needs to be tied to exec (ala
setjmp/longjmp), which means it either ties to execve(2) or exec*(3).
Note that execve(2) already includes a
Bill Fumerola [EMAIL PROTECTED] wrote:
Unless there is strong feelings against it, I'd like to commit the smb
patches (as seen on www.samba.org) and ipsec/ike patches (recently mailed
to the tcpdump mailing list and [EMAIL PROTECTED]) to tcpdump(1).
I also think it's a good idea. Judging from
Robert Watson [EMAIL PROTECTED] wrote:
- How can I choose a guaranteed free TCP port?
www.iana.org
IANA -- Internat Assigned Numbers Authority
This is fine in theory, but doesn't work quite as well in practice.
I spent several years (unsuccessfully) trying to convince a sister
company that
Warner Losh [EMAIL PROTECTED] wrote:
What purpose is served by the twisty maze of ifdefs in telnetd?
Probably for portability.
I'd
like to unifdef many of them. I'm trying to track down a bug and the
twisty maze makes it very hard to follow. Comments?
There's nothing stopping you unifdefing
Dag-Erling Smorgrav [EMAIL PROTECTED] wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
specifically how you say you increment it, then decrement it,
if you have multiple handlers where one can interupt another
you can have the counter get jumbled.
Not if increment / decrement is atomic.
John-Mark Gurney [EMAIL PROTECTED] wrote:
and even then, I don't believe in filling sockaddr_in w/ bzero, I
believe in using getsockaddr on it so that you actually get all the
fields filled out properly...
% man getsockaddr
No manual entry for getsockaddr
%
The only getsockaddr() I can find in
It's fairly common, when spawning new processes, to want to make sure
all unwanted FDs are closed. Currently, the options for doing this are:
1) Use fcntl(fd, F_SETFD, FD_CLOEXEC) to set the close-on-exec flag
when the file is opened/cloned. This may not be practical if the
FD must
Ville-Pertti Keinonen [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Peter Jeremy) writes:
I can't believe these figures.
Based on the figures below, maybe I was overly hasty in this statement.
The changes between 2.x and 3.x magic files have far more impact than
I would have expected.
What
Ville-Pertti Keinonen [EMAIL PROTECTED] wrote:
Note that there are race conditions in your code.
It was intended as a first cut, rather than tested code. Note that
most of it was lifted from the code for select() and fdcloseexec().
If it ever gets
committed (I don't think it's particularly
I wrote:
Looking at ktrace with MALLOC_OPTIONS=U, it does do a lot of
realloc()ing (once for every 20 active lines in .../magic) and sbrk()s
to a maximum size of ~390KB - not really significant.
and in a later message:
When I profile file in a slow system (like a 386 or 486), there is an
"John W. DeBoskey" [EMAIL PROTECTED] wrote:
I like this approach. I have a number of often spawned daemon
processes that could benefit from this.
I don't suppose that you have any statistics showing that the
for (i = 3; i getdtablesize(); i++) close(i);
approach would be too slow?
Doug [EMAIL PROTECTED] wrote:
The more complete the feature set, the better
off we are for my money.
Someone offering money? Quick, who's got the donations hat... :-)
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Jordan recently mentioned "Wonderful World of Linux 2.4 (Second
Edition)" http://features.linuxtoday.com/stories/8191.html.
This article makes the statement "Linux is still the only operating
system completely compatible with the IPv4 specification", which is
further expanded in a followup
Assar Westerlund [EMAIL PROTECTED] wrote:
As an enhancement, the strtol() check should verify that the passed
service number is completely numeric:
--- inetd.c.orig Mon Aug 2 22:35:28 1999
+++ inetd.c Mon Aug 2 22:41:52 1999
@@ -830,34 +830,50 @@
continue;
1 - 100 of 502 matches
Mail list logo