Re: aout support not working on todays -current

Hi Bob, Go into your kernel of choice and build it with the following: options COMPAT_AOUT now to enable AOUT binaries from the kernel loader. Make and Install and reboot the about new kerenl and aout will now work for you. :) joseph AOUT binaries... elf is the all around executable format fo

Re: make release.9 fails ... ?

Hi Marc, It Should be dhclient-script.sh (a bug in the release builder?) then it works... :) Joseph On Wed, 2003-01-22 at 19:06, Marc G. Fournier wrote: > Evening ... > > I found the release man page this evening, after more searching, and > understand from it that a simple: > > cd /usr/src >

su and SIGHUP problem

On 5.0-CURRENT cvsuped recently, I am seenig very similar problem discussed in the following. Subject: zsh exits upon ^C after su'ing to root with zsh as its shell http://docs.freebsd.org/cgi/getmsg.cgi?fetch=368539+0+archive/2002/freebsd-current/20020602.freebsd-current Subject: su gets SIGH

Another take on adduser

A couple of months ago I wrote a shell implementation of adduser. One of the things that bothered me about the old version was the way its policy and configuration pretty much duplicated that of pw(8). Being able to set inconsistent policy like this is not good. Also, pw already implemented all of

Re: Simple way to build boot disks?

Hi Marc...:) Just build your kernel and do a make release... just takes a little time then run the script /usr/src/release/i386/mkisoimages.sh --- READ the info about this in the shell script so you build what you want and you can even set up drives to be mounted ... YOU can build a bootable CD wi

Re: make release.9 fails ... ?

scrappy> I found the release man page this evening, after more searching, and scrappy> understand from it that a simple: >From release(7): floppies Generate a new set of boot floppies. This will call the release.5, release.9, and release.10 targets to re-generate

Re: psm0 not found on a Sony Vaio w/ 5.0-RELEASE

In message: Ben Hockenhull <[EMAIL PROTECTED]> writes: : I recently installed 5.0-RELEASE on a Sony Vaio R505EC laptop and it's : working pretty well, save for the fact that i can run X because my touchpad : isn't found upon boot probe. : : It use

Re: vm panic

- Original Message - From: "Jake Burkholder" <[EMAIL PROTECTED]> To: "David Xu" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, January 23, 2003 12:33 PM Subject: Re: vm panic >... > Don't know if this is the problem or not but the lockmgr code uses the > pid as the l

Re: first snag with 5.0 - XFree86 4 (fwd)

Recompile and install the with X*4-Server from /usr/ports/x11-servers. Your X server was built on a RC kernel base not the RELEASE the /dev/io mappings are slightly different. The following is the offending line in your snippet Build Operating System: FreeBSD 5.0-RC i386 [ELF] It should say

Re: vm panic

Apparently, On Thu, Jan 23, 2003 at 11:45:13AM +0800, David Xu said words to the effect of; > panic: lockmgr: locking against myself > Debugger("panic") > Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 > db>trace > Debugger(c0381630,c03e4ee0,c037fd14,da447c28,1) at Debugger+0x54 > pani

vm panic

panic: lockmgr: locking against myself Debugger("panic") Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 db>trace Debugger(c0381630,c03e4ee0,c037fd14,da447c28,1) at Debugger+0x54 panic(c037fd14,0,c037fc88,eb,1fb) at panic+0xab lockmgr(c138e85c,2,0,c3c150e0,c3c1514) at lockmgr+0x512 _vm_ma

make release.9 fails ... ?

Evening ... I found the release man page this evening, after more searching, and understand from it that a simple: cd /usr/src make buildworld cd release make floppies Should give me what I need ... But, when I try, the release.9 stage gives: atelier# make release.9 rm -rf /R/stage/mfsf

psm0 not found on a Sony Vaio w/ 5.0-RELEASE

I recently installed 5.0-RELEASE on a Sony Vaio R505EC laptop and it's working pretty well, save for the fact that i can run X because my touchpad isn't found upon boot probe. It used to be /dev/psm0 under 4.x-STABLE. I understand I may need to edit sys/isa/psm.c and add my device, but I'm not su

Re: 5.0 and Thinkpad T20: ACPI related panics

Hi -current, just FYI regarding my suspend/resume problem on the T20 (seems like other people have the same problem): > On Wed, 22 Jan 2003, Lukas Ertl wrote: > > > I think I've found the culprit: it's the sound device. If I remove "device > > pcm" from the kernel, I can suspend/resume after swit

Re: How to build -current and install to empty slice?

Ray Kohler wrote: On Sun, Jan 19, 2003 at 05:05:37PM -0800, Darren Pilgrim wrote: How do tell make to use /5/usr/obj instead of /usr/obj? Will MAKEOBJDIRPREFIX=/5/usr/obj do this? I have more questons: Can I force make to ignore /etc/make.conf and /etc/defaults/make.conf and read another set

Re: vinum root [Was: I want a sysctl kern.allow_shooting_into_my_foot!]

[EMAIL PROTECTED] (Joerg Wunsch) wrote: > The biggest problem of all this is, of course, the bootstrapping > step. The bootstrap still needs an `a' partition in order to read > at least /boot/loader etc. from. The solution is to produce a faked > overlay `a' partition that sits at exactly the po

an0: record length mismatch

Hi, just upgraded my laptop to yesterday's -current, and I keep seeing an0: record length mismatch -- expected 104, got 852 for Rid ff11 an0: record length mismatch -- expected 132, got 172 for Rid ff00 an0: record length mismatch -- expected 156, got 158 for Rid ff10 together with an0: device

5.0 ufs read-only mount bug

Hi ... I have recently been upgrading to 5.0 [now on RELEASE!] and I have one patch I've been applying which solves a problem introduced by a change in ffs_mountfs() where a read-only mount request insists on opening the device in R/W mode. This is fine for the reasons it was done, but it means

RE: ran out of room on / while installing the world

On 22-Jan-2003 Kirk R. Wythers wrote: > I just ran into a problem trying to a 'make installworld' while going > from 4.7 to 5.0-R. I thought I checked and had 30M free on / before I > started this. However, after building, the world, building the kernel, > installing the kernel, running mergemaste

ran out of room on / while installing the world

I just ran into a problem trying to a 'make installworld' while going from 4.7 to 5.0-R. I thought I checked and had 30M free on / before I started this. However, after building, the world, building the kernel, installing the kernel, running mergemaster -p, I went to install the world and got the e

Re: I want a sysctl kern.allow_shooting_into_my_foot!

"Daniel C. Sobral" <[EMAIL PROTECTED]> wrote: >> You can turn this debugging off from userland with: >> sysctl kern.geom.debugflags=0 > > Why not make it a loader tunable? Why should it? It's a debugging flag, so it's IMHO sufficient that it can be set from DDB (that's what i did). -- ch

Simple way to build boot disks?

G'day ... I'm having a bugger of a time getting my laptop with a third-party ethernet adapter installed with 5.0, since it won't properly configure the adapter ... what I'd like to do is build a custom boot kernel, that gets rid of everything but what I require for that laptop, so that the o

Re: background fsck did not create lost+found

< said: > Unfortunately, I think it is possible that the unreferenced inode > has not been initialized, even though it is allocated in the inode > bitmap, so you could potentially get random junk. That is definitely true on UFS2, which I had forgotten. UFS2 inodes are only initialized when they

Re: vinum & growfs

Alex Deiter <[EMAIL PROTECTED]> wrote: > Say me please, sometime growfs will learn to work with vinum > volumes? The growfs maintainers know about the problem, and are working on a solution. We learned about that problem too late before 5.0R was due, so since a quick fix couldn't be produced in

Re: vinum root [Was: I want a sysctl kern.allow_shooting_into_my_foot!]

Ollivier Robert <[EMAIL PROTECTED]> wrote: >> Oh, i should add: in my case, it's loaded before mounting the >> root (root is on vinum). > And how did you achieved this ? I thought vinum isn't able to do > that... Well, the patch for -current is currently only sitting here on my machine(s). Greg

Re: background fsck did not create lost+found

hi, there! On Wed, Jan 22, 2003 at 02:43:37PM -0500, Garance A Drosihn wrote: > > > > > Would that be a big problem to allow some fsck option not > > > > > to erase all these softupdates-pending inodes, but to put > > > > > them in lost+found as usual? > > > > > > > > It certainly couldn't b

Re: kernel panic with today's CURRENT on sparc64 at boot

On Tue, 2003/01/21 at 17:33:42 +, [EMAIL PROTECTED] wrote: > Hi > > cvsup'd to . today on an E220R, single CPU with two Symbios scsi cards. > Box had been running fine with RC3, but would not boot with -CURRENT > kernel: > > Current: > > hme4: Ethernet address: 08:00:20:b7:ef:44 > miibus4:

Re: I want a sysctl kern.allow_shooting_into_my_foot!

[EMAIL PROTECTED] wrote: Hmm, since this happens during boot, you cannot set the debug flag with sysctl in time, so you have to compile a custom kernel for it: in sys/geom/geom_kern.c change: int g_debugflags; to int g_debugflags = G_T_ACCESS; and recompile + reboot. This will make GEOM pr

Re: background fsck did not create lost+found

At 12:53 AM +0600 1/23/03, Max Khon wrote: On Wed, Jan 22, 2003 at 07:18:44PM +0100, Jan Srzednicki wrote: > > > Would that be a big problem to allow some fsck option not > > > to erase all these softupdates-pending inodes, but to put > > > them in lost+found as usual? > > > > It certainly

Re: background fsck did not create lost+found

Thus spake Garrett Wollman <[EMAIL PROTECTED]>: > <<[EMAIL PROTECTED]> said: > > > Would that be a big problem to allow some fsck option not to erase all > > these softupdates-pending inodes, but to put them in lost+found as usual? > > It certainly couldn't be done with the background fsck, becau

Re: background fsck did not create lost+found

hi, there! On Wed, Jan 22, 2003 at 07:18:44PM +0100, Jan Srzednicki wrote: > > > Would that be a big problem to allow some fsck option not to erase all > > > these softupdates-pending inodes, but to put them in lost+found as usual? > > > > It certainly couldn't be done with the background fsck, b

Re: Adduser difference between 5.0 and earlier versions

Use this patch, as it fixes the value of uidstart to be the next available uid, instead of the uid of the previously added user. Scot Index: adduser.sh === RCS file: /home/ncvs/src/usr.sbin/adduser/adduser.sh,v retrieving revision 1.

Re: background fsck did not create lost+found

On Wed, 22 Jan 2003, Garrett Wollman wrote: > > Would that be a big problem to allow some fsck option not to erase all > > these softupdates-pending inodes, but to put them in lost+found as usual? > > It certainly couldn't be done with the background fsck, because > background fsck works on a snap

Re: background fsck did not create lost+found

< said: > Would that be a big problem to allow some fsck option not to erase all > these softupdates-pending inodes, but to put them in lost+found as usual? It certainly couldn't be done with the background fsck, because background fsck works on a snapshot and not the running filesystem; thus, it

Mounting Other *BSD Partitions

I've got a test box that boots Windows, NetBSD, and both FreeBSD STABLE and CURRENT. The FreeBSD CURRENT system is having trouble mounting the NetBSD partitions. The STABLE system has no problem with the NetBSD slice and its partitions. Have all of the CURRENT changes made it impossible to mount s

Re: adduser(8) in 5.0-R

If memory serves me right, Mike Makonnen wrote: > I have cc'ed bmah, because I think it should be in the errata. Done. Thanks! Bruce. msg50715/pgp0.pgp Description: PGP signature

LOR: arp mutex/radix node head

On yesterday's -current: lock order reversal 1st 0xc03d2740 arp mutex (arp mutex) @ /usr/src/sys/netinet/if_ether.c:151 2nd 0xc64c6b7c radix node head (radix node head) @ /usr/src/sys/net/route.c:549 Will try to get a trace next time it happens. Lars -- Lars Eggert <[EMAIL PROTECTED]>

Re: 4.7-amd cannot mount exports from 5.0-RELEASE

Masafumi NAKANE wrote: > On Mon, 20 Jan 2003 09:15:40 +0100, > Michael Nottebrock <[EMAIL PROTECTED]> wrote: > >>Yes, that's exactly what I'm experiencing here... uhoh. First >>errata-topic discovered 2 hours after the release? :} > > > Well, not so quick. I took another -CURRENT box and the probl

RE: Fatal trap 12: page fault while in kernel mode

On 22-Jan-2003 Peter Kostouros wrote: > Hi > > I am having a similar problem to what has been reported previously > regarding X. Basically I get a fatal trap 12. (cvsup'ed about one hour > ago.) I have attached a backtrace I hope is useful. > > When I started X within gdb, I received the followi

RE: acpi_cpu printf

On 21-Jan-2003 Nate Lawson wrote: > How is this? > > --- acpi_cpu.c 16 Oct 2002 17:28:52 - 1.14 > +++ acpi_cpu.c 21 Jan 2003 06:07:43 - > @@ -295,8 +295,10 @@ > /* set initial speed */ > acpi_cpu_power_profile(NULL); > > -printf("acpi_cpu: CPU throttling enabled

Re: Adduser difference between 5.0 and earlier versions

Here's the requested changes to make it re'ask the question on an invalid input. I left the code in for the default answer, but commented out. Scot Index: adduser.sh === RCS file: /home/ncvs/src/usr.sbin/adduser/adduser.sh,v retriev

Re: first snag with 5.0 - XFree86 4 (fwd)

thanks all, securelevel was 2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: I want a sysctl kern.allow_shooting_into_my_foot!

As [EMAIL PROTECTED] wrote: > >You are saying that the close should read? > >error = (*devsw(drive->dev)->d_close) (drive->dev, FWRITE | FREAD, 0, NULL); > > Yes, d_close should match whatever the corresponding d_open is called with. Thanks for pointing this out, this indeed seems to fix this ca

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Bernd Walter writes: >> da1a closed but without FREAD|FWRITE, which turns the close into a no-op. > >[125]cicely5# grep d_open * >grep: CVS: Operation not permitted >vinumext.h:d_open_t vinumopen; >vinumio.c: drive->lasterror = (dsw->d_open) (drive->dev, FWRITE

Re: I want a sysctl kern.allow_shooting_into_my_foot!

On Wed, Jan 22, 2003 at 02:40:28PM +0100, [EMAIL PROTECTED] wrote: > In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: > > >Here's the result. What does it mean to me? (debug flag set from > >DDB, and turned off in single-user again.) > > Here's the bug: > > g_dev_open(da1a, 3, 0, 0)

ACPI features in FreeBSD 5.0

Hi, I have got a Sony Vaio PCG FX-705 Laptop (Athlon Based). I have Installed FreeBSD 5.0 on. Now what has happend: Yesterday evening I have turned off my Laptop as root using halt (everything) worked fine. Today when I went intu my office. My Laptop was turned on and hanged during boot time. An

Linux-base version with 5.0 floppy install

I'm just installing 5.0-RELEASE from the floppies. Answering yes to "do you want Linux binary compatibility" during sysinstall causes it to fetch linux_base-6.1 - I rather thought it would install 7.1. The package retrieval (from ftp.uk.freebsd.org) goes OK but then the pkg_add fails. Sysinstall

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: >Here's the result. What does it mean to me? (debug flag set from >DDB, and turned off in single-user again.) Here's the bug: g_dev_open(da1a, 3, 0, 0) da1a opened (FREAD|FWRITE) g_access_rel(0xc1178a40(da1a), 1, 1, 0)

subscribe

To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: PS/2 mouse problems with -CURRENT

On Wed, Jan 22, 2003 at 12:49:04AM -0600, Chip Norkus wrote: > But try disabling ACPI and see if your PS/2 mouse suddenly works. ;) As you can see from my first post >> Same part of newer -CURRENT (I have disable ACPI, but I get same >> result with ACPI too): >> atkbdc0: at port 0x64,0x60 on isa

Re: Statement regarding FreeBSD release ISO images

> Thanks, and go buy some 5.0 CD's =-) > Of course ! MediaHouse in russia had a litle bit of delay - about a 2-3 monts !!! Realy im think that needed only one disk . Tere is no need to very fast updates in home , where realy ussing 4 disks. To Unsubscribe: send mail to [EMAIL PROTECTED] with

subscribe

-- wbr, andris, dc jelgava To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: I want a sysctl kern.allow_shooting_into_my_foot!

According to Joerg Wunsch: > Oh, i should add: in my case, it's loaded before mounting the > root (root is on vinum). And how did you achieved this ? I thought vinum isn't able to do that... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-C

Re: I want a sysctl kern.allow_shooting_into_my_foot!

As Bernd Walter wrote: > Now that you say it - vinum isn't loaded before going multiuser. Oh, i should add: in my case, it's loaded before mounting the root (root is on vinum). -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NI

Re: I want a sysctl kern.allow_shooting_into_my_foot!

As [EMAIL PROTECTED] wrote: > If this is not enough, you can try to set > > int g_debugflags = G_T_ACCESS | G_T_TOPOLOGY; > > But that will result in much more debugging output. Here's the result. What does it mean to me? (debug flag set from DDB, and turned off in single-user again.) -

Re: I want a sysctl kern.allow_shooting_into_my_foot!

On Wed, Jan 22, 2003 at 01:25:59PM +0100, [EMAIL PROTECTED] wrote: > In message <[EMAIL PROTECTED]>, Bernd Walter writes: > You can also try this, it's more easily informative: > > sysctl -n kern.geom.confdot | dot -Tps > _.ps ; gv _.ps > > You need the graphviz and ghostscript ports for th

Re: Error Mounting /dev/acd0 on /dist: during sysinstall of 5.0-RELEASE

Hi, I have a similar problem, i.e., a clean installation process for 5.0-RELEASE produces the error: "Error Mounting /dev/acd0 on dist: Operation not supported by device (19)" (I wound up doing a minimal ftp install and then did a binary upgrade with the CD as the distribution medium.) Nate s

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Bernd Walter writes: >On Tue, Jan 21, 2003 at 11:06:05PM +0100, [EMAIL PROTECTED] wrote: >> In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: >> >As [EMAIL PROTECTED] wrote: >> > >> >> Hang on. >> >> >> >> If no disk partitions of any kind are open, there is noth

Re: I want a sysctl kern.allow_shooting_into_my_foot!

On Tue, Jan 21, 2003 at 11:06:05PM +0100, [EMAIL PROTECTED] wrote: > In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: > >As [EMAIL PROTECTED] wrote: > > > >> Hang on. > >> > >> If no disk partitions of any kind are open, there is nothing which > >> prevents you from doing a "dd if=/dev/zero of

Re: background fsck did not create lost+found

On Mon, 20 Jan 2003, David Schultz wrote: > > First two entries clearly correspond to the missing file, which should > > have been put in /home/lost+found. But, the poroblem is that no lost+found > > directory was created, while it should (as fsck_ffs(8) says). I guess its > > a bug, probably in t

Fatal trap 12: page fault while in kernel mode

Hi I am having a similar problem to what has been reported previously regarding X. Basically I get a fatal trap 12. (cvsup'ed about one hour ago.) I have attached a backtrace I hope is useful. When I started X within gdb, I received the following: Program received signal SIGUSR1. User defined si

Statement regarding FreeBSD release ISO images

All, There seems to be some confusion created by choices that we made for the 5.0 release regarding ISO image availability. To refresh, from FreeBSD 4.4 to 4.7, we made available 5 iso images for i386 and alpha. This consisted of a mini-disc1 that contained only the bits needed for installing, a

Re: 4.7-amd cannot mount exports from 5.0-RELEASE

Masafumi NAKANE <[EMAIL PROTECTED]> writes: > I've been encountering the exact same problem past a few days. My > -CURRENT box is -CURRENT as of 01/18. I have the same behaviour here. Additionnal tests show that a Linux client running am-utils (6.0.7) also hangs (same error message) when trying