It seems David Dawes wrote:
>
> >> >I also run the card without its BIOS, as that tends to get in the way.
> >> >I think the FastTrack is just an Ultra/33 with another BIOS chip on it.
> >>
> >> I'll try pulling the BIOS tomorrow. We didn't get this card for it's
> >> RAID features anyway.
> >
>
Peter Jeremy wrote:
> Mike Smith wrote:
> >> The kernel has been built with gcc-2.8.1 -O2.
> >
> >Please rebuild with the system compiler and -O at most.
>
> It makes no difference. The kernel loads and runs happily from the
> old bootloader, but crashes with /boot/loader. (I disabled my
> gcc-
Mike Smith writes:
> I just committed a tweak that allows you to say:
>
> set kern.vm.kmem.size=
>
> at the loader prompt or in /boot/loader.rc to override the default
> VM_KMEM_SIZE value.
>
> If anyone has any more of these tunables that can easily be enhanced
> like this, please let
On Fri, Jan 22, 1999 at 11:43:56AM +1100, Gregory Bond wrote:
> my vote: A version of the standard keymap with CapsLock and LeftCtl
> functions swapped so the control key is under my left finger like God
> intended!
Take your existing keymap and swap 029 and 058 with these:
029 clock clock
Peter Jeremy wrote:
> Mark Blackman wrote:
> >FWIW, I've done it under 2.2.7 by
> >
> >1) installing booteasy on both wd0 *AND* wd2
> >2) altering the boot.config to
> > 1:wd(2,a)kernel
>
> This works for an a.out 3.0 kernel, but the old bootloader can't handle
> ELF kernels, so this isn't a u
yes matt said that it was broken...
On Thu, 21 Jan 1999, Christian Kuhtz wrote:
>
> Looks like top's broken. It no longer shows swap space status on 4.0-CURRENT.
> Side effect of the VM update?
>
> --
> "Logic is a little bird, sitting in a tree; that smells *awful*."
>
Kazutaka YOKOTA wrote:
> ScrollLock does "back scroll" too. You want both?
My Libretto 70CT has no Scroll Lock, only a Pause.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of t
d...@tar.com said:
%For kernel threading you just use libc. Whether or not libc generates
% thread safe (re-entrant) calls depends on whether its also linked
%with a library that 1) sets __isthreaded to a non-zero value, 2) has a
%_spinlock() implementationm, and 3) implements the functions
%flock
I have modified sysinstall to include support for the Finnish
keyboards. (I know, we had a discussion less than 1 year ago
about the Swedish and the Finnish keyboards :-) I hope this
gets in 3.1-RELEASE as some Finnish users may be unaware of
the fact that they might use the Swedish keyboard settin
On Fri, 22 Jan 1999, Gregory Bond wrote:
> my vote: A version of the standard keymap with CapsLock and LeftCtl
> functions
> swapped so the control key is under my left finger like God intended!
My vote is both of the above. I've never found a use for CapsLock, but
LeftCtl is important enough
On Thu, 21 Jan 1999, Jaye Mathisen wrote:
>
> The readme in /usr/share/examples hasn't been updated in a while...
>
> WHat tag should I be using now to track 3.0-current/3.1? (Not the 4.x
> branch).
>
> Right now, I have tag=., and I can't get a compilable kernel to save my
> life, problems in
On Thu, Jan 21, 1999 at 23:03:45 +, Tim wrote:
> How do I set up the CSN now as I get CSN 1 disabled and CSN 2 disabled
> on boot.
you can put this pnp information in /kernel.config
and, in your /boot/boot.conf, put
load /kernel
load -t userconfig_script /kernel.config
boot
this works fine o
> :Execute anything from NFS would result in an "Input/output error", but if I
> do
> :a hexdump of the executable first, the execution would be successful. If I
> :reverse the order, i.e., execute first then hexdump, execution would fail and
> :hexdump would hang at "pgtblk". No problem with FFS.
> Mike Smith writes:
>
> > I just committed a tweak that allows you to say:
> >
> > set kern.vm.kmem.size=
> >
> > at the loader prompt or in /boot/loader.rc to override the default
> > VM_KMEM_SIZE value.
> >
> > If anyone has any more of these tunables that can easily be enhanced
> > l
:With NFS v3 there seem still to be some open issues.
:Im running the latest (4.0)-current with the new vm/NFS changes.
:While I haven't found any problems with NFSv2 so far, v3 still seems to make
:trouble.
:
:I noticed the error some months ago, while my /usr/obj was NFS mounted, and
:a build fai
Hi,
after todays build I wasn't able to login:
Instead of installing libdescrypt.* and linking libcrypt.* to libdescrypt.*
I suddenly got libexpcrypt.* files, with no DES code in.
It seems the international secure distribution isn't in sync any more.
I am missing /usr/src/secure/lib/libcrypt/crypt
On Thursday, 21 January 1999 at 21:23:52 -0500, Christian Kuhtz wrote:
>
> Looks like top's broken. It no longer shows swap space status on 4.0-CURRENT.
> Side effect of the VM update?
Yup. Matt announced it.
Greg
--
See complete headers for address, home page and phone numbers
finger g...@lemi
:
:Looks like top's broken. It no longer shows swap space status on 4.0-CURRENT.
:Side effect of the VM update?
Yes. I've only made pstat -s ( aka swapinfo ) work so far.
systat -swap is also broken. Both are on my TODO list.
-Matt
In message <199901220043.laa22...@lightning.itga.com.au> Gregory Bond writes:
: my vote: A version of the standard keymap with CapsLock and LeftCtl
: functions swapped so the control key is under my left finger like
: God intended!
What's wrong with us.unix.kbd?
Warner
To Unsubscribe: send mail
Mike Smith wrote:
>> The kernel has been built with gcc-2.8.1 -O2.
>
>Please rebuild with the system compiler and -O at most.
It makes no difference. The kernel loads and runs happily from the
old bootloader, but crashes with /boot/loader. (I disabled my
gcc-2.8.1, changed make.conf to -O, re-r
What is the trick to get past this problem? Or can a release not be
made as before?
Thanks a lot,
ed
disklabel: ioctl DIOCWLABEL: Operation not supported by device
Warning: Block size restricts cylinders per group to 4.
Warning: 2880 sector(s) in last cylinder unallocated
/dev/rvn0c: 2880 s
Looks like top's broken. It no longer shows swap space status on 4.0-CURRENT.
Side effect of the VM update?
--
"Logic is a little bird, sitting in a tree; that smells *awful*."
-- /usr/bin/fortune
[Disclaimer: I speak for myself and m
It's time to do a functional split on boot.flp / kern+mfsroot.flp
builds. Hmmm. What to axe.. Let me thwap on this a bit over
the weekend. :)
- Jordan
>
> Looks like the Alpha AXP boot floppy has bitten the dust also:
>
> Making the regular boot floppy.
> Compressing doc files...
> disklabel
:Execute anything from NFS would result in an "Input/output error", but if I do
:a hexdump of the executable first, the execution would be successful. If I
:reverse the order, i.e., execute first then hexdump, execution would fail and
:hexdump would hang at "pgtblk". No problem with FFS.
:
:-lq
On Thu, Jan 21, 1999 at 02:06:22PM +0100, Søren Schmidt wrote:
>It seems David Dawes wrote:
>>
>> That didn't improve things, but with the patch I got lots of messages
>> like the following (for a disk attached to the onboard PIIX4):
>>
>> wd1: DMA failure, DMA status 0
>>
>> (The box isn't SMP
Execute anything from NFS would result in an "Input/output error", but if I do
a hexdump of the executable first, the execution would be successful. If I
reverse the order, i.e., execute first then hexdump, execution would fail and
hexdump would hang at "pgtblk". No problem with FFS.
-lq
To Unsub
my vote: A version of the standard keymap with CapsLock and LeftCtl functions
swapped so the control key is under my left finger like God intended!
Greg,
home of us.iso-lock-ctl.kbd
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
The recent changes to src/secure/libcrypt have severely broken
"make buildworld". Can some please back out the recent changes,
and give to the committer named "brandon" a pointed hat?
PS: This makes my attempt to test Matt's VM change rather difficult.
--
Steve
finger ka...@troutmask.apl.washi
> The kernel has been built with gcc-2.8.1 -O2.
Please rebuild with the system compiler and -O at most. We're
hard-pressed enough as it is to support our own software without
introducing complete unknowns into the equation.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you
"Daniel C. Sobral" wrote:
>Well, kind of. You "hard code" the name wd2 in your kernel
>configuration file. [...] Ie, s/wd2/wd1/
> in your kernel configuration file (and rebuild :).
It was wd0 (the generic). Making it wd2 didn't help.
Mark Blackman wrote:
>FWIW, I've done it under 2.2.7 by
>
>1)
Splitting the thread...
"Daniel C. Sobral" wrote:
>> /boot/loader could load my 2.x kernel (although it happily handled
> ^^
>You mean "could not", right?
That's correct.
>Is it kzipped, your 2.x kernel? (Is there any detail about it that
>you think it is not relevant? :-)
>> 104 Pause Start screen saver (saver).
>:
>> The above assignments for the keycodes 1, 57, 70, 84 and 92 are
>> compatible with many, if not all, existing keymaps.
>
>So far so good!
>
>> The assignments for 104 and 108 are new.
>
>104 (Pause?) does the "Backscroll" on
> On Thu, Jan 21, 1999 at 12:26:04PM -0800, Steve Kargl wrote:
> > cd /usr/src/secure/lib/libcrypt; /usr/obj/usr/src/tmp/usr/bin/make
> > -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend;
> > /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE
> > -DNOSHARED all;
Hi,
I am currently running 3.0-RELEASE -current last updated 15th Jan (I
think) and after a make world things were great kernel builds in an
instant, computer boots faster etc etc.
However I am unable to use help in the new bootloader, it sais the file
boot.help cant be found and as such I do not
On Thu, 21 Jan 1999, Jaye Mathisen wrote:
>
>
> The readme in /usr/share/examples hasn't been updated in a while...
>
> WHat tag should I be using now to track 3.0-current/3.1? (Not the 4.x
> branch).
>
> Right now, I have tag=., and I can't get a compilable kernel to save my
> life, problems
"me too"
-DNOSECURE seems to help but it hasn't completed yet.
julian
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
The readme in /usr/share/examples hasn't been updated in a while...
WHat tag should I be using now to track 3.0-current/3.1? (Not the 4.x
branch).
Right now, I have tag=., and I can't get a compilable kernel to save my
life, problems in syscons.
To Unsubscribe: send mail to majord...@freebsd
This, no response on Ctrl-Alt-F1, happens as well when you kill the X
server (because it is somehow stuck) so that the login prompt of xdm
appears again.
So I bet it has something to do with and is either located in syscons or
in X.
Nick
> > It seems that if the splash screen image is not cl
> >
> >If anyone has any more of these tunables that can easily be enhanced
> >like this, please let me know.
>
>Is there a way from the boot loader that one can find out what options
> are available to be tuned?
At the moment, the values are picked up on-demand by the kernel as it's
initia
>> On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with
>> 768MB RAM) poking about in the code adding:
>>
>> options "VM_KMEM_SIZE=(24*1024*1024)"
>> options "VM_KMEM_SIZE_MAX=(128*1024*1024)"
>>
>> seems like a good way foward. Is it?
>
>>From wha
I cvsup'ed current today, and am having a problem with the
build. I am running current as of a couple of weeks ago,
and during the buildworld, I get an error in the
/usr/src/secure/lib/libcrypt directory, because the
Makefile is refering to crypt.c crypt-md
> -Original Message-
> From: Mike Smith [mailto:m...@smith.net.au]
> Sent: Thursday, January 21, 1999 8:25 PM
> To: p...@originative.co.uk
> Cc: curr...@freebsd.org
> Subject: Re: KLD naming
>
...
> Ah, understood. I'd be inclined to use a suffix, so that our
> prefix-based classifica
Norman C. Rice wrote:
> On Thu, Jan 21, 1999 at 12:26:04PM -0800, Steve Kargl wrote:
> > make: don't know how to make crypt-md5.c. Stop
> > *** Error code 2
> > 1 error
> >
> > Seem crypt-md5.c was moved into the attic, but the Makefile was updated.
>
> Do you mean "wasn't" updated?
Yes, of cour
On Thu, Jan 21, 1999 at 12:26:04PM -0800, Steve Kargl wrote:
> cd /usr/src/secure/lib/libcrypt; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO
> -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend;
> /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE
> -DNOSHARED all; /usr/obj/
In article <19990121201420.a50...@titan.klemm.gtn.com>,
Andreas Klemm wrote:
> cc -O -pipe -DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING -Wall
> -I/home/src/libexec/ftpd/../../contrib-crypto/telnet -DKERBEROS
> -I/usr/obj/home/src/tmp/usr/include -o ftpd ftpd.o ftpcmd.o logwtmp.o
> p
"Richard Seaman, Jr." wrote:
> > BTW, why does FreeBSD use -D_THREAD_SAFE AND -D_REENTRANT (math.h)
> > while most other PThread (final) implementations use -D_REENTRANT?
> Don't know. Using _REENTRANT would be preferable, IMO.
Now if only a committer would agree... (I'll send patches if needed)
> On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with
> 768MB RAM) poking about in the code adding:
>
> options "VM_KMEM_SIZE=(24*1024*1024)"
> options "VM_KMEM_SIZE_MAX=(128*1024*1024)"
>
> seems like a good way foward. Is it?
>From what I can
subscribe current
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Julian Elischer wrote:
[..]
> > > I just realised however, that if we make them go away we break
> > > SMP right?
> >
> > No. I don't think the patches affect SMP one way or the other.
> > If someone tries to run kernel threads of any kind (linuxthreads
> > in emulation, linuxthread in FreeBSD n
"Joerg B. Micheel" writes:
> > consolidating all that config information in one place, such as
> > /etc/rc.conf, would be a good thing.
> Agreed, it really isn't such a good idea to clutter /etc/ with all
> those single line configuration files.
Actually, they did it for a reason, and it's not re
On Thu, Jan 21, 1999 at 11:42:14AM -0800, Kurt D. Zeilenga wrote:
> >This is nagging at me. Having two headers of the same name, but importantly
> >different content is asking for touble. There needs to be a way to ensure
> >that only one or the other is picked up. The best way I can think of i
In article <199812280019.qaa22...@hub.freebsd.org> you wrote:
> On 28 Dec, Dmitrij Tejblum wrote:
>> I once suggested this patch:
>>
> [ patch snipped ]
>>
>> Dima
>>
> My, I forgot about that patch. It is working so far right now (I've
> managed to bring the swap usage to levels which would tri
> I've taken this off list. I'm not sure we're quite addressing the same
> issue.
No, I think we were at angles for a bit here. But I do believe that
this is something work copying to people on the list, as you do raise a
very good point. I hope this was on -current. 8)
> > I've thought about
On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote:
> On Thu, Jan 21, 1999 at 11:04:38AM -0800, Julian Elischer wrote:
> >
> >
> > On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote:
> >
> > > > And when are COMPAT_LINUX_THREADS and VM_STACK going away?
> > >
> > > I have no idea. I was hoping that
cd /usr/src/secure/lib/libcrypt; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO
-DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend;
/usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE
-DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC
-DNOPROFILE -DNOSH
>
> Is there meta information in a .ko file? That way you could do a kldinfo to
> find out where to go for more info, etc.
There's not time to standardise this, so I would say that 3.x .ko files
won't have metainformation internally, no. Certainly 4.x .ko files
will carry a lot more metainfo
On Thu, 21-Jan-1999 at 10:54:36 -0500, David E. Cross wrote:
> I posted this awhile ago to -questions, but never received a reply.
>
> We have a number of FreeBSD NFS servers here. Occasionally we need to
> change the exports list on the servers and send mountd a SIGHUP. This
> leads to a condit
Is there meta information in a .ko file? That way you could do a kldinfo to
find out where to go for more info, etc.
On Thu, Jan 21, 1999 at 11:13:49AM -0800, Mike Smith wrote:
> I've thought about this, and I think it would be a very bad idea.
>
> We want to keep this *simple*. In the case o
Edwin Culp wrote...
> I'm getting a lot of these SCSI disk errors from Current as of Sunday
> with the onboard Adaptec Controler with an IBM netfinity 3500. Can
> someone tell me if I should worry and/or what they mean?
>
> Thanks,
>
> ed
>
> (da0:ahc0:0:0:0): parity error during Data-In phase.
On Thu, Jan 21, 1999 at 11:04:38AM -0800, Julian Elischer wrote:
>
>
> On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote:
>
> > > And when are COMPAT_LINUX_THREADS and VM_STACK going away?
> >
> > I have no idea. I was hoping that at least COMPAT_LINUX_THREADS
> > would go away before the branch.
At 06:12 PM 1/21/99 +0200, Jeremy Lea wrote:
>On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote:
>> Actually, the new version, in FreeBSD "ports" form, doesn't require
>> -DLINUXTHREADS anymore, but it does require -I/usr/local/include to
>> pick up the right header, since it ins
I've been seeing this since yesterday morning when trying to
cvsup:
Rmdir ispell/word2x
Delete ispell/yodl/Makefile,v
Delete ispell/yodl/files/md5,v
Rmdir ispell/yodl/files
Delete ispell/yodl/patches/patch-aa,v
Rmdir ispell/yodl/patches
Delete ispell/yodl/pkg/COMMENT,v
Delete ispell/yodl/p
On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote:
> > And when are COMPAT_LINUX_THREADS and VM_STACK going away?
>
> I have no idea. I was hoping that at least COMPAT_LINUX_THREADS
> would go away before the branch. I don't have commit authority,
> so it isn't up to me.
>
hmm did you send me
Just wanted to let you know ...
cc -O -pipe -DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING -Wall
-I/home/src/libexec/ftpd/../../contrib-crypto/telnet -DKERBEROS
-I/usr/obj/home/src/tmp/usr/include -o ftpd ftpd.o ftpcmd.o logwtmp.o popen.o
skey-stuff.o klogin.o -lskey -lmd -lcrypt -lut
> > Well whistle is giving htis away so we don'tthink it should
> > be whistle_xxx
> > any more than the kernel should be UCB/...
> > It occur to me that eventually every single device driver
> > will be a KLD
> > an also a lot of other things besides...
> > there are going to be a LOT of files
Given a message id and a mailing list, is there some way construct a
URL that will fetch that mail message. This will make doing the
UPDATING file a little easier when long messages are sent to
-current. I can say blah blah blah changed, see for
details.
Warner
To Unsubscribe: send mail to ma
In message
Andrzej Bialecki writes:
: I'm more than willing to test it in low memory conditions.. :-) I have
: that special 386SX/4MB RAM machine in the corner to test things like
: picobsd memory requirements...
So how well does this work? I have a 4MB machine that I'd like to run
FreeBSD on,
Current cvsup'd today at 12:08 EST -- make world failed looking
for /usr/src/secure/lib/libcrypt/crypt-md5.c. It appears that
crypt-md5.c and crypt.3 were moved to /usr/src/lib/libcrypt/
on Thu Jan 21 13:50:09 1999 UTC by brandon, but
/usr/src/secure/lib/libcrypt/Makefile
still references cryp
Kazutaka YOKOTA wrote:
:
> 104 Pause Start screen saver (saver).
:
> The above assignments for the keycodes 1, 57, 70, 84 and 92 are
> compatible with many, if not all, existing keymaps.
So far so good!
> The assignments for 104 and 108 are new.
104 (Pause?) does the
On Thu, Jan 21, 1999 at 06:12:29PM +0200, Jeremy Lea wrote:
> On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote:
> > Actually, the new version, in FreeBSD "ports" form, doesn't require
> > -DLINUXTHREADS anymore, but it does require -I/usr/local/include to
> > pick up the right
I'm getting a lot of these SCSI disk errors from Current as of Sunday
with the onboard Adaptec Controler with an IBM netfinity 3500. Can
someone tell me if I should worry and/or what they mean?
Thanks,
ed
(da0:ahc0:0:0:0): parity error during Data-In phase.
SEQADDR == 0x10e
SCSIRATE == 0x88
(da
Looks like the Alpha AXP boot floppy has bitten the dust also:
Making the regular boot floppy.
Compressing doc files...
disklabel: ioctl DIOCWLABEL: Operation not supported by device
Warning: Block size restricts cylinders per group to 4.
Warning: 2880 sector(s) in last cylinder unallocated
/dev/
On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with
768MB RAM) poking about in the code adding:
options "VM_KMEM_SIZE=(24*1024*1024)"
options "VM_KMEM_SIZE_MAX=(128*1024*1024)"
seems like a good way foward. Is it?
--
GeoffB
To Unsubscribe: send mail to m
> -Original Message-
> From: Julian Elischer [mailto:jul...@whistle.com]
> Sent: Thursday, January 21, 1999 5:39 PM
> To: p...@originative.co.uk
> Cc: m...@smith.net.au; c...@adsu.bellsouth.com; obr...@nuxi.com;
> curr...@freebsd.org
> Subject: RE: KLD naming
>
> Well whistle is giving ht
On Thu, 21 Jan 1999, Christian Kuhtz wrote:
> On Thu, Jan 21, 1999 at 09:34:28AM +, Doug Rabson wrote:
> > On Wed, 20 Jan 1999, Mike Smith wrote:
> >
> > > I guess it depends on how fancy we want to get. Here are some examples
> > > that I've been rolling around; some are fanciful, some p
Kazutaka YOKOTA wrote:
>
> * 101/102/104 Enhanced Keyboard support
>
> Key CodeKey Stroke Function
> -
> 1 Ctrl-Alt-EscEnter DDB (debug).
> 57 Ctrl-Alt-Space
On Thu, 21 Jan 1999 p...@originative.co.uk wrote:
>
> Why not have a third party identifier on the front, e.g.
>
> whistle_ng_rfc1490
>
> You can determine your own naming scheme then and if we make this
> standard then it will ensure that third party supplied modules don't
> result in name sp
Hi,
On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote:
> Actually, the new version, in FreeBSD "ports" form, doesn't require
> -DLINUXTHREADS anymore, but it does require -I/usr/local/include to
> pick up the right header, since it installs a pthread.h into
> /usr/local/include
I recently looked at keymaps in /usr/share/syscons/keymaps and found
many minor errors. In addition to that, there is so much
inconsistency among existing keymaps. True that national keyboards have
different layout of regular keys (alphanumeric keys and symbol keys).
But, it is absurd that functi
I posted this awhile ago to -questions, but never received a reply.
We have a number of FreeBSD NFS servers here. Occasionally we need to
change the exports list on the servers and send mountd a SIGHUP. This
leads to a condition that in many ways is much worse than a server reboot.
What happens
Yes, indeed, I have looked at nsd in Irix 6.5 and I like it. What Irix does
well, Irix does very well (save a couple of PRs I have filed with SGI of
course ;).
--
David Cross
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
>From: "John W. DeBoskey"
>Date: Thu, 21 Jan 1999 00:54:36 -0500 (EST)
> If you really want to make things easier for the beginner, why
>not provide a DOS boot program. Then you wouldn't even have to
>worry about boot floppies. Tell new folks to copy the boot program
>to the DOS partition and r
On Thu, Jan 21, 1999 at 09:34:28AM +, Doug Rabson wrote:
> On Wed, 20 Jan 1999, Mike Smith wrote:
>
> > I guess it depends on how fancy we want to get. Here are some examples
> > that I've been rolling around; some are fanciful, some practical)
> >
> > dev_generic device (eg
It appears that revision 1.9 of lib/libpam/modules/pam_kerberosIV/klogin.c
and revision 1.3 of lib/libpam/modules/pam_kerberosIV/pam_kerberosIV.c
broke ftpd when compiling with MAKE_KERBEROS defined. The errors I get when
compiling with 4.0-current sources (and presumably 3.0-stable though I
haven
I'm trying to get 3.0-RELEASE to run as stable as possible on a PII
with aic7895 onboard scsi controller.
my dmesg output is:
Timecounter "i8254" frequency 1193182 Hz cost 3126 ns
Timecounter "TSC" frequency 349069134 Hz cost 140 ns
CPU: Pentium II (quarter-micron) (349.07-MHz 686-class CPU)
It seems David Dawes wrote:
>
> That didn't improve things, but with the patch I got lots of messages
> like the following (for a disk attached to the onboard PIIX4):
>
> wd1: DMA failure, DMA status 0
>
> (The box isn't SMP.)
Hmm, and it is an uptodate -current system ??
Just use this part the
On Thu, Jan 21, 1999 at 01:21:03PM +0100, Søren Schmidt wrote:
>It seems David Dawes wrote:
>> I've been playing with a Promise FastTrack RAID (IDE) controller with
>> 3.0-current as of yesterday. Although it is recognised in the PCI bus
>> probe as a "Promise Ultra/33" (it has the same vendor/ch
It seems David Dawes wrote:
> I've been playing with a Promise FastTrack RAID (IDE) controller with
> 3.0-current as of yesterday. Although it is recognised in the PCI bus
> probe as a "Promise Ultra/33" (it has the same vendor/chip ID as the
> non-RAID card), the probes in i386/isa/wd.c fail. I
I've been playing with a Promise FastTrack RAID (IDE) controller with
3.0-current as of yesterday. Although it is recognised in the PCI bus
probe as a "Promise Ultra/33" (it has the same vendor/chip ID as the
non-RAID card), the probes in i386/isa/wd.c fail. I added some debugging
printfs to the
With NFS v3 there seem still to be some open issues.
Im running the latest (4.0)-current with the new vm/NFS changes.
While I haven't found any problems with NFSv2 so far, v3 still seems to make
trouble.
I noticed the error some months ago, while my /usr/obj was NFS mounted, and
a build failed whi
I just csvup'ed the sources...(I had the sources from January 12's
snapshot). While trying to do a "make world", eventually I get this message.
c++ -pg -I/usr/obj/usr/src/tmp/usr/include/g++ -nostdinc -O -pipe
-I/usr/src/gnu
/lib/libstdc++/../../../contrib/libg++/include
-I/usr/obj/usr/src/tmp/usr
> -Original Message-
> From: Julian Elischer [mailto:jul...@whistle.com]
> Sent: Thursday, January 21, 1999 7:58 AM
> To: Mike Smith
> Cc: Christian Kuhtz; David O'Brien; curr...@freebsd.org
> Subject: Re: KLD naming
>
>
> well you're about to get your first test
> we are releasing t
FWIW, I've done it under 2.2.7 by
1) installing booteasy on both wd0 *AND* wd2
2) altering the boot.config to
1:wd(2,a)kernel
3) compiling above kernel with
config kernel root on wd2
Mark
In message <74039.916912...@axl.noc.iafrica.com>, Sheldon Hearn writes:
>
>
>On Thu, 21 Jan
On Thu, 21 Jan 1999 18:21:45 +0900, "Daniel C. Sobral" wrote:
> Well, kind of. You "hard code" the name wd2 in your kernel
> configuration file. Loader assigns numbers sequentially.
FWIW, I've never seen FreeBSD boot off a drive on the secondary IDE
controller using a boot manager on the primar
Peter Jeremy wrote:
>
> tutorial: http://www.freebsd.org/~peter/elfday.html). I found that
> /boot/loader could load my 2.x kernel (although it happily handled
^^
You mean "could not", right?
> [gzip'd] -current kernels in both a.out and ELF format). The stage2
> loader
On Wed, 20 Jan 1999, Matthew Dillon wrote:
> The new swapper and a bunch of VM stuff I've been sitting
> on is going to be committed into the new -current tree tonight.
I'm more than willing to test it in low memory conditions.. :-) I have
that special 386SX/4MB RAM machine in the corner
On Thursday, 21 January 1999 at 0:24:24 -0800, Chris Knight wrote:
> At 02:13 PM 1/21/99 +1030, you wrote:
>> I've just committed a new version of Vinum with a large number of
>> changes. It works fine here, much better than the old version, but
>> there's just a possibility that things may go wr
On Wed, 20 Jan 1999, Mike Smith wrote:
> I guess it depends on how fancy we want to get. Here are some examples
> that I've been rolling around; some are fanciful, some practical)
>
> dev_generic device (eg. dev_sio)
> bus_bus support (eg. bus_pci)
> ne
On Thursday, 21 January 1999 at 0:55:38 -0800, Matthew Dillon wrote:
> It's all in. The more feedback the better.
>
> You will have to recompile KVM-related support programs, especially
> pstat. I also suggest recompiling libkvm, ps, top, vmstat, systat,
> etc...
>
> The ne
It's all in. The more feedback the better.
You will have to recompile KVM-related support programs, especially
pstat. I also suggest recompiling libkvm, ps, top, vmstat, systat,
etc...
The new swapper is not understood by top or systat yet but it is
well understood by ps
1 - 100 of 105 matches
Mail list logo
