On Thu, 18 Feb 1999, Bruce Evans wrote:
> >cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> >-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
> >-fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include
> >-DKERNEL -include opt_global.h -mno-fp-r
On Wed, 17 Feb 1999, Benjamin Lewis wrote:
> Hello-
>
> I've been trying to get 3.1 or 4.0 to run on a Compaq Professional Workstation
> 6000 with dual PII-300s, using the built-in symbios 53c875 SCSI controller,
> and
> the built-in "ThunderLan" ethernet adapter. The machine works perfectly wi
On Thu, 18 Feb 1999, Michael Reifenberger wrote:
> Hi,
> On Wed, 17 Feb 1999, Benjamin Lewis wrote:
> ...
> > We then tried to boot with the 3.1 and the 4.0 boot floppies. Neither was
> > able to find the SCSI controller or the ethernet device. Of course, we find
> > it odd that 2.2.8 found the
On Thu, 18 Feb 1999, Sheldon Hearn wrote:
>
>
> On Wed, 17 Feb 1999 19:12:59 EST, "John W. DeBoskey" wrote:
>
> > Just fyi, current as of 2pm EST.
> >
> > ../../nfs/nfs_syscalls.c:92: warning: `nfsrv_zapsock' declared `static' but
> > never defined
> > *** Error code 1
>
> I get this when I
Yes I know now... and it does work the only problem now is that
I've only seen it once because I never turn the machine off !! :)
On Tue, 16 Feb 1999, Warner Losh wrote:
> In message Matthew Thyer
> writes:
> : I have "apm" in the kernel and it probes as apm v 1.2 but when
> : the "shutdown
On Thu, 18 Feb 1999 09:21:17 GMT, Doug Rabson wrote:
> It should be fixed now.
Thanks! Kernel's back down 100KB in file size. :-)
Ciao,
Sheldon.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Hi folks,
It seems that newfs_msdos doesn't work on 4.0-current - when I try to
format msdos partition "newfs_msdos /dev/wd0s1" (one created with
sysinstall) my machine after few seconds of disk activity just hangs -
no messages on console, no messages in logs, keyboard blocked (however I
can swit
Nate Williams wrote:
> > @@ -138,9 +138,9 @@
> > usage(msg)
> > char *msg;
> > {
> > - warnx("enabler: %s", msg);
> > + fprintf(stderr, "enabler: %s\n", msg);
> > fprintf(stderr,
> > -"usage: pccardc enabler slot driver [-m addr size] [-a iobase] [-i
> > irq]\n");
> > +"Usa
> > > @@ -138,9 +138,9 @@
> > > usage(msg)
> > > char *msg;
> > > {
> > > - warnx("enabler: %s", msg);
> > > + fprintf(stderr, "enabler: %s\n", msg);
> > > fprintf(stderr,
> > > -"usage: pccardc enabler slot driver [-m addr size] [-a iobase] [-i
> > > irq]\n");
> > > +"Usag
Greetings,
I've begun a series of patches against the 4.0-current tree that I hope you
will find helpful. As this is my first attempt at contributing to freebsd,
I hope you will excuse any potentional ``newbie'' behaviour in the field.
I'm not sure whether or not this has already been done, but
> Basically, it is a patch into libkvm and w, that will allow a user (with
> the exception to the super user, naturally) to only view processes or
> information belonging to him/herself.
> options I_AM_A_PARANOID_GOOD
The only problem with this is setuid binaries. The processes may have
b
huh? can you expand on this...
On Thu, 18 Feb 1999, Sheldon Hearn wrote:
>
>
> On Thu, 18 Feb 1999 09:21:17 GMT, Doug Rabson wrote:
>
> > It should be fixed now.
>
> Thanks! Kernel's back down 100KB in file size. :-)
>
> Ciao,
> Sheldon.
>
>
> To Unsubscribe: send mail to majord...@freebsd
On Thu, 18 Feb 1999 11:54:01 PST, Julian Elischer wrote:
> huh? can you expand on this...
Um, sure.
When my kernel build broke, I tried removing the option NFS_NOSERVER.
This allowed me to build a kernel. After the problem in nfs_syscalls.c
was repaired today (maybe last night), I put the opti
[Expanded audience]
This is a generic problem with the present VFS system and also with some
specific parts of FreeBSD. There is "bleed-over" of all sorts of
parameters from filesystems and devices that they are mounted on and
devices that are sourced from them. (e.g. blocksizes etc.)
luckily at
I'm seeing a problem with uptime in recent -currents which doesn't make any
sense to me.
odin# uptime
uptime: /dev//umount: /proc: not currently mounted
umount:: No such file or directory
uptime: /dev// /var: not currently mounted
umount: /usr: n: No such file or directory
3:24PM up 1 day, 18:17
On Thu, 18 Feb 1999, Sheldon Hearn wrote:
>
>
> On Thu, 18 Feb 1999 11:54:01 PST, Julian Elischer wrote:
>
> > huh? can you expand on this...
>
> Um, sure.
>
> When my kernel build broke, I tried removing the option NFS_NOSERVER.
> This allowed me to build a kernel. After the problem in nfs_s
On Thu, 18 Feb 1999 21:38:37 GMT, Doug Rabson wrote:
> Interesting stats. Can you run size(1) on them too. I wonder how much
> of that is actual code.
Feast your eyes. :-)
textdata bss dec hex filename
1049161 84468 120572 1254201 132339 /kernel
1153284 85752 123692
On Thu, 18 Feb 1999, Doug Rabson wrote:
...
> It may be that we aren't detecting the bridge properly in the 3.1 pci
> code.
dmesg under 2.2.7 shows:
...
eisa0:
Probing for devices on the EISA bus
DPT: EISA SCSI HBA Driver, version 1.4.3
Probing for devices on PCI bus 0:
chip0 rev 3 on pci0:0:0
On Thu, 18 Feb 1999, Michael Reifenberger wrote:
> On Thu, 18 Feb 1999, Doug Rabson wrote:
> ...
> > It may be that we aren't detecting the bridge properly in the 3.1 pci
> > code.
> dmesg under 2.2.7 shows:
> ...
> eisa0:
> Probing for devices on the EISA bus
> DPT: EISA SCSI HBA Driver, versio
On Thu, Feb 18, 1999, Erik Funkenbusch put this into my mailbox:
> I'm seeing a problem with uptime in recent -currents which doesn't make any
> sense to me.
I've had that with 3.0-STABLE, as well. I'm not sure why, but it kept
saying:
uptime: /dev//chris: No such file or directory
... uptim
I am having some performance problems on my -current ( update last weekend)
I hooked up a new Seagate ST36530N yesterday ( connected to an Adaptec 2940U)
and sequential write is very slow.
Compared to an IBM DORS-32160 connected to the same controller ( even the same
cable) it is half as fast.
Io
On Thu, 18 Feb 1999, Chris Costello wrote:
> On Thu, Feb 18, 1999, Erik Funkenbusch put this into my mailbox:
> > I'm seeing a problem with uptime in recent -currents which doesn't make any
> > sense to me.
>
>I've had that with 3.0-STABLE, as well. I'm not sure why, but it kept
> saying:
>
> > Basically, it is a patch into libkvm and w, that will allow a user (with
> > the exception to the super user, naturally) to only view processes or
> > information belonging to him/herself.
> The only problem with this is setuid binaries. The processes may have
> been started by me (top, etc.
Hello,
I am planning to setup my SMP system and want to know if some can share
his/her experience with me. I would like to use AMD K6-2 (for lower price).
is there anyone using AMD K6-2 for your SMP system. If so, please share
your expeience with me. Thanks.
Clarence
To Unsubscribe: send ma
Hi
I cant install the freebsd unix filesystem, i downloaded boot.flp and made the
image to a
floopy, when i shutdown and restart the computer, the boot command prompt
appear,
after a while it automatic shutdown, the kernel configuration dont appear, i
tryied de -cv , d and s command but was
Mike Smith writes:
> > > I usually keep -O to just '-O' - I had been upping it recently, but then
> > > it
> > > started breaking even some of my simple programs, so leasson learn't, it's
> > > staying at just '-O' from now on in... (safety first? :-)
> >
> > -O2 works fine too. -O3 does not. W
I've adjusted MAXUSERS to 128 on my heavily loaded PIIs and the crashes
have not re-occurred for 24 hours now. (Had to adjust NMBCLUSTERS up,
though)
The panics were happening every 5-8 hours like clockwork prior to this.
I believe that these crashes are caused by heavy network traffic, not
heavy
On Thu, Feb 18, 1999 at 07:05:39PM -0500, a little birdie told me
that Brian Feldman remarked
> > On Thu, Feb 18, 1999, Erik Funkenbusch put this into my mailbox:
> > >
> > > Any ideas?
>
> Yes. Look at /var/run/wtmp. Look CAREFULLY at /dev/null.
Look even more carefully at /var/run/utmp, since
On Thu, 18 Feb 1999, Matthew D. Fuller wrote:
> On Thu, Feb 18, 1999 at 07:05:39PM -0500, a little birdie told me
> that Brian Feldman remarked
> > > On Thu, Feb 18, 1999, Erik Funkenbusch put this into my mailbox:
> > > >
> > > > Any ideas?
> >
> > Yes. Look at /var/run/wtmp. Look CAREFULLY at
I am a Student studying Information Systems and I want to added to your current
mailing list. Please add my e-mail address to any list regarding freebsd.
Thank you,
Pat Cahill
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Sounds familiar to me.
I had trouble with a Seagate Wide scsi harddisk in a HP Kajak.
First thought it's the NCR. Repllaces it with a AHA 2940UW.
Nothing helps. Installed FreeBSD 2.2.7.
With 2.2.7 the disk maxed at about 12 MB/sec write and write.
When I enabled tagged command queuing in 2.2.7, th
31 matches
Mail list logo
