As Mike Smith wrote ...
> >
> > Everyone should take a peak at http://www.troll.no/announce/lizard.html
> > if you haven't already. Definately take a look at the screenshots.
> >
> > Lizard is a fully graphical Linux installation for Caldera Systems
> > Open Linux. IMO, having an easy, reliable
As Mike Smith wrote ...
> >
> > Everyone should take a peak at http://www.troll.no/announce/lizard.html
> > if you haven't already. Definately take a look at the screenshots.
> >
> > Lizard is a fully graphical Linux installation for Caldera Systems
> > Open Linux. IMO, having an easy, reliable a
On Thursday, 1 July 1999 at 22:59:56 -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Greg Lehey writes:
>> Is that what you meant?
>
> No. You need to set
> machdep.pccard.pcic_irq
> to be zero in your boot loader.
Yes. Somebody else told me that. I tried it (and confirmed th
On Thursday, 1 July 1999 at 22:59:56 -0600, Warner Losh wrote:
> In message <19990702105346.h87...@freebie.lemis.com> Greg Lehey writes:
>> Is that what you meant?
>
> No. You need to set
> machdep.pccard.pcic_irq
> to be zero in your boot loader.
Yes. Somebody else told me that. I tried
In message <[EMAIL PROTECTED]> Greg Skafte writes:
: I've got an adaptec 1542 card using aha driver and RELENG_3 detects it no
: problems.
OK.
: If I use the adaptec on board utilities it finds my UMAX scanner no probs.
OK.
: when I try to boot the machine hangs just after the waiting for sc
In message <19990701163631.a20...@gras-varg.worldgate.com> Greg Skafte writes:
: I've got an adaptec 1542 card using aha driver and RELENG_3 detects it no
: problems.
OK.
: If I use the adaptec on board utilities it finds my UMAX scanner no probs.
OK.
: when I try to boot the machine hangs ju
In message <[EMAIL PROTECTED]> Greg Lehey writes:
: Is that what you meant?
No. You need to set
machdep.pccard.pcic_irq
to be zero in your boot loader.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <19990702105346.h87...@freebie.lemis.com> Greg Lehey writes:
: Is that what you meant?
No. You need to set
machdep.pccard.pcic_irq
to be zero in your boot loader.
Warner
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the
> Feel free, just don't ask me questions about it since I honestly don't
> have time right now to explain to many hundreds of people how to build
> this stuff. In a nutshell, use egcs to compile everything from the
> following list: turbovision 0.7, qt 1.42, libh 0.1 (see below).
>
> libh is th
On Thu, 1 Jul 1999, Josef Grosch wrote:
> I have done installs on FreeBSD, Redhat, HP/UX, and Solaris and I have to
> say that Redhat is very confusing. FreeBSD does have it's warts but it is
> better than Redhat. HP/UX and Solaris also have their problems, just ask
> Nicole Harrington how she li
> Feel free, just don't ask me questions about it since I honestly don't
> have time right now to explain to many hundreds of people how to build
> this stuff. In a nutshell, use egcs to compile everything from the
> following list: turbovision 0.7, qt 1.42, libh 0.1 (see below).
>
> libh is the
On Thu, 1 Jul 1999, Josef Grosch wrote:
> I have done installs on FreeBSD, Redhat, HP/UX, and Solaris and I have to
> say that Redhat is very confusing. FreeBSD does have it's warts but it is
> better than Redhat. HP/UX and Solaris also have their problems, just ask
> Nicole Harrington how she lik
On Thu, Jul 01, 1999 at 03:18:00PM -0700, Ron 'The InSaNe One' Rosson wrote:
> On Thu, 01 Jul 1999, Matthew Jacob was heard blurting out:
>
> >
> > > That being said... I've heard some of my ex-coworkers (who were all
> > > FreeBSD people when they worked here) come up to me in this impressed
>
On Thu, Jul 01, 1999 at 03:18:00PM -0700, Ron 'The InSaNe One' Rosson wrote:
> On Thu, 01 Jul 1999, Matthew Jacob was heard blurting out:
>
> >
> > > That being said... I've heard some of my ex-coworkers (who were all
> > > FreeBSD people when they worked here) come up to me in this impressed
> >
> Would it be possible to have this code put up for www/ftp or
> something, so that anyone who is interested could have a look?
Feel free, just don't ask me questions about it since I honestly don't
have time right now to explain to many hundreds of people how to build
this stuff. In a nutshell,
> Would it be possible to have this code put up for www/ftp or
> something, so that anyone who is interested could have a look?
Feel free, just don't ask me questions about it since I honestly don't
have time right now to explain to many hundreds of people how to build
this stuff. In a nutshell,
From: "Jordan K. Hubbard" <[EMAIL PROTECTED]>
Subject: Re: Major device number for firewire
Date: Thu, 01 Jul 1999 19:49:29 -0700
Message-ID: <[EMAIL PROTECTED]>
jkh> I assume you mean a major character device number only? You can
jkh> have 127 (decimal).
jkh>
Thanks, I want to get just one
From: "Jordan K. Hubbard"
Subject: Re: Major device number for firewire
Date: Thu, 01 Jul 1999 19:49:29 -0700
Message-ID: <70335.930883...@zippy.cdrom.com>
jkh> I assume you mean a major character device number only? You can
jkh> have 127 (decimal).
jkh>
Thanks, I want to get just one charac
I assume you mean a major character device number only? You can
have 127 (decimal).
Any prediction on when you think this driver will be ready to bring
into -current? It sounds quite promising!
- Jordan
>
> Folks,
>
> I have been developing firewire (IEEE1394) device driver on FreeBSD and
I assume you mean a major character device number only? You can
have 127 (decimal).
Any prediction on when you think this driver will be ready to bring
into -current? It sounds quite promising!
- Jordan
>
> Folks,
>
> I have been developing firewire (IEEE1394) device driver on FreeBSD and
>
On Thu, 1 Jul 1999, Mark J. Taylor wrote:
>
> There is a Linux X server for the Voodoo Banshee, over at:
> http://developer.soundblaster.com/linux/
>
> You might have some luck running it under the Linux emulator.
> I've never tried it, as I don't have a Banshee.
Thanks! This appears to wor
On Thu, 1 Jul 1999, Mark J. Taylor wrote:
>
> There is a Linux X server for the Voodoo Banshee, over at:
> http://developer.soundblaster.com/linux/
>
> You might have some luck running it under the Linux emulator.
> I've never tried it, as I don't have a Banshee.
Thanks! This appears to work
Folks,
I have been developing firewire (IEEE1394) device driver on FreeBSD and
the driver is working quite stable. I would like to reserve major
device number for firewire.
P.S.
The driver code can be obtained from following:
ftp://ftp.uec.ac.jp/pub/firewire
Folks,
I have been developing firewire (IEEE1394) device driver on FreeBSD and
the driver is working quite stable. I would like to reserve major
device number for firewire.
P.S.
The driver code can be obtained from following:
ftp://ftp.uec.ac.jp/pub/firewire
On Thursday, 1 July 1999 at 18:47:27 -0500, Stan Shkolnyy wrote:
> Hello All,
>
> Well, I entered 'gdb', then 'continue' and now I can debug the kernel
> remotely. How do I switch DDB back? Ctrl-Alt-Esc now causes DDB to
> contact the remote GDB instead of accepting input from me.
A nuisance, is
On Thursday, 1 July 1999 at 18:47:27 -0500, Stan Shkolnyy wrote:
> Hello All,
>
> Well, I entered 'gdb', then 'continue' and now I can debug the kernel
> remotely. How do I switch DDB back? Ctrl-Alt-Esc now causes DDB to
> contact the remote GDB instead of accepting input from me.
A nuisance, isn
On Thursday, 1 July 1999 at 13:08:11 -0700, Mike Smith wrote:
>>
>> Indeed. Is it possibly interrupting on a line which something else is
>> using? I've found a problem on my Latitude where it appears that the
>> machine only has two interrupts free (3 and 9). If I put a modem on 3
>> and an E
On Thursday, 1 July 1999 at 13:08:11 -0700, Mike Smith wrote:
>>
>> Indeed. Is it possibly interrupting on a line which something else is
>> using? I've found a problem on my Latitude where it appears that the
>> machine only has two interrupts free (3 and 9). If I put a modem on 3
>> and an Et
>>If the mapping is being done via a device mapping, then the region will
>> be marked non-cacheable.
>
>I remember that he said he created a character device /dev/tulip to
>represent the network card. Actually, his work borrowed a lot from the
>Cornell U-Net project (now the basis of VIA?). C
>>If the mapping is being done via a device mapping, then the region will
>> be marked non-cacheable.
>
>I remember that he said he created a character device /dev/tulip to
>represent the network card. Actually, his work borrowed a lot from the
>Cornell U-Net project (now the basis of VIA?). Ca
Hello All,
Well, I entered 'gdb', then 'continue' and now I can debug the kernel
remotely. How do I switch DDB back? Ctrl-Alt-Esc now causes DDB to
contact the remote GDB instead of accepting input from me.
Thank you,
Stan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe free
Hello All,
Well, I entered 'gdb', then 'continue' and now I can debug the kernel
remotely. How do I switch DDB back? Ctrl-Alt-Esc now causes DDB to
contact the remote GDB instead of accepting input from me.
Thank you,
Stan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe f
Julian Elischer writes:
> a bit late
> you should check teh cvs rep for these files..
> peter's already checked it in... :-)
>
Wow, he's fast. ;-) I should have checked my committers folder
sooner..
Thanks Peter.
Cheers,
Drew
---
Julian Elischer writes:
> a bit late
> you should check teh cvs rep for these files..
> peter's already checked it in... :-)
>
Wow, he's fast. ;-) I should have checked my committers folder
sooner..
Thanks Peter.
Cheers,
Drew
> a bit late
> you should check teh cvs rep for these files..
> peter's already checked it in... :-)
Don't count on Peter's changes; I'm going to try to beat them up again.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\-- J
> a bit late
> you should check teh cvs rep for these files..
> peter's already checked it in... :-)
Don't count on Peter's changes; I'm going to try to beat them up again.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ msm...@freebsd.org
\\-- J
On Wed, Jun 30, 1999 at 08:02:06PM -0500, Stan Shkolnyy wrote:
> On Wed, 30 Jun 1999, Nik Clayton wrote:
> > Sorry it's taken me a while to reply to this; ironically, most of my time
> > has been spent on freebsd-doc recently.
> >
> > On Sat, Jun 26, 1999 at 12:03:59PM -0500, Constantine Shkolny
On Wed, Jun 30, 1999 at 08:02:06PM -0500, Stan Shkolnyy wrote:
> On Wed, 30 Jun 1999, Nik Clayton wrote:
> > Sorry it's taken me a while to reply to this; ironically, most of my time
> > has been spent on freebsd-doc recently.
> >
> > On Sat, Jun 26, 1999 at 12:03:59PM -0500, Constantine Shkolny w
a bit late
you should check teh cvs rep for these files..
peter's already checked it in... :-)
On Thu, 1 Jul 1999, Andrew Gallatin wrote:
>
> Peter Wemm writes:
>
> Peter,
>
> Thanks for the details. I wasn't sure if it was something that was
> supposed to work... I assume it still wor
a bit late
you should check teh cvs rep for these files..
peter's already checked it in... :-)
On Thu, 1 Jul 1999, Andrew Gallatin wrote:
>
> Peter Wemm writes:
>
> Peter,
>
> Thanks for the details. I wasn't sure if it was something that was
> supposed to work... I assume it still work
On Thu, 1 Jul 1999, David Greenman wrote:
> >A graduate student here implements a mmap() interface to a TCP/IP network
> >card. He notices that it takes much longer time to copy from mmapp()'ed
> >area to another user area than it takes to copy the same amount of data
> >from kernel space to us
On Thu, 1 Jul 1999, David Greenman wrote:
> >A graduate student here implements a mmap() interface to a TCP/IP network
> >card. He notices that it takes much longer time to copy from mmapp()'ed
> >area to another user area than it takes to copy the same amount of data
> >from kernel space to use
Peter Wemm writes:
Peter,
Thanks for the details. I wasn't sure if it was something that was
supposed to work... I assume it still works when built in by config &
should be left in place for that reason though, right? (haven't tried
it here..)
> Personally, I think we should use a kernel e
Peter Wemm writes:
Peter,
Thanks for the details. I wasn't sure if it was something that was
supposed to work... I assume it still works when built in by config &
should be left in place for that reason though, right? (haven't tried
it here..)
> Personally, I think we should use a kernel en
>A graduate student here implements a mmap() interface to a TCP/IP network
>card. He notices that it takes much longer time to copy from mmapp()'ed
>area to another user area than it takes to copy the same amount of data
>from kernel space to user space. The students here have no idea why this
>c
>A graduate student here implements a mmap() interface to a TCP/IP network
>card. He notices that it takes much longer time to copy from mmapp()'ed
>area to another user area than it takes to copy the same amount of data
>from kernel space to user space. The students here have no idea why this
>co
hmm
Unfortunatly Linux is nt relevent to FreeBSD so we can't comment
directly..
it is possible that the mmapped region is marked non-cachable,
which migh tmake a difference.
I have no idea where "memcpy_to_iovec" in Linux is copying to
so it's hard to comment.
julian
On Thu, 1 Jul 1999, Zhih
hmm
Unfortunatly Linux is nt relevent to FreeBSD so we can't comment
directly..
it is possible that the mmapped region is marked non-cachable,
which migh tmake a difference.
I have no idea where "memcpy_to_iovec" in Linux is copying to
so it's hard to comment.
julian
On Thu, 1 Jul 1999, Zhihu
A graduate student here implements a mmap() interface to a TCP/IP network
card. He notices that it takes much longer time to copy from mmapp()'ed
area to another user area than it takes to copy the same amount of data
from kernel space to user space. The students here have no idea why this
could
A graduate student here implements a mmap() interface to a TCP/IP network
card. He notices that it takes much longer time to copy from mmapp()'ed
area to another user area than it takes to copy the same amount of data
from kernel space to user space. The students here have no idea why this
could
There is a Linux X server for the Voodoo Banshee, over at:
http://developer.soundblaster.com/linux/
You might have some luck running it under the Linux emulator.
I've never tried it, as I don't have a Banshee.
-Mark Taylor
NetMAX Developer
[EMAIL PROTECTED]
http://www.netmax.com/
On 01-Ju
There is a Linux X server for the Voodoo Banshee, over at:
http://developer.soundblaster.com/linux/
You might have some luck running it under the Linux emulator.
I've never tried it, as I don't have a Banshee.
-Mark Taylor
NetMAX Developer
mtay...@cybernet.com
http://www.netmax.com/
On 01-
Mike Smith wrote:
> > Personally, I think we should use a kernel environment variable passed in
> > from loader, since kern_envp is available *real early*, from the very
> > beginning of init386(), which is called form locore just after going
> > virtual. It needs a couple of tweaks to get this t
Mike Smith wrote:
> > Personally, I think we should use a kernel environment variable passed in
> > from loader, since kern_envp is available *real early*, from the very
> > beginning of init386(), which is called form locore just after going
> > virtual. It needs a couple of tweaks to get this to
I've been messing around for awhile, and I'm confused (go figure).
I've got an adaptec 1542 card using aha driver and RELENG_3 detects it no
problems.
If I use the adaptec on board utilities it finds my UMAX scanner no probs.
when I try to boot the machine hangs just after the waiting for scs
I've been messing around for awhile, and I'm confused (go figure).
I've got an adaptec 1542 card using aha driver and RELENG_3 detects it no
problems.
If I use the adaptec on board utilities it finds my UMAX scanner no probs.
when I try to boot the machine hangs just after the waiting for scsi
On Thu, 1 Jul 1999, Leif Neland wrote:
> Does anyone have any inside information on subj?
> The website still claims: "We are planning to release 3.3.4 some time in
> June 1999"
>
> I'm longing to get support for my S3 Trio3D.
Heh. It now says early july. I have a Voodoo Banshee I want to use
On Thu, 1 Jul 1999, Leif Neland wrote:
> Does anyone have any inside information on subj?
> The website still claims: "We are planning to release 3.3.4 some time in
> June 1999"
>
> I'm longing to get support for my S3 Trio3D.
Heh. It now says early july. I have a Voodoo Banshee I want to use.
>
> > That being said... I've heard some of my ex-coworkers (who were all
> > FreeBSD people when they worked here) come up to me in this impressed
> > tone: "You wouldn't believe how much easier it is to install RedHat!'.
> > *sigh* I'm not bitching... just being loyal :)
>
> That's ridiculous.
>
> > That being said... I've heard some of my ex-coworkers (who were all
> > FreeBSD people when they worked here) come up to me in this impressed
> > tone: "You wouldn't believe how much easier it is to install RedHat!'.
> > *sigh* I'm not bitching... just being loyal :)
>
> That's ridiculous.
> Personally, I think we should use a kernel environment variable passed in
> from loader, since kern_envp is available *real early*, from the very
> beginning of init386(), which is called form locore just after going
> virtual. It needs a couple of tweaks to get this to work, and in
> particula
On Thu, 01 Jul 1999, Matthew Jacob was heard blurting out:
>
> > That being said... I've heard some of my ex-coworkers (who were all
> > FreeBSD people when they worked here) come up to me in this impressed
> > tone: "You wouldn't believe how much easier it is to install RedHat!'.
> > *sigh* I'm
> Personally, I think we should use a kernel environment variable passed in
> from loader, since kern_envp is available *real early*, from the very
> beginning of init386(), which is called form locore just after going
> virtual. It needs a couple of tweaks to get this to work, and in
> particular
On Thu, 01 Jul 1999, Matthew Jacob was heard blurting out:
>
> > That being said... I've heard some of my ex-coworkers (who were all
> > FreeBSD people when they worked here) come up to me in this impressed
> > tone: "You wouldn't believe how much easier it is to install RedHat!'.
> > *sigh* I'm
> That being said... I've heard some of my ex-coworkers (who were all
> FreeBSD people when they worked here) come up to me in this impressed
> tone: "You wouldn't believe how much easier it is to install RedHat!'.
> *sigh* I'm not bitching... just being loyal :)
That's ridiculous. I've used bot
> That being said... I've heard some of my ex-coworkers (who were all
> FreeBSD people when they worked here) come up to me in this impressed
> tone: "You wouldn't believe how much easier it is to install RedHat!'.
> *sigh* I'm not bitching... just being loyal :)
That's ridiculous. I've used both
> > Everyone should take a peak at http://www.troll.no/announce/lizard.html
> > if you haven't already. Definately take a look at the screenshots.
> >
> > Lizard is a fully graphical Linux installation for Caldera Systems
> > Open Linux. IMO, having an easy, reliable and attractive installer
> >
> > Everyone should take a peak at http://www.troll.no/announce/lizard.html
> > if you haven't already. Definately take a look at the screenshots.
> >
> > Lizard is a fully graphical Linux installation for Caldera Systems
> > Open Linux. IMO, having an easy, reliable and attractive installer
> > i
>
> Everyone should take a peak at http://www.troll.no/announce/lizard.html
> if you haven't already. Definately take a look at the screenshots.
>
> Lizard is a fully graphical Linux installation for Caldera Systems
> Open Linux. IMO, having an easy, reliable and attractive installer
> is an exc
>
> Everyone should take a peak at http://www.troll.no/announce/lizard.html
> if you haven't already. Definately take a look at the screenshots.
>
> Lizard is a fully graphical Linux installation for Caldera Systems
> Open Linux. IMO, having an easy, reliable and attractive installer
> is an exce
Does anyone have any inside information on subj?
The website still claims: "We are planning to release 3.3.4 some time in
June 1999"
I'm longing to get support for my S3 Trio3D.
Leif
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Does anyone have any inside information on subj?
The website still claims: "We are planning to release 3.3.4 some time in
June 1999"
I'm longing to get support for my S3 Trio3D.
Leif
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the messa
>
> Indeed. Is it possibly interrupting on a line which something else is
> using? I've found a problem on my Latitude where it appears that the
> machine only has two interrupts free (3 and 9). If I put a modem on 3
> and an Ethernet board on 9, it works, but only by putting pccardd on
> irq
>
> Indeed. Is it possibly interrupting on a line which something else is
> using? I've found a problem on my Latitude where it appears that the
> machine only has two interrupts free (3 and 9). If I put a modem on 3
> and an Ethernet board on 9, it works, but only by putting pccardd on
> irq 5
I am very happy to report that with the recent commits to -current
I can now run my script that reads some 16000 small files in over NFS
links at full speed and to completion without locking the box. *BSEG*
Many, many thanks for this, it was a huge area of concern for my
boss that
I am very happy to report that with the recent commits to -current
I can now run my script that reads some 16000 small files in over NFS
links at full speed and to completion without locking the box. *BSEG*
Many, many thanks for this, it was a huge area of concern for my
boss that
> My bad, as the current generation says, and it's a major item on my
> TODO list to spend about 2 days pouring through his code and
> generating a comprehensive set of comments about where to go from
> there. Unfortunately, this code is also in the very early stages and
> represents about 34,00
> My bad, as the current generation says, and it's a major item on my
> TODO list to spend about 2 days pouring through his code and
> generating a comprehensive set of comments about where to go from
> there. Unfortunately, this code is also in the very early stages and
> represents about 34,000
> > What actual marketing information do we actually have that says that in
> > order to go after the desktops we aren't currently installed on we have to
> > add a lot of engineering effort to the installer? Would it be better to
>
> Well, just to clear up what looks like a misunderstanding in
> > What actual marketing information do we actually have that says that in
> > order to go after the desktops we aren't currently installed on we have to
> > add a lot of engineering effort to the installer? Would it be better to
>
> Well, just to clear up what looks like a misunderstanding in t
> What actual marketing information do we actually have that says that in
> order to go after the desktops we aren't currently installed on we have to
> add a lot of engineering effort to the installer? Would it be better to
Well, just to clear up what looks like a misunderstanding in the
making,
> What actual marketing information do we actually have that says that in
> order to go after the desktops we aren't currently installed on we have to
> add a lot of engineering effort to the installer? Would it be better to
Well, just to clear up what looks like a misunderstanding in the
making,
>OK, I'll add a few comments to this.
And I'll respond... The actual pros and cons of the current installer and
what a new one would look like is not the real question to answer here,...
I have to say that what we have isn't that bad- it fails only in some
areas where it violates the principle
>OK, I'll add a few comments to this.
And I'll respond... The actual pros and cons of the current installer and
what a new one would look like is not the real question to answer here,...
I have to say that what we have isn't that bad- it fails only in some
areas where it violates the principle o
> through so-called "spiffy" installs is growing exponentially. Keeping a
> simple interface rather than trying to play human engineering with no
> real human interfaces lab and a 500K$ testing budget might be better.
> Just my 2 cents... I'll shut up now... (I mean, why should *I* beef so
> much?
> through so-called "spiffy" installs is growing exponentially. Keeping a
> simple interface rather than trying to play human engineering with no
> real human interfaces lab and a 500K$ testing budget might be better.
> Just my 2 cents... I'll shut up now... (I mean, why should *I* beef so
> much?
In article [EMAIL PROTECTED]>
you write:
>Personally, I think we should use a kernel environment variable passed in
>from loader, since kern_envp is available *real early*, from the very
>beginning of init386(), which is called form locore just after going
>virtual. It needs a couple of tweaks t
In article
you
write:
>Personally, I think we should use a kernel environment variable passed in
>from loader, since kern_envp is available *real early*, from the very
>beginning of init386(), which is called form locore just after going
>virtual. It needs a couple of tweaks to get this to work
> if it gave me lots more diagnostics. Joe Average, on the other hand,
> likes a spiffy, clean interface. We try to accomodate both types by
> having a simplistic install and then some detail output on a seperate
> VTY. This could still be done with an even spiffier graphical installation
> on th
> if it gave me lots more diagnostics. Joe Average, on the other hand,
> likes a spiffy, clean interface. We try to accomodate both types by
> having a simplistic install and then some detail output on a seperate
> VTY. This could still be done with an even spiffier graphical installation
> on the
True... But such a configuration doesn't preclude the use of a more
detailed listing on vty1 the way we do it now. With our current installation
setup its similar to this already. Its text based and some of the
menus are not exactly intuitive (No... I don't have a better suggestion
just yet). If
True... But such a configuration doesn't preclude the use of a more
detailed listing on vty1 the way we do it now. With our current installation
setup its similar to this already. Its text based and some of the
menus are not exactly intuitive (No... I don't have a better suggestion
just yet). If s
Reminds me of SCO. I personally don't much like it- it makes it harder
than hell to figure out what's gone wrong when it doesn't work.
On Thu, 1 Jul 1999, Steve Ames wrote:
>
> Everyone should take a peak at http://www.troll.no/announce/lizard.html
> if you haven't already. Definately take a l
Reminds me of SCO. I personally don't much like it- it makes it harder
than hell to figure out what's gone wrong when it doesn't work.
On Thu, 1 Jul 1999, Steve Ames wrote:
>
> Everyone should take a peak at http://www.troll.no/announce/lizard.html
> if you haven't already. Definately take a lo
Andrew Gallatin wrote:
>
> I have a user with a need to run a machine in varying memory
> configurations. The machine has 512MB & she needs to artificially
> constrain memory to multiples of 32MB from 32MB to 512MB. (32MB, 64MB,
> 96MB, 128MB ...)
>
> I was planning on having her edit /kernel.
Andrew Gallatin wrote:
>
> I have a user with a need to run a machine in varying memory
> configurations. The machine has 512MB & she needs to artificially
> constrain memory to multiples of 32MB from 32MB to 512MB. (32MB, 64MB,
> 96MB, 128MB ...)
>
> I was planning on having her edit /kernel.c
I have a user with a need to run a machine in varying memory
configurations. The machine has 512MB & she needs to artificially
constrain memory to multiples of 32MB from 32MB to 512MB. (32MB, 64MB,
96MB, 128MB ...)
I was planning on having her edit /kernel.config & change the value of
iosize n
I have a user with a need to run a machine in varying memory
configurations. The machine has 512MB & she needs to artificially
constrain memory to multiples of 32MB from 32MB to 512MB. (32MB, 64MB,
96MB, 128MB ...)
I was planning on having her edit /kernel.config & change the value of
iosize np
In article [EMAIL PROTECTED]>
you write:
>On Wed, 30 Jun 1999, Jonathan Lemon was heard blurting out:
>
>> In article
>[EMAIL PROTECTED]>
> you write:
>> >I don't seem to see support for GRE (IP-in-IP encaspulation) in FreeBSD
>> >(although I might be blind)...anyone working on support it or is t
In article
you
write:
>On Wed, 30 Jun 1999, Jonathan Lemon was heard blurting out:
>
>> In article
>
> you write:
>> >I don't seem to see support for GRE (IP-in-IP encaspulation) in FreeBSD
>> >(although I might be blind)...anyone working on support it or is there
>> >already an implementation?
1 - 100 of 120 matches
Mail list logo
