> On 9. Jun 2021, at 04:17, grarpamp wrote:
>
> On 4/17/20, Ryan Moeller wrote:
>>
On Apr 17, 2020, at 4:56 PM, Pete Wright wrote:
>>>
>>> On 4/17/20 11:35 AM, Ryan Moeller wrote:
OpenZFS brings many exciting features to FreeBSD, including:
* native encryption
>>> Is there
On 4/17/20, Ryan Moeller wrote:
>
>> On Apr 17, 2020, at 4:56 PM, Pete Wright wrote:
>>
>> On 4/17/20 11:35 AM, Ryan Moeller wrote:
>>> OpenZFS brings many exciting features to FreeBSD, including:
>>> * native encryption
>> Is there a good doc reference on available for using this? I believe
At 7:43 PM +0200 2003/05/02, Matthias Buelow wrote:
The two programs, however, only do the same thing if you consider
that they're both compressors. bzip2 eats much more resources than
gzip, both space and time. And the algorithm is rather overkill for
small files anyways.
Granted, the
Hello all,
Pardon this poor question but I was looking for up to date documentation
about FreeBSD-current (5.0-RC3). Most important points to me are new kernell
config and IPFilter implementation (didn't saw anything related in new files
concerning kernell tuning and config).
Can someone tell
ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/5.0-RC3/RELNOTES.HTM
/usr/src/UPDATING
and the files in /usr/src/sys/i386/conf (replacing i386 with your
architecture)
would be a good start
good luck
Tim
On Wednesday 15 January 2003 02:13 am, Coercitas Temet'Nosce wrote:
Hello
Does documentation for the rcng system exist? It sounds like it's still
changing, so I wouldn't be surprised if the docs are minimal at the moment.
Is there another mailing list where this is more properly asked?
I ask because I'm working on a set of KDE tools to administer FreeBSD
man 8 rc
man 8 rc.subr
--
Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc
[EMAIL PROTECTED] | Fingerprint: D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9
msg48581/pgp0.pgp
Description: PGP signature
On Wednesday 11 December 2002 10:49 pm, Mike Makonnen wrote:
man 8 rc
man 8 rc.subr
I was really hoping for documentation on how the PROVIDES/REQUIRES stuff was
handled and calculated. I'm familiar with the rc scripts in general.
I suppose I can read the code. :-)
-Cliff L. Biffle
To
| : When my laptop is booting (Toshiba with ToPIC97, NoteWorthy modem,
| : LinkSys modem card) something odd happens:
| :
| : IP packet filtering initialized, divert disabled, rule-based forwarding
| : disabled
| : , default to accept, unlimited logging
| : pccard: card inserted, slot 0
| :
| In -current look at /boot/device.hints. In stable this is still in
| the kernel config file.
Is the hints file going to become standard, or is it just a tool to
help developers writing drivers for -current?
jm
--
My other computer is your windows box.
To Unsubscribe: send mail to [EMAIL
In message: [EMAIL PROTECTED]
j mckitrick [EMAIL PROTECTED] writes:
: | Maybe hints consume ed0 and sio0 likely.
:
: So, the game is afoot! Is there anything I can do to help track this
: down?
In -current look at /boot/device.hints. In stable this is still in
the kernel config
In message: [EMAIL PROTECTED]
j mckitrick [EMAIL PROTECTED] writes:
:
: | In -current look at /boot/device.hints. In stable this is still in
: | the kernel config file.
:
: Is the hints file going to become standard, or is it just a tool to
: help developers writing drivers for
| : Is the hints file going to become standard, or is it just a tool to
| : help developers writing drivers for -current?
|
| It is standard in current, so in 5.0-release and newer people will
| have to cope.
So the idea is that drivers will be modules dynamically loaded based on
the hints
In message: [EMAIL PROTECTED]
j mckitrick [EMAIL PROTECTED] writes:
: So the idea is that drivers will be modules dynamically loaded based on
: the hints file?
Not currently. But someone could come in and do that project.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
On Tue, Feb 12, 2002 at 10:33:25AM -0700, M. Warner Losh wrote:
| In message: [EMAIL PROTECTED]
| j mckitrick [EMAIL PROTECTED] writes:
| : So the idea is that drivers will be modules dynamically loaded based on
| : the hints file?
|
| Not currently. But someone could come in and do
| It isn't a huge effort conceptutally, but there is a lot of
| infrastructure that CardBus depends on that isn't in -stable or only
| partially MFC'd. If someone wanted to start cranking on it, they
| could get it done in a few weeks worth of work.
Where would be a good place to start?
jm
--
In message: [EMAIL PROTECTED]
Miguel Mendez [EMAIL PROTECTED] writes:
: So, in your opinion, how hard would it be to MFC from a recent -CURRENT
: to 4.5-RELEASE? More or less importing the stuff and little fixing or is
: a major rewrite of some part needed? Because as it seems that no
In message: [EMAIL PROTECTED]
j mckitrick [EMAIL PROTECTED] writes:
: | CardBus:
: | PCMCIA standard for PCI cards in the PC Card form factor.
:
: I was pretty close on this as well. These are specifically 32-bit
: cards, correct?
Yes.
: |
Thanks, Warner!
On Mon, Feb 11, 2002 at 09:37:08AM -0700, M. Warner Losh wrote:
| NEWBUS:
| The current way of doing FreeBSD device configuration. This
| is approximately sys/kern/subr_bus.c, bus_if.m and device_if.m.
That part is pretty clear.
| CardBus:
| PCMCIA standard for PCI
In message: [EMAIL PROTECTED]
j mckitrick [EMAIL PROTECTED] writes:
: On Mon, Feb 11, 2002 at 03:56:00PM -0700, M. Warner Losh wrote:
: | NEWCARD is up and running, but has issues for some cards, bridges and
: | lacks some useful features.
:
: That reminds me, there was something I
I was wondering if any of the developers here had any docs for the via
kt133 south bridge. I need the docs so that I can write a driver for the
hardware monitoring features of this chip... I looked on via's website,
but the docs there are incomplete...
Ken
To Unsubscribe: send mail to [EMAIL
On Tue, Oct 31, 2000 at 12:02:47PM -0500, Kenneth Wayne Culver wrote:
I was wondering if any of the developers here had any docs for the via
kt133 south bridge. I need the docs so that I can write a driver for the
hardware monitoring features of this chip... I looked on via's website
I think one of our Japanese friends has been trying to get these docs
from VIA. With little luck it seems.
Hrmm, well I'll send a messege or something over to VIA... I'm going to
make this driver in such a way that it would be easy to add more drivers
for other hwmon stuff in the future...
Ken
It seems Kenneth Wayne Culver wrote:
I think one of our Japanese friends has been trying to get these docs
from VIA. With little luck it seems.
Hrmm, well I'll send a messege or something over to VIA... I'm going to
make this driver in such a way that it would be easy to add more drivers
friends has been trying to get these docs
from VIA. With little luck it seems.
Hrmm, well I'll send a messege or something over to VIA... I'm going to
make this driver in such a way that it would be easy to add more drivers
for other hwmon stuff in the future...
Hmm, I have the docs
Well, it's time I learned about the rather cryptic newbus stuff...
So where are the best docs to read on it.?
Ones that give an overview?
"UTSL" and "See man 9 {cryptic function name}" are not the
answers I'm looking for...
Someone once mentionned an actual
document
In message [EMAIL PROTECTED] Julian Elischer writes:
: Someone once mentionned an actual
: document but I've been unable to find it.
: Was it my imagination?
: (and if so, why isn't there one?)
What do you mean actual document? man pages are actual documents.
What kind of document do you want?
On Thu, 14 Sep 2000, Warner Losh wrote:
In message [EMAIL PROTECTED] Julian Elischer writes:
: Someone once mentionned an actual
: document but I've been unable to find it.
: Was it my imagination?
: (and if so, why isn't there one?)
What do you mean actual document? man pages are
In message [EMAIL PROTECTED] Matthew Jacob
writes:
: I would imagine an overall architecture doc. Sort of like what
: Jordan just did for sysinst (e.g.).
Then he should ask for an architecture doc rather than being so snippy
and snide about "actual documentation."
Warner
To Unsubscribe: send
On Thu, 14 Sep 2000, Warner Losh wrote:
In message [EMAIL PROTECTED] Julian Elischer writes:
: Someone once mentionned an actual
: document but I've been unable to find it.
: Was it my imagination?
: (and if so, why isn't there one?)
What do you mean actual document? man pages are actual
In message [EMAIL PROTECTED] Matthew Jacob
writes:
: I would imagine an overall architecture doc. Sort of like what
: Jordan just did for sysinst (e.g.).
Then he should ask for an architecture doc rather than being so snippy
and snide about "actual documentation."
Probably, but I
Ah, okay, for some reason I was looking at the 'disklabel -B' stuff, but
that never worked :( I've gotten into the habit of doing the whole
'buildkernel/buildworld/etc' procedure, and just hadn['t gotten to the
point doing the 'installworld' :(
thanks ...
On Thu, 7 Sep 2000, Warner Losh
How do I upgrade it 'with the new kernel', as the UPDATING file
suggests? I've looked at the man pages for loader, and it doesn't suggest
anything ... help?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL
On 2000-Feb-06 21:19:31 +1100, Jeroen Ruigrok/Asmodai [EMAIL PROTECTED] wrote:
And what is wrong with rev 1.20 of doc-common?
One obvious problem was pointed out by Joerg in his 1.20 commit message:
: alas the brain^Wnice sed(1) magic needs to be taught to
: _not_ strip those comments now.
A
-On [2205 00:01], Nik Clayton ([EMAIL PROTECTED]) wrote:
-current,
Peter Jeremy forwarded this to me. I'm happy to commit it, because
it solves the problem. However, I don't understand the cause of the
problem, so I don't know whether or not the fix is an appropriate one
or not.
And what
Only recommendation I might pass on is being consistant in the use
of "USA" instead of "US". The document starts off with references
to "USA" and then changes to "US".
Following the custom used in current crypto source (i.e. "USA_RESIDENT"
in make.conf) I would suggest using "USA".
Keith
Can people please review this for style and content, for inclusion in
the FAQ? I'll also need someone to mark it up once it's ready since SGML
is currently not among my abilities :-)
Thanks,
Kris
As of FreeBSD 4.0, the OpenSSL toolkit is a part of the base
system. OpenSSL
On Tue, Jan 25, 2000 at 12:49:04AM -0800, Kris Kennaway wrote:
Can people please review this for style and content, for inclusion in
the FAQ? I'll also need someone to mark it up once it's ready since SGML
is currently not among my abilities :-)
Is this FAQ material, or better off in the
American
Will support for building release docs in English only be
revived?
/mode
For the immediate future, it looks like it will -- it seems as though
we don't have the man power to make the necessary changes to sysinstall
to support "installing the docs as packages", so
available as packages so that those
people that want formatted docs, but who have neither the time, the
inclination, or the machine horsepower to download the textproc/docproj
port have a very easy way of installing and managing formatted
documentation -- specifically, pkg_add(1).
If people want
-stable, -current,
On Sun, Aug 22, 1999 at 11:05:11AM +0100, Nik Clayton wrote:
[ cc'd to -current ]
On Sat, Aug 21, 1999 at 07:54:51PM -0400, jack wrote:
mode ugly monolingual American
Will support for building release docs in English only be
revived?
/mode
For the immediate
* From: "Jordan K. Hubbard" [EMAIL PROTECTED]
* This makes the ports tree have a dependency on the doc tree. I don't think
* this dependency should be there. It's bad enough that the src/ tree
* depends on doc/ (and the reason I want the documentation available as
* packages is to
wrote:
For the immediate future, it looks like it will -- it seems as though
we don't have the man power to make the necessary changes to sysinstall
to support "installing the docs as packages", so I'm going to fix up
src/release/Makefile as necessary to cope with the new directory
[ cc'd to -current ]
On Sat, Aug 21, 1999 at 07:54:51PM -0400, jack wrote:
mode ugly monolingual American
Will support for building release docs in English only be
revived?
/mode
For the immediate future, it looks like it will -- it seems as though
we don't have the man power to make
For the immediate future, it looks like it will -- it seems as though
we don't have the man power to make the necessary changes to sysinstall
to support "installing the docs as packages", so I'm going to fix up
src/release/Makefile as necessary to cope with the new directory str
It seems Mike Tancsa wrote:
On 24 Feb 1999 18:39:36 -0500, in sentex.lists.freebsd.current you wrote:
Hmm, which suggests that I need to leave the do it by hand code in
there and recommend removing the BIOS :(
Are there any plans to support the Promise Fast Trak IDE RAID controller ?
At 04:49 AM 2/25/99 , Søren Schmidt wrote:
It seems Mike Tancsa wrote:
On 24 Feb 1999 18:39:36 -0500, in sentex.lists.freebsd.current you wrote:
Hmm, which suggests that I need to leave the do it by hand code in
there and recommend removing the BIOS :(
Are there any plans to support the
Well, sortof, the FastTrak is AFAIK the exact same HW as the Ultra33, just
with a more advanced BIOS that does the RAID stuff. The current planned
support is to use it just as a Ultra33 controller, and then use ccd to
do the RAID magic under FreeBSD.
Interesting. So the BIOS doesnt
In 199902230725.caa02...@y.dyson.net, John S. Dyson wrote:
Søren Schmidt said:
It should work, but the promise support in the old system is, well,
hacky at best. I'm not sure if Promise supports more than one card
at a time, but from looking at the chip specs, it should work just
It seems Martin Cracauer wrote:
In 199902230725.caa02...@y.dyson.net, John S. Dyson wrote:
Søren Schmidt said:
It should work, but the promise support in the old system is, well,
hacky at best. I'm not sure if Promise supports more than one card
at a time, but from looking at the
On 24 Feb 1999 18:39:36 -0500, in sentex.lists.freebsd.current you wrote:
Hmm, which suggests that I need to leave the do it by hand code in
there and recommend removing the BIOS :(
Are there any plans to support the Promise Fast Trak IDE RAID controller ?
---Mike
Mike Tancsa
Martin Cracauer said:
In 199902230725.caa02...@y.dyson.net, John S. Dyson wrote:
Søren Schmidt said:
It should work, but the promise support in the old system is, well,
hacky at best. I'm not sure if Promise supports more than one card
at a time, but from looking at the chip
It seems John S. Dyson wrote:
Søren Schmidt said:
It should work, but the promise support in the old system is, well,
hacky at best. I'm not sure if Promise supports more than one card
at a time, but from looking at the chip specs, it should work just
fine, and if the hardware works,
Søren Schmidt said:
It seems John S. Dyson wrote:
Søren Schmidt said:
It should work, but the promise support in the old system is, well,
hacky at best. I'm not sure if Promise supports more than one card
at a time, but from looking at the chip specs, it should work just
fine,
Hi,
I initially intended to ask this to John Dyson, but I don't know how
to reach him. Maybe someone else on this list can anserw :)
I'm looking for documentations about the promise PCI IDE controller,
to add support for this in NetBSD. Does someone know how John got the
informations for the
got the
informations for the FreeBSD support ?
I sent a mail to the support address listed on their www page, but
got nothing back yet ...
You can the docs from their web/ftp site, I did (long ago), bear in
mind that they are pretty limitted, and only provides rudimentary
information
Søren Schmidt writes:
If you have questions, I might be able to answer, having just written
the support for our new ata/atapi system
Is this new ata/atapi system the rumored rewrite of the existing IDE
(i386/isa/wd.c, /pci/ide_pci.c) driver? How close are you to
completion?
I
It seems Andrew Gallatin wrote:
Søren Schmidt writes:
If you have questions, I might be able to answer, having just written
the support for our new ata/atapi system
Is this new ata/atapi system the rumored rewrite of the existing IDE
(i386/isa/wd.c, /pci/ide_pci.c) driver?
Søren Schmidt writes:
Is this new ata/atapi system the rumored rewrite of the existing IDE
(i386/isa/wd.c, /pci/ide_pci.c) driver? How close are you to
completion?
Yes. I have ATA disks running, and I'm close to having the ATAPI
part done also. So far things are looking very
Søren Schmidt said:
It should work, but the promise support in the old system is, well,
hacky at best. I'm not sure if Promise supports more than one card
at a time, but from looking at the chip specs, it should work just
fine, and if the hardware works, at least the new driver will support
60 matches
Mail list logo
