Re: newfs/fsck problem (bad superblocks)

> I also wonder if this is related to the 'make release' problems. During "make release", src/release/Makefile does create floppies for installation. Copying 'mfsroot.gz' (mfsroot imagefile) to a newly newfs-ed floppy image (mfsroot.flp, 1.44MB size) causes kernel hungup. -- - Makoto `MAR' MATS

PPP over ATM

I was wondering what the state of PPP over ATM is, if there is at all. And would like to offer my services in it's development if it isn't finished (or started) yet. I inquired on #FreeBSDHelp on EFNet but I didn't get any useful results. I am not sure if this is the correct place to be pos

Re: newfs/fsck problem (bad superblocks)

Reverting src/sbin/newfs/mkfs.c to revision 1.29 fixes the problem. With just a quick review of the patch, I'm not sure I understand what forces the last dirty buffer to be written. revert the patch? try to fix it? comments? -John - John W. De Boskey's Original Message - > Hi, > >

newfs/fsck problem (bad superblocks)

Hi, I posted a question concerning fsck yesterday. A number of people replied with the 'bad harddisk' comment. I have followed up some more on the problem, and can now reproduce it on different filesystems. Below, I umount my /usr/obj, newfs it, mount it, unmount it, and then fsck it.

-current hangs during boot

Hi there, I've done a very recent week's make world(S) on -current, making and installing world and kernel go fine, but all hang on boot, with no error codes or msgs. When boot, all go fine at the beginning, and stop right after showing the msg: : : /dev/da0s1e: FILESYSTEM CLE

(no subject)

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

Re: new rc.network6 and rc.firewall6

> However, Umemoto-san and me will discuss this, since we [he mostly] have > been working on this for the last few months. Sounds good to me. My comments were, just to make it clear again, just food for thought and not out-and-out objections. If even 47 more files in /etc is what it takes to ge

m4 not in build tools for make world

Heya, I don't know if m4 should be in the build tools that are made during make world, but it isn't. And because I had the GNU m4 installed as m4 and not gm4 the building of the boot blocks went belly up (bootblocks crashed on boot). Just my $0.02 DocWilco To Unsubscribe: send mai

HEADS UP: -current a bit rocky at the moment..

This is a friendly little heads up that -current seems to be a bit wobbly at the moment. First of all, the WITNESS code now actually does something... and manages to hang the kernel while doing so. So for now you probably don't want WITNESS in your kernel config. Secondly, there have been report

FreeBSD watchdog problem worsens...

Umm.. I write this in hope that someone will take a note of a big problem(NO this is not a bug report) namley that the current src tree PCI dir has changed som much so the patch for the watchdog problem with some network cards is not appliable any more. http://www.mcs.net/~locke/vrfix/Either

Re: CURRENT locks up

Jeroen Ruigrok van der Werven wrote: > > CURRENT with sources from around this afternoon GMT+2 just locks up. > > Hardware is an ABIT BP6 mainboard. > > System boots up normally the first time, except for the rediculous long > entropy gathering. > > Anyway, rebooted the system by means of a re

Re: new rc.network6 and rc.firewall6

Jeroen Ruigrok van der Werven wrote: > > -On [20001021 20:10], Jordan Hubbard ([EMAIL PROTECTED]) wrote: > >> I wish to update rc.network6 and introduce rc.firewall6. > > > >H. I must confess that I see /etc as getting rather cluttered > >these days. Is

CURRENT locks up

CURRENT with sources from around this afternoon GMT+2 just locks up. Hardware is an ABIT BP6 mainboard. System boots up normally the first time, except for the rediculous long entropy gathering. Anyway, rebooted the system by means of a reboot command. And I get the following: SMP: AP CPU #1

Re: Junior Kernel Hacker Task: M_ZERO

On Sat, Oct 21, 2000 at 09:48:47AM -0400, Garrett Rooney wrote: > > If anybody is looking for a simple task to perform in the FreeBSD > > kernel: this is it. > > > > A quick grep tells me that there are at least 91 files in the src/sys > > tree which could use this flag to simplify and optimize t

Re: new rc.network6 and rc.firewall6

-On [20001021 20:10], Jordan Hubbard ([EMAIL PROTECTED]) wrote: >> I wish to update rc.network6 and introduce rc.firewall6. > >H. I must confess that I see /etc as getting rather cluttered >these days. Is there no way to perhaps collapse some of the most >related functio

Re: new rc.network6 and rc.firewall6

> I wish to update rc.network6 and introduce rc.firewall6. H. I must confess that I see /etc as getting rather cluttered these days. Is there no way to perhaps collapse some of the most related functionality into single files and start passing arguments or something? Just a comment.. - Jo

new rc.network6 and rc.firewall6

Hi, I wish to update rc.network6 and introduce rc.firewall6. - ipv6_prefix_* and ipv6_ifconfig_* work for end node - rtsol should be work to only one interface - new variable ipv6_defaultrouter is added - ipv6_firewall_enable, ipv6_firewall_type, ipv6_f

Printing lockups in -current / Nutscrape

Hi, this has happened twice now, and I think it's about time to report it. I'm running -current Tue Oct 17 00:02:26 CDT 2000, and have noticed that under this and a -current from a few weeks ago that while printing in netscape, the whole system will lock. no panic, just big-red-button-time.. so

Re: strange problem of PPPoE + NAT

On Sat, Oct 21, 2000 at 11:08:28PM +1000, Idea Receiver wrote: > > I just upgrade one of my server to -current. that server connect to ADSL > and act as a gateway. > > however, after I upgrade that server to -current, all other clients > (all windows 98) start acting really strange. clients was

Re: Junior Kernel Hacker Task: M_ZERO

> If anybody is looking for a simple task to perform in the FreeBSD > kernel: this is it. > > A quick grep tells me that there are at least 91 files in the src/sys > tree which could use this flag to simplify and optimize the code. i'll probably start looking at these this week sometime... some

Re: Junior Kernel Hacker Task: M_ZERO

I'd be willing to take this task. - Original Message - From: "Poul-Henning Kamp" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 20, 2000 9:12 PM Subject: Junior Kernel Hacker Task: M_ZERO [...] > If anybody is looking for a simple task to perform in the FreeBSD > ker

Re: Bug in libc_r or broken application?

On Sat, 21 Oct 2000, Blaz Zupan wrote: > Just tried installing "ohphone" under FreeBSD-current. "ohphone" is a H323 > compatible phone that can be used for Voice over IP, it's available in the > FreeBSD ports collection. Just starting the application produces the message > "User signal 2". That's

strange problem of PPPoE + NAT

I just upgrade one of my server to -current. that server connect to ADSL and act as a gateway. however, after I upgrade that server to -current, all other clients (all windows 98) start acting really strange. clients was unable to connect to more then 60% of web sites. for example, clients can

Bug in libc_r or broken application?

Just tried installing "ohphone" under FreeBSD-current. "ohphone" is a H323 compatible phone that can be used for Voice over IP, it's available in the FreeBSD ports collection. Just starting the application produces the message "User signal 2". That's it, nothing else, whatever option you supply. C

Re: current.freebsd.org problems?

matusita> When I backout this change, the problem seems disappeared... This is sample shell script to reproduce recent kernel hungup: #!/bin/sh dd of=/tmp/image if=/dev/zero count=1440 bs=1k awk 'BEGIN {printf "%c%c", 85, 170}' | \ dd of=/tmp/image obs=1 seek=510 conv=notrunc vnconfig -s la

Re: current.freebsd.org problems?

jhay> It looks like I spoke too soon. My 2000-10-05 kernel that previously jhay> worked also now panics. It must be somewhere when the floppies are jhay> made. Maybe there is a problem in newfs(8). peter 2000/10/16 17:41:37 PDT Modified files: sbin/newfs mkfs.c Log: I

Re: current.freebsd.org problems?

> > jhay> For now I just went back to an older kernel that works for me. > > Would you please explain "an older kernel" ? I'm using a kernel as of > Sep/30/2000 and it panics. > > *** > > Note that this (Sep/30/2000) kernel doesn't panic until Oct/13/2000. > Between Oct/14/2000 and Oct/17/2000

Re: Kernel PANICS during "make release"

matusita> super-block backups (for fsck -b #) at: matusita> <<>> matusita> Yes, during a newfs. Console shows following messages: Maybe I'm wrong. Attached "ps" output says no 'newfs' is running but "cp". So, copying "mfsroot.gz" to a directory of floppy image causes kernel hungup...