eBSD-jp/I18N-flp/4.3-RELEASE/20010507/
> p.s. one question - should I translate LOCALIZE.TXT? It exists only in
> the form of English.
You don't have to translate it, but of course, if you translate it to
Korean, I will put it at texts/ko/.
> And please add my name to LOCALIZE.TXT
Hi folks,
Is there a good reason why sysctl(8) won't display _any_ output for
opaque MIB entries named as arguments? I'm specifically interested in
kern.proc.all. I can ``sysctl -A | grep kern.proc.all'', but it's weird
that neither of these two do anything useful:
sysctl -A kern.proc
On 7 May 2001, Dag-Erling Smorgrav wrote:
> Alfred Perlstein <[EMAIL PROTECTED]> writes:
> > The silly part of it is that the socket's initial credentials
> > might be different than the holder's credentials.
>
> That's a feature, just like you can open /dev/io as root, then drop
> root privs an
Sheldon Hearn <[EMAIL PROTECTED]> writes:
> Is there a good reason why sysctl(8) won't display _any_ output for
> opaque MIB entries named as arguments?
Yes it will, with -X. The interesting question is why there isn't an
option to make it display just one variable in hex, and why it doesn't
pri
On 07 May 2001 18:51:22 +0200, Dag-Erling Smorgrav wrote:
> Yes it will, with -X. The interesting question is why there isn't an
> option to make it display just one variable in hex, and why it doesn't
> print a message when it omits printing an opaque variable.
Do you think it'd be okay to a
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> Sheldon Hearn <[EMAIL PROTECTED]> writes:
> > Is there a good reason why sysctl(8) won't display _any_ output for
> > opaque MIB entries named as arguments?
> Yes it will, with -X. The interesting question is why there isn't an
> option to make it
Sheldon Hearn <[EMAIL PROTECTED]> writes:
> On 07 May 2001 18:51:22 +0200, Dag-Erling Smorgrav wrote:
> > Yes it will, with -X. The interesting question is why there isn't an
> > option to make it display just one variable in hex, and why it doesn't
> > print a message when it omits printing an o
On Mon, May 07, 2001 at 07:24:39PM +0200, Dag-Erling Smorgrav wrote:
> Sheldon Hearn <[EMAIL PROTECTED]> writes:
> > On 07 May 2001 18:51:22 +0200, Dag-Erling Smorgrav wrote:
> > > Yes it will, with -X. The interesting question is why there isn't an
> > > option to make it display just one variab
In message <[EMAIL PROTECTED]>, Sheldon Hearn writes:
>
>
>On 07 May 2001 18:51:22 +0200, Dag-Erling Smorgrav wrote:
>
>> Yes it will, with -X. The interesting question is why there isn't an
>> option to make it display just one variable in hex, and why it doesn't
>> print a message when it omits
On Mon, May 07, 2001 at 07:43:39PM +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Sheldon Hearn writes:
> >
> >
> >On 07 May 2001 18:51:22 +0200, Dag-Erling Smorgrav wrote:
> >
> >> Yes it will, with -X. The interesting question is why there isn't an
> >> option to make it disp
Peter Pentchev <[EMAIL PROTECTED]> writes:
> How about e.g. 'sysctl -a hw', which still shows *all* MIB's?
> At least on ref5 as of this very moment..
Yes, because '-a' means 'show all non-opaque' and 'hw' is ignored.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to
On Mon, May 07, 2001 at 07:52:15PM +0200, Dag-Erling Smorgrav wrote:
> Peter Pentchev <[EMAIL PROTECTED]> writes:
> > How about e.g. 'sysctl -a hw', which still shows *all* MIB's?
> > At least on ref5 as of this very moment..
>
> Yes, because '-a' means 'show all non-opaque' and 'hw' is ignored.
Peter Pentchev <[EMAIL PROTECTED]> writes:
> On Mon, May 07, 2001 at 07:52:15PM +0200, Dag-Erling Smorgrav wrote:
> > Peter Pentchev <[EMAIL PROTECTED]> writes:
> > > How about e.g. 'sysctl -a hw', which still shows *all* MIB's?
> > Yes, because '-a' means 'show all non-opaque' and 'hw' is ignored
Robert Suetterlin wrote:
>
> Hello!
>
> I asked this already on freebsd-questions and was suggested to ask on this list, too.
>
> I have a linux driver for a video grabber card (dfg/bw1 from 'the imaging
>source'). This card does not use a well bt848 or similar chip. I would like to
On 05-May-01 Alfred Perlstein wrote:
> * Ceri Storey <[EMAIL PROTECTED]> [010505 11:59] wrote:
>> On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote:
>> > > Note : this is a way to kill your keyboard : an AT keyboard is not
>> > > hot-plug compatible
>> >
>> > i have never killed
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
I am working on a FreeBSD device driver for my Co's GSN adapter and need
to be able to set my TCP/IP window size to 512KB (or perhaps more). I
have tried doing this with sysctl:
root@sebulba:p0 /root> sysctl -w net.inet.tcp.recvspace=524288
net.inet.tcp.recvspace: 131072 -> 524288
root@sebulba:p
On Mon, May 07, 2001 at 16:20:05 -0500, Bob Willcox wrote:
>
> I am working on a FreeBSD device driver for my Co's GSN adapter and need
> to be able to set my TCP/IP window size to 512KB (or perhaps more). I
> have tried doing this with sysctl:
>
> root@sebulba:p0 /root> sysctl -w net.inet.tcp.r
Sun, May 06, 2001 at 17:14:08, rakshe (Rohit Rakshe) wrote about "Re: FPU exception,
kernel panic":
(I cannot even guarantree 50% this is the same problem, but...)
There were some reports in current@ about incorrect usage of i586_bzero()
which uses FPU for zero-filling. It generated random ker
On Mon, May 07, 2001 at 08:32:06AM +0300, Valentin Nechayev wrote:
> Sun, May 06, 2001 at 17:14:08, rakshe (Rohit Rakshe) wrote about "Re: FPU
>exception, kernel panic":
>
> (I cannot even guarantree 50% this is the same problem, but...)
> There were some reports in current@ about incorrect us
On Mon, May 07, 2001 at 04:20:05PM -0500, Bob Willcox wrote:
> root@sebulba:p0 /root> ftp 192.168.1.2
> ftp: socket: No buffer space available
One possibility is that your process limits for sbsize are
too low. You could check what it says in login.conf.
(I note that our tcsh doesn't support sbs
On Mon, May 07, 2001 at 10:52:47PM +0100, David Malone wrote:
> On Mon, May 07, 2001 at 04:20:05PM -0500, Bob Willcox wrote:
> > root@sebulba:p0 /root> ftp 192.168.1.2
> > ftp: socket: No buffer space available
>
> One possibility is that your process limits for sbsize are
> too low. You could ch
On Mon, May 07, 2001 at 04:45:31PM -0500, Bob Willcox wrote:
> On Mon, May 07, 2001 at 03:38:02PM -0600, Kenneth D. Merry wrote:
> > On Mon, May 07, 2001 at 16:20:05 -0500, Bob Willcox wrote:
> > >
> > > I am working on a FreeBSD device driver for my Co's GSN adapter and need
> > > to be able to
On Mon, May 07, 2001 at 17:15:20 -0500, Bob Willcox wrote:
> On Mon, May 07, 2001 at 04:45:31PM -0500, Bob Willcox wrote:
> > On Mon, May 07, 2001 at 03:38:02PM -0600, Kenneth D. Merry wrote:
> > > On Mon, May 07, 2001 at 16:20:05 -0500, Bob Willcox wrote:
> > > >
> > > > I am working on a FreeBS
On Mon, May 07, 2001 at 04:17:53PM -0600, Kenneth D. Merry wrote:
> On Mon, May 07, 2001 at 17:15:20 -0500, Bob Willcox wrote:
> > On Mon, May 07, 2001 at 04:45:31PM -0500, Bob Willcox wrote:
> > > On Mon, May 07, 2001 at 03:38:02PM -0600, Kenneth D. Merry wrote:
> > > > On Mon, May 07, 2001 at 16
Hello,
I'm using 4.2 release and i need bridging.
Luigi tells in the manpage that the option
to select specific devices for bridging is
still in development.
Does anybody know how far this work is done
in 4.3 stable ?
I need this feature very urgently, and all
of my experiments with net.link.et
Valentin Nechayev <[EMAIL PROTECTED]> writes:
> (I cannot even guarantree 50% this is the same problem, but...)
> There were some reports in current@ about incorrect usage of i586_bzero()
> which uses FPU for zero-filling. It generated random kernel panics mainly
> on K6-2, also on P5-MMX and simi
> Hello,
>
> I'm using 4.2 release and i need bridging.
> Luigi tells in the manpage that the option
> to select specific devices for bridging is
> still in development.
>
> Does anybody know how far this work is done
> in 4.3 stable ?
it works on 4.3-RELEASE
cheers
luigi
> I
Am I correct in assuming that:
$ cd /usr/src
$ make installworld DESTDIR=/vol1/FreeBSD
will install the entire OS into /vol1/FreeBSD?
Has anyone ever tried this? ;)
--
Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED]
>>> The opinions expressed above are entirely my own <<<
"
What happened to this patch/this discussion?
To remind everyone, the issue was to print specific file-system
specific mount options as in
dima@spike% /sbin/mount -vt nfs
pid295@spike:/host on /host (nfs, v2, udp, hard, intr)
pid295@spike:/st on /st (nfs, v2, udp, hard, intr)
instead of ju
Where is the picoBSD source code ? Can i compile for ARM processor ?
Best Regards Michael Trimarchi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
dave> $ cd /usr/src
dave> $ make installworld DESTDIR=/vol1/FreeBSD
dave> will install the entire OS into /vol1/FreeBSD?
Yes (or it should be).
dave> Has anyone ever tried this? ;)
You should have already seen the result that uses "make installworld
DESTDIR=/what/ever" -- FreeBSD distribution
32 matches
Mail list logo
