On Wed, Aug 04, 1999 at 03:59:00PM -0500, Jonathan Lemon wrote:
> getkerninfo() is depreciated, we use sysctl() instead. In fact, most of
> the information provided by getkerninfo() is implemented in terms of
> sysctl().
> The route(4) manpage says:
>
> User processes can obtain informat
John Polstra wrote:
>Peter Jeremy wrote:
>> Assar Westerlund wrote:
>> >Peter Jeremy writes:
>> >> We need to be able to build an application that has no dynamically
>> >> loaded code for recovery purposes (/stand and /sbin) as well as for
>> >> security.
>> >
>> >Isn't that the same problem a
On Wed, Aug 04, 1999 at 03:59:00PM -0500, Jonathan Lemon wrote:
> getkerninfo() is depreciated, we use sysctl() instead. In fact, most of
> the information provided by getkerninfo() is implemented in terms of
> sysctl().
> The route(4) manpage says:
>
> User processes can obtain informa
John Polstra <[EMAIL PROTECTED]> wrote:
>Peter Jeremy <[EMAIL PROTECTED]> wrote:
>> Assar Westerlund <[EMAIL PROTECTED]> wrote:
>> >Peter Jeremy <[EMAIL PROTECTED]> writes:
>> >> We need to be able to build an application that has no dynamically
>> >> loaded code for recovery purposes (/stand and
In article <99aug5.074611est.40...@border.alcanet.com.au>,
Peter Jeremy wrote:
> Assar Westerlund wrote:
> >Peter Jeremy writes:
> >> We need to be able to build an application that has no dynamically
> >> loaded code for recovery purposes (/stand and /sbin) as well as for
> >> security.
> >
>
Dag-Erling Smorgrav scribbled this message on Aug 4:
> "Kelly Yancey" writes:
> > [...]
>
> Which reminds me - has anyone thought of using DMA for zeroing pages,
> to avoid cache invalidation? The idea is to keep a chunk of zeroes on
> disk and DMA it into memory instead of clearing pages "manual
In article <[EMAIL PROTECTED]>,
Peter Jeremy <[EMAIL PROTECTED]> wrote:
> Assar Westerlund <[EMAIL PROTECTED]> wrote:
> >Peter Jeremy <[EMAIL PROTECTED]> writes:
> >> We need to be able to build an application that has no dynamically
> >> loaded code for recovery purposes (/stand and /sbin) as we
On Wed, Aug 04, 1999 at 01:20:59PM +0200, Dag-Erling Smorgrav wrote:
> "Kelly Yancey" writes:
> > [...]
>
> Which reminds me - has anyone thought of using DMA for zeroing pages,
> to avoid cache invalidation? The idea is to keep a chunk of zeroes on
> disk and DMA it into memory instead of cleari
Dag-Erling Smorgrav scribbled this message on Aug 4:
> "Kelly Yancey" <[EMAIL PROTECTED]> writes:
> > [...]
>
> Which reminds me - has anyone thought of using DMA for zeroing pages,
> to avoid cache invalidation? The idea is to keep a chunk of zeroes on
> disk and DMA it into memory instead of cl
On Wed, 4 Aug 1999, Oscar Bonilla wrote:
[skip]
> 2. Make the C library nsdispatch aware. The dtab[] array will be
>filled dynamicaly from the contents of /etc/nsswitch.conf.
>I'm still not sure if this has to be done "whithin" the C library
>or if nsdispatch should fill the dtab[] arr
On Wed, Aug 04, 1999 at 01:20:59PM +0200, Dag-Erling Smorgrav wrote:
> "Kelly Yancey" <[EMAIL PROTECTED]> writes:
> > [...]
>
> Which reminds me - has anyone thought of using DMA for zeroing pages,
> to avoid cache invalidation? The idea is to keep a chunk of zeroes on
> disk and DMA it into memo
On 04-Aug-99 Matthew Dillon wrote:
> I kinda like the second choice the best but the first choice is what
> most
> other system calls use.
That doesn't make it right =)
The second avoids the 'the data is different but the size is the same' problem
which would seem to be not too uncomm
On Wed, 4 Aug 1999, Oscar Bonilla wrote:
[skip]
> 2. Make the C library nsdispatch aware. The dtab[] array will be
>filled dynamicaly from the contents of /etc/nsswitch.conf.
>I'm still not sure if this has to be done "whithin" the C library
>or if nsdispatch should fill the dtab[] ar
On 04-Aug-99 Matthew Dillon wrote:
> I kinda like the second choice the best but the first choice is what
> most
> other system calls use.
That doesn't make it right =)
The second avoids the 'the data is different but the size is the same' problem
which would seem to be not too uncom
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 majord...@freebsd.org
with "unsubscribe freebsd-hackers" in t
I'm doing some research on resource limits and I can't find any
information at all on the ignoretime capability that's in
/usr/src/etc/login.conf. A 'grep -iR ignoretime *' in /usr/src didn't
return any hits outside of the login.conf files in /usr/src/etc and the
picobsd stuff. Does anyone
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
I'm doing some research on resource limits and I can't find any
information at all on the ignoretime capability that's in
/usr/src/etc/login.conf. A 'grep -iR ignoretime *' in /usr/src didn't
return any hits outside of the login.conf files in /usr/src/etc and the
picobsd stuff. Does anyone
Were there any issues related to a memory leak in the routing table ?
I am running freebsd-stable.
After a few days vmstat -m shows the memory used by routing table to be
very high and log messages "arpresolve: cant allocate llinfo for
a.b.c.d"
"arplookup a.b.c.d failed could not allocate llinfo"
Assar Westerlund wrote:
>Peter Jeremy writes:
>> We need to be able to build an application that has no dynamically
>> loaded code for recovery purposes (/stand and /sbin) as well as for
>> security.
>
>Isn't that the same problem as with PAM?
Quite probably PAM has the same problem. I haven't
In message
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 change in how things tr
Dag-Erling Smorgrav wrote:
>Which reminds me - has anyone thought of using DMA for zeroing pages,
This sounds reasonable. Some DMA engines support filling regions
and memory-memory copies, but I'm not sure about what can be done
with the DMA engine(s) in PCs.
> The idea is to keep a chunk of zer
Were there any issues related to a memory leak in the routing table ?
I am running freebsd-stable.
After a few days vmstat -m shows the memory used by routing table to be
very high and log messages "arpresolve: cant allocate llinfo for
a.b.c.d"
"arplookup a.b.c.d failed could not allocate llinfo"
On Wed, 4 Aug 1999, Warner Losh wrote:
> In message
> 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
Assar Westerlund <[EMAIL PROTECTED]> wrote:
>Peter Jeremy <[EMAIL PROTECTED]> writes:
>> We need to be able to build an application that has no dynamically
>> loaded code for recovery purposes (/stand and /sbin) as well as for
>> security.
>
>Isn't that the same problem as with PAM?
Quite probabl
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
In article
you write:
>-hackers,
>
>As docs/12220 points out;
>
>We want to extract routing information by specifying a particular
>destination IP address. The man page on Route and Rtentry mention
>that this information can be acquired using getkerninfo command. But
>there
Dag-Erling Smorgrav <[EMAIL PROTECTED]> wrote:
>Which reminds me - has anyone thought of using DMA for zeroing pages,
This sounds reasonable. Some DMA engines support filling regions
and memory-memory copies, but I'm not sure about what can be done
with the DMA engine(s) in PCs.
> The idea is to
On Wed, 4 Aug 1999, Warner Losh wrote:
> 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 comp
In message 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
-stable is present in the
In message
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 new kernel, then reb
In article
[EMAIL PROTECTED]> you write:
>-hackers,
>
>As docs/12220 points out;
>
>We want to extract routing information by specifying a particular
>destination IP address. The man page on Route and Rtentry mention
>that this information can be acquired using getkerninfo command.
As Dag-Erling Smorgrav wrote ...
> "Kelly Yancey" writes:
> > [...]
>
> Which reminds me - has anyone thought of using DMA for zeroing pages,
> to avoid cache invalidation? The idea is to keep a chunk of zeroes on
> disk and DMA it into memory instead of clearing pages "manually". This
> assumes
On Wed, 4 Aug 1999, Warner Losh wrote:
>
> 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 complain
On Wed, 4 Aug 1999, Warner Losh wrote:
>
> 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 a
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 Unsubscri
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:
: 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
As Dag-Erling Smorgrav wrote ...
> "Kelly Yancey" <[EMAIL PROTECTED]> writes:
> > [...]
>
> Which reminds me - has anyone thought of using DMA for zeroing pages,
> to avoid cache invalidation? The idea is to keep a chunk of zeroes on
> disk and DMA it into memory instead of clearing pages "manual
On Wed, 4 Aug 1999, Warner Losh wrote:
>
> 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 complai
On Tue, Aug 03, 1999 at 07:52:26PM -0400, Bill Fumerola wrote:
> On Tue, 3 Aug 1999, Ted Faber wrote:
>
> > http://www.sciencedaily.com/releases/1999/08/990802072727.htm
>
> The Duke release credits one Andrew Gallatin for a couple quotes.
>
> Not only FreeBSD in the news, but one of our own com
On Wed, 4 Aug 1999, Warner Losh wrote:
>
> 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
-hackers,
As docs/12220 points out;
We want to extract routing information by specifying a particular
destination IP address. The man page on Route and Rtentry mention
that this information can be acquired using getkerninfo command. But
there is no such man page. Is it possi
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
After collecting a bunch of emails from the list, this is the
approach I'll be taking:
1. use the existing nsdispatch code obtained from NetBSD as a base
for parsing the /etc/nsswitch.conf file.
2. Make the C library nsdispatch aware. The dtab[] array will be
filled dynamicaly from the cont
On Tue, Aug 03, 1999 at 07:52:26PM -0400, Bill Fumerola wrote:
> On Tue, 3 Aug 1999, Ted Faber wrote:
>
> > http://www.sciencedaily.com/releases/1999/08/990802072727.htm
>
> The Duke release credits one Andrew Gallatin for a couple quotes.
>
> Not only FreeBSD in the news, but one of our own co
:The argument for versioning is not simply because the size of ip_number
:might change (it should be a sockaddr) but because other fields might be
:added or removed. To avoid allocating a new syscall whenever this happens,
:the structure should be versioned.
:
:Putting sizeof(whatever) at the begin
-hackers,
As docs/12220 points out;
We want to extract routing information by specifying a particular
destination IP address. The man page on Route and Rtentry mention
that this information can be acquired using getkerninfo command. But
there is no such man page. Is it poss
> > Because most modern BIOSes do CHS translation, the BIOS geometry is
> > not always evident from the geometry reported by the drive, and
> > FreeBSD may get this wrong, particularly if no existing partitions
> > are defined.
> >
> > Since you are installing to a drive with no pre-existing non-F
After collecting a bunch of emails from the list, this is the
approach I'll be taking:
1. use the existing nsdispatch code obtained from NetBSD as a base
for parsing the /etc/nsswitch.conf file.
2. Make the C library nsdispatch aware. The dtab[] array will be
filled dynamicaly from the con
Peter Jeremy writes:
> We need to be able to build an application that has no dynamically
> loaded code for recovery purposes (/stand and /sbin) as well as for
> security.
Isn't that the same problem as with PAM?
/assar
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freeb
"Brian F. Feldman" writes:
> As I read it, sockaddr is a transparent type (overloaded, as it were).
> So we would use something like:
> struct jail {
> ...
> struct sockaddr;
> char [SOCK_MAXADDRLEN - sizeof(struct sockaddr)];
> char [s
Soren Schmidt writes:
> > I started looking at the kernel modules and porting them, however, I
> > must confess that I don't fully understand exactly what the linux
> > kernel module does, which makes it somewhat harder to implement the
> > same functionality on FreeBSD :-)
>
> If you provide an
:The argument for versioning is not simply because the size of ip_number
:might change (it should be a sockaddr) but because other fields might be
:added or removed. To avoid allocating a new syscall whenever this happens,
:the structure should be versioned.
:
:Putting sizeof(whatever) at the begi
On Wed, 4 Aug 1999, Doug Rabson wrote:
> The argument for versioning is not simply because the size of ip_number
> might change (it should be a sockaddr) but because other fields might be
> added or removed. To avoid allocating a new syscall whenever this happens,
> the structure should be version
On 4 Aug 1999, Assar Westerlund wrote:
> "Brian F. Feldman" writes:
> > On Tue, 3 Aug 1999, Mike Smith wrote:
> > >
> > > Actually, with interfaces like this you should generally pass a pointer
> > > to the structure in userspace, and stick a version number constant in
> > > the beginning of t
> > Because most modern BIOSes do CHS translation, the BIOS geometry is
> > not always evident from the geometry reported by the drive, and
> > FreeBSD may get this wrong, particularly if no existing partitions
> > are defined.
> >
> > Since you are installing to a drive with no pre-existing non-
Peter Jeremy <[EMAIL PROTECTED]> writes:
> We need to be able to build an application that has no dynamically
> loaded code for recovery purposes (/stand and /sbin) as well as for
> security.
Isn't that the same problem as with PAM?
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "u
"Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> As I read it, sockaddr is a transparent type (overloaded, as it were).
> So we would use something like:
> struct jail {
> ...
> struct sockaddr;
> char [SOCK_MAXADDRLEN - sizeof(struct sockaddr)];
>
Soren Schmidt <[EMAIL PROTECTED]> writes:
> > I started looking at the kernel modules and porting them, however, I
> > must confess that I don't fully understand exactly what the linux
> > kernel module does, which makes it somewhat harder to implement the
> > same functionality on FreeBSD :-)
>
On Wed, 4 Aug 1999, Doug Rabson wrote:
> The argument for versioning is not simply because the size of ip_number
> might change (it should be a sockaddr) but because other fields might be
> added or removed. To avoid allocating a new syscall whenever this happens,
> the structure should be versio
On 4 Aug 1999, Assar Westerlund wrote:
> "Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> > On Tue, 3 Aug 1999, Mike Smith wrote:
> > >
> > > Actually, with interfaces like this you should generally pass a pointer
> > > to the structure in userspace, and stick a version number constant in
> >
Robert Nordier wrote:
>
> Because most modern BIOSes do CHS translation, the BIOS geometry is
> not always evident from the geometry reported by the drive, and
> FreeBSD may get this wrong, particularly if no existing partitions
> are defined.
>
> Since you are installing to a drive with no pre-e
On Wed, 4 Aug 1999, Alfred Perlstein wrote:
> so one must purchase the program to get the kernel mods, is there
> an evaluation that can be downloaded?
They have all described on website. The program is key-protected, you can
buy a key, or ask for evaluation key, which will work one month.
You n
On Wed, 4 Aug 1999, Milan Kopacka wrote:
> On Wed, 4 Aug 1999, Alfred Perlstein wrote:
>
> > > I started looking at the kernel modules and porting them, however, I
> > > must confess that I don't fully understand exactly what the linux
> > > kernel module does, which makes it somewhat harder to i
On Wed, 4 Aug 1999, Alfred Perlstein wrote:
> > I started looking at the kernel modules and porting them, however, I
> > must confess that I don't fully understand exactly what the linux
> > kernel module does, which makes it somewhat harder to implement the
> > same functionality on FreeBSD :-)
>
I have a really strong urge to submit a PR to make fetch default to passive
mode, instead of requiring a command-line switch ...
In this day and age, with firewalls and NAT abound, it's a bit odd that such
a change has not already been made. Am I missing something? Is there a
reason we haven't d
Robert Nordier wrote:
>
> Because most modern BIOSes do CHS translation, the BIOS geometry is
> not always evident from the geometry reported by the drive, and
> FreeBSD may get this wrong, particularly if no existing partitions
> are defined.
>
> Since you are installing to a drive with no pre-
> > > It's usually best to temporarily change fdisk partition types,
> > > so that sysinstall sees no existing FreeBSD slice on the drive.
> > > However, there may be other problems involved here as well.
> >
> > Hmmm. This sounds a good plan. Would the following then work
> > (I'm using `partitio
On Wed, 4 Aug 1999, Alfred Perlstein wrote:
> so one must purchase the program to get the kernel mods, is there
> an evaluation that can be downloaded?
They have all described on website. The program is key-protected, you can
buy a key, or ask for evaluation key, which will work one month.
You
On 4 Aug 1999, Assar Westerlund wrote:
> Alfred Perlstein writes:
> > I heard they have released the source to the kernel modules needed
> > to run it.
> >
> > why not port them over? :)
>
> I started looking at the kernel modules and porting them, however, I
> must confess that I don't fully u
On Wed, 4 Aug 1999, Milan Kopacka wrote:
> On Wed, 4 Aug 1999, Alfred Perlstein wrote:
>
> > > I started looking at the kernel modules and porting them, however, I
> > > must confess that I don't fully understand exactly what the linux
> > > kernel module does, which makes it somewhat harder to
It seems Assar Westerlund wrote:
> Alfred Perlstein writes:
> > I heard they have released the source to the kernel modules needed
> > to run it.
> >
> > why not port them over? :)
>
> I started looking at the kernel modules and porting them, however, I
> must confess that I don't fully understa
On Wed, 4 Aug 1999, Alfred Perlstein wrote:
> > I started looking at the kernel modules and porting them, however, I
> > must confess that I don't fully understand exactly what the linux
> > kernel module does, which makes it somewhat harder to implement the
> > same functionality on FreeBSD :-)
I have a really strong urge to submit a PR to make fetch default to passive
mode, instead of requiring a command-line switch ...
In this day and age, with firewalls and NAT abound, it's a bit odd that such
a change has not already been made. Am I missing something? Is there a
reason we haven't
Graham Wheeler wrote:
>
> Robert Nordier wrote:
> >
> > It's usually best to temporarily change fdisk partition types,
> > so that sysinstall sees no existing FreeBSD slice on the drive.
> > However, there may be other problems involved here as well.
>
> Hmmm. This sounds a good plan. Would the f
Alfred Perlstein writes:
> I heard they have released the source to the kernel modules needed
> to run it.
>
> why not port them over? :)
I started looking at the kernel modules and porting them, however, I
must confess that I don't fully understand exactly what the linux
kernel module does, whi
> What makes you think you haven't got 80mbps? How would you tell?
Something like this in your dmesg/boot output.
da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing
Enabled
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of
Why does open() at "sys/kern/vfs_syscalls.c" line 1023 call
vfs_object_create() when vnopen() ("sys/kern/vfs_vnops.c" line 174)
already does so?
vfs_object_create checks for this and doesn't leak, but it looks
funny to me.
-Alfred Perlstein - [bri...@rush.net|bri...@wintelcom.net]
systems admin
> > > It's usually best to temporarily change fdisk partition types,
> > > so that sysinstall sees no existing FreeBSD slice on the drive.
> > > However, there may be other problems involved here as well.
> >
> > Hmmm. This sounds a good plan. Would the following then work
> > (I'm using `partiti
On 4 Aug 1999, Assar Westerlund wrote:
> Alfred Perlstein <[EMAIL PROTECTED]> writes:
> > I heard they have released the source to the kernel modules needed
> > to run it.
> >
> > why not port them over? :)
>
> I started looking at the kernel modules and porting them, however, I
> must confess
It seems Assar Westerlund wrote:
> Alfred Perlstein <[EMAIL PROTECTED]> writes:
> > I heard they have released the source to the kernel modules needed
> > to run it.
> >
> > why not port them over? :)
>
> I started looking at the kernel modules and porting them, however, I
> must confess that I
Graham Wheeler wrote:
>
> Robert Nordier wrote:
> >
> > It's usually best to temporarily change fdisk partition types,
> > so that sysinstall sees no existing FreeBSD slice on the drive.
> > However, there may be other problems involved here as well.
>
> Hmmm. This sounds a good plan. Would the
Alfred Perlstein <[EMAIL PROTECTED]> writes:
> I heard they have released the source to the kernel modules needed
> to run it.
>
> why not port them over? :)
I started looking at the kernel modules and porting them, however, I
must confess that I don't fully understand exactly what the linux
ker
> What makes you think you haven't got 80mbps? How would you tell?
Something like this in your dmesg/boot output.
da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing
Enabled
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the
Why does open() at "sys/kern/vfs_syscalls.c" line 1023 call
vfs_object_create() when vnopen() ("sys/kern/vfs_vnops.c" line 174)
already does so?
vfs_object_create checks for this and doesn't leak, but it looks
funny to me.
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
systems admin
Robert Nordier wrote:
>
> It's usually best to temporarily change fdisk partition types,
> so that sysinstall sees no existing FreeBSD slice on the drive.
> However, there may be other problems involved here as well.
Hmmm. This sounds a good plan. Would the following then work
(I'm using `partiti
The 53c141 is an auto-sensing single-ended/LVDS terminator, permitting
you to connect single-ended and LVDS drives to the same cable. It is
transparent.
If you want 80mbps you need
1. a wide LVDS (aka Ultra2 or fast40) drive
2. a wide LVDS terminator
The 40 in the portion of ncr.c you quote is M
> Hey all, I purchased a Tekram DC-390U2W scsi controller to use with
> a FreeBSD server of mine. It uses the NCR 53c141 (and 53c895?)
> chipset(s). I see that ncr.c supports the NCR 53c8xx family of
> chipsets.. which the controller is seen as having a 53c895, which
> only supports 40Mb/sec op
On Wed, 4 Aug 1999, Niall Smart wrote:
> Olivia Cheriton wrote:
> >
> > Niall,
> >
> > VMware will support FreeBSD as a guest operating system, but unfortunately
> > we currently do not have plans to support FreeBSD as a host operating
> > system. I have noted your request of FreeBSD host suppo
d...@flood.ping.uio.no (Dag-Erling Smorgrav) writes:
> Ville-Pertti Keinonen writes:
> > I certainly don't expect any of the available voices to be able to
> > pronounce Finnish names correctly, even with phonetic specifications.
> If the software were *designed* to speak Finnish, I'd expect it
On Wed, 4 Aug 1999, Peter Jeremy wrote:
> Oscar Bonilla wrote:
> >If anyone has any comments, suggestions, etc. I would appreciate it.
>
> Overall, I like the idea of NSS. But, having worked on Solaris 2.x
> for some time, we need to avoid some of the blunders Sun made: The
> biggest problem wi
Hey all, I purchased a Tekram DC-390U2W scsi controller to use with a
FreeBSD server of mine. It uses the NCR 53c141 (and 53c895?) chipset(s). I
see that ncr.c supports the NCR 53c8xx family of chipsets..
which the controller is seen as having a 53c895, which only supports
40Mb/sec operation(?)
Robert Nordier wrote:
>
> It's usually best to temporarily change fdisk partition types,
> so that sysinstall sees no existing FreeBSD slice on the drive.
> However, there may be other problems involved here as well.
Hmmm. This sounds a good plan. Would the following then work
(I'm using `partit
The 53c141 is an auto-sensing single-ended/LVDS terminator, permitting
you to connect single-ended and LVDS drives to the same cable. It is
transparent.
If you want 80mbps you need
1. a wide LVDS (aka Ultra2 or fast40) drive
2. a wide LVDS terminator
The 40 in the portion of ncr.c you quote is
"Kelly Yancey" writes:
> [...]
Which reminds me - has anyone thought of using DMA for zeroing pages,
to avoid cache invalidation? The idea is to keep a chunk of zeroes on
disk and DMA it into memory instead of clearing pages "manually". This
assumes your disk supports DMA, of course.
DES
--
Dag
"Brian F. Feldman" writes:
> On Tue, 3 Aug 1999, Mike Smith wrote:
> >
> > Actually, with interfaces like this you should generally pass a pointer
> > to the structure in userspace, and stick a version number constant in
> > the beginning of the structure. The size is often not enough of a
>
Ville-Pertti Keinonen writes:
> I certainly don't expect any of the available voices to be able to
> pronounce Finnish names correctly, even with phonetic specifications.
If the software were *designed* to speak Finnish, I'd expect it to
cope with Finnish much better than it currently does with E
> Hey all, I purchased a Tekram DC-390U2W scsi controller to use with
> a FreeBSD server of mine. It uses the NCR 53c141 (and 53c895?)
> chipset(s). I see that ncr.c supports the NCR 53c8xx family of
> chipsets.. which the controller is seen as having a 53c895, which
> only supports 40Mb/sec o
> At 8:01 PM +0200 8/3/99, Robert Nordier wrote:
>
> > > - If I select 3.2 at the PowerBoot menu, it comes up
> > > with two messages about "invalid partition", [...]
> > > It seems to want to boot 'da(0,a)/kernel', but if I
> > > type in 'da(0,e)/kernel', then it boots up fi
1 - 100 of 125 matches
Mail list logo
