and so
it cannot return a value.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"No matter how cynical I get, I just can't keep up."-- Nora Ephron
To Uns
In article <000101bec73c$e20e3660$[EMAIL PROTECTED]>,
Kelly Yancey <[EMAIL PROTECTED]> wrote:
>
> Also, in case it hasn't been notice already (I'm running -stable from May
> 18th), the mmap(2) manpage has a typo: it has "#include "
So what'
Brian F. Feldman wrote:
> On Tue, 6 Jul 1999, John Polstra wrote:
>
>> In article <[EMAIL PROTECTED]>,
>>
>> The application itself has to get involved if it wants to do async
>> name lookups, or async anything else, for that matter. Suppose you
>&
a
filter rule that sends back a reset:
add reset tcp from any to any auth setup in via etha16
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"No matter
Doug wrote:
> John Polstra wrote:
>>
>> Are you sure? If you simply don't run an identd, the queries will
>> get an instant connection refused error. That's even faster than
>> sending back a bogus response.
>
> Many daemons that request ident,
that
would make dd a lot more useful for the case Luigi brought up.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"No matter how cynical I get, I just can'
e ID with something like:
>
> ln -s "Warm-Fuzzy" .fakeid
Ick. Please, no more abuse of symbolic links! Once (malloc) was
enough.
Data is held in files, not in filenames.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra &a
and gdb). It might be better just
to install libiberty from one of those places.
Left as an exercise for the reader: Figure out how the two differ
and which one is "better". :-)
John
--
John Polstra [EMAIL PROTEC
Brian F. Feldman wrote:
> On Mon, 19 Jul 1999, John Polstra wrote:
>
>> Left as an exercise for the reader: Figure out how the two differ
>> and which one is "better". :-)
>
> I'd rather hurt myself severely.
Of course. That's a prerequisite fo
In article <[EMAIL PROTECTED]>,
Oscar Bonilla <[EMAIL PROTECTED]> wrote:
> Couldn't we do this with /etc/auth.conf?
The plan when PAM was brought in was to eliminate auth.conf. I don't
think we should be looking for new uses for it.
el without also rebuilding userland.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"No matter how cynical I get, I just can't keep up."-- Nora Ephron
T
ned to serve four separate but related functions.
We're only using the authentication function currently. For an
overview of PAM, see PAM(8) in the manual pages. There is also a spec
in "src/contrib/libpam/doc/specs/rfc86.0.txt".
John
---
John Polstra
to *each
other* is all ld cares about. That's been the traditional behavior
on every Unix system I've ever used that supported -L at all.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattl
ses of weird shared objects," you'd really better get
used to it. It was the wave of the future 10 years ago. It's not
going away. Dynamic linking provides flexibility and modularity that
you just can't get from static linking.
John
--
John Polstra
In article <[EMAIL PROTECTED]>,
Daniel C. Sobral <[EMAIL PROTECTED]> wrote:
>
> Do whatever you want: as a fs layer.
That would be good advice, if FS layers worked.
John
--
John Polstra [EMAIL PROTECTED]
John D.
will do
some day). In any case, your system has to be working to a certain
degree to be recovered, or else you have to use external media such as
the fixit disk.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.
m is setuid or setgid. I'm
not 100% sure from the original post whether that's the case or not.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"No matter how cyn
se for naming the sections that
contain linker sets. gensetdefs knows this convention, and so do the
macros in . The compiler, assembler, and linker
aren't aware of anything special about the names.
John
--
John Polstra [EMAIL PROTECTED]
J
, except I feel that when there are cases where we
can do useful things which rely on dynamic linking, we shouldn't let
static linking hold us back. Plenty of people disagree with me,
though.
John
---
John Polstra [EMAIL PRO
ional sense. They're monolithic whereas traditional archive
libraries are made up of separate object files which are subsetted by
the linker.
To really understand the issues I think it's necessary to read through
the dynamic linker sources and understand what it's doing. T
te, if you would have just _run_ the program with a umask of 2
then it would have worked too. It honors the umask setting unless
overridden in the supfile.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.
it seems.
No, longs are 64 bits on the Alpha. Ints are 32 bits, though.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"No matter how cynical I get, I just can'
be
consistent with that file's conventions.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"No matter how cynical I get, I just can't keep up."
Mike Pritchard wrote:
>>
>> Note, if you would have just _run_ the program with a umask of 2
>> then it would have worked too. It honors the umask setting unless
>> overridden in the supfile.
>
> Yes, but if I ever run cvsup by hand I wind up with cvsup
> going through my whole tree and resetti
head
> pointer)
When the list is empty, stqh_last points at stqh_first (which means it
must be a pointer to pointer). That way, STAILQ_INSERT_TAIL doesn't
have to treat an empty list as a special case.
John
--
John Polstra [EMAIL PROTE
)
says, "The file should not be locked on entry." But when stat calls
vn_stat, the vnode is locked. Which is correct -- or doesn't it
matter?
Thanks,
John
---
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.
Alfred Perlstein wrote:
> On Sun, 15 Aug 1999, John Polstra wrote:
>>
>> 1. I have a pointer to a vnode and I want to get the corresponding
>> dev_t and inode number. Is there a non-sleazy way to do that other
>> than calling vn_stat?
>
> use vn_todev from &
ion type. The new dynamic linker was
committed well before the binutils changes that required it. But
still it can bite people who aren't tracking -current very closely.
That's life in currentland.
John
--
John Polstra
he traditional distinction, but it's different on
FreeBSD/i386. SIGSEGV means you accessed memory that is unmapped.
SIGBUS means you accessed memory that is mapped, but protected
(unwritable and/or unreadable). To further confuse matters,
FreeBSD/alpha generates SIGSEGV for both
can't help it, then please just take a break
from the lists entirely for a couple of weeks. You're not doing a
thing to help our reputation.
Remember, the _individual_ you are replying to is not personally
responsible for the sum total
more. For CVSup mirrors, send the
request to [EMAIL PROTECTED] or [EMAIL PROTECTED]
John Polstra
CVSup Mirrormeister
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"No matte
e tree.
Er, global is part of the base system. :-)
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"No matter how cynical I get, I just can't keep up."
ularity to 1ms or less. Consider,
however, that some interfaces using programmed I/O may require
a considerable time to output packets. So, re- ducing the
granularity too much might actually cause ticks to be missed thus
reducing the accuracy of operation.
John
--
John Polstra
I put a few pictures from FreeBSDCon here for your enjoyment:
http://www.freebsd.org/~jdp/freebsdcon1999/
John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
please tell me, <[EMAIL PROTECTED]>. Writing to a list like
-hackers generally won't cut it. You need to let me personally know
as soon as possible.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.
interrupt handler.
I'm probably way off the mark, but I have to ask. Are you sure
you're not simply running out of mbufs? I noticed your maxusers is
only 32 and I didn't see an options line to raise NMBCLUSTERS.
John
--
John Polstra
ts it? I've never heard of
that one.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"No matter how cynical I get, I just can't keep up."-- Nora Ep
the stack and changes back to the previous
section.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"No matter how cynical I get, I just can't keep up."
vfs.aio.max_aio_per_proc: 32
vfs.aio.max_aio_queue_per_proc: 256
vfs.aio.max_aio_procs: 32
vfs.aio.max_aio_queue: 1024
vfs.aio.max_buf_aio: 16
And worst of all:
#define AIO_LISTIO_MAX 16
John
--
John Polstra [EMAIL PROTECTED]
John
ound for the 3.x branch??
Yes, the underscores are gone permanently because we switched from
a.out to ELF as the object file format.
You can test for it at compile time with #ifdef __ELF__.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra &
e assembler just
> ignores the @ character.
I think it would be much better to remove all of the platform-specific
asm statements from gensetdefs and put them into a header
. Gensetdefs would then emit an include of that
header to get the needed definitions.
This isn't very high on my personal p
spute that point, but it is worth mentioning that POSIX
specifically guarantees that st_dev and st_ino "taken together
uniquely identify the file within the system." So it is OK for
applications to rely on that.
John
--
John Polstra [EMAIL PROTEC
Garance A Drosihn wrote:
> At 10:40 AM -0800 11/18/99, John Polstra wrote:
>>I don't dispute that point, but it is worth mentioning that POSIX
>>specifically guarantees that st_dev and st_ino "taken together
>>uniquely identify the file within the system." So
enough so that this
approach isn't necessary.
For CVSup I plan to experiment with using a small farm of disk I/O
subprocesses (processes, not threads), communicating with the master
process via shared memory and/or pipes. Without trying it, I can't
on in Unix between "slow"
I/O devices and "fast" ones. Disks are "fast" ones, and the process
always blocks until the full I/O has completed.
This is not some kind of brokenness particular to FreeBSD; it's the
way Unix has always behaved.
John
--
John Polstr
D
(www.isc.org) and it might be distributed separately too -- I forget.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"No matter how cynical I get, I just can't keep up
at Jan 1 00:00:02 CET 1900
> Sat Jan 1 00:00:03 CET 1900
>
> In short: yes it works.
>
> Happy New Millenium to all of you!
Huh? That doesn't look so good to me!
(Just kidding, just kidding. ;-)
John
--
John Polstra
rks_, and well. But
> it tastes strongly of hack.]
I think the approach is reasonable, but it shouldn't go into the
pthreads library. It's too heavyweight for that -- too much machinery
when your average client just wants to read from a file.
Pthreads will eventually handle disk I/O b
tion of LD_PRELOAD and Solaris's: on Solaris the filenames
> listed in LD_PRELOAD are space-separated, but on FreeBSD they are
> colon or semicolon separated.
That could be a bug. You're probably the first person on earth to
have more than one library in LD_PRELOAD. :-) What does Li
In article <[EMAIL PROTECTED]>,
Tony Finch <[EMAIL PROTECTED]> wrote:
> John Polstra <[EMAIL PROTECTED]> wrote:
> >The right way to do it on FreeBSD is like this:
> >gcc -fpic -c *.c
> >gcc -shared -o libshim.so *.o
>
> That works fine, than
In article <[EMAIL PROTECTED]>,
Chad David <[EMAIL PROTECTED]> wrote:
>
> Since the ~Jan 25 I have been getting an error while
> running any java programs on 3.4-stable. I cvsup'd,and
> ran a make world this afternoon and it still fails. It doesn't
> always hit... about 50% of the time.
>
> T
In article <[EMAIL PROTECTED]>,
Chad David <[EMAIL PROTECTED]> wrote:
>
> Yes this fixed it. Thanks.
Thanks for testing it. I have merged the fix into -stable now.
John
--
John Polstra [EMAIL PROTECTED]
John D.
ross-compiler, not C.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa
To Unsubscrib
c-linker /usr/libexec/ld-elf.so.1
-L/usr/libexec/elf -L/usr/libexec -L/usr/lib /tmp/ccWvs216.o
/usr/libexec/elf/ld: warning: cannot find entry symbol _start; defaulting to 08048074
/tmp/ccWvs216.o: In function `main':
/tmp/ccWvs216.o(.text+0xf): undefined reference to `printf'
John
nostdlib causes the
crt* files and libc to be omitted from the link, then it works.
Making it do something useful is _your_ problem, not ours. :-) We
don't recommend or support linking that way.
John
--
John Polstra [EMAIL PROTECTED]
John D.
t.
I agree that this is not the time to change it. But in the long run,
if the ports framework is misusing /bin/sh then the framework needs to
be fixed. We shouldn't let bugs there influence what we do with the
shell.
John
--
John Polstra [EM
the algorithm itself is not patented. Is that not the case?
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"Disappointment is a good sign of basic intelligence."
In article <[EMAIL PROTECTED]>,
Bill Fenner <[EMAIL PROTECTED]> wrote:
>
> I've got this program in my head that takes a CVS tree and turns it
> into a branch ofanother CVS tree (e.g. FreeBSD rev 1.7 turns into
> rev 1.1.1.7) but it's never managed to make it out of my head, so
> it must be hard
In article <[EMAIL PROTECTED]>,
Doug Barton <[EMAIL PROTECTED]> wrote:
>
> Given that Bash in both standard and POSIX mode complains about 'for i
> in ; do echo $i; done', I would say that it's not POSIX compatible. What
> could/does depend on this behavior "working?"
It works for the rea
Doug Barton wrote:
>
> Agreed on all counts. By "this behavior" I was referring to the
> example.
Yep -- I was agreeing with you. :-)
John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
tio of called functions to total functions.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"Disappointment is a good sign of basic intelligence." -- Chögyam Trungp
th a different filename
for script, of course). Send the output to me and I'll try to
figure out what's happening.
After you're done, you should restore your original (non-debugging)
rtld. It's more efficient and also probably more secure.
John
--
send-pr and tell me the
PR number? That way I won't forget about it. If you'll include
some patches in the PR it will help a lot, too. :-)
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.S
(),
for example, but the ABI standard says nothing about how that is
implemented lower down.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc.Seattle, Washington USA
"Disappointment is a good sign of
suppose?
Right.
> Sounds like trying to emulate "SVR4" in itself isn't sufficient. We
> can still call the kld svr4.ko, but it's really doing SCO/SolarisX86
> syscall emulation.
Yep.
John
--
John Polstra [EMAI
fs to ensure that
the compiler is GCC and its version is late enough to support it.
See the other examples in . It would be used like
this:
extern void *isp_static_fw_vector(void) __weak_definition;
#pragma weak is bad because you can't put #pragmas into macros.
John
--
John Polstra
201 - 266 of 266 matches
Mail list logo