> Yes, to be consistent with the state of world WRT NFS. Or at least with
> the leader -- Solaris. This has been the default in 3.0-C since the
> am-utils import.
Yeah, well, amd is a whole other ball of wax. That's clearly broken
in both 3.0-stable and 4.0-current and we're going to have to re
At 04:03 PM 1/30/99 -0800, you wrote:
>> > Any ideas why this isn't working? Is it working in -current but not
>-stable?
>>
>
>This led me to believe that he was running -stable and simply
>posted to the wrong group.
I am running -stable. I didn't 'exactly' post to the wrong group. I
posted
>> > sched_yield() is a stub that informs you nicely that it doesn't exist :)
>> > Use the options:
>> > options "P1003_1B"
>> > options "_KPOSIX_PRIORITY_SCHEDULING"
>> > options "_KPOSIX_VERSION=199309L"
>>
>> Peter: is there any harm in enabling these features permanentl
> errors on "current" and checked the amd.conf file it was using.
> Version 3 of NFS seemed to be the default (!) for amd
Yes, to be consistent with the state of world WRT NFS. Or at least with
the leader -- Solaris. This has been the default in 3.0-C since the
am-utils import.
> it to version
> I can't see any way that this could compromise the stability of
> -STABLE, so I agree. Peter committed the change to -CURRENT, so I'll
> leave it to him.
I'd prefer it if you did it - Peter is probably too busy to even
notice this request. :)
- Jordan
To Unsubscribe: send mail to majord...@fr
On Saturday, 30 January 1999 at 16:03:48 -0800, Jake wrote:
>> In -CURRENT it is now:
>>
>> if [ "X$skip_diskconf" != "XYES" -a -n "$vinum_slices" ]; then
>> vinum read $vinum_slices
>> fi
>
> Has this been fixed in -stable?
No.
> There was the problem of $vinum_slices not being initializ
> In -CURRENT it is now:
>
> if [ "X$skip_diskconf" != "XYES" -a -n "$vinum_slices" ]; then
> vinum read $vinum_slices
> fi
Has this been fixed in -stable?
There was the problem of $vinum_slices not being initialized
because it was being used before rc.conf had been sourced.
>
> > Any
Quoth Mike Tancsa:
> Jan 29 21:37:05 ns3 /kernel: file: table is full
>
> I have maxusers set to 128
> ns3# sysctl -a | grep -i files
> kern.maxfiles: 4136
> kern.maxfilesperproc: 4136
Try running `pstat -T' and see what number of file descriptors is
generally in use.
FYI, I've had to bump it u
In article <91639.917702...@zippy.cdrom.com>,
Jordan K. Hubbard wrote:
>
> As of the day before yesterday, I started getting all manner of NFS
> errors on "current" and checked the amd.conf file it was using.
> Version 3 of NFS seemed to be the default (!) for amd so I changed
> it to version 2 a
In article ,
Kris Kennaway wrote:
>
> This fixes the problems I was having with vn devices - at least, I can once
> again cvsup on a vn device, which was guaranteed to fail instantly before.
That's my baby, the ultimate kernel test. I feel so proud. :-)
John
--
John Polstra
On Friday, 29 January 1999 at 22:41:52 -0800, Chris Knight wrote:
> There have been changes to rc and rc.conf lately to autostart Vinum. But
> on my system it does not auto load at start and I wind up manually loading
> the module, reading the config and mounting the volume. Any help if
> figurin
I have a 3.0 STABLE box that under heavy smtp activity is getting
Jan 29 21:37:05 ns3 /kernel: file: table is f
Jan 29 21:37:05 ns3 /kernel: ull
Jan 29 21:37:05 ns3 /kernel: file: table is full
I have maxusers set to 128
ns3# sysctl -a | grep -i files
kern.maxfiles: 4136
kern.maxfilesperproc: 4
Somebody wrote me recently to tell me they were having trouble getting
the Columbia Appletalk package to work with a PCI ethernet card. Looking
through both the Columbia Appletalk code and the kernel, I think the
problem is a general one not necessarily related to a given ethernet
driver. I'm not s
On Fri, 29 Jan 1999, Brian Somers wrote:
> > Would it be possible to add an exponential delay when connecting fails for
> > either reason?
> >
> > I just received my specified phone-bill. It filled 42 pages, with hundreds
> > of calls with a duration of 17 seconds. (Because my modem needs to be
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
> < said:
>
> > sched_yield() is a stub that informs you nicely that it doesn't exist :)
> > Use the options:
> > options "P1003_1B"
> > options "_KPOSIX_PRIORITY_SCHEDULING"
> > options "_KPOSIX_VERSION=199309L"
>
> Peter: is there any harm in enabling these features per
> > Matt, get over it. bde didn't slam *YOU* in the commit messages. You
> > were never mentioned personally. Also, taking your complaint to
> > -current is not proper proceedure for handling grievances.
>
> While this is true, I think the overall point he made was reasonable
> considering how
<
said:
> sched_yield() is a stub that informs you nicely that it doesn't exist :)
> Use the options:
> options "P1003_1B"
> options "_KPOSIX_PRIORITY_SCHEDULING"
> options "_KPOSIX_VERSION=199309L"
Peter: is there any harm in enabling these features permanently?
-GAWoll
On Sat, Jan 30, 1999 at 03:33:26PM -0300, Paulo Fragoso wrote:
> Hi,
>
> I'm trying to install StarOffice 5.0 in my FBSD-3.0-STABLE (26Jan1999).
> When setup is running the kernel reports:
>
> linux_clone(303): Not enabled
> Jan 30 15:05:39 foker /kernel: cmd setup.bin pid 303 tried to use
> non-
On Sat, 30 Jan 1999, Paulo Fragoso wrote:
> Hi,
>
> I'm trying to install StarOffice 5.0 in my FBSD-3.0-STABLE (26Jan1999).
> When setup is running the kernel reports:
>
> linux_clone(303): Not enabled
> Jan 30 15:05:39 foker /kernel: cmd setup.bin pid 303 tried to use
> non-present sched_yield
>
> If I split sigaction(), sigsuspend(), sigpending(), sigprocmask() and
> sigaltstack() into front-end and back-end pieces a-la NetBSD so that
> emulator-specific signal semantics can be imposed without totally
> duplicating those routines inside the emulator (like I did with
> sendit() and rec
Hi,
I'm trying to install StarOffice 5.0 in my FBSD-3.0-STABLE (26Jan1999).
When setup is running the kernel reports:
linux_clone(303): Not enabled
Jan 30 15:05:39 foker /kernel: cmd setup.bin pid 303 tried to use
non-present sched_yield
Jan 30 15:05:53 foker last message repeated 892 times
What
I don't know whether I should file a bug report on this issue.
Consider the following little program:
/* t.c */
#include
#include
int
main( void)
{
sigset_t set;
sigpending( &set);
return 0;
}
Compiling
On Fri, Jan 29, 1999 at 01:23:05AM -0800, Matthew Dillon wrote:
[...]
> Please try this diff ( against RELENG_3 kern/vfs_bio.c ) and
> tell me if it works.
>
> This is for STABLE only. Current already has this patch.
Hello Matthew,
thank you for reviewing vfs_bio.c. Your patch seem
On Sat, 30 Jan 1999, Daren Sefcik wrote:
> I am now up to 4.0 and lkm is not working...
>
> rover# modstat
> modstat: /dev/lkm: Device not configured
>
> I have not used it much but I know it worked with
> my 3.0 system...any pointers would be great.
The lkm system has been superceded by a new
Daniel C. Sobral wrote:
> Robert Nordier wrote:
> >
> > Daniel C. Sobral wrote:
> > >
> > > Y'know, in my computer that F5 is "Drive 0", and the system will not
> > > boot unless I select it first. Selecting it, makes the OSes boot and
> > > F5 disappear.
> >
> > Try the following patch. You can
< said:
> If I split sigaction(), sigsuspend(), sigpending(), sigprocmask() and
> sigaltstack() into front-end and back-end pieces a-la NetBSD so that
> emulator-specific signal semantics can be imposed without totally
> duplicating those routines inside the emulator (like I did with
> sendit() a
Daren Sefcik wrote:
>
> I am now up to 4.0 and lkm is not working...
>
> rover# modstat
> modstat: /dev/lkm: Device not configured
>
> I have not used it much but I know it worked with
> my 3.0 system...any pointers would be great.
My guess: add "option lkm" to your kernel configuration file.
I am now up to 4.0 and lkm is not working...
rover# modstat
modstat: /dev/lkm: Device not configured
I have not used it much but I know it worked with
my 3.0 system...any pointers would be great.
thanks,
Daren
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current
Robert Nordier wrote:
>
> Daniel C. Sobral wrote:
> >
> > Y'know, in my computer that F5 is "Drive 0", and the system will not
> > boot unless I select it first. Selecting it, makes the OSes boot and
> > F5 disappear.
>
> Try the following patch. You can use the utility
[...]
Right on the mark.
Scenario: Two machines, releng3.freebsd.org (running 3.0-stable) and
current.freebsd.org (running 4.0-current). releng3 has all the disk
space and is the NFS server. current is an NFS client and uses
releng3 for its CVS repository, FTP snapshot stashing area, etc.
As of the day before yesterday,
On Sat, 30 Jan 1999, Matthew Dillon wrote:
> This is a tentitive fix for the vn device problems reported earlier.
This fixes the problems I was having with vn devices - at least, I can once
again cvsup on a vn device, which was guaranteed to fail instantly before.
THanks!
Kris
-
(ASP) M
On Sat, 30 Jan 1999, Greg Lehey wrote:
> On Friday, 29 January 1999 at 11:02:48 -0700, Warner Losh wrote:
> >> If I were working on this code written by someone else it'd leave my
> >> editor looking like the top example, that's for sure. I think that
> >> "How easy is it to edit a piece of code
On Fri, Jan 29, 1999 at 04:26:53PM +1100, John Birrell
wrote:
> I can image a new subscriber to this list reading a few of these messages
> and thinking: "why would I want to use an OS developed by these people?".
>
> We spend so much of our time looking up our own collective asses searching
>
In message
, Alfred Perlstein writes
>
>On Thu, 28 Jan 1999, Rod Taylor wrote:
>
>> I have 2 cheap 100mbit nics (rj45 only). Both use the ReaTek 8139 chipset
>> (from the best that I can tell). Both are PCI.
>
>...snip
>
>> Tried to get help in #freebsd in efnet, but no-one had suggestions tha
On Thu, Jan 28, 1999 at 10:33:20PM -0600, Bruce Albrecht
wrote:
> performance at 10 Mbps, but it's a real dog at 100 Mbps. I'm only
> able to achieve 45-50 Mbps throughput with a dual P6-200 machine, and
> it uses nearly 30% of the CPU to do it.
Hmm.. We tried the cards here and got ca 9MB/s o
Daniel C. Sobral wrote:
> Robert Nordier wrote:
> >
> > The boot manager menu, for example
> >
> > F1 FreeBSD
> > F2 UNIX
> > F5 Drive 1
> >
> > Default: F1
>
> Y'know, in my computer that F5 is "Drive 0", and the system will not
> boot unless I select it first. Selecting
This is a tentitive fix for the vn device problems reported earlier.
It has not been well tested. Basically, the vn device tries to
do something different for B_PAGING bp's to get around potential
low-memory deadlocks. Previously this only applied to paging/swapping,
and the s
38 matches
Mail list logo
