Re: Device permissions with DEVFS

On Tue, 19 Nov 2002, Tim Robbins wrote: > I'm glad you brought this up... I'd like to see /dev/devctl made mode 600 > instead of 644 because it does not look very robust and because only one > devctl can be open at a time. > > The two other security/reliability bugs I can see are that the async >

Re: Device permissions with DEVFS

On Mon, 18 Nov 2002, Kris Kennaway wrote: > Something that needs to be addressed before 5.0 is the insecure > default permissions on many devices. For example, on my system, the > following devices have insecure permissions on 5.0 (but not on 4.x > with the default MAKEDEV settings): > > crw-r--r

Re: Run two copies of named from rc.conf?

At 4:41 PM -0800 2002/11/18, Terry Lambert wrote: But. If you are transiently connected, then if the on site DNS server is authoritative, then there is no way to look up externally hosted services via DNS, unless the external DNS, also a hosted service, and therefore not transiently connecte

Re: Device permissions with DEVFS

On Mon, Nov 18, 2002 at 09:03:06PM -0800, Kris Kennaway wrote: > Something that needs to be addressed before 5.0 is the insecure > default permissions on many devices. For example, on my system, the > following devices have insecure permissions on 5.0 (but not on 4.x > with the default MAKEDEV se

Re: Are SysV semaphores thread-safe on CURRENT?

Brian Smith wrote: > >Sure SysV semaphores are thread-safe. When a thread blocks on > >one, the entire process blocks (no threads run). You won't > >get any safer than that ;-) > > Yikes that isn't good. Is that only in STABLE? or does CURRENT > do that as well? I guess I'll have to protect t

Re: Run two copies of named from rc.conf?

John De Boskey wrote: >This an interesting thread, but it seems to be getting > a bit off target. I need to kick off 2 name servers. The > first is authoritive for the domain as seen externally > and the 2nd which is authoritive for the internal network. > >The internal forwards to the ext

Re: Warning messages emitted by disklabel -r

In message: <[EMAIL PROTECTED]> Vallo Kallaste <[EMAIL PROTECTED]> writes: : partition c: partition extends past end of unit : Warning, partition c doesn't start at 0! : Warning, An incorrect partition c may cause problems for standard system utilities : partition e: partition extends p

Device permissions with DEVFS

Something that needs to be addressed before 5.0 is the insecure default permissions on many devices. For example, on my system, the following devices have insecure permissions on 5.0 (but not on 4.x with the default MAKEDEV settings): crw-r--r-- 1 root operator 117, 0 Nov 18 14:49 acd0 crw

Re: Are SysV semaphores thread-safe on CURRENT?

< said: > Is this the recommended method of preventing these problems? The recommended method of preventing these problems generally is to use POSIX semaphores (or other POSIX synchronization mechanisms appropriate to threaded programs. However, the code to implement process-shared POSIX semapho

Re: Are SysV semaphores thread-safe on CURRENT?

On Mon, 18 Nov 2002 21:33:38 -0500 (EST), Daniel Eischen wrote: >[ I assume you mean semop, semctl, not sema_* or sem_* ] Yes ... semop() specifically is causing the problems... >Sure SysV semaphores are thread-safe. When a thread blocks on >one, the entire process blocks (no threads run). You

Re: Run two copies of named from rc.conf?

- Terry Lambert's Original Message - > Brad Knowles wrote: > > Sorry, I wasn't think of transient networks. Indeed, that does > > make things a lot uglier. I'll have to think some more about all the > > various implications, however. > > One of the draft RFC's in the FTP director

Re: Kernel won't build without 'device bpf'

> Buildkernel dies without "device bpf" in the config file. > > I think this is due to Sam's commit on 11-14 changing > sys/net/bpf.c and bpf.h. > > Anyone else seeing this? Yup, I'll fix it. Thanks. Sam To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" i

Re: Are SysV semaphores thread-safe on CURRENT?

On Mon, 18 Nov 2002, Brian Smith wrote: > I've been porting an application from Linux to FreeBSD using STABLE, and it appears >from looking at the > semaphore code that the SysV semaphores are not thread safe on STABLE. I don't have >CURRENT source > code to look at currently. Does anyone k

Are SysV semaphores thread-safe on CURRENT?

I've been porting an application from Linux to FreeBSD using STABLE, and it appears from looking at the semaphore code that the SysV semaphores are not thread safe on STABLE. I don't have CURRENT source code to look at currently. Does anyone know if they are thread-safe in CURRENT? Thanks!

Kernel won't build without 'device bpf'

Buildkernel dies without "device bpf" in the config file. I think this is due to Sam's commit on 11-14 changing sys/net/bpf.c and bpf.h. Anyone else seeing this? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Run two copies of named from rc.conf?

Brad Knowles wrote: > Sorry, I wasn't think of transient networks. Indeed, that does > make things a lot uglier. I'll have to think some more about all the > various implications, however. One of the draft RFC's in the FTP directory I referenced is a "Best Current Practices" document. -

Re: Run two copies of named from rc.conf?

Brad Knowles wrote: > It depends on how you do it. You could $INCLUDE the exterior > file inside the interior file, if that subset of information is the > same. You could also use BIND 9 "views". Otherwise, split-horizon > can be a pain. If you have a LAN behind a transient network conn

Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

On Mon, Nov 18, 2002 at 06:15:24PM -0500, Garrett Wollman wrote: > < said: > > > It's described in the file itself. Can you please file a PR about the > > missing manpage documentation? > > make.conf is no longer installed in -current. A user trying to > understand why some glop is being added

alpha tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

< said: > It's described in the file itself. Can you please file a PR about the > missing manpage documentation? make.conf is no longer installed in -current. A user trying to understand why some glop is being added automatically to CFLAGS will probably not think to read /usr/share/examples/etc

Re: Run two copies of named from rc.conf?

At 10:01 PM -0800 2002/11/17, Terry Lambert wrote: Interior and exterior DNS is a useful case; however, there are multiple ways to set it up; in general, it's not possible to have interior authoritative DNS at the same time you have exterior authoritative DNS (this was a mistake we made on th

Re: Run two copies of named from rc.conf?

At 9:15 PM -0800 2002/11/17, Juli Mallett wrote: Or at least abstracting it in such a way that it doesn't get in anyone's way, and so it won't trigger the "what if I need N" where N>2 case, and in some meaningful way... Like maybe using a named_configs lists, and start one named for each con

a.out toolchain port needed for 5.0

When support for building a.out binaries was removed from -current it was implied that a toolchain port would be created, but so far this hasn't happened. Who will step up and do this before 5.0-RELEASE? Kris msg46889/pgp0.pgp Description: PGP signature

Re: New NVidia drivers on -current

At 9:11 AM +0100 2002/11/18, David Holm wrote: BTW, why hasn't anyone set the mailing list to automatically set the reply-to address to [EMAIL PROTECTED]? . -- Brad Knowles, <[EMAIL PROTECTED]> "They that can give up essential liberty to obta

Re: Warning messages emitted by disklabel -r

On Mon, 18 Nov 2002, Vallo Kallaste wrote: > On Mon, Nov 18, 2002 at 01:00:37PM -0800, Julian Elischer > <[EMAIL PROTECTED]> wrote: > > [snip] > > In pre-geom days we had a "realhack" (TM) that would fiddle the > > label if you read it direct from the disk. In other words > > it "fixed" it t

Re: Lost disklabel

On Wed, Nov 13, 2002 at 09:19:11AM -0600, Patrick Hartling wrote the words in effect of: > I have a machine that is running -current from October 10, 2002. It had > been running fine for about two weeks--up until I had to reboot it. > When it came back up, one of my disks apparently lost its di

Re: Lock order reversals in sys_pipe.c and kern_sig.c

On Mon, Nov 18, 2002 at 12:18:08PM -0800, Alfred Perlstein wrote: > * Kris Kennaway <[EMAIL PROTECTED]> [021118 12:01] wrote: > > On Mon, Nov 18, 2002 at 11:39:01AM -0800, Alfred Perlstein wrote: > > > > > Well now they are, I will investigate as time permits. > > > > Thanks. > > > > > I'm still

Re: Warning messages emitted by disklabel -r

On Mon, Nov 18, 2002 at 01:00:37PM -0800, Julian Elischer <[EMAIL PROTECTED]> wrote: [snip] > In pre-geom days we had a "realhack" (TM) that would fiddle the > label if you read it direct from the disk. In other words > it "fixed" it to always look (u relative I think) even if you > read i

Re: Lock order reversals in sys_pipe.c and kern_sig.c

On 18-Nov-2002 John Baldwin wrote: > > On 18-Nov-2002 Alfred Perlstein wrote: >> * Kris Kennaway <[EMAIL PROTECTED]> [021118 12:01] wrote: >>> On Mon, Nov 18, 2002 at 11:39:01AM -0800, Alfred Perlstein wrote: >>> >>> > Well now they are, I will investigate as time permits. >>> >>> Thanks. >>>

Re: Warning messages emitted by disklabel -r

On Mon, 18 Nov 2002, Vallo Kallaste wrote: > On Mon, Nov 18, 2002 at 11:23:14AM -0800, Julian Elischer > <[EMAIL PROTECTED]> wrote: > > > what are the warnings? > > what version of disklabel.c? > > Here's script output: > > Script started on Mon Nov 18 21:46:07 2002 [...] > sysid 165 (0xa5),(

Re: Lock order reversals in sys_pipe.c and kern_sig.c

On 18-Nov-2002 Alfred Perlstein wrote: > * Kris Kennaway <[EMAIL PROTECTED]> [021118 12:01] wrote: >> On Mon, Nov 18, 2002 at 11:39:01AM -0800, Alfred Perlstein wrote: >> >> > Well now they are, I will investigate as time permits. >> >> Thanks. >> >> > I'm still in a holding pattern about addin

Re: Lock order reversals in sys_pipe.c and kern_sig.c

* Kris Kennaway <[EMAIL PROTECTED]> [021118 12:01] wrote: > On Mon, Nov 18, 2002 at 11:39:01AM -0800, Alfred Perlstein wrote: > > > Well now they are, I will investigate as time permits. > > Thanks. > > > I'm still in a holding pattern about adding more debugging info to > > lockd now that we're

Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

On Mon, Nov 18, 2002 at 08:57:24PM +0100, Joerg Wunsch wrote: > As Kris Kennaway wrote: > > > > What am i supposed to do in order to get cross-compilation working > > > properly? > > > > NO_CPU_CFLAGS=yes > > > > This is documented in make.conf. > > At least not in my version of make.conf's man

Re: Lock order reversals in sys_pipe.c and kern_sig.c

On Mon, Nov 18, 2002 at 11:39:01AM -0800, Alfred Perlstein wrote: > Well now they are, I will investigate as time permits. Thanks. > I'm still in a holding pattern about adding more debugging info to > lockd now that we're in release candidate mode. I may ask for a > branch to be done, but i'm

Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

As Kris Kennaway wrote: > > What am i supposed to do in order to get cross-compilation working > > properly? > > NO_CPU_CFLAGS=yes > > This is documented in make.conf. At least not in my version of make.conf's man page. Just checked, neither in the current version. I (and obviously not only I

Re: Warning messages emitted by disklabel -r

On Mon, Nov 18, 2002 at 11:23:14AM -0800, Julian Elischer <[EMAIL PROTECTED]> wrote: > what are the warnings? > what version of disklabel.c? Here's script output: Script started on Mon Nov 18 21:46:07 2002 bash-2.05b# dd if=/dev/zero of=/dev/da1 bs=1k count=512 512+0 records in 512+0 records out

Re: Lock order reversals in sys_pipe.c and kern_sig.c

* Kris Kennaway <[EMAIL PROTECTED]> [021118 11:06] wrote: > I've just turned witness back on on the bento cluster, and got the > following lock order reversals a number of times overnight: > > Nov 18 07:45:40 gohan11 kernel: 1st 0xc6887200 pipe mutex (pipe mutex) @ >/local0/src-client/sys/kern/s

Re: Warning messages emitted by disklabel -r

On Mon, 18 Nov 2002, Vallo Kallaste wrote: > Hi > > Just did the following: > dd if=/dev/zero of=/dev/da1 bs=1k count=512 #remove old stuff > fdisk -I da1#cover the entire disk with one da1s1 slice > fdisk da1 #check what's put there > disklabel -rw da1s1 auto#install virg

Re: Processes hanging in thrd_sleep

On Sun, Nov 17, 2002 at 03:41:36PM -0600, Alan L. Cox wrote: > This late-night commit might help: > > jeff2002/11/17 01:33:00 PST > > Modified files: > sys/kern kern_exec.c > Log: >- Release the imgp vnode prior to freeing exec_map resources to avoid > deadlo

Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

On Mon, Nov 18, 2002 at 02:14:58PM +0100, Joerg Wunsch wrote: > What am i supposed to do in order to get cross-compilation working > properly? I've already tried a number of things, and my -current > from August at least gave in when setting MACHINE_ARCH=avr for > the cross-coimpilation. Previou

Lock order reversals in sys_pipe.c and kern_sig.c

I've just turned witness back on on the bento cluster, and got the following lock order reversals a number of times overnight: Nov 18 07:45:40 gohan11 kernel: 1st 0xc6887200 pipe mutex (pipe mutex) @ /local0/src-client/sys/kern/sys_pipe.c:465 Nov 18 07:45:40 gohan11 kernel: 2nd 0xc0447780 sigio

Re: Asking for tester (small patch to chown(8)/chgrp(1))

< said: > I'm concerned about the used character: "-r" is similiar to "-R" Yes, `-r' would be a very poor choice for the reason you state. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

As Matthew N. Dodd wrote: > > I really /hate/ this CPU feature crap. > > So do I. > > I've also found that the only way to reliablly disable it is to comment it > out from sys.mk. Maybe i should do this using a preconfigure script in my port... >:-) -- cheers, J"org .-.-. --..

Re: problem with phoenix

Hi, > On Mon, 18 Nov 2002 10:51:16 -0600 > John Newman <[EMAIL PROTECTED]> said: jnn> I'm running a recently (as in today) cvsup'd current box. Today I compiled jnn> phoenix 0.4. Oddly enough it would say "Connection refused" to any URL. jnn> Looking at truss/tcpdump I realized it was A

Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failureof ports you maintain])

On Mon, 18 Nov 2002, Joerg Wunsch wrote: > I really /hate/ this CPU feature crap. So do I. I've also found that the only way to reliablly disable it is to comment it out from sys.mk. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84

problem with phoenix

I'm running a recently (as in today) cvsup'd current box. Today I compiled phoenix 0.4. Oddly enough it would say "Connection refused" to any URL. Looking at truss/tcpdump I realized it was ALWAYS trying to connect to an ipv6 address, for any site. I searched around google and found this link:

Re: Run two copies of named from rc.conf?

In the last episode (Nov 17), John De Boskey said: > It would be nice if rc.conf could start a 2nd copy of named (split > dns). Comments on the following simplistic patch? Just upgrade to bind 9 and set up two views. Much easier :) -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe

sparc64 snapshots

Hi All, Im planning on tinkering with -CURRENT on my blade 100, but before I grab the 5.0-20021031 snapshot I want to check if there is a newer snapshot in the pipeline that might be worth while holding out for? Are there any other gotchas before I should embark on this? should I be running an

sparc64 tinderbox failure

Mon Nov 18 15:15:00 GMT 2002 cvs [update aborted]: /home/ncvs/CVSROOT: Interrupted system call To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: ccd & disklabel (what should work?)

> In trying to setup a ccd on a -current system I > seem to have run into a few issues: > > /etc/ccd.conf: > # ccd ileave flags component devices > ccd0 64 none/dev/ad1s1a /dev/ad2s1a > > # ccdconfig -g > ccd064 0 /dev/ad1s1a /dev/ad2s1a >

devfs rules and symbolik links

I'i try to set up jail with following script, however as result, urandom/stdin/stdout/stderr will not appear. They exist before applying devfs rules, but I cannot find rules how to unhide those. Any ideas!? best regards, taavi PS. sshd "PRNG not seeded" seems to be related to "urandom" existanc

FreeBSD 5.0-DP2 & Mylex AcceleRAID 170

Hello, (again & again) I'm trying to install 5.0-DP2 on my little server and at this time: DEBUG: trying to piece 82 of 249: /base/base.dd (da0:mly0:1:0:0): Request Requered (da0:mly0:1:0:0): Retrying Command And sysinstall hangs ... vd To Unsubscribe:

CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

- Forwarded message from Kris Kennaway <[EMAIL PROTECTED]> - One or more ports that you maintain are currently unbuildable under FreeBSD 5.0-CURRENT/i386 on the FreeBSD package-building cluster. [...] - End forwarded message - ... gmake[2]: Entering directory `/tmp/a/ports/devel

make buildkernel broken at net/bpf.c ?

I see these changes were made about four days ago and I seem to be the only one having problems. BTW, I don't use "device bpf" in my kernel config. cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-

Re: icecast broken by signal changes

On Mon, Nov 18, 2002 at 02:43:28AM -0800, Kris Kennaway wrote: > http://bento.freebsd.org/errorlogs/5-latest/icecast-1.3.12_1.log > > cc -DHAVE_CONFIG_H -I. -I. -I.. -D_REENTRANT -I/usr/include/readline -pthread > threads.c: In function `thread_block_signals': > threads.c:467: `SIGBUS' undeclar

alpha tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

icecast broken by signal changes

http://bento.freebsd.org/errorlogs/5-latest/icecast-1.3.12_1.log cc -DHAVE_CONFIG_H -I. -I. -I.. -D_REENTRANT -I/usr/include/readline -pthread threads.c: In function `thread_block_signals': threads.c:467: `SIGBUS' undeclared (first use in this function) threads.c:467: (Each undeclared identifier

Warning messages emitted by disklabel -r

Hi Just did the following: dd if=/dev/zero of=/dev/da1 bs=1k count=512 #remove old stuff fdisk -I da1#cover the entire disk with one da1s1 slice fdisk da1 #check what's put there disklabel -rw da1s1 auto#install virgin disklabel disklabel -e da1s1 #add partition e:, copi

Re: New NVidia drivers on -current

David Holm wrote: > Note that the patch has already been applied so no need to patch your kernel! > > BTW, why hasn't anyone set the mailing list to automatically set the reply-to > address to [EMAIL PROTECTED]? Because the poster may not be a list subscriber, and the most important person to rep

Re: boot0cfg -B

[EMAIL PROTECTED] wrote, On 11/18/02 07:52: Any reason why this doesn't work ? sheel>sudo boot0cfg -B ad0 boot0cfg: /dev/ad0: Operation not permitted securelevel too high ? Dan -- Dan Lukes tel: +420 2 21914205, fax: +420 2 21914206 root of FIONet, KolejNET, webmaster of www.fre

Re: makewhatis.local

On Sat, Nov 16, 2002 at 05:51:15PM +0900, Jun Kuriyama wrote: > > I've installed fresh -current box and it seems it does not have > /usr/libexec/makewhatis.local script. > > How about connecting makewhatis.local to the build? That is shell > script and doesn't require perl. > This will be addre

Re: SMP stability ? [was Re: more info from panic from running

[EMAIL PROTECTED] wrote, On 11/17/02 18:34: > > I haven't been able to complete a full buildworld with an SMP on a > > Abit BP6 (bi-celeron) board for two weeks (the kernel config is just > > a full GENERIC with SMP and APICIO options enabled). > > I also am running a BP6. IS ANYONE successfull

Re: New NVidia drivers on -current

On 2002-11-17 23:53 +, Kris Kennaway wrote: > > [...] > > Try putting this in your loader.conf: > > hw.pci.allow_unsupported_io_range=1 > > This allowed the device to probe for me, but the system locks up when > I try and start X. > Do you by any chance either have an SiS chipset or a regu

Re: New NVidia drivers on -current

On Monday 18 November 2002 09.03, David Holm wrote: > > Hi, > I suggest you read the following post to this list: > http://www.freebsd.org/cgi/getmsg.cgi?fetch=1510354+0+/usr/local/www/db/tex >t/2002/freebsd-current/20021110.freebsd-current > > It talks about the (now deprecated) kernel config opti

Re: New NVidia drivers on -current

On Monday 18 November 2002 07.29, Mikhail Teterin wrote: > Has anyone tried them yet? After removing the #error triggered by > __FreeBSD_version being over 50, I got the thing nvidia.ko to build, > but: > > 00:50:30 aldan shutdown: reboot by root: New world, kernel. Nvidia drivers > 00:56:12 al