Re: df -l broken

Maxime Henrion <[EMAIL PROTECTED]> wrote: > I looked at the code a bit more closely and you're entirely right. I > think I figured out why my patch caused a core dump. Here is a more > correct patch that should fix the problem without causing core dumps. Seems to work. mount(8) has still the

SoundBlaster PCI-128 performance

I'm getting low volume, background noise, and slight distortion playing audio through my SoundBlaster PCI-128. I tested it using mpg123, mpg321, vlc, and ogle. I am running a recent -current: FreeBSD 5.0-CURRENT #2: Wed Nov 28 23:28:15 PST 2001 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/NEKO

Re: PATCH: sysinstall to remove userconfig code

> BTW, how dou you think my other patch (use 'devfs' while mounting > filesystems, use fsck_ffs instead of fsck) for sysinstall, which was > posted about a week before to [EMAIL PROTECTED]? You can fetch from: > > http://people.freebsd.org/~matusita/5.0-CURRENT-20011121-JPSNAP_usedevfs /patch>

Re: PATCH: sysinstall to remove userconfig code

jkh> Looks good to me, I'd say commit it! Thanks! I'll commit it in this weekend. BTW, how dou you think my other patch (use 'devfs' while mounting filesystems, use fsck_ffs instead of fsck) for sysinstall, which was posted about a week before to [EMAIL PROTECTED]? You can fetch from: http:/

Re: PATCH: sysinstall to remove userconfig code

Looks good to me, I'd say commit it! - Jordan > dsyphers> DEBUG: kget: error buffer sizing > matusita> This is because sysinstall still want to get userconfig data > matusita> and put the result to /boot/kernel.conf. > > Userconfig was gone in 5-current, so we can safely remove kget() from > sy

XFree86 3.3.6 dying

With a recently re-built XFree86, running on -current from last Sunday, whenever I hit one of the keypad keys, the X server crashes. This is somewhat disconcerting... The kernel prints "sigreturn: eflags = 0x13282, was 0x256" (the old eflags value an addition I made to that printf whilst trackin

merging openbsd's pf into FreeBSD

Hello - I am wondering if the FreeBSD team has any thoughts about importing OpenBSD's new pf into FreeBSD. Has anyone looked at the code? During an interview with Theo himself, he talked about the new features of pf, compared with ipf. http://www.kerneltrap.org/article.php?sid=389 Thanks Davi

Re: df -l broken

On Fri, 30 Nov 2001, Maxime Henrion wrote: > Mikko Tyolajarvi wrote: [...] > > They don't have to be mounted, just loaded. E.g. if "nfs" > > shows up with "lsvfs", "df -l " will work, if not, it won't. > > (dunno about other network file systems). > [...] > > I looked at the code a bit more clos

Re: df -l broken

Mikko Tyolajarvi wrote: > In local.freebsd.current you write: > > >On Mon, Nov 26, 2001 at 12:07:22AM +0100, Maxime Henrion wrote: > >> If my patch is exact, then the bug should manifest itself only if there > >> are no network filesystems mounted. Do you have any network fs mounted > >> on your

Re: df -l broken

In local.freebsd.current you write: >On Mon, Nov 26, 2001 at 12:07:22AM +0100, Maxime Henrion wrote: >> If my patch is exact, then the bug should manifest itself only if there >> are no network filesystems mounted. Do you have any network fs mounted >> on your box ? >No networked filesystems he

Is your family protected financially?

LIFEQUOTE SAVE UP TO 70% ON LIFE INSURANCE PREMIUMS Protect Your Family In Case Of Death Plan For Your Childs Education Protect Your Estate The LEADING source for Life Insurance Companies! The BEST Agents! And The FRIENDLIEST Staff! CLICK HERE For a FREE Quote! It's QUICK , EASY and COMPLET

Re: Archos 6000

ps> has anyone tested using a Archos 6000 (using a isd200 interface) with the ps> umass driver under freebsd? Just bought one (the 20G version but same interface) this weekend and can verify that it does not work with -STABLE. I also saw the Linux driver but I don't know the USB code at all. Ho

Re: linuxulator unimplemented syscalls

> Your problem is probably somewhere other than ioctl 0x7201; try > trussing/stracing the app and see what it's trying to access. > Alright, I'll try that, I think I have another clue though, I got it to find the file (it was looking in /usr/compat/linux/mnt/cdrom instead of the regular /mnt/cdro

Re: linuxulator unimplemented syscalls

In the last episode (Nov 29), Kenneth Wayne Culver said: > On Thu, 29 Nov 2001, Dan Nelson wrote: > > From Linux headers: > > > > #define TUNIOCGETINFO 0x7201 /* get version of driver & capabilities of tuner */ > > > > Doubtful that its failure will affect you. I assume ftruncate64() > > shou

Re: linuxulator unimplemented syscalls

On Thu, 29 Nov 2001, Dan Nelson wrote: > In the last episode (Nov 28), Kenneth Culver said: > > I was just wondering if the following syscalls had any chance of being > > implemented anytime soon? > > > > linux: syscall ftruncate64 is obsoleted or not implemented (pid=5695) > > linux: syscall m

sysinstall - no extended partitions

hi.. i wanted to know... that why doesn't the sysinstall utility support the viewing of extended partitions... i mean.. why doesn't it support the viewing of exisitng FAT32/FAT16 extended/logical partitons is not supported... thanks.. regards Yours Sincerely, <[EMAIL PROTECTED]>

WARNING: Driver mistake: destroy_dev on 154/1

ASR is still broken for SMP. WARNING: Driver mistake: destroy_dev on 154/1 kernel panic: "dont do that" Tyan Thunder K7 with 2 1.2GHz Ahtlon's Adaptec 3200S Rev 3607 Current as of this morning. -- [EMAIL PROTECTED] 39:FF:7C:52:66:9D:B9:A3 EA:67:3C:7F:D1:B6:30:36 Polymer physicist

Re: ntfs fs

ls -l does a stat on each file ls on its own does not. On Thu, 29 Nov 2001, Jan Stocker wrote: > Hi, > after a 'ls -l' on a ntfs mounted partition my system freezes and reboots. A > normal 'ls' really runs quite fine... > > Jan > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "

Archos 6000

has anyone tested using a Archos 6000 (using a isd200 interface) with the umass driver under freebsd? if it isn't working, is anyone working on getting it supported? there is a linux driver (http://bjorn.haxx.se/isd200/) but i don't really grok usb and the linux driver.. --

Re: ntfs fs

On Thu, Nov 29, 2001 at 08:03:55PM +0100, Jan Stocker wrote: > Hi, > after a 'ls -l' on a ntfs mounted partition my system freezes and reboots. A > normal 'ls' really runs quite fine... > Jan, This message contains very little useful information. See http://www.freebsd.org/doc/en_US.ISO8859-1

ntfs fs

Hi, after a 'ls -l' on a ntfs mounted partition my system freezes and reboots. A normal 'ls' really runs quite fine... Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Perl build breakage

Hello, I am getting the following error in the make depend stage; could anyone shed a light? (The host system is 5-current as of around May 1.) Thanks, Eugene snip snip ===> libperl ===> miniperl ===> perl Extracting config.h (with

Re: linuxulator unimplemented syscalls

In the last episode (Nov 28), Kenneth Culver said: > I was just wondering if the following syscalls had any chance of being > implemented anytime soon? > > linux: syscall ftruncate64 is obsoleted or not implemented (pid=5695) > linux: syscall mmap2 is obsoleted or not implemented (pid=5691) > li

Re: Panic changing screen mode with vidcontrol

On Mon, 26 Nov 2001, Peter Jeremy wrote: > Having installed a new kernel and userland from sources about a day > old, my vidcontrol command now causes a panic: > > Fatal trap 12: page fault while in vm86 mode > fault virtual address = 0xc359b > ... > The backtrace shows nothing useful - gdb doe

Re: LINT fails due to '/bin/sh:Argument list too long'

On Mon, 26 Nov 2001, Robert Watson wrote: > Decided to run a LINT build on my POSIX.1e capability tree in p4 today, > and ran into something a bit unusual: > > make buildkernel KERNCONF=LINT > ... > boss/p4/rwatson/trustedbsd/cap/sys/kern/link_aout.c > /cboss/p4/rwatson/trustedbsd/cap/sys/kern/su

Re: cdrecord produces broken CDs on -CURRENT: The Answer !

Christoph Herrmann wrote: > > The Problem was the use of vfs.ioopt=2 ! > As long as vfs.ioopt is 1 or 2 the CDs are broken and with > vfs.ioopt=0 the CDs are o.k. > > I didn't see any other problems with the use of vfs.ioopt=2, > especially no Filesystem corruption :-). Are there other known >