Wes Peters [EMAIL PROTECTED] wrote:
Darryl Okahata wrote:
... however, how the H*LL are the clueless newbie hordes supposed
to know or learn this? As much as we'd like them to be, they're not
exactly born with this knowledge, and I somehow doubt there's an "XXX
for Dummies"
Last week the releases built fine, now i get the following error :
---
cd /usr/src/kerberosIV/lib/libsl ; make install
DESTDIR=/R/stage/trees/krb SHARED=copies
=== lib/libacl
cd /usr/src/kerberosIV/lib/libacl ; make install
Darryl Okahata wrote:
The "old-fashioned way"? While the "look before you leap"
philosophy, which is excellent advice, has been around Usenet since time
immemorial, I've yet to meet or hear about anyone that's actually done
it (when they were a newbie, that is), although people here
Might the following be helpful? Or, does it exist somewhere on the net now?
http://www.blackhelicopters.org/~dispatch/stupid-bsd-questions.txt
If it is of any use, I'll clean it up for general consumption.
==ml
(who prefers to curse the candle, as opposed to light the darkness)
To
"Daniel C. Sobral" [EMAIL PROTECTED] wrote:
Why the hell does the clueless newbie hordes expects any answer when
posting a message to a list without reading the list charter and
without a single clue of how the list works is beyond me.
No one's disputing this. In fact, I agree with
If you want to do this, I suggest a round of releases that have mount
complain about the @ syntax before you kill it. POLA, you know.
A complaint such as:
WARNING: path@server syntax is deprecated, use server:path
would be sufficient.
A good idea, but how can one make a difference
Is there a way to force a Freebsd system to route to the same logican IP
network rather than send a redirect?
The situation occurs with segmented bridges where customers on the same
logical IP network are on separate bridge groups. When trying to reach one
another, they are getting redirects
what kind of broken bridges do you have in mind which do not pass
broadcast traffic ? (and if the answer is FreeBSD 3.2R, yest this is a
known bug with some cards, and i have a fix ready for commit as soon as
i get a chance to breath).
this is not your bridge code, btw, this is our
On Mon, 4 Oct 1999, Luoqi Chen wrote:
If you have a crash dump, could you look at the 4 longwords starting
at address 0xc02698c0? It seemed to be an accouting problem. Do you
by any chance use any kld module? zalloc() calls from within a module
do not lock the vm_zone data structure, which
On Tue, 5 Oct 1999, Martin Blapp wrote:
If you want to do this, I suggest a round of releases that have mount
complain about the @ syntax before you kill it. POLA, you know.
A complaint such as:
WARNING: path@server syntax is deprecated, use server:path
would be sufficient.
On 05-Oct-99 Martin Blapp wrote:
Not many people are aware that our userland mount_nfs(8) and
umount(8)
support the following NFS-URL-syntax:
mount /some/path/to/directory@nfs-server /mntpoint
This, however, seems to be BSD-specific. Neither Solaris, Linux, Irix
or any other Operating
On Tue, Oct 05, 1999 at 10:21:36AM -0400, Dennis wrote:
Is there a way to force a Freebsd system to route to the same logican IP
network rather than send a redirect?
Uhm, did you try this?
sysctl -w net.inet.ip.redirect=0
BTW, whether or not sending redirects, the original packet is
Hi,
The system in question (3.3-stable) needs to use a large FS (ca. 40GB).
The defaults for such filesystem are ridiculous, given that it will hold
at most couple of hundred big data files. So, my question is:
* should I change the cpg (default 16) to some bigger value?
* is it safe to run
:Not many people are aware that our userland mount_nfs(8) and umount(8)
:support the following NFS-URL-syntax:
:
:mount /some/path/to/directory@nfs-server /mntpoint
:
:This, however, seems to be BSD-specific. Neither Solaris, Linux, Irix
:...
:
:I propose to remove the '@' feature because of the
On Tue, Oct 05, 1999, [EMAIL PROTECTED] wrote:
Might the following be helpful? Or, does it exist somewhere on the net now?
http://www.blackhelicopters.org/~dispatch/stupid-bsd-questions.txt
If it is of any use, I'll clean it up for general consumption.
This is a very interesting
Date: Tue, 5 Oct 1999 14:19:22 -0700
From: Pat Dirks [EMAIL PROTECTED]
[Lots of interesting, useful stuff elided -- dhw]
ADOPTING "FOREIGN" FILESYSTEMS
...
Note that one interesting option might be to provide a one-time-only
"adoption" which has no permanent effect; when the disk is
On Tue, 5 Oct 1999, Pat Dirks wrote:
Hi,
I'm the File Systems Tech Lead at Apple in the Mac OS X Core OS group.
We've been struggling with the question of how best to handle permissions
on disks that are moved between systems for Mac OS X and Mac OS X Server:
the problem is that
Digital Unix, aka Compaq Tru64 Unix, formerly know as DEC OSF/1
supports this syntax. In fact, this is the only syntax it supports,
IIRC, so FreeBSD is not the only OS to use it.
You are not correct when you state that this is the only syntax it
supports. Digital Unix does support the
Greetings -
I have installed FBSD 3.3-R on an HP Kayak XU, and have run into some
interesting problems with the AMD PCNet-Fast (if_lnc) driver. This
machine has an HP combo card (PN #5183-2725 or #5064-3616) with
NCR SCSI and AMD PCNet-Fast chipsets.
While booting up, I get the following kernel
Hi,
The system in question (3.3-stable) needs to use a large FS (ca. 40GB).
The defaults for such filesystem are ridiculous, given that it will hold
at most couple of hundred big data files. So, my question is:
* should I change the cpg (default 16) to some bigger value?
* is it safe
On Tue, 5 Oct 1999, Pat Dirks wrote:
as "local". As part of this "adoption" process the users is prompted to
choose one of two ways to handle the existing permissions on the disk:
* Retain them as-is (useful for cases where you have external
reasons to believe
the numeric
It most likely is. I've found a pretty reliable way to crash Netscape 4.6
and 4.7-freebsd (either us or export): Open two windows, and visit
slashdot in both of them.
Don't ask me _why_ it works, but it does. :)
It causes the BSDI version to hang and chew CPU. The linux and windoze
versions
What do you all think about
http://www.FreeBSD.org/~green/OpenBSD.libc_r.cancel.patch
? I isolated the set of commits that added cancelling to OpenBSD's
libc_r, and it seems (since they took it from us originally :) it
should be relatively simple to port :/
--
Brian Fundakowski Feldman
In brief: I'm developing drivers for the Mylex DAC960/1100 and AMI
MegaRAID/Dell PERC/HP whatever families of RAID controllers,
and I need some more hardware to test with. Details below.
Current status:
- Mylex DAC960 driver works with P/PL/PD/PU controllers. Support
:Hi,
:
:The system in question (3.3-stable) needs to use a large FS (ca. 40GB).
:The defaults for such filesystem are ridiculous, given that it will hold
:at most couple of hundred big data files. So, my question is:
:
:* should I change the cpg (default 16) to some bigger value?
No, let
Darryl Okahata wrote:
That's actually a good idea. Tell you what, you read the previous
threads and prepare a good FAQ entry in docbook, send me the patches
and I'll commit it.
I'll take you up on this, if you can guarantee that it'll show up
on the FreeBSD web page FAQ in a
26 matches
Mail list logo
