In message <[EMAIL PROTECTED]> Sheldon Hearn writes:
: If you do end up messing with inetd's existing ident service, please
: make sure that the default behaviour remains the same and that the
: operator must do something to enable an ident service that reports more
: than just "UNKNOWN-ERROR".
Y
: > I don't see a point to that.
Some ftpd and sendmail servers make the queries. When I have my fake
identd in place, they go much faster... :-)
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <[EMAIL PROTECTED]> Ben Rosengart
writes:
: I used to run a public shell machine, and one of my users cracked
: someone else's site. Identd made it much easier to figure out who the
: problem user was.
Unfortunately, I've seen the dark side of identd which makes me *HATE*
it with a p
In message <[EMAIL PROTECTED]> Chris Costello writes:
:The whole point of ident was -- and still is -- to
: authenticate or verify who created a specific TCP connection.
NO. The IDENT protocol was never intended to authenticate who was on
the other end. *NEVER*. People ABUSED it as such, b
In message <[EMAIL PROTECTED]> Bill Paul writes:
: - Why is the vpp voltage alwats left at 0?
I think that is what the standard suggested. Since I've not yet
recieved the standard, I can't look it up.
: - Is it safe for me to change the code so that it's set to 5 volts?
: Obviously I'm going
In message <[EMAIL PROTECTED]> Chris Costello writes:
:I was only specifying what I gathered from the RFC. What was
: ident actually intended for, then?
It was at best a way to track back malicious connections for log files
after the fact. Only after the initial standard came out did people
In message <[EMAIL PROTECTED]> "Brian F.
Feldman" writes:
: How in the world could my inetd ident service be exploited? I just fixed
: the only problematic feature, fake id, to make it not read anything but a
: regular file and not let you try to use someone else's name. I can't see
: any way th
In message <[EMAIL PROTECTED]> Mark Murray writes:
: The low-voltage cards are keyed so you cannot plug them into 5v
: slots; perhaps the dual-voltage slots have protective circuitry
: that co-operates with this?
Yes. The dual voltage cards are supposed to bring certain pins high
and/or low to d
In message <[EMAIL PROTECTED]> "Brian F.
Feldman" writes:
: Good idea. I'll have it check to see that it's a regular file.
Make sure that you do this with the stat, open, fstat interlocking so
that there isn't a race here.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscrib
In message <[EMAIL PROTECTED]> John Polstra writes:
: Really?? Even though their connect() call failed? Ick! I know
: sendmail doesn't behave that way. I'll take your word about the IRC
: daemons -- I don't know anything about them.
Yes. At least that's what I've observed. However, I believ
In message <[EMAIL PROTECTED]> Doug writes:
: Sure, but I don't think that compromised boxes are the norm, unless I'm
: missing something here.
The response doesn't have to come from the box being asked the
question in order for it to be accepted. If you can load the box
being asked highl
In message <[EMAIL PROTECTED]> "Brian F.
Feldman" writes:
: I have this fixed in my latest code (on freefall of course). I did not
: use an original stat because that's pointless, as it adds another race
: condition. The only downside to my approach is that if it's a symlink
: to a dev, the dev c
In message <[EMAIL PROTECTED]> Bill Paul writes:
: slt->pwr.vcc = 50;
: slt->pwr.vpp = 0;
to
: slt->pwr.vcc = 50;
: slt->pwr.vpp = 50;
OK. I've read more of the MindShare book. I believe this is a good
change because Vpp is supposed to be connected to Vcc (that is,
In message <[EMAIL PROTECTED]> Jon Ribbens writes:
: No, if the *process* hits its *administrative* resource limits.
: i.e. setrlimit(2).
That should (and I believe does) make malloc fail.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of t
In message <[EMAIL PROTECTED]> Wes Peters writes:
: Didn't my message from yesterday make it to the list? On card insert,
: you're supposed to read the voltage requirements for Vcc and apply *that*
: voltage to Vcc, Vpp1, and Vpp2.
If it did, I missed it...
Warner
To Unsubscribe: send mail t
In message
<[EMAIL PROTECTED]> "Brian
F. Feldman" writes:
: Ahh, I misunderstood you. In _this_ case you just proposed, the stat is
: really pointless. What good would it do?
It would let you know if you should even try to open the file... But
that doesn't solve the race. The fstat tells you if
In message <[EMAIL PROTECTED]> Wes Peters writes:
: >From this, I'd say the card inserted event should read the Vcc wanted
: value (from the Socket Present State Register?) and apply THAT voltage
: to Vcc, Vpp1, and Vpp2, rather than just applying 5.0 volts. You might
: seriously damage any 3.3v
In message <[EMAIL PROTECTED]> Wes Peters writes:
: It shouldn't be all that hard to read the register and set the voltages
: appropriately. Table 5-1 on p. 54 has the PC Card register values for
: CVS[2:1] and what they mean.
Agreed...
: Quatech or Socket Communications? I don't see one right
In message <[EMAIL PROTECTED]> "Jordan K. Hubbard" writes:
: Paging Terry Lambert, Terry Lambert - do you read me? It's time for
: your annual rant on the topic of memory overcommit. :-)
I thought it was time for his annual rant about how the current
FreeBSD development model is going to have pr
In message <[EMAIL PROTECTED]>
The Hermit Hacker writes:
: I need to build a keyboard map such that:
:
: F1 == ESC OP
: F2 == ESC OQ
: Shift-F1 == ESC [31~
: Shift-F2 == ESC [32~
Why not do this with Xterm translations? Generally speaking xmodmap
and friends are poor choices
In message <[EMAIL PROTECTED]> "David O'Brien" writes:
: Since no one has repsonded to this querry, I will be un-staticizing these
: so they will be available to drivers.
No. Please don't. This is the first I've seen this. There will be
another cis reading interface as part of the newbusificat
In message <[EMAIL PROTECTED]> Ade Lovett writes:
: This is going to be for both -current and MFC'd back into -stable, yes?
The interface for doing this I'll be merging back into -stable.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of th
In message <[EMAIL PROTECTED]> Scott Mitchell writes:
: Ugh. In that case, can someone back out Poul-Henning's changes to the
: if_xe.c in the -STABLE tree? That's (I hope) the only thing stopping it
: from working. At least that way only my code will be bogus :-) Believe
: me, I know it's ugl
In message <[EMAIL PROTECTED]> Wayne Cuddy
writes:
: Even though I am developing on FBSD is there a "more portable" way to do this?
No. Well, not short of execing.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <[EMAIL PROTECTED]> Mike Smith writes:
: if (strlen(buf) >= sizeof(buf))
: return(error);
This can never be true with the strl functions They don't run off
the end, so strlen(buf) is always going to be < sizeof(buf) since it
doesn't include the traling null.
W
In message <[EMAIL PROTECTED]> Mike Smith writes:
: What's really stupid is that most of the time you're trying to use
: these functions to fix code that looks like:
: strcpy(buf, str1);
: strcat(buf, str2);
: strcat(buf, str3);
: without overflowing buf. This is dumb! Use asp
In message <[EMAIL PROTECTED]> Mike Smith writes:
: Ugh. Take the first example in the paper; it rewrites as
:
: len = asprintf(&path, "%s/.foorc");
:
: as opposed to
:
: strlcat(path, homedir, sizeof(path));
: strlcat(path, "/", sizeof(path));
: strlcat(path, ".foord",
In message <19990715194203.A54146@mad> Tim Vanderhoek writes:
: Looking at OpenBSD's actual definition of strlcat() which returns the
: number of chars that would have been in the final string is
: potentially non-useful, but not really too terrible.
No. It is useful. If you look at the ret
In message <[EMAIL PROTECTED]> Mike Smith writes:
: I still think this is the wrong way to deal with the problem. 8)
We mildly disagree here. The strl* functions are the end all, be all
of security. They are just designed to make the existing code that
uses static buffers easy to make more robu
In message <[EMAIL PROTECTED]> Warner Losh writes:
: We mildly disagree here. The strl* functions are the end all, be all
: of security.
NOTE: This should have read:
We mildly disagree here. The strl* functions are NOT the end all, be
all of security.
which changes its meaning quite
In message <[EMAIL PROTECTED]> Sheldon Hearn writes:
: If you see my point, let me know and I'll send you an alternative
: strlcpy.3 .
I can see your point. I don't know if I'll like your man pages better
or not, but I'd be willing to give them a spin.
Warner
To Unsubscribe: send mail to [EMA
What purpose is served by the twisty maze of ifdefs in telnetd? 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?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body o
In message <[EMAIL PROTECTED]> Peter Jeremy writes:
: There's nothing stopping you unifdefing telnetd on your system. I
: have no opinion as to the merits (or otherwise) of leaving the
: ifdef's in the main code tree.
True, but since some of what I'm doing is making sure that there are
no securi
> (most of it are due to lack of a real getopt routine).
FreeBSD does have a real, 100% posix compatible getopt. Maybe you are
missing one of the numerous, non-standard Linux extentions? Gnu's
getopt can be found in about a dozen different places in the FreeBSD
tree. cvs, tar, etc.
Warner
In message <[EMAIL PROTECTED]> Per
Lundberg writes:
: I know it isn't standard. But it works well, and is used by a lot of
: programs. Perhaps it should have been put in another library than libc,
: though. Actually, I'd better suggest this to the GNU people right ahead.
There has been talking o
In message <[EMAIL PROTECTED]> Chris Costello writes:
: getopt other than --foo-bar flags that everyone I know hates?
Not everyone hates them...
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Maybe the P60 is memory starved. Thrashing would cause this huge
factor of speed difference...
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <[EMAIL PROTECTED]> Geoffrey Robinson writes:
: pccardc: /dev/card0: Device not configured
Rebuild your kernel with pccard support.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
[[ Warning, you'll need something which can display Kanji to be able
to read what I've written. I'm using mule and netscape. I've tried
to make the non-Japanese parts separate enough that if you only
understand English and have only english viewing programs, you can
safely ignore the
In message <[EMAIL PROTECTED]> Dirk GOUDERS writes:
: My sound card is a SBPCI128 by Creative Labs.
Nice card... I have one too. Plays mp3 well :-). Also plays video
sound well and xgalaga works with sound!...
NOTE: The SBPC64 doesn't work without an external patch... Be
careful.
: I only u
In message <[EMAIL PROTECTED]> "David E. Cross" writes:
: Any-who, is there a way I can get a look at the raw mbuf/mbuf-clusters?
: I have a feeling that seeing the data in them would speak volumes of
: information. Preferably a way to see them without DDB/panic would be ideal.
I've also seen pr
In message <[EMAIL PROTECTED]> Chris Costello writes:
:Are you going to be listing all the RFCs that apply? For
: example, DNS is 1033, 1034, and 1035, and NNTP is 0850 and 0977.
DNS is also 1123 and a few others in the 2xxx range. Then again, a
lot are 1123 :-) NNTP should just list 977,
In message <[EMAIL PROTECTED]> Frank Mayhar writes:
: I'm just doing a "make upgrade" on a clean /usr/obj. It crashes when it gets
: to libmytinfo. That's it.
:
: Any help or pointers would be greatly appreciated. Thanks.
You might try to get a hold of 3.1 release, do a make upgrade to that,
In message <[EMAIL PROTECTED]> Sheldon Hearn writes:
: This doesn't look right. If I can execute a binary, I can have the
: system allocate memory to me and but the binary image in it. It's my
: memory. :-)
Also, one can use a custom libc to get around the readonly ness, since
functions in libc c
In message <[EMAIL PROTECTED]> Sean Eric Fagan writes:
: if you care about security, you made the damned executable suid or
: sgid. Then ktrace, ptrace, truss, and core dumps do not work. Even
: if it simply does setuid(getruid()).
It also disables attacking the contents of the executable by
LD
In message <[EMAIL PROTECTED]> Dirk GOUDERS writes:
: What I still don't understand is the following message at boot time:
: pcm1: using I/O space register mapping at 0xe400
: I am wondering why there is a message concerning pcm1 instead of pcm0...
Quirks in config system in -stable cau
In message
<[EMAIL PROTECTED]> "Brian
F. Feldman" writes:
: But we can install from a single downloaded boot floppy, over the
: Internet, which is better.
Is that still true? I thought we went back to two floppies to do
this...
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsub
In message <[EMAIL PROTECTED]> Sheldon Hearn writes:
: I have a feeling it'll be time soon enough for us to make each of the
: decisions that is normally affected by securelevel dependant on the
: value of sysctl knobs. Presumeably one or more of them would be
: "write-once" knobs. :-)
Yes. That
In message <[EMAIL PROTECTED]> Sheldon Hearn writes:
: +#ifdef SUPPORT_DOT
: +/* Older configurations used '.' between user and group */
: +if ((group = strchr(q, ':')) != NULL ||
: +(group = strchr(q, '.')) != NULL) {
: +#else
:
In message <[EMAIL PROTECTED]> "David O'Brien" writes:
: Before importing, it must display a version number of 1.0 (or drop the
: version number). This is not Linux where everything is version 0.xy.
For a long time the new boot loader was in the tree with a version
0.xx...
Warner
To Unsubscri
In message <[EMAIL PROTECTED]> "Brian F.
Feldman" writes:
: if ((p1 = (u_char *)mmap(NULL,
: - (size_t)length, PROT_READ, MAP_SHARED, fd1, off1)) == (u_char *)MAP_FAILED)
: + (size_t)mlength, PROT_READ, MAP_SHARED, fd1, off1)) == (u_char
:*)MAP_FAILED)
: err(E
In message <[EMAIL PROTECTED]> "Jordan K. Hubbard" writes:
: It already is. That's not the question under discussion here - we're
: talking about how to make things work in the post-installation boot
: scenario.
I'm in favor of having it in the kernel by default. With one
proviso. Any place wh
In message <[EMAIL PROTECTED]> "Brian F.
Feldman" writes:
: And how about having
: if (securelevel > 3)
: return (EPERM);
: in bpf_open()?
There are no security levels > 3. I'd be happy with > 0. This is
consistant with the meaning of "raw devices".
Warner
To Unsubscr
In message <[EMAIL PROTECTED]>
Alfred Perlstein writes:
: What about the one-way sysctls that have been suggested?
They need to be implemente dfirst. A quick securelevel > 0 in bpf_open
would allow many people's objections to bpf in the kernel by default.
Warner
To Unsubscribe: send mail to
In message <[EMAIL PROTECTED]> "Jordan K. Hubbard" writes:
: > There are no security levels > 3. I'd be happy with > 0. This is
: > consistant with the meaning of "raw devices".
:
: Would you be willing to make this change?
Yes. I will make this change tomorrow unless there is significant
obj
In message <[EMAIL PROTECTED]> Sergey Babkin writes:
: Disabling bpf it will break rarpd (and also rbootd but it is less
: important). I think such a thing should be mentioned in documentation.
Not if they are started before the secure level is raised.
Warner
To Unsubscribe: send mail to [EMA
In message <[EMAIL PROTECTED]> Bernd Walter writes:
: Maybe a set of sysctls with a switch to off only behavour would be a
: better way.
Actually, a better way would be to have the interfaces to the network
stack that would handle this stuff w/o needing to resort to bpf.
Warner
To Unsubscribe:
In message <[EMAIL PROTECTED]> Christopher Masto writes:
: I hope you mean "> 1". I often diagnose problems using tcpdump etc.,
: and I don't think bpf should be broken just because someone wants the
: minor "flags can't be turned off" feature of level 1.
Flags can't be turned off at level 1, an
In message <[EMAIL PROTECTED]> Bernd Walter writes:
: > There are no security levels > 3. I'd be happy with > 0. This is
: > consistant with the meaning of "raw devices".
: That would mean you can't run a secured DHCP server :(
No. That would mean you'd have to start DHCP before raising the
se
In message <[EMAIL PROTECTED]> Wes Peters writes:
: Do we have a list of all services that use bpf? I'm willing to edit the man
: pages, given a list. I guess I could just grep-o-matic here, huh?
Yes. I'm also in a holding off pattern until we know the exact impact
for all daemons that use th
In message <[EMAIL PROTECTED]> John-Mark Gurney writes:
: I vote for allowing inetd.conf to specify a port number instead of a
: service name... it should be very easy to make the modification, and
: I'm willing to do all the work, assuming no one on -committers objects..
I'd love to be able to
In message <[EMAIL PROTECTED]> Juha Nurmela
writes:
: Yes, but (this might be a trademark ;) commonly the arguments would
: be used during the sysinit->attach, and at that time sysctl has not yet
: been able to change anything. Use of sysctl would require a sidestep
: from attach and later contin
In message <[EMAIL PROTECTED]> "Daniel C. Sobral" writes:
: Modules are not just drivers. Forget about drivers, and try again.
: :-)
But the generic mechanism extends beyond just drivers :-)
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of
In message <[EMAIL PROTECTED]> Dag-Erling Smorgrav writes:
: Allow me to re-quote the message I answered:
:
: > I vote for allowing inetd.conf to specify a port number instead of a
: > service name...
I've said it before, and I'll say it again: This is an excellent idea!
Warner
To Unsubscribe
In message <[EMAIL PROTECTED]> Dag-Erling Smorgrav writes:
: Daniel Eischen <[EMAIL PROTECTED]> writes:
: > Dag-Erling Smorgrav wrote:
: > > The correct way to do this is to fix getservbyname() so it accepts
: > > port numbers.
: > Are you sure this is what you want?
I'm 100% positive that I want
In message <[EMAIL PROTECTED]> Bill
Fumerola writes:
: Copying the telnet line and changing the first word to 'http' does wonders
: for being to access machines from inside a school district's firewall.
What if the service has no name?
: Choosing ports by number would be nice, however the same
In message <[EMAIL PROTECTED]> Bill
Fumerola writes:
: I agree. The change should be made in inetd, not in getportbyname()
Or getservbyname (which is really what you'd want to change). I have
patches to inetd that I've enclosed here. They are gorss, but the
code itself doesn't lend itself to n
In message <[EMAIL PROTECTED]> Darren Reed writes:
: Why not just use the changes NetBSD made to their inetd ~6 years ago ?
Didn't know about them?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <[EMAIL PROTECTED]> Brian Somers writes:
: Yes, but do it the other way 'round - strtol first, if it's not all
: numeric, getservbyname().
I did it getservbyname first in case there were any legacy services
that were all numbers. Traditionally, this is hwo things were done
with IP ad
In message <[EMAIL PROTECTED]> Brian Somers writes:
: Exactly - ditto for gethostbyname(). In the case of gethostbyname(),
: I believe that domain names can't have a number as the first
: character - I would have thought this idea should follow through with
: services.
No. That is in error.
I have a freebsd-stable system. I can't build a kernel for
freebsd-current on that system unless I upgrade my compiler to egcs.
Will this cause problems for our upgrade proceedure?
gcc 2.7.2.3 doesn't like i386/include/atomic.h. It complains about
bad assmbler contraints.
Warner
To Unsubscr
In message
<[EMAIL PROTECTED]> David
Scheidt writes:
: I upgraded a -STABLE system to -CURRENT using source a month or two
: ago. The first step is to build the new toolchain, so you shouldn't
: ever be compiling a new kernel with an old compiler.
In the past, we've given advise to build a
In message <[EMAIL PROTECTED]> Osokin Sergey
writes:
: try to cvsup your source tree to 4.0, then rebuild your system
: with simply make world procedure.
I can't do that. This system *MUST* be a 3.2-stable system. I was
building the kernel to test to see if a nasty NFS bug I've found in
-stabl
In message
<[EMAIL PROTECTED]> David
Scheidt writes:
: Read the docs? Who me? It sounds like the 3.X to 4.0-RELEASE documentation
: should say not to do this. Unless, of course, gcc-2.95 is imported before
: t hen.
Give me a F*ing break. No such documetation exists and the more that
we cha
I'm seeing on a -stable system that netstat will always print values
obtained from sysctl rather than from the core file specified. Can
anybody confirm this? It doesn't seem like feature to me...
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the
In message <001201bedfb8$92fa3440$[EMAIL PROTECTED]> "Biju Susmer" writes:
: I dont think it should be a problem.. Since other OSs can work with this
: configuration without any problem, why FBSD should refuse this configuration?
: When i was using 2.2.7-stable, FBSD used to recognize my CDROM *so
In message
<[EMAIL PROTECTED]> "Brian
F. Feldman" writes:
: Since it was made to work? The problem here is that this person, for some
: reason, is misconfiguring their system and expecting it to work as if it
: were configured properly.
Odd, all of the machines that I've seen shipped lately have
In message <[EMAIL PROTECTED]> John Baldwin writes:
: Perhapas have a group that has write access to all the archive and stick the
: user in that group? That doesn't prevent checkins, however.
You can do that inside the respository itself. Just try to do a
commit on your local mirror of the Fre
In message <[EMAIL PROTECTED]> Chris writes:
: As always when a misconfiguration (read 'not to spec') is used enough
: then it quickly becomes somewhat of a de facto standard.
I'd love to see chapter and verse on this :-)
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
In message <[EMAIL PROTECTED]> Bill
Fumerola writes:
: cvsup seems to set the wrong attributes after I've forced them to work
: that way.
I see this when I cvsup as root too (although the file you quoted
should be r--r--r--. I can't get the modes on the directories to be
775...
Warner
To Uns
In message <[EMAIL PROTECTED]> "Brian F.
Feldman" writes:
: You can always use off_t with "%qd", (int64_t)foo.
But that isn't portbale. %qd is a bsdism. %lld and %llu are the
latest C standards way to say that.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-
In message <[EMAIL PROTECTED]> "Brian F.
Feldman" writes:
: Sorry, kinda used to quad rather than long long. I'm pretty sure ll
: isn't yet supported by the kernel printf functions...
You may be right about that.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-
In message <11366.934157821@localhost> "Jordan K. Hubbard" writes:
: > I have a parallel port Iomega Zip Drive. I have installed 3.2-RELEASE and
: > although the vpo0 is detected it does not see da0, and when I try "mount -t
:
: I'm not surprised, since da0 would be a SCSI device.
But vpo0 is a
In message <[EMAIL PROTECTED]> "Daniel C. Sobral" writes:
: Well, Terry does, though I don't quite recall his reasoning. :-)
: Notice, he objects the way FreeBSD is today, with the bind resolver
: API inside libc.
The size of _res has changed. Although it starts with an _, it is
officially part
In message <[EMAIL PROTECTED]> Dag-Erling Smorgrav writes:
: superblock (or one of its backup copies), you can determine the offset
: and size of the FS. It won't tell you anything about *other*
: partitions though.
It will give a fairly strong hint, however. If you know what is taken
up by this
In message <[EMAIL PROTECTED]> Kenny Drobnack
writes:
: This may be a stupid question, but what's to keep from putting xfs in
: FreeBSD? Is there something in the licenses that says you can't use
: GPL'ed software and software under the BSD License together?
The BSD license allows binary only a
In message <[EMAIL PROTECTED]> "Brian F.
Feldman" writes:
: What do you all think about growing a gnu subdirectory in src/lib/libcompat?
: Things like a getopt_long implementation (yes, if it will be accepted,
: I am volunteering to write it...) would go there, and all sorts of lame
: GNU libc cr
In message <[EMAIL PROTECTED]> free bsd writes:
: I would like to know, if there a way (a tools) to make a partition "fat16".
fdisk to mark the partion as fat16, newfs_msdos to splat a file system
onto it.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers
In message <[EMAIL PROTECTED]> Steve Kargl writes:
: If you're writing unencumbered code, placing it under
: libcompat/gnu may lead to confusion because all other
: directory paths containing gnu contain GPL'd code.
: Just stick it into libcompat.
Or libiberty :-) That way we can have a GPL-free
In message <[EMAIL PROTECTED]> "Brian F.
Feldman" writes:
: There
: is simply no reason to assume that anything under a gnu directory is GPLd,
: or that anything GPLd is going to be under a gnu directory (which it's not.)
I'm afraid there is. It has been stated many times in the past that
all G
In message <[EMAIL PROTECTED]> "Louis A. Mamakos" writes:
: It violates the "starts with alpha" "requirement" in 952 and 1101
: that you quotes, yet we use these things all the time.
That requirement has been relaxed. See RFC 1123.
Bottom line is that _ is an illegal character in a hostname,
In message <25455.934497542@localhost> "Jordan K. Hubbard" writes:
: > So Solaris does the right thing by understanding underscore I guess.
: > Since it is not forbidden to use it in hostnames.
:
: It does not do the right thing and it is indeed forbidden. :)
Also, all modern versions of bind sp
In message <[EMAIL PROTECTED]> "Louis A. Mamakos" writes:
: The DNS can store names where the values used for each octet of a
: label in a DNS name can have any value at all between 0 and 255,
: including " ", ".", and other rude things. The general purpose
: mechansim can be (ab)sed for all sort
In message <[EMAIL PROTECTED]>
Brian McGroarty writes:
: So do the old and new Playstation models. The MIPS core is being
: manufactured by several companies: IDT alone has something like
: a dozen variants available with and without MMU, FP, 5000 vs
: 1 core, etc. and is in far wider use tha
In message <[EMAIL PROTECTED]> Narvi writes:
: > Nintendo 64 uses MIPS.
: >
:
: Which doesn't matter all that much. MIPS cpus for nintendo could be made
: by say MISP, not SGI (and SGI sold/is trying to sell MIPS).
Acutally, the Nintendo 64 uses the Vr4300 series of chips from NEC. I
think the
In message <[EMAIL PROTECTED]> "Daniel
O'Connor" writes:
: How about just adding some flags to mount and modifying UFS so that
: you can override the uid/gid on mount.. I assume you mean Joe uses
: something like sudo so he can mount the disk..
Doesn't umapfs do that?
Warner
To Unsubscribe: s
In message <[EMAIL PROTECTED]> "Daniel O'Connor" writes:
: IMHO being abe to override UID:GID's would be useful in a normal
: mount because umapfs adds more complexity to work. (Though I can see
: that doing it in the various FS's would suck royally)
I don't understand the objection... umapfs is
In message <[EMAIL PROTECTED]> Christopher Masto writes:
: Do they still not allow you to release the specs? How is the code
: going to become part of FreeBSD if they won't allow its release?
I didn't sign an NDA to get my copy of the spec or the hardware...
I also don't have time to devote to
In message <[EMAIL PROTECTED]> Matthew Jacob
writes:
: Neither did I. But I was requested by Jim Jonez of Onstream to not release
: the specs.
Same here... Just pointing out that OnStream is being cooperative.
: > I also don't have time to devote to the onstream IDE project. I'm
: > looking f
In message <[EMAIL PROTECTED]> David
Scheidt writes:
: Couldn't you turn it off only for NFS mounted files?
For the general case (eg the code checked into the system), the check
needs to remain enabled. Anything else is insecure.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "
901 - 1000 of 2062 matches
Mail list logo
