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
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 t
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 ti
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"
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 mome
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.
>
>
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.
> > 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
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
>
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
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 Lin
> 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 wi
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 bigcdim
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!
De
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
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:~/
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 (CLEAR
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 Chi
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
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 doin
> 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
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 moun
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 sayin
> > > 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 for
: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 st
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)
> > >
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:
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
> > >
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:
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.
Tha
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
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 yoursel
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 m
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 delete
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 tak
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.
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
> 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: se
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
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 b
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. Tapan
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
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
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
44 matches
Mail list logo
