RE: Problems booting recent -current

On Mon, 4 Jun 2001, John Baldwin wrote: > > On 03-Jun-01 Tony Fleisher wrote: > > I just tried to boot a -current kernel cvsupped > > at Sat Jun 2 14:11:35 PDT 2001, and was thrown > > the following error trying to boot to single-user > > (transcribed by hand): > > > > src/sys/kern/kern_sync.

RE: Problems booting recent -current

On 03-Jun-01 Tony Fleisher wrote: > I just tried to boot a -current kernel cvsupped > at Sat Jun 2 14:11:35 PDT 2001, and was thrown > the following error trying to boot to single-user > (transcribed by hand): > > src/sys/kern/kern_sync.c:385 sleeping with "eventhandler" > locked from src/sys

RE: Problems with -CURRENT

Howdy, I thought it was just me that had the problem, but it appears to be the recent dirpref commit. I managed to get a working system by booting to single user, fsck'ing all partitions, then using tunefs to specify the number of files per directory to be greater than zero. I also specified the

RE: Problems with -CURRENT

On 13-Apr-01 Matthew Schlegel wrote: > I have been working on doing an update to the latest -CURRENT (last cvsup for > this upgrade attempt was this morning at about 9:30 PDT) for the last > couple days from : > FreeBSD msops.crossgain.com 5.0-CURRENT FreeBSD 5.0-CURRENT >#0: Wed Jun 28 13:23:44

RE: Problems with fsck after dirpref changes

On 10-Apr-01 Niels Chr. Bank-Pedersen wrote: > > Is it me fsck'ing up, or is fsck(8) lacking behind in the > dirpref changes? > > > Automatic boot in progress... > /dev/da0s1a: BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN > FIRST ALTERNATE > > /dev/da0s1a: UNEXPECTED

Re: problems with sound in 5.0-20010126-CURRENT

> > Mar 8 16:07:17 choplifter /boot/kernel/kernel: pcm1: hwptr went > > backwards 536 - > 444 > > This has been a known problem for several months now. Please do not > run -CURRENT unless you follow the freebsd-current mailing list > closely. Sorry -- I forgot to mention that I did search the arc

Re: problems with sound in 5.0-20010126-CURRENT

<[EMAIL PROTECTED]> writes: > The sound mostly works. I can play MP3s using mpg123/x11amp/xmms... > The problem is that when I start moving the mouse around a lot, the > sound distorts and the kernel occasionally spits out a message like: > > Mar 8 16:07:17 choplifter /boot/kernel/kernel: pcm1:

Re: Problems compiling kern_mutex.c

> > Matthew Thyer <[EMAIL PROTECTED]> writes: > > /usr/src/sys/kern/kern_mutex.c:593: warning: no previous prototype for `_mtx_ > > assert' > > /usr/src/sys/kern/kern_mutex.c: In function `_mtx_assert': > > /usr/src/sys/kern/kern_mutex.c:595: `MA_OWNED' undeclared (first use in this > > function

Re: Problems compiling kern_mutex.c

Matthew Thyer <[EMAIL PROTECTED]> writes: > /usr/src/sys/kern/kern_mutex.c:593: warning: no previous prototype for `_mtx_ > assert' > /usr/src/sys/kern/kern_mutex.c: In function `_mtx_assert': > /usr/src/sys/kern/kern_mutex.c:595: `MA_OWNED' undeclared (first use in this > function) > /usr/src/sy

Re: Problems syncing disks in recent -current (since 19th)

On Wed, Feb 21, 2001 at 09:55:22PM +, Josef Karthauser wrote: > Hi Kirk, > > A number of us have problem reliably syncing disks with softupdates in > recent -current from about the 19th. Is it possible that you broke > something with your recent commit? I forgot to mention that the syncing

RE: Problems syncing disks in recent -current (since 19th)

Howdy, I think this is unrelated. I'm getting the same thing happening on a system I built prior to Kirk's recent commit - I haven't yet had time to find the cause. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob

Re: problems with today's world

In message <[EMAIL PROTECTED]> Ilya Naumov writes: : i have installed today's world and now cannot compile almost anyting (incuding the :same world) because as (gnu assembler) coredumps every time. A patch was installed to fix this. If you can grab an old as, you can fix this with a recompile o

Re: problems with today's world

Ilya Naumov wrote: > i have installed today's world and now cannot compile almost anyting (incuding the >same world) because as (gnu assembler) coredumps every time. > > it could be because of the older kernel (built yesterday), but i cannot recomile it >due to the problem described above. any

Re: problems with playback via pcm device

> > This could be related to the entropy gathering by the random kthread. Have you > > tried removing the random device from your kernel? > > yes, i've tried. no effect. This seems to have fixed the problem for me, thanks! I'm using the machine now and am getting no keyboard-related glitches in

Re: problems with playback via pcm device

On Fri, 9 Feb 2001, John Baldwin wrote: > >> i have Ensoniq ES1371-based soundcard supported by pcm driver and > >> experience some problems. the sound played is interruped by clicks and > >> distorsions, and they appear more often when the disk activity is high. > >> during playback the kernel g

Re: problems with playback via pcm device

On 09-Feb-01 Mike Holling wrote: >> i have Ensoniq ES1371-based soundcard supported by pcm driver and >> experience some problems. the sound played is interruped by clicks and >> distorsions, and they appear more often when the disk activity is high. >> during playback the kernel generates messag

Re: problems with playback via pcm device

> i have Ensoniq ES1371-based soundcard supported by pcm driver and > experience some problems. the sound played is interruped by clicks and > distorsions, and they appear more often when the disk activity is high. > during playback the kernel generates messages like 'pcm0: hwptr went > backwards

Re: problems with playback via pcm device

In message <[EMAIL PROTECTED]> Ilya Naumov writes: : during playback the kernel generates messages like 'pcm0: hwptr went : backwards 64 -> 32'. any ideas? : FreeBSD 5.0-CURRENT #2: Thu Feb 8 18:19:26 MSK 2001 Interrupt latency in current really sucks right now. Warner To Unsubscribe: send ma

Re: Problems related to disappearnce of libgcc_r

On Wed, Jan 10, 2001 at 02:20:01AM +0200, Maxim Sobolev wrote: > Yes, I know it's possible, but to provide a hack in one place istead of > 20+ places (find /usr/ports -type f | xargs grep -l gcc_r | wc -l) is > much easier both in the terms of efforts and testing required. After > all, it would on

Re: Problems related to disappearnce of libgcc_r

On Tue, Jan 09, 2001 at 02:04:05PM -0800, Peter Wemm wrote: > We need to be a little careful for ports that are supposed to work on > RELENG_4 and -CURRENT. RELENG_4 and -current are the same in this reguard. I should bump __FreeBSD_version in both and then people can use that as the cut over da

Re: Problems related to disappearnce of libgcc_r

> > On Tue, 9 Jan 2001, Peter Wemm wrote: > > "David O'Brien" wrote: > > > On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: > > > > I wonder if anyone noticed that disappearance of libgcc_r will cause lot of > > > > ports to break. Therefore it would be nice if some form of compatib

Re: Problems related to disappearnce of libgcc_r

> > "David O'Brien" wrote: > > On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: > > > I wonder if anyone noticed that disappearance of libgcc_r will cause lot of > > > ports to break. Therefore it would be nice if some form of compatibility sh > im > > > is provided, for example

Re: Problems related to disappearnce of libgcc_r

On Tue, 9 Jan 2001, Peter Wemm wrote: > "David O'Brien" wrote: > > On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: > > > I wonder if anyone noticed that disappearance of libgcc_r will cause lot of > > > ports to break. Therefore it would be nice if some form of compatibility sh >

Re: Problems related to disappearnce of libgcc_r

"David O'Brien" wrote: > On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: > > I wonder if anyone noticed that disappearance of libgcc_r will cause lot of > > ports to break. Therefore it would be nice if some form of compatibility sh im > > is provided, for example symlink from /

Re: Problems related to disappearnce of libgcc_r

On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: > I wonder if anyone noticed that disappearance of libgcc_r will cause lot of > ports to break. Therefore it would be nice if some form of compatibility shim > is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_

Re: Problems related to disappearnce of libgcc_r

On Tue, 9 Jan 2001, Maxim Sobolev wrote: > Hi, > > I wonder if anyone noticed that disappearance of libgcc_r will cause lot of > ports to break. Therefore it would be nice if some form of compatibility shim > is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_r.a > automat

Re: Problems in making world

Hi! On Tue, 5 Dec 2000, David O'Brien wrote: > On Tue, Dec 05, 2000 at 11:06:12AM +0300, Hostas Red wrote: > > I have a following problem in making world for some time already: > ... > > Any suggestions? > > rm -rf /usr/obj/* > cd /usr/src && make cleandir > update your /usr/src and try again

Re: Problems in making world

On Tue, Dec 05, 2000 at 11:06:12AM +0300, Hostas Red wrote: > I have a following problem in making world for some time already: ... > Any suggestions? rm -rf /usr/obj/* cd /usr/src && make cleandir update your /usr/src and try again To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscr

RE: Problems with kthread_exit() and SMPng

On Thu, 5 Oct 2000, John Baldwin wrote: > You need Giant before calling kthread_exit(). Ok. > >> After some examination I've found that two fields in the Giant mutex > >> structure set to unexpected values: > > It should have died much earlier if you had INVARIANTS turned on. :( It >

RE: Problems with kthread_exit() and SMPng

Ugh, my mail client ate my reply, lemme try again. > On 05-Oct-00 Boris Popov wrote: >> Hello, >> >> Currently I'm trying to make KLD which uses kernel threads >> unloadable under recent -current. The prototype of functions looks like >> this: >> >> void >> my_thread(void*arg) >> { >

RE: Problems with kthread_exit() and SMPng

On 05-Oct-00 Boris Popov wrote: > Hello, > > Currently I'm trying to make KLD which uses kernel threads > unloadable under recent -current. The prototype of functions looks like > this: > > void > my_thread(void*arg) > { > while(wearewanted) { > do_something(); >

Re: problems with aureal soundcard: kernel fault when playing mp3s

On Tue, Sep 05, 2000 at 08:30:48AM -0700, Peter S. Housel wrote: > > [Alexander, I'm Cc:ing you on this just in case you have heard of > > anyone else having similar problems with Aureal cards with recent > > -currents] Sorry, I couldn't respond any earlier. I was out of business for a while. >

Re: problems with aureal soundcard: kernel fault when playing mp3s

> "Peter" == Peter S Housel <[EMAIL PROTECTED]> writes: Peter> Viren R.Shah <[EMAIL PROTECTED]> wrote: >> >> My last good kernel was from aug 14. On a kernel from 09/05, I get a >> page fault as soon as I try to play mp3s using mpg123. >> >> Note that I have an Aureal Vortex 8830, so

Re: problems with aureal soundcard: kernel fault when playing mp3s

At Tue, 5 Sep 2000 10:32:21 -0400 (EDT), Viren R.Shah <[EMAIL PROTECTED]> wrote: > [Alexander, I'm Cc:ing you on this just in case you have heard of > anyone else having similar problems with Aureal cards with recent > -currents] > > My last good kernel was from aug 14. On a kernel from 09/05, I

Re: problems with /usr/bin/awk

On Mon, 21 Aug 2000 19:17:31 MST, Tony Fleisher wrote: > awk: ./guile-snarf.awk:17: (FILENAME=- FNR=9680) fatal error: internal > error > Abort trap - core dumped > *** Error code 1 Hi Tony, Aharon Robbins has come back with an "official patch" that fixes the problem. It has been committed i

Re: Problems with sym device driver?

>From the keyboard of Wes Peters: > > I just updated my sources after a few days and reconfiged, recompiled & booted > > a machine with with a NCR810a card. It panicked partway through the boot > > messages (prior to mounting filesystems) saying that it couldn't allocate > > space for sym1's data

Re: Problems with sym device driver?

Stephen Hocking wrote: > > I just updated my sources after a few days and reconfiged, recompiled & booted > a machine with with a NCR810a card. It panicked partway through the boot > messages (prior to mounting filesystems) saying that it couldn't allocate > space for sym1's data. The previous ke

Re: Problems with sym device driver?

>From the keyboard of Stephen Hocking: > I just updated my sources after a few days and reconfiged, recompiled & booted > a machine with with a NCR810a card. It panicked partway through the boot > messages (prior to mounting filesystems) saying that it couldn't allocate > space for sym1's data

Re: Problems with sym device driver?

> > > WARNING: / was not properly dismounted > > > pid 271 (ldconfig), uid 0: exited on signal 11 (core dumped) > > > > Er, why is ldconfig dumping core? > > > it's the linux ldconfig and it hasn't been brandelf'd after obrien > made a change that required that. > > Yup - that's right. I've

Re: Problems with sym device driver?

On Tue, Aug 29, 2000 at 09:18:07AM -0700, John Polstra wrote: > > WARNING: / was not properly dismounted > > pid 271 (ldconfig), uid 0: exited on signal 11 (core dumped) > > Er, why is ldconfig dumping core? it's the linux ldconfig and it hasn't been brandelf'd after obrien made a change that

Re: Problems with sym device driver?

In article <[EMAIL PROTECTED]>, Stephen Hocking <[EMAIL PROTECTED]> wrote: > This is a multipart MIME message. > > --==_Exmh_8210834560 > Content-Type: text/plain; charset=us-ascii > > I just updated my sources after a few days and reconfiged, recompiled & booted > a machine with with a NCR810

Re: problems with /usr/bin/awk

On Thu, Aug 24, 2000 at 05:19:34PM +0200, Sheldon Hearn wrote: > So I'm a bit stumped as far as formulating an easy How-To-Repeat is > concerned. :-( How about wedging a printenv into the makefile, before the call to awk, so that you can re-create the environment when testing it? -- Andrew T

Re: problems with /usr/bin/awk

I also was able to get it to run properly when not redirecting to a file. I wonder if there might be some dependancy in the system that causes different behavior with this when output is to a tty vs. a filehandle. I tried this with a copy of /bin/sh from 4.0-RELEASE, and had the same result, so

Re: problems with /usr/bin/awk

On Tue, 22 Aug 2000 12:27:01 +0200, Sheldon Hearn wrote: > > awk: ./guile-snarf.awk:17: (FILENAME=- FNR=9680) fatal error: internal > > error > > Abort trap - core dumped > > *** Error code 1 > > I get the same thing here. Inspecting the core dump, one finds that the > abort() happens in eval

Re: problems with /usr/bin/awk

Tony, On Mon, Aug 21, 2000 at 07:17:31PM -0700, Tony Fleisher wrote: > I have been running cvsup nightly to grab -current and -ports, > and noticed some strangeness with awk that seemed to start last > week sometime. > > When building /usr/ports/lang/guile, the build exited with an > awk 'intern

Re: Problems with stable (believed to be in -current as well)

Sean O'Connell wrote: > > Rod Taylor stated: > : Wesley Morgan wrote: > : > > : > On Sun, 13 Aug 2000, Rod Taylor wrote: > : > > : > > My server functions properly (harddrives inside). My diskless machines > : > > (mounting same filesystems via NFS) are having problems. Thanks in > : > > advanc

Re: Problems with stable (believed to be in -current as well)

Wesley Morgan wrote: > > On Sun, 13 Aug 2000, Rod Taylor wrote: > > > My server functions properly (harddrives inside). My diskless machines > > (mounting same filesystems via NFS) are having problems. Thanks in > > advance. > > > > bash-2.03$ top > > top: nlist failed > > > > If you installe

Re: Problems with ATAPI CD driver

Soren Schmidt wrote: > > It seems Donn Miller wrote: > > I've got a BTC 24x ATAPI CDROM driver, and I can't mount it. Attached is > > my dmesg.out. Typing mount /cdrom causes the mount command to hang, and > > it never did this before. Also, I'm getting these strange syslog > > messages. (See

Re: Problems with ATAPI CD driver

It seems Donn Miller wrote: > I've got a BTC 24x ATAPI CDROM driver, and I can't mount it. Attached is > my dmesg.out. Typing mount /cdrom causes the mount command to hang, and > it never did this before. Also, I'm getting these strange syslog > messages. (See attached file messages.out.) I t

Re: Problems building kernel with IPSEC_DEBUG

On Thu, 6 Jul 2000, Jim Bloom wrote: > While compiling a kernel with recent code (cvsup 22:30 -0400 July 6), I > had some undefined symbols. I traced the symbols to netkey/key_debug.c > and found that it did not test IPSEC_DEBUG correctly. I have attached > a patch below. Fixed! Kris -- I

Re: Problems building kernel with IPSEC_DEBUG

On Thu, 6 Jul 2000, Jim Bloom wrote: > While compiling a kernel with recent code (cvsup 22:30 -0400 July 6), I > had some undefined symbols. I traced the symbols to netkey/key_debug.c > and found that it did not test IPSEC_DEBUG correctly. I have attached > a patch below. Whee! Thanks. I'll

Re: Problems with nlist on -current?

Bernd Luevelsmeyer wrote: > > Dampure, Pierre Y. wrote: > > > > I installed 5.0-2621-CURRENT on a new system (OR840, 2x733EB, 512MB > > RDRAM) and had problems with top / systat / vmstat all failing after > > reporting problems with nlist: > [...] > > At a guess, you don't use /boot/loader?

Re: Problems with nlist on -current?

Dampure, Pierre Y. wrote: > > I installed 5.0-2621-CURRENT on a new system (OR840, 2x733EB, 512MB > RDRAM) and had problems with top / systat / vmstat all failing after > reporting problems with nlist: [...] At a guess, you don't use /boot/loader? The loader seems to be no longer optional,

Re: Problems building ports/x11-toolkits/wxGTK

[Please send followups to -ports, where this belongs.] On Fri, Jun 23, 2000 at 04:06:55PM +0200, Norbert Irmer wrote: > I tried to build the wxGTK-2.1.16 port, and noticed that > a few AC_CHECK(..) macros in the configure script > don't work. > > The first header file which is not found is > >

Re: Problems building ports/x11-toolkits/wxGTK

Sorry, it should be: /usr/include/X11 -> /usr/X11R6/include/X11 and CONFIGURE_ENV= GTK_CONFIG="${X11BASE}/bin/gtk12-config"\ CCFLAGS="-I${X11BASE}/include"\ LDFLAGS="-L${X11BASE}/lib" Norbert Irmer wrote: > > Hello, > > I tried to build the wxGTK-

Re: Problems with PCM and ESS 1868

my SBLive just wont play any mp3. it just simplye stop immediantly. It was ok before my recent make world. On Sun, 11 Jun 2000, Donn Miller wrote: > The recent commits to PCM, as of a few days back, have given me > problems with my ESS 1868. When I play MP3's with mpg123, I get a lot > of lou

Re: Problems with PCM and ESS 1868

On Sun, 11 Jun 2000, Donn Miller wrote: > The recent commits to PCM, as of a few days back, have given me > problems with my ESS 1868. When I play MP3's with mpg123, I get a lot > of loud pops and clicks during playback. Otherwise, the MP3s DO play > all the way through. However, when I try to

Re: Problems with PCM and ESS 1868

I was about to post something like this myself. I've got an SBLive and I hear the same pops and clicks during any audio playback (mp3/wav/whatever). It all worked great up until a couple days ago. On Sun, 11 Jun 2000, Donn Miller wrote: > The recent commits to PCM, as of a few days back, have g

Re: Problems with source_rc_confs

On Fri, 2 Jun 2000, Alexander Leidinger wrote: > I know, but I had to modify them to get it running. If that's true, you already had some sort of custom modifications which interfered with the way the system is supposed to work. That's not "bad," it just makes debugging more complicated.

Re: Problems with source_rc_confs

On 2 Jun, Sheldon Hearn wrote: >> At the moment my /etc/rc contains: >> ---snip--- >> # If there is a global system configuration file, suck it in. >> # >> if [ -r /etc/defaults/rc.conf ]; then >> . /etc/defaults/rc.conf >> . /etc/rc.conf >> . /etc/rc.conf.local >>

Re: Problems with source_rc_confs

On Fri, 02 Jun 2000 12:07:13 +0200, Alexander Leidinger wrote: > At the moment my /etc/rc contains: > ---snip--- > # If there is a global system configuration file, suck it in. > # > if [ -r /etc/defaults/rc.conf ]; then > . /etc/defaults/rc.conf > . /etc/rc.conf > . /et

Re: Problems with source_rc_confs

On 2 Jun, Sheldon Hearn wrote: >> after the update of my rc scripts (~a month ago if I remember correctly) >> to use source_rc_conf it didn't boots as expected. E.g. it didn't starts >> anything from rc.i386. I had to source rc.conf* manually in rc.i386. > > Could you run mergemaster again to

Re: Problems with source_rc_confs

On Fri, 02 Jun 2000 09:46:04 +0200, Alexander Leidinger wrote: > after the update of my rc scripts (~a month ago if I remember correctly) > to use source_rc_conf it didn't boots as expected. E.g. it didn't starts > anything from rc.i386. I had to source rc.conf* manually in rc.i386. Could you

Re: problems with Ghostscript5/55/6

On Tue, May 02, 2000 at 09:52:43AM -0500, Bruce Burden wrote: > I am trying to get Ghostscript running on a 4.0-STABLE >environment. Here is what I get: Please post this to [EMAIL PROTECTED] where Ports savy people hang out. [EMAIL PROTECTED] is to discuss FreeBSD kernel and native use

Re: problems with Ghostscript5/55/6

> Ghostscript55: > > It will build and install. When I run "gs", I get: > > bash-2.03# gs /usr/local/share/ghostscript/5.50/examples/tiger.ps > Aladdin Ghostscript 5.50 (1998-9-16) > Copyright (C) 1998 Aladdin Enterprises, Menlo Park, CA. All rights reserved. > This software comes with NO

Re: problems with Ghostscript5/55/6

On Tue, 2 May 2000, Bruce Burden wrote: > Ghostscript55: > > It will build and install. When I run "gs", I get: > > bash-2.03# gs /usr/local/share/ghostscript/5.50/examples/tiger.ps > Aladdin Ghostscript 5.50 (1998-9-16) > Copyright (C) 1998 Aladdin Enterprises, Menlo Park, CA. All righ

Re: Problems configuring Vadem VG-469 PCMCIA controller.

On Thu, 27 Apr 2000, Warner Losh wrote: > Add the vendor ID to pccard/pcic.c: > static struct isa_pnp_id pcic_ids[] = { > {PCIC_PNP_82365,NULL}, /* PNP0E00 */ > {PCIC_PNP_CL_PD6720,NULL}, /* PNP0E01 */ > {PCIC_PNP_VLSI_82C146,

Re: Problems configuring Vadem VG-469 PCMCIA controller.

In message Dave Belfer-Shevett writes: : Vendor ID AEI0218 (0x1802a904), Serial Number 0x01234567 You'll have to add this ID to the list of IDs in the pcic driver for 4.0. I'll try to do this when I get back if you can wait. And if you can't t

Re: Problems with MAKEDEV.

On Fri, Apr 14, 2000 at 11:41:55AM +0100, Ashley Penney wrote: > When booting up I noticed the block device warning message. I > did some investigation and discovered that some ad4/ad5 devices > were still block ones. It seems that the MAKEDEV script only > makes up to ad3, but my disks are on

Re: Problems with MAKEDEV.

At 18:12 -0600 14/4/00, Nate Williams wrote: >[...] >You can easily run out of inodes on the roof partition. Sure, my roof leaks from time to time. But _inodes_? :-) :-) -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between

Re: Problems with MAKEDEV.

> > >That's always struck me a bit odd... I thought 'MAKEDEV std' made > > >the generic set of devices and that 'MAKEDEV all' should make... well.. > > >_ALL_. *shrug* > > > > What do you define as `all'? Say I have a big FTP server with 8 wide > > SCSI controllers, each with 15 disks - that's d

Re: Problems with MAKEDEV.

On Fri 2000-04-14 (18:34), David Scheidt wrote: > Sure. What's the point of having both std and all, though? How much does > it hurt to have a few extra device files kicking around? 'std' is standard devices (leaving out exotic ones), and 'all' is at least one of every device out there. Neil

Re: Problems with MAKEDEV.

On Sat, 15 Apr 2000, Peter Jeremy wrote: > On 2000-Apr-14 22:49:40 +1000, Steve Ames <[EMAIL PROTECTED]> wrote: > >That's always struck me a bit odd... I thought 'MAKEDEV std' made > >the generic set of devices and that 'MAKEDEV all' should make... well.. > >_ALL_. *shrug* > > What do you define

Re: Problems with MAKEDEV.

On 2000-Apr-14 22:49:40 +1000, Steve Ames <[EMAIL PROTECTED]> wrote: >That's always struck me a bit odd... I thought 'MAKEDEV std' made >the generic set of devices and that 'MAKEDEV all' should make... well.. >_ALL_. *shrug* What do you define as `all'? Say I have a big FTP server with 8 wide SC

Re: Problems with MAKEDEV.

On Fri, Apr 14, 2000 at 11:41:55AM +0100, Ashley Penney wrote: > When booting up I noticed the block device warning message. I > did some investigation and discovered that some ad4/ad5 devices > were still block ones. It seems that the MAKEDEV script only > makes up to ad3, but my disks are on

Re: Problems with MAKEDEV.

On Fri, Apr 14, 2000 at 08:58:29PM +1000, Peter Jeremy wrote: > On 2000-Apr-14 20:43:12 +1000, Ashley Penney <[EMAIL PROTECTED]> wrote: > > It seems that the MAKEDEV script only > >makes up to ad3, but my disks are on ad4/ad5 (ATA-66, Abit BP6). > > "MAKEDEV all" is designed to create a generic

Re: Problems with MAKEDEV.

On 2000-Apr-14 20:43:12 +1000, Ashley Penney <[EMAIL PROTECTED]> wrote: > It seems that the MAKEDEV script only >makes up to ad3, but my disks are on ad4/ad5 (ATA-66, Abit BP6). "MAKEDEV all" is designed to create a generic set of devices that covers most situations. It _doesn't_ cover all sit

Re: Problems with 4.0 installworld (fwd)

cate. -- Charles Forsythe <[EMAIL PROTECTED]> -- Forwarded message -- Date: Mon, 10 Apr 2000 13:24:41 -0700 (PDT) From: Kris Kennaway <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Problems with 4.0 installworld On Mon, 10 Apr 2000 [E

Re: problems using pccard 3c589c with 4.0-snap install

In message <[EMAIL PROTECTED]> Robert Watson writes: : As a followup email, I suppose I'm specifically asking if there's a way to : make sysinstall allocate IRQ3 to the card, as that seems to be the : differentiating factor in terms of hardware configuration allocated : between 3.3-PAO and 4.0-sn

Re: problems using pccard 3c589c with 4.0-snap install

In message <[EMAIL PROTECTED]> Robert Watson writes: : Any pointers--especially ones that get the install of 4.0 working ``out of : the box'' on this notebook would be much appreciated. Make buildworld + make installworld from your 3.3 PAO system. I've not had the time/energy to make the instal

Re: problems using pccard 3c589c with 4.0-snap install

As a followup email, I suppose I'm specifically asking if there's a way to make sysinstall allocate IRQ3 to the card, as that seems to be the differentiating factor in terms of hardware configuration allocated between 3.3-PAO and 4.0-snapshot. I.e., rather than a sysinstall field saying, ``Which

Re: Problems with Linksys NIC and the new dc driver.

On Fri, Mar 10, 2000 at 06:13:14PM +, [EMAIL PROTECTED] wrote: > I am currently experiencing problems with the 0307 -CURRENT snapshot, and > the dc driver. I previously have had no problems with the pn driver I had [snip] Yes, I'm using a LinkSys card with -CURRENT: dc0: port 0xd400-0xd4f

Re: Problems with 'pwd' and unionfs

On Sat, 4 Mar 2000, Dan Potter wrote: > ... > In libc there is a non-kernel version of getcwd that runs lstat() on each > directory and then searching its parent, trying to divine which sub-tree > is '.' at the time. I dumped a copy of that into a copy of pwd.c to trace > through it and see what

Re: Problems with -current snapshot of 02242000

> Tried to install the snapshot, but it hangs at Probing devices. > ALT-F2 shows as last entry: > > DEBUG: Found a disk device named mlxd0 > > Verbose boot seems not to show more. System is still active, ALT-CONTROL-DEL > will ask if you really want to stop the install. > > System is an AMD K7-

Re: Problems with -current snapshot of 02242000

On Thu, Feb 24, 2000 at 08:31:30PM -0800, Ulf Zimmermann wrote: > Tried to install the snapshot, but it hangs at Probing devices. > ALT-F2 shows as last entry: > > DEBUG: Found a disk device named mlxd0 > > Verbose boot seems not to show more. System is still active, ALT-CONTROL-DEL > will ask i

Re: Problems with Recent PPP Changes

> Thanks for the reply. > > > Date: Wed, 16 Feb 2000 01:16:25 -0700 > > From: Warner Losh <[EMAIL PROTECTED]> > > > > In message <[EMAIL PROTECTED]> Thomas Dean writes: > > : What change to ppp did I miss? > > > > There were some quoting and comment recognition changes at one > > point... > >

Re: Problems with Recent PPP Changes

A very careful reading of the man page shows: Note that two parsers will examine these escape sequences, so in order to have the `chat parser' see the escape character, it is necessary to escape it from the `command parser'. This means that in practice you should use two escapes, for exam

RE: Problems with Recent PPP Changes

be somebody can make this new qouting behavior more clear in an example in the sample ppp.conf installed in /etc? Just so other new users of 4.0 won't get bitten by the same thing. > -Original Message- > From: Thomas Dean [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, Februar

Re: Problems with Recent PPP Changes

Thanks for the reply. > Date: Wed, 16 Feb 2000 01:16:25 -0700 > From: Warner Losh <[EMAIL PROTECTED]> > > In message <[EMAIL PROTECTED]> Thomas Dean writes: > : What change to ppp did I miss? > > There were some quoting and comment recognition changes at one > point... > That is the problem.

Re: problems with openssl in 4.0rc and ports/security/openssh

> > internat:/home/ftp/pub/FreeBSD/releases/i386/4.0-2211-SNAP/des > cat des.?? | >tar -tzvf - | grep rsa > > -r--r--r-- root/wheel12208 Feb 12 07:09 2000 usr/include/openssl/rsa.h > > > > Or is there something that I miss? > > That looks right. I think the original person was getting t

Re: problems with openssl in 4.0rc and ports/security/openssh

> > I installed a fresh 4.0 release candidate this morning, including the > > crypto stuff (des, kerberos...). Tried to install openssh from ports > > tree as well, but couldn't. It was looking for > > /usr/include/openssl/rsa.h which was not there, and I couldn't find a > > knob to turn RSA requi

Re: problems with openssl in 4.0rc and ports/security/openssh

On Sat, 12 Feb 2000, Poul-Henning Kamp wrote: > Could somebody send a short overview of the "crypto in FreeBSD" > situation ? I bet there are more people than me who have lost > track of what is in, what is out and what USA_RESIDENT changes... See the new chapter 6.5 in the handbook for an exp

Re: problems with openssl in 4.0rc and ports/security/openssh

In message <[EMAIL PROTECTED]>, "Jordan K. Hubbard" writes: >> Are there any plan to distribute USA_RESIDENT=NO version of >> des binary distribution? > >I have no current plans to build such a thing and am USA_RESIDENT >myself so it would be a questionable thing from a legal standpoint, I >think.

Re: problems with openssl in 4.0rc and ports/security/openssh

> Are there any plan to distribute USA_RESIDENT=NO version of > des binary distribution? I have no current plans to build such a thing and am USA_RESIDENT myself so it would be a questionable thing from a legal standpoint, I think. I can hardly wait until September when the RSA patent expires! :

Re: problems with openssl in 4.0rc and ports/security/openssh

The problem initially reported was made worse by a couple of things. First, Kris has not yet committed the changes to the openssh port so that it will issue errors about the cryptography not being installed "correctly". This will not be in all ports that use openssl when 4.0 is released. The po

Re: problems with openssl in 4.0rc and ports/security/openssh

On Sat, 12 Feb 2000, John Hay wrote: > and to me it looks like rsa.h is included: > > internat:/home/ftp/pub/FreeBSD/releases/i386/4.0-2211-SNAP/des > cat des.?? | >tar -tzvf - | grep rsa > -r--r--r-- root/wheel12208 Feb 12 07:09 2000 usr/include/openssl/rsa.h > > Or is there somethin

Re: problems with openssl in 4.0rc and ports/security/openssh

> > > Related question: > > > > Are there any plan to distribute USA_RESIDENT=NO version of > > des binary distribution? > > > > If not, non-USA users must rebuilt the crypto libraries from > > source to use international-crypto packages. > > > > The des distribution (des/des.??) of the 4.0 re

Re: problems with openssl in 4.0rc and ports/security/openssh

On Sat, 12 Feb 2000, Motoyuki Konno wrote: > Related question: > > Are there any plan to distribute USA_RESIDENT=NO version of > des binary distribution? > > If not, non-USA users must rebuilt the crypto libraries from > source to use international-crypto packages. > > The des distribution (de

Re: problems with openssl in 4.0rc and ports/security/openssh

Hi, Kris Kennaway <[EMAIL PROTECTED]>wrote: > > I installed a fresh 4.0 release candidate this morning, including the > > crypto stuff (des, kerberos...). Tried to install openssh from ports > > tree as well, but couldn't. It was looking for > > /usr/include/openssl/rsa.h which was not there, and

Re: problems with openssl in 4.0rc and ports/security/openssh

On Fri, 11 Feb 2000, Mark Huizer wrote: > I installed a fresh 4.0 release candidate this morning, including the > crypto stuff (des, kerberos...). Tried to install openssh from ports > tree as well, but couldn't. It was looking for > /usr/include/openssl/rsa.h which was not there, and I couldn't

<    1   2   3   4   5   6   7   8   >