Re: Network problem with Laptop/Current.
In message <37235ef6.a74d6...@mexcomusa.net> Edwin Culp writes: : With a kernel from April 20 everything works except my pcmcia Viking : Modem which hasn't worked since last weekend. Is anyone else else : having this problem? Could I be doing something wrong? I'm painfully aware of this problem. I see variations on this theme many times. I'm about 2/3 through reworking pcic/pccard to work with the newer, much nicer newbus functions for allocating resources and such. This should be hitting the tree in the early part of this week. Until then, use the April 20th kernel. Warner To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Network problem with Laptop/Current.
In message <199904260643.iaa47...@freebsd.dk> Soren Schmidt writes: : It works fine with both 3.1 and 4.0-current, the reason it fails now : is because the pcic/pccard stuff has not been moved to new-bus yet. : The patches (well 3 oneliners) fixes this for the time being, until : somebody has the time to convert the driver to new-bus. The three oneliners kinda sorta fix it for the time being. Not all laptops are fixed by it (I know my vaio has me using the zp driver because of random panics when I unplug the card). However, if they work for you, more power to you. Rest assured that I'm working on the pcic/pccard stuff right now and should have stage one of newbusification done early this week. Phase one is where minimal cahnges are done to get rid of unstable interrupt hacking that it is doing which used to be right, but now is bogus. Phase two will be much more radical, hopefully obviating the need for pccardd in most cases. Warner To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Network problem with Laptop/Current.
It seems Warner Losh wrote: > In message <199904260643.iaa47...@freebsd.dk> Soren Schmidt writes: > : It works fine with both 3.1 and 4.0-current, the reason it fails now > : is because the pcic/pccard stuff has not been moved to new-bus yet. > : The patches (well 3 oneliners) fixes this for the time being, until > : somebody has the time to convert the driver to new-bus. > > The three oneliners kinda sorta fix it for the time being. Not all > laptops are fixed by it (I know my vaio has me using the zp driver > because of random panics when I unplug the card). However, if they > work for you, more power to you. > > Rest assured that I'm working on the pcic/pccard stuff right now > and should have stage one of newbusification done early this week. > Phase one is where minimal cahnges are done to get rid of unstable > interrupt hacking that it is doing which used to be right, but now is > bogus. Phase two will be much more radical, hopefully obviating the > need for pccardd in most cases. Cool!, let me know if there is something I can test for you!! -Søren To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: config & NO_F00F_HACK
Chris Costello wrote:
> On Sun, Apr 25, 1999, a.leidin...@wurzelausix.cs.uni-sb.de wrote:
> > Hi,
> >=20
> > # ident LINT
> > LINT:
> > $Id: LINT,v 1.589 1999/04/24 21:45:44 peter Exp $
> >=20
> > with:
> > option NO_F00F_HACK
> >=20
> > # config WORK
> > WORK:15: unknown option "NO_F0F_HACK"
> ^
>
>You made a typo.
No, it is a parsing/stringification botch. It's parsed like this:
ID: NO_F
NUMBER: 00 (octal 0)
ID: F_HACK
Of course, an atoi of "00" and then a sprintf("%d") results in a single "0".
I've fixed this here and will commit it shortly, but I'm a bit nervous about
the scope of the change required to prevent this information loss. :-/ I
don't know enough lex/yacc to do context-sensitive tokenization.
Cheers,
-Peter
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: config & NO_F00F_HACK
On 26 Apr, Peter Wemm wrote: > I've fixed this here and will commit it shortly, but I'm a bit nervous about > the scope of the change required to prevent this information loss. :-/ I > don't know enough lex/yacc to do context-sensitive tokenization. What about pseudo-device "i4bq921" at the moment I have to quote. Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: config & NO_F00F_HACK
Alexander Leidinger wrote: > On 26 Apr, Peter Wemm wrote: > > > I've fixed this here and will commit it shortly, but I'm a bit nervous abou t > > the scope of the change required to prevent this information loss. :-/ I > > don't know enough lex/yacc to do context-sensitive tokenization. > > What about > pseudo-device "i4bq921" > at the moment I have to quote. I don't think anything much can be done about that.. The tokenizer essentially ignores whitespace, so these are the same: pseudo-device snp 4 pseudo-device snp4 Without the quotes, your example above is parsed something like this: pseudo-device i 4 bq 921 Ie: a request for 4 units of the i device and 921 units of the bq device, which do not exist, or it will be a syntax error. Unfortunately, you can't use "options i4bq921" since there is: #if NI4BQ921 > 0and... conf/files:i4b/layer2/i4b_l2fsm.c optional i4bq921 That 'N' prefix is for the unit count. Sigh... Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: config & NO_F00F_HACK
On Mon, Apr 26, 1999 at 05:37:51PM +0800, Peter Wemm wrote: [parsing hell elided] > Sigh... Maybe config should be rewritten in perl :-) Ducking, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/_/ jos.bac...@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: config & NO_F00F_HACK
> > On Sun, Apr 25, 1999, a.leidin...@wurzelausix.cs.uni-sb.de wrote:
> > > Hi,
> > >=20
> > > # ident LINT
> > > LINT:
> > > $Id: LINT,v 1.589 1999/04/24 21:45:44 peter Exp $
> > >=20
> > > with:
> > > option NO_F00F_HACK
> > >=20
> > > # config WORK
> > > WORK:15: unknown option "NO_F0F_HACK"
> > ^
> >
> >You made a typo.
>
> No, it is a parsing/stringification botch. It's parsed like this:
>
> ID: NO_F
> NUMBER: 00 (octal 0)
> ID: F_HACK
>
> Of course, an atoi of "00" and then a sprintf("%d") results in a single "0".
>
> I've fixed this here and will commit it shortly, but I'm a bit nervous about
> the scope of the change required to prevent this information loss. :-/ I
> don't know enough lex/yacc to do context-sensitive tokenization.
>
This should be fairly simple, please try this,
Index: lang.l
===
RCS file: /home/ncvs/src/usr.sbin/config/lang.l,v
retrieving revision 1.19
diff -u -r1.19 lang.l
--- lang.l 1999/04/24 18:59:19 1.19
+++ lang.l 1999/04/26 11:47:35
@@ -105,11 +105,14 @@
int hex __P((char *));
%}
-WORD [-A-Za-z_][-A-Za-z_]*
+WORD [A-Za-z_][-A-Za-z_]*
+ALNUM [A-Za-z_][-A-Za-z_0-9]*
+%s NONUM
%%
-{WORD} {
+{WORD} {
int i;
+ BEGIN(0);
if ((i = kw_lookup(yytext)) == -1)
{
yylval.str = strdup(yytext);
@@ -118,6 +121,22 @@
}
tprintf("(%s) ", yytext);
return i;
+ }
+{WORD} {
+ int i;
+
+ if ((i = kw_lookup(yytext)) == -1)
+ REJECT
+ if (i == CONTROLLER || i == DEVICE || i == DISK ||
+ i == PSEUDO_DEVICE || i == AT || i == ON)
+ BEGIN(NONUM);
+ tprintf("(%s) ", yytext);
+ return i;
+ }
+{ALNUM} {
+ yylval.str = strdup(yytext);
+ tprintf("id(%s) ", yytext);
+ return ID;
}
\\\"[^"]+\\\" {
yytext[strlen(yytext)-2] = '"';
> Cheers,
> -Peter
>
-lq
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: config & NO_F00F_HACK
Luoqi Chen wrote:
> > > On Sun, Apr 25, 1999, a.leidin...@wurzelausix.cs.uni-sb.de wrote:
> > > > Hi,
> > > >=20
> > > > # ident LINT
> > > > LINT:
> > > > $Id: LINT,v 1.589 1999/04/24 21:45:44 peter Exp $
> > > >=20
> > > > with:
> > > > option NO_F00F_HACK
> > > >=20
> > > > # config WORK
> > > > WORK:15: unknown option "NO_F0F_HACK"
> > > ^
> > >
> > >You made a typo.
> >
> > No, it is a parsing/stringification botch. It's parsed like this:
> >
> > ID: NO_F
> > NUMBER: 00 (octal 0)
> > ID: F_HACK
> >
> > Of course, an atoi of "00" and then a sprintf("%d") results in a single "0"
.
> >
> > I've fixed this here and will commit it shortly, but I'm a bit nervous abou
t
> > the scope of the change required to prevent this information loss. :-/ I
> > don't know enough lex/yacc to do context-sensitive tokenization.
> >
> This should be fairly simple, please try this,
It works here fine, but I can't pretend that I understand it. :-) Will you
commit it?
Cheers,
-Peter
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: config & NO_F00F_HACK
Jos Backus wrote: > > On Mon, Apr 26, 1999 at 05:37:51PM +0800, Peter Wemm wrote: > [parsing hell elided] > > Sigh... > > Maybe config should be rewritten in perl :-) If it properly respected spaces, it would have been enough. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Encanto Networks chooses FreeBSD over Linux
Carlos C. Tapang wrote: > > Just came across an interesting article in Investor's Business Daily (April > 26th issue) in the Computers and Technology section. The title is "Windows > Foes Pose A Threat: Ex-Novell CEO". In it Bob Frankenberg cites the reason > why his company chose FreeBSD over Linux: they did a very careful evaluation > and "found that there was a 2-1 or 3-1 improvement over Linux". "... A lot > of work had been done to maximize transaction-processing performance." > But "Linux, on the other hand, performs better for individual use" because > of "better network performance". The last sentence above says that "Linux performs better for individual use _because_of_better_network_performance." This is not what the article conveyed. The correct interpretation is rather that Encanto Networks Inc. chose FreeBSD because the company needed better network performance, *not* better desktop performance. A quote from the article follows: We did a very careful evaluation. The reason we went with FreeBSD is that a lot of work had been done to maximize transaction-processing performance. This can improve the speed of accessing Web pages. We found there was a 2- 1 or 3-1 improvement over Linux. Linux, on the other hand, performs better for individual use. In general, if I'm a user of a desktop computer - instead of a network user - I'll get a faster response time on Linux than FreeBSD. We needed better network performance. [referring to an asset of FreeBSD] Paal Sommerhein To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Network problem with Laptop/Current.
> Rest assured that I'm working on the pcic/pccard stuff right now > and should have stage one of newbusification done early this week. > Phase one is where minimal cahnges are done to get rid of unstable > interrupt hacking that it is doing which used to be right, but now is > bogus. Phase two will be much more radical, hopefully obviating the > need for pccardd in most cases. Go Warner Go! Nate To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
file disappeared?
The subject says it all: I removed a file, but according to df, it's still there! pcayk:~/tmp$ df -k . Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/wd0s1f7621844 69756693642899%/usr pcayk:~/tmp$ ls -l -rw-r--r-- 1 ayk1 users 716247040 Apr 22 1999 bigcdimage.iso pcayk:~/tmp$ rm bigcdimage.iso pcayk:~/tmp$ df -k . Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/wd0s1f7621844 69756693642899%/usr How on earth did that happen?!!! So I decided to run fsck, with -p at first: pcayk:/usr/home/ayk1# fsck -p -f /dev/wd0s1f /dev/rwd0s1f: UNREF FILE I=053 OWNER=ayk1 MODE=100644 /dev/rwd0s1f: SIZE=716247040 MTIME=Apr 22 20:36 1999 (CLEARED) /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) /dev/rwd0s1f: 176217 files, 6275813 used, 1346031 free (39575 frags, 163307 blocks, 0.5% fragmentation) OK - the file's there - time to salvage it. pcayk:/usr/home/ayk1# fsck -f /dev/wd0s1f ** /dev/rwd0s1f ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups SUMMARY INFORMATION BAD SALVAGE? [yn] y BLK(S) MISSING IN BIT MAPS SALVAGE? [yn] y FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? [yn] y 176217 files, 6275839 used, 1346005 free (39581 frags, 163303 blocks, 0.5% fragmentation) * FILE SYSTEM MARKED CLEAN * * FILE SYSTEM WAS MODIFIED * pcayk:/usr/home/ayk1# df -k Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/wd0s1a 63503327992562456%/ /dev/wd0s1f 7621844 69756643643399%/usr /dev/wd0s1e 63503112114721219%/var /dev/wd2s1e 8002964 734610716620 100%/usr/local/mp3-archive procfs 440 100%/proc Arrgghhh - now I've done it! Any suggestions on how to deal with this? Thanks, Alex pcayk:~/tmp$ uname -a FreeBSD pcayk.ukc.ac.uk 3.1-STABLE FreeBSD 3.1-STABLE #0: Sun Apr 4 15:58:45 BST 1999 a...@pcayk.ukc.ac.uk:/usr/src/sys/compile/SHAKA i386 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
Dean Lombardo didn't write: > > The subject says it all: I removed a file, but according to df, it's > still there! (snipped) > Thanks, > > Alex Sorry about the name mixup - I accidentally left Netscape open on a friend's box...Anyway, email a...@ukc.ac.uk, not me! Dean To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
On Mon, 26 Apr 1999, Dean Lombardo wrote: > The subject says it all: I removed a file, but according to df, it's > still there! > > pcayk:~/tmp$ df -k . > Filesystem 1K-blocks UsedAvail Capacity Mounted on > /dev/wd0s1f7621844 69756693642899%/usr > > pcayk:~/tmp$ ls -l > -rw-r--r-- 1 ayk1 users 716247040 Apr 22 1999 bigcdimage.iso > > pcayk:~/tmp$ rm bigcdimage.iso > > pcayk:~/tmp$ df -k . > Filesystem 1K-blocks UsedAvail Capacity Mounted on > /dev/wd0s1f7621844 69756693642899%/usr > > > How on earth did that happen?!!! Are you running soft updates? It takes ~30s for changes to take effect if you are. I noticed this myself last week. > So I decided to run fsck, with -p at first: > > > pcayk:/usr/home/ayk1# fsck -p -f /dev/wd0s1f > /dev/rwd0s1f: UNREF FILE I=053 OWNER=ayk1 MODE=100644 > /dev/rwd0s1f: SIZE=716247040 MTIME=Apr 22 20:36 1999 (CLEARED) > /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) > /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) > /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) > /dev/rwd0s1f: 176217 files, 6275813 used, 1346031 free (39575 frags, > 163307 blocks, 0.5% fragmentation) I assume this was in single user mode, otherwise you made a gigantic mess. :-) Doug White Internet: dwh...@resnet.uoregon.edu| FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite| www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
Thank you for a quick response. > > pcayk:~/tmp$ df -k . > > Filesystem 1K-blocks UsedAvail Capacity Mounted on > > /dev/wd0s1f7621844 69756693642899%/usr > > > > pcayk:~/tmp$ ls -l > > -rw-r--r-- 1 ayk1 users 716247040 Apr 22 1999 bigcdimage.iso > > > > pcayk:~/tmp$ rm bigcdimage.iso > > > > pcayk:~/tmp$ df -k . > > Filesystem 1K-blocks UsedAvail Capacity Mounted on > > /dev/wd0s1f7621844 69756693642899%/usr > > > > How on earth did that happen?!!! > > Are you running soft updates? It takes ~30s for changes to take effect if > you are. I noticed this myself last week. I believe not - doesn't that involve adding a "SOFTUPDATES" option to the kernel? I don't have that in my kernel; therefore, disc access should be synchronous by default, right? And it had definitely been longer than 30s before I decided to run fsck (or before the first run completed). What does it all mean? That I have a file occupying 700+ Mb on my hard drive that I can't get rid of? :-( By the way, rm returned almost instantaneously - normally it takes a few seconds to remove such a huge file (that was the reason I even noticed the problem in the first place.) If this is a bug, I would be glad to help, but this kind of error is hard to reproduce... Perhaps someone with an in-depth knowledge of ufs can tell me what really happened (and what exactly did fsck do to my drive, just to make things worse.) > > So I decided to run fsck, with -p at first: > > > > > > pcayk:/usr/home/ayk1# fsck -p -f /dev/wd0s1f > > /dev/rwd0s1f: UNREF FILE I=053 OWNER=ayk1 MODE=100644 > > /dev/rwd0s1f: SIZE=716247040 MTIME=Apr 22 20:36 1999 (CLEARED) > > /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) > > /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) > > /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) > > /dev/rwd0s1f: 176217 files, 6275813 used, 1346031 free (39575 frags, > > 163307 blocks, 0.5% fragmentation) > > I assume this was in single user mode, otherwise you made a gigantic mess. > :-) I did, didn't I? Alex --- A mathematician is a machine for converting coffee into theorems. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
Doug White wrote:
> On Mon, 26 Apr 1999, Dean Lombardo wrote:
>
> > So I decided to run fsck, with -p at first:
> >
> >
> > pcayk:/usr/home/ayk1# fsck -p -f /dev/wd0s1f
> > /dev/rwd0s1f: UNREF FILE I=053 OWNER=ayk1 MODE=100644
> > /dev/rwd0s1f: SIZE=716247040 MTIME=Apr 22 20:36 1999 (CLEARED)
> > /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED)
> > /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED)
> > /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED)
> > /dev/rwd0s1f: 176217 files, 6275813 used, 1346031 free (39575 frags,
> > 163307 blocks, 0.5% fragmentation)
>
> I assume this was in single user mode, otherwise you made a gigantic mess.
> :-)
>
Doesn't the file system just need to be unmounted?
Qualifier: I'm not a file system hacker.
Can VFS_STATFS return a value that indicates whether a file system
is mounted? If so, it would seem logical to have fsck check the status.
status = VFS_STATFS(mp, sbp, p);
if (status & MOUNTED)
perror("file system mounted");
--
Steve
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
RE: file disappeared?
A file's storage isn't freed until its last reference is removed. An open file descriptor is a reference. Do you perhaps have a hung CD burner process or something similar running? If there is something holding that file open, a reboot would almost certainly clear the space. Jason Young ANET Chief Network Engineer > -Original Message- > From: owner-freebsd-curr...@freebsd.org > [mailto:owner-freebsd-curr...@freebsd.org]on Behalf Of Alex > Sent: Monday, April 26, 1999 1:44 PM > To: Doug White > Cc: freebsd-current@FreeBSD.ORG > Subject: Re: file disappeared? > > > > Thank you for a quick response. > > > > > pcayk:~/tmp$ df -k . > > > Filesystem 1K-blocks UsedAvail Capacity Mounted on > > > /dev/wd0s1f7621844 69756693642899%/usr > > > > > > pcayk:~/tmp$ ls -l > > > -rw-r--r-- 1 ayk1 users 716247040 Apr 22 1999 bigcdimage.iso > > > > > > pcayk:~/tmp$ rm bigcdimage.iso > > > > > > pcayk:~/tmp$ df -k . > > > Filesystem 1K-blocks UsedAvail Capacity Mounted on > > > /dev/wd0s1f7621844 69756693642899%/usr > > > > > > How on earth did that happen?!!! > > > > Are you running soft updates? It takes ~30s for changes to > take effect if > > you are. I noticed this myself last week. > > > > I believe not - doesn't that involve adding a "SOFTUPDATES" option to the > kernel? I don't have that in my kernel; therefore, disc access should be > synchronous by default, right? And it had definitely been longer than 30s > before I decided to run fsck (or before the first run completed). > > What does it all mean? That I have a file occupying 700+ Mb on my hard > drive that I can't get rid of? :-( > > By the way, rm returned almost instantaneously - normally it takes a few > seconds to remove such a huge file (that was the reason I even noticed the > problem in the first place.) If this is a bug, I would be glad to help, > but this kind of error is hard to reproduce... > > Perhaps someone with an in-depth knowledge of ufs can tell me what really > happened (and what exactly did fsck do to my drive, just to make things > worse.) > > > > > So I decided to run fsck, with -p at first: > > > > > > > > > pcayk:/usr/home/ayk1# fsck -p -f /dev/wd0s1f > > > /dev/rwd0s1f: UNREF FILE I=053 OWNER=ayk1 MODE=100644 > > > /dev/rwd0s1f: SIZE=716247040 MTIME=Apr 22 20:36 1999 (CLEARED) > > > /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) > > > /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) > > > /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) > > > /dev/rwd0s1f: 176217 files, 6275813 used, 1346031 free (39575 frags, > > > 163307 blocks, 0.5% fragmentation) > > > > I assume this was in single user mode, otherwise you made a > gigantic mess. > > :-) > > > I did, didn't I? > > Alex > > --- > A mathematician is a machine for converting coffee into theorems. > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
In reply:
> Can VFS_STATFS return a value that indicates whether a file system
> is mounted? If so, it would seem logical to have fsck check the status.
>
> status = VFS_STATFS(mp, sbp, p);
> if (status & MOUNTED)
>perror("file system mounted");
I am saying this without having looked at the code first, but I
believe that it is already impossible to umount a filesystem with any
OPEN files on it: "filesystem in use". Assuming that all of the
buffers are flushed upon close, the only thing you really should get
is a clean flag problem, as would happen in a crash on a filesystem
with no open files.
It looks more like he crashed to me, but then something could be
munged up in the code.
is softupdates on?
jim
--
All opinions expressed are mine, if you| "I will not be pushed, stamped,
think otherwise, then go jump into turbid | briefed, debriefed, indexed, or
radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner"
--
Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw
voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant
--
HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
Dean Lombardo wrote: > > Dean Lombardo didn't write: > > > > > The subject says it all: I removed a file, but according to df, it's > > still there! Some running process still has the file open. As soon as that process exits, the space will be freed. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr w...@softweyr.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
RE: file disappeared?
> A file's storage isn't freed until its last reference is removed. An open > file descriptor is a reference. Do you perhaps have a hung CD burner process > or something similar running? Nothing like that - I used a CD burner on another machine, and then ftp'ed the image to my home dir in case I needed more copies. After a few days, I decided that I didn't need it after all, and deleted it... or did I? The question is how badly did I screw things up by running fsck? It still reports pcayk:/etc# fsck -p -f /dev/wd0s1f /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) /dev/rwd0s1f: 176225 files, 6278980 used, 1342864 free (39576 frags, 162911 blocks, 0.5% fragmentation) (I think with -p it doesn't actually salvage anything, just checks the disk). Worth a reboot? Alex --- A mathematician is a machine for converting coffee into theorems. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
On Mon, 26 Apr 1999, Jim Bryant wrote:
> In reply:
> > Can VFS_STATFS return a value that indicates whether a file system
> > is mounted? If so, it would seem logical to have fsck check the status.
> >
> > status = VFS_STATFS(mp, sbp, p);
> > if (status & MOUNTED)
> >perror("file system mounted");
>
> I am saying this without having looked at the code first, but I
> believe that it is already impossible to umount a filesystem with any
> OPEN files on it: "filesystem in use".
umount -f
will force a dismount and make all open references go to deadfs afaik.
-Alfred
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
Jim Bryant wrote:
> In reply:
> > Can VFS_STATFS return a value that indicates whether a file system
> > is mounted? If so, it would seem logical to have fsck check the status.
> >
> > status = VFS_STATFS(mp, sbp, p);
> > if (status & MOUNTED)
> >perror("file system mounted");
>
> I am saying this without having looked at the code first, but I
> believe that it is already impossible to umount a filesystem with any
> OPEN files on it: "filesystem in use". Assuming that all of the
> buffers are flushed upon close, the only thing you really should get
> is a clean flag problem, as would happen in a crash on a filesystem
> with no open files.
>
I wasn't clear in my response. Running "fsck -p" on a mounted
file system can supposedly lead to Bad Things. It seems that fsck
should determine if the file systm is mounted before it can to some
damage.
--
Steve
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
> > > The subject says it all: I removed a file, but according to df, it's > > > still there! > > Some running process still has the file open. As soon as that process > exits, the space will be freed. Of course... stupid me! I used vnconfig to mount the image and then unmounted it, but forgot to do a vnconfig -u... Of course, it's a bit too late now - just got a kernel panic trying to do so (not entirely unexpected - anyone want a core dump... :-) vnconfig was a one-off thing and not a running process, therefore difficult to detect. Many thanks to everyone who responded, and I do apologise for wasting your time. Alex To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: RE: file disappeared?
:Nothing like that - I used a CD burner on another machine, and then ftp'ed :the image to my home dir in case I needed more copies. After a few days, :I decided that I didn't need it after all, and deleted it... or did I? : :The question is how badly did I screw things up by running fsck? : :It still reports : :pcayk:/etc# fsck -p -f /dev/wd0s1f :/dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) :/dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) :/dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) :/dev/rwd0s1f: 176225 files, 6278980 used, 1342864 free (39576 frags, :162911 blocks, 0.5% fragmentation) : :(I think with -p it doesn't actually salvage anything, just checks the :disk). : :Worth a reboot? : :Alex Good god. Alex. NEVER RUN FSCK OUTSIDE OF SINGLE-USER MODE. Also, never 'guess' what an option is supposed to do. Read the man page. In this case, you guessed wrong. -p does salvage things. Reboot, get into the boot prompt, type 'boot -s' ( if a newer boot prompt ) or simply '-s' if an older boot prompt. When you get into SINGLE user mode, type 'fsck'. Do not specify any other options. The fsck run in normal boot will not properly clean up the mess, because the filesystem will probably be marked valid when it isn't. Then reboot again. -Matt Matthew Dillon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
In reply:
> On Mon, 26 Apr 1999, Jim Bryant wrote:
>
> > In reply:
> > > Can VFS_STATFS return a value that indicates whether a file system
> > > is mounted? If so, it would seem logical to have fsck check the status.
> > >
> > > status = VFS_STATFS(mp, sbp, p);
> > > if (status & MOUNTED)
> > >perror("file system mounted");
> >
> > I am saying this without having looked at the code first, but I
> > believe that it is already impossible to umount a filesystem with any
> > OPEN files on it: "filesystem in use".
>
> umount -f
>
> will force a dismount and make all open references go to deadfs afaik.
>
> -Alfred
I stand corrected.
I must of misinterpreted the -f to mean -f[orget-this-option!], in a
moment of self-preservation. As I recall -f is a last resort.
jim
--
All opinions expressed are mine, if you| "I will not be pushed, stamped,
think otherwise, then go jump into turbid | briefed, debriefed, indexed, or
radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner"
--
Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw
voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant
--
HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
RE: file disappeared?
Fscking a live system is a Bad Idea(tm) and should be avoided. Reboot into single-user and fsck it manually (while unmounted). Jason Young ANET Chief Network Engineer > -Original Message- > From: Alex [mailto:a...@ukc.ac.uk] > Sent: Monday, April 26, 1999 2:06 PM > To: Jason Young > Cc: Doug White; freebsd-current@FreeBSD.ORG > Subject: RE: file disappeared? > > > > > A file's storage isn't freed until its last reference is > removed. An open > > file descriptor is a reference. Do you perhaps have a hung CD > burner process > > or something similar running? > > > Nothing like that - I used a CD burner on another machine, and then ftp'ed > the image to my home dir in case I needed more copies. After a few days, > I decided that I didn't need it after all, and deleted it... or did I? > > The question is how badly did I screw things up by running fsck? > > It still reports > > pcayk:/etc# fsck -p -f /dev/wd0s1f > /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) > /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) > /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) > /dev/rwd0s1f: 176225 files, 6278980 used, 1342864 free (39576 frags, > 162911 blocks, 0.5% fragmentation) > > (I think with -p it doesn't actually salvage anything, just checks the > disk). > > Worth a reboot? > > Alex > > --- > A mathematician is a machine for converting coffee into theorems. > > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
On Mon, 26 Apr 1999, Alex wrote: > > > pcayk:~/tmp$ df -k . > > > Filesystem 1K-blocks UsedAvail Capacity Mounted on > > > /dev/wd0s1f7621844 69756693642899%/usr > > > > > > pcayk:~/tmp$ ls -l > > > -rw-r--r-- 1 ayk1 users 716247040 Apr 22 1999 bigcdimage.iso > > > > > > pcayk:~/tmp$ rm bigcdimage.iso > > > > > > pcayk:~/tmp$ df -k . > > > Filesystem 1K-blocks UsedAvail Capacity Mounted on > > > /dev/wd0s1f7621844 69756693642899%/usr > > > > > > How on earth did that happen?!!! > > > > Are you running soft updates? It takes ~30s for changes to take effect if > > you are. I noticed this myself last week. > > I believe not - doesn't that involve adding a "SOFTUPDATES" option to the > kernel? I don't have that in my kernel; therefore, disc access should be > synchronous by default, right? And it had definitely been longer than 30s > before I decided to run fsck (or before the first run completed). If you're running default disk access then I'm guessing some program still has the file open. Perhaps 'cdrecord' hung? > > I assume this was in single user mode, otherwise you made a gigantic mess. > > :-) > > I did, didn't I? For the future, running fsck in multiuser mode is a no-no. Doug White Internet: dwh...@resnet.uoregon.edu| FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite| www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
Doug White once wrote: > > > I assume this was in single user mode, otherwise you made a gigantic mess. > > > :-) > > > > I did, didn't I? > > For the future, running fsck in multiuser mode is a no-no. Not "in multiuser mode" but "on a mounted filesystem", is it? -mi To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Network problem with Laptop/Current.
NAKAGAWA Yoshihisa wrote: > > PC-Card VLSI 82C146 (5 mem & 2 I/O windows) > > It is probably TI CardBus controller, -current code not support it > correctly. You should be use PAO. > I cannot use paq with current and it has been working fine for sometime. The newbus seems to have killed it. Thanks ed To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Network problem with Laptop/Current.
Warner Losh wrote: > In message <199904260643.iaa47...@freebsd.dk> Soren Schmidt writes: > : It works fine with both 3.1 and 4.0-current, the reason it fails now > : is because the pcic/pccard stuff has not been moved to new-bus yet. > : The patches (well 3 oneliners) fixes this for the time being, until > : somebody has the time to convert the driver to new-bus. > > The three oneliners kinda sorta fix it for the time being. Not all > laptops are fixed by it (I know my vaio has me using the zp driver > because of random panics when I unplug the card). However, if they > work for you, more power to you. > > Rest assured that I'm working on the pcic/pccard stuff right now > and should have stage one of newbusification done early this week. > Phase one is where minimal cahnges are done to get rid of unstable > interrupt hacking that it is doing which used to be right, but now is > bogus. Phase two will be much more radical, hopefully obviating the > need for pccardd in most cases. > > Warner I'll be glad to test with a generic k6-2 running current, if it will help. Thanks, ed To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
According to Dean Lombardo: > How on earth did that happen?!!! Are you using softupdates ? If yes, there is a 30s window where the space is still taken and not given back to the system. > So I decided to run fsck, with -p at first: Never run fsck on a live filesystem, you could screw up yourself big time. > Any suggestions on how to deal with this? Either do a lot of sync or just wait 30s. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
On Mon, 26 Apr 1999, Mikhail Teterin wrote: > Doug White once wrote: > > > > > I assume this was in single user mode, otherwise you made a gigantic > > > > mess. > > > > :-) > > > > > > I did, didn't I? > > > > For the future, running fsck in multiuser mode is a no-no. > > Not "in multiuser mode" but "on a mounted filesystem", is it? Actually, I believe you're correct. I apologize for the goof. Doug White Internet: dwh...@resnet.uoregon.edu| FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite| www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: fxp driver and dhclient
Eric Hodel wrote: > > When running dhclient with the kernel fxp driver I get a kernel panic in > ifconfig. Might be some other things I enabled in the kernel, but I haven't > double-checked yet. I got it all straightened out, something in the config file was messing up, but I accidentally deleted it before I could figure out what. -- Eric Hodel hodel...@seattleu.edu "If you understand what you're doing, you're not learning anything." -- A. L. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
Alex wrote: > > > pcayk:~/tmp$ rm bigcdimage.iso > > > pcayk:~/tmp$ df -k . > > > Filesystem 1K-blocks UsedAvail Capacity Mounted on > > > /dev/wd0s1f7621844 69756693642899%/usr > > > How on earth did that happen?!!! > > > > Are you running soft updates? It takes ~30s for changes to take effect if > > you are. I noticed this myself last week. > > I believe not - doesn't that involve adding a "SOFTUPDATES" option to the > kernel? I don't have that in my kernel; therefore, disc access should be > synchronous by default, right? And it had definitely been longer than 30s > before I decided to run fsck (or before the first run completed). Ok, something has the file open then - storage is not freed until the last reference to the file disappears. This is so that you can rm a file on a multitasking system without making processes that might be using the file at the time fall over and die (for a similar effect, try "rm /var/log/messages" -- You'll note that storage for the file isn't freed until you kill syslogd; in fact, if you generage log messages the file will "grow" and consume more space even though it doesn't have a directory entry. An application might have the file open; Alternatively, since it's a disk image which I presume you've been testing, you could have it attached to a vn device; if that's the case, something like "vnconfig -u /dev/vn0" will detach it, close the last reference to the file, and free the associated storage. Finally, it's possible that there was a hard link to the file. Given that fsck bitched about it being an unref'ed file that's probably unlikely, but the fact stil remains that hardlinks are a legitimate reason for storage to remain allocated after you've deleted something: Once again, the file isn't really deleted until the last reference to it disappears. > Perhaps someone with an in-depth knowledge of ufs can tell me what really > happened (and what exactly did fsck do to my drive, just to make things > worse.) No need for an in-depth knowledge of UFS; this is standard UNIX behaviour, regardless of the underlying filesystem. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
Alex wrote: > The question is how badly did I screw things up by running fsck? > (I think with -p it doesn't actually salvage anything, just checks the > disk). > Worth a reboot? Definitely: -p *does* salvage things. Boot to single user and run fsck manually to make sure everything's ok. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Kant Kompile Current today
uname -a: FreeBSD cerebro.mn26.integris-ds.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Apr 20 23:50:52 CDT 1999 sl...@cerebro.mn26.integris-ds.com:/usr/src/sys/compile/MYCONFIG i386 cvsup'ed a couple minutes ago gives me this. (I attatched a gzip'ed copy of the build log too) ===> doc /usr/obj/usr/src/gnu/usr.bin/awk/doc created for /usr/src/gnu/usr.bin/awk/doc cd /usr/src/gnu/usr.bin/bc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -D_BUILD_TOOLS cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -D_BUILD_TOOLS all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -D_BUILD_TOOLS -B install cleandir obj rm -f .depend /usr/obj/usr/src/gnu/usr.bin/bc/GPATH /usr/obj/usr/src/gnu/usr.bin/bc/GRTAGS /usr/obj/usr/src/gnu/usr.bin/bc/GSYMS /usr/obj/usr/src/gnu/usr.bin/bc/GTAGS bison -y -d -o bc.c /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y conflicts: 1 shift/reduce cc -L/opt/gnome/lib -I/opt/gnome/include -L/usr/local/lib -I/usr/local/include -I. -I/usr/src/gnu/usr.bin/bc -I/usr/src/gnu/usr.bin/bc/../../../contrib/bc/h -DHAVE_CONFIG_H -I/usr/obj/usr/src/tmp/usr/include -c bc.c /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y: In function `yyparse': /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: `interactive' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: for each function it appears in.) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: `quiet' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:170: `break_label' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:174: `genstr' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:181: `continue_label' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:200: `next_label' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:244: `if_label' undeclared (first use in this function) *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- Shawn <=== America Held Hostage ===> Day 2287 for the poor and the middle class. Day 2306 for the rich and the dead. 635 days remaining in the Raw Deal. <> build.log.gz Description: application/gunzip
Re: config & NO_F00F_HACK
> It works here fine, but I can't pretend that I understand it. :-) Will you > commit it? > > Cheers, > -Peter > There's some problems with one I posted (e.g. can't deal with cases where a keyword is followed immediately by a number like irq1), I'll commit a better one. -lq To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Network problem with Laptop/Current.
Warner Losh wrote: > In message <37235ef6.a74d6...@mexcomusa.net> Edwin Culp writes: > : With a kernel from April 20 everything works except my pcmcia Viking > : Modem which hasn't worked since last weekend. Is anyone else else > : having this problem? Could I be doing something wrong? > > I'm painfully aware of this problem. I see variations on this theme > many times. I'm about 2/3 through reworking pcic/pccard to work with > the newer, much nicer newbus functions for allocating resources and > such. This should be hitting the tree in the early part of this > week. Until then, use the April 20th kernel. > > Warner Thank you, that is what I'm doing:-) ed To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Floppies and laptops
I realize there are only so many drivers you can crunch on a floppy... with that in mind, and with the advent of many laptops comnig about that people would like to net-install, would it not be more practical to provide an alternate mfsroot that would be more apt to find your PCMCIA card? Would be a really handy tool/option to have. -F To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Encanto Networks chooses FreeBSD over Linux
Thanks for the correction. I misread it. Yes, Mr. Frankenberg does say in effect that FreeBSD has better network performance than Linux, and that Linux is only good for desktop use. Carlos C. Tapang http://www.genericwindows.com -Original Message- From: PÃ¥l Sommerhein To: Carlos C. Tapang Cc: freebsd-current@freebsd.org ; freebsd-sta...@freebsd.org Date: Monday, April 26, 1999 8:41 AM Subject: Re: Encanto Networks chooses FreeBSD over Linux >Carlos C. Tapang wrote: >> >> Just came across an interesting article in Investor's Business Daily (April >> 26th issue) in the Computers and Technology section. The title is "Windows >> Foes Pose A Threat: Ex-Novell CEO". In it Bob Frankenberg cites the reason >> why his company chose FreeBSD over Linux: they did a very careful evaluation >> and "found that there was a 2-1 or 3-1 improvement over Linux". "... A lot >> of work had been done to maximize transaction-processing performance." >> But "Linux, on the other hand, performs better for individual use" because >> of "better network performance". > >The last sentence above says that "Linux performs better for individual use >_because_of_better_network_performance." This is not what the article >conveyed. The correct interpretation is rather that Encanto Networks Inc. >chose FreeBSD because the company needed better network performance, *not* >better desktop performance. A quote from the article follows: > > We did a very careful evaluation. The reason > we went with FreeBSD is that a lot of work had > been done to maximize transaction-processing > performance. This can improve the speed of > accessing Web pages. We found there was a > 2- 1 or 3-1 improvement over Linux. > > Linux, on the other hand, performs better for > individual use. In general, if I'm a user of a > desktop computer - instead of a network user > - I'll get a faster response time on Linux than > FreeBSD. We needed better network performance. > > > [referring to an asset of FreeBSD] > > >Paal Sommerhein > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: suspend mode broken since one week ago
On Fri, 23 Apr 1999, Warner Losh wrote: > In message <87so9r3x44@muon.xs4all.nl> Peter Mutsaers writes: > : Is this a bug that I should report through send-pr, is it already > : known as a bug or is this an intentional change in behaviour? > > This is a known bug. I thought I kludged around it in apm.c in the > timeframe that you mentioned. Do you have > $Id: apm.c,v 1.80 1999/04/21 07:57:55 imp Exp $ > or newer? Yup. * $Id: apm.c,v 1.80 1999/04/21 07:57:55 imp Exp $ and zzz (and apm -z) don't do much. If we had ACPI support, I'd try hitting the power button - alex To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
RE: Fatal Trap 12
Warner, Thanks for the pointer! The only card I have that specifies a memory address is ed0 at 0xd8000. I removed the memory address in my config file, rebuilt the kernel and everything seems to works fine now. This is a older NE2000 clone card with jumpers for irq and memory address. I have been using this card for years without a problem or complaint. Why would it cause problems now? Thanks again. Greg Shaffer > -Original Message- > From: Warner Losh [mailto:i...@harmony.village.org] > Sent: Monday, April 26, 1999 12:34 AM > To: Greg Shaffer > Subject: Re: Fatal Trap 12 > > > In message <000101be8f95$45256410$024ab...@aegis.leaky.com> "Greg > Shaffer" writes: > : At trace in ddb provides the following: > : kvtop(0) at kvtop+0x2d > : isa_compat_probe(...) at isa_compat_probe+0x297 > : DEVICE_PROBE(...) at DEVICE_PROBE+0x25 > > Hmmm. Looks like somebody is trying to use location zero... I've > seen this when I had a bogus mem address for a card. > > Warner > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Our routed - Vern says it's old and buggy.
Do we have any plans to update it to his latest offering? I believe NetBSD's already done so and would be a good source for the bits if we need them. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
