Julian mumbled something about:
> how about doug white :-)
> He mentionned being a bit short on cash to go to USEnix
I need the plane ticket & hotel ... I have the student membership so the
actual show is like $100. The plane and hotel could break my measly
credit cards, not to mention my soon-
On Thu, 27 May 1999, Doug White wrote:
> If anyone had a DV (FireWire) camera they could make available, I could
> ship my mac G3/350 down and edit the data it into video clips, then serve
> it with QuickTime Streaming. Put together a decent webpage for it all ...
> burn it to CD... whee ... :)
Some of you maybe saw my letter about the (4)tty ioctl "TIOCMGET int *state".
The issue has been solved and the answer is that indeed the sio.c driver only
reads the status line at opening.
However a status line change will trigger a interrupt, and cause the driver to
read status lines once more.
my questions are at /usr/src/sys/i386/boot/biosboot
v 3.0
1. during boot stage, the initialized data is loaded after kernel text,
but, where is the file that the initialized data is defined in?
2. what is raw boot?
thank you
end
__
»¶ÓÊ
David Scheidt wrote:
>
> On Wed, 26 May 1999, Graeme Tait wrote:
>
> > It contains about 900,000 files, most of which are small, occupying
> > around 2-5 fragments. The small files are updated monthly from a tar
>
> >
> > However, I don't understand how the FFS works, so I'm just probing and
> >
On 27 May 1999, Graeme Tait proclaimed:
> BTW, I realize there is probably a better way to do this (database,
> etc.), and we are thinking in that direction, but for the moment we
> have a legacy setup and not much time to rework it. Also, I would have
> thought that having many tiny files was not
> -Original Message-
> From: Dom Mitchell [SMTP:dom.mitch...@palmerharvey.co.uk]
> Sent: Thursday, May 27, 1999 11:20 AM
> To: Graeme Tait
> Cc: David Scheidt; freebsd-hackers@freebsd.org; i...@boatbooks.com
> Subject: Re: File system gets too fragmented ???
>
> It sounds like yo
On Thu, 27 May 1999, Graeme Tait wrote:
>
> I've received several answers along this direction, but I want to emphasize
> one
> point that I think is being overlooked. When the filesystem is fresh and a
> new
> archive is expanded to create ~900,000 small files each of 2-5 512 byte frags
>
Hi,
I've been experimenting around a bit with the bpf interface, but I seem to
do something completely wrong. I tried to recreate an ARP request, but it
doesn't seem to work. Can anyone find the problem in the source
included..? I've tried just about any combination of host-to-network- and
network
zzh...@cs.binghamton.edu (Zhihui Zhang) writes:
> Suppose you want to mv a directory file (with subdirectories) to another
> name (it is like grafting a subtree to another point), the namecache
> associated with the source directory file will be purged by calling
> cache_purge() (done in ufs_renam
On May 27, 5:07am, Graeme Tait wrote:
} Subject: Re: File system gets too fragmented ???
} I've received several answers along this direction, but I want to emphasize
one
} point that I think is being overlooked. When the filesystem is fresh and a
new
} archive is expanded to create ~900,000
> I don't think that this dump is useful for debugging this problem. Perhaps,
> if
> you compile the kernel with DEBUG_LOCKS, you will get more useful info.
>
> Dima
I checked through the source for DEBUG_LOCKS, it doesn't appear to do anything
other than to printout information information
On May 26, 6:59pm, Graeme Tait wrote:
} Subject: File system gets too fragmented ???
} The filesystem is built with 4096 byte blocks, 512 byte fragments, and
} 2048 bytes/inode, and is mounted 'async noatime'.
}
} It contains about 900,000 files, most of which are small, occupying
} around 2-5 f
On Thu, May 27, 1999 at 07:15:56AM -0700, Don Lewis wrote:
> }
> } The problem seems to be that with successive updates that slightly change
> the
> } size of files, or add or delete files, that a large number of unallocated
> } fragments are created.
Long ago, back when disks were small, slow
On May 27, 10:32am, "David E. Cross" wrote:
} Subject: Re: kernel debugging assistance
} > I don't think that this dump is useful for debugging this problem. Perhaps,
if
} > you compile the kernel with DEBUG_LOCKS, you will get more useful info.
} >
} > Dima
}
} I checked through the source for
>
> It might help somewhat if a file that grows by a fragment can allocate
> the free fragment immediately preceeding it instead of being relocated
> to a fresh block. I don't know if FFS does this or not.
>
Really? FFS allocates free fragments with bitmap, so it should be able to
find free fr
I apologise if this has been discussed before.
The ports collection seems to be growing at alarming rates. On one
hand, this is very good; on the other, it has the unfortunate downside
of having to store ten billion little files on one's hard drive. The
current size of the ports collection is 30
On Thu, 27 May 1999, Max Gotlib wrote:
> Hi!
>
> Some days ago I've faced with the following problem:
> I need some kind of action (while coding user space
> program actively handling the serial port) to get
> sure all the bytes I've wrote to it are _transmitted_.
> I know about "ioctl(fd, TIOCDR
It seems on 2.2.8 and 3.1, pthread_attr_getschedpolicy and
pthread_attr_setschedpolicy are not implemented.
nm /usr/lib/libc_r.a | grep pthread_attr_getschedpolicy
Even tho I could see it from the pthread manpage.
So, how do you guys do thread scheduling?
Thanks!
To Unsubscribe: s
On 27 May 1999, Ville-Pertti Keinonen wrote:
> zzh...@cs.binghamton.edu (Zhihui Zhang) writes:
>
> > Suppose you want to mv a directory file (with subdirectories) to another
> > name (it is like grafting a subtree to another point), the namecache
> > associated with the source directory file will
On Thu, 27 May 1999, Don Lewis wrote:
> On May 26, 6:59pm, Graeme Tait wrote:
> } The filesystem is built with 4096 byte blocks, 512 byte fragments, and
> } 2048 bytes/inode, and is mounted 'async noatime'.
>
> If a file shrinks by one fragment, it'll most likely leave a one
> fragment gap in th
>>I have multiprocessor machine:
>>
>>matherboard SOYO 5TX2/X5 with 2 intel 166 proceccors
>>multiport card Cyclades Cyclom 8Yep
>>
>>All good work until somthing do start to send to /dev/cXX
>>Then kernel panic and reboot !!!
>>
>There seems to be a problem with nested locks. What was the panic
>
> It seems on 2.2.8 and 3.1, pthread_attr_getschedpolicy and
> pthread_attr_setschedpolicy are not implemented.
>
> nm /usr/lib/libc_r.a | grep pthread_attr_getschedpolicy
>
> Even tho I could see it from the pthread manpage.
>
> So, how do you guys do thread scheduling?
Upgrade to 3.2-sta
>>There seems to be a problem with nested locks. What was the panic
>>message?
>
>I have the same problem with my Cyclom Ye cards (both the isa & pci
>variety)
>
>The kernel panics with:
>
>panic messages:
>---
>panic: rslock: cpu: 0, addr: 0xf026a15c, lock: 0x0001
>mp_lock = 0001; cpuid
We've encountered a situation where mbuf allocations inside a device
interrupt handler fails occasionally...and it always seems to happen when
rtalloc() is interrupted. Is this due to some sort of locking (rtalloc is
run at splnet())...should it perhaps be run at splimp() to avoid this problem?
W
On Thu, 27 May 1999, Alex Belits wrote:
> On Thu, 27 May 1999, Doug White wrote:
>
> > If anyone had a DV (FireWire) camera they could make available, I could
> > ship my mac G3/350 down and edit the data it into video clips, then serve
> > it with QuickTime Streaming. Put together a decent webpa
Peter Brevik wrote:
>
> Some of you maybe saw my letter about the (4)tty ioctl "TIOCMGET int *state".
> The issue has been solved and the answer is that indeed the sio.c driver only
> reads the status line at opening.
> However a status line change will trigger a interrupt, and cause the driver to
> From: Dennis
> Date: 1999-05-27 09:43:09 -0700
> To: hack...@freebsd.org
> Subject: mbuf stuff
>
> We've encountered a situation where mbuf allocations inside a device
> interrupt handler fails occasionally...and it always seems to
happen when
> rtalloc() is interrupted. Is this due to some s
> > I don't think that this dump is useful for debugging this problem. Perhaps,
> > if
> > you compile the kernel with DEBUG_LOCKS, you will get more useful info.
>
> I checked through the source for DEBUG_LOCKS, it doesn't appear to do anything
> other than to printout information informati
> Darren Reed wrote:
> >
> > It appears that having "pccardd" enabled in /etc/defaults/rc.conf
> > causes it to be started very early with the end result of the
> > "pcic controller" also allocating irq9 (in a separate pair of
> > messages). i.e. this appears early on:
> >
> > PC-Card Cirrus Log
> In some mail from Wes Peters, sie said:
> [...]
> > PC-Card Intel 82365 (5 mem & 2 I/O windows)
> > pcic: controller irq 3
> > ^^
> > Initializing PC-card drivers: sio
>
> Why does it list "sio" here ? I don't see where sio is actually
> used with PCMCIA here...why doesn't i
> Hi!
>
> Some days ago I've faced with the following problem:
> I need some kind of action (while coding user space
> program actively handling the serial port) to get
> sure all the bytes I've wrote to it are _transmitted_.
> I know about "ioctl(fd, TIOCDRAIN)", but this ioctl
> is accomplished
> my questions are at /usr/src/sys/i386/boot/biosboot
> v 3.0
This code is obsolete and not used anymore.
> 1. during boot stage, the initialized data is loaded after kernel text,
> but, where is the file that the initialized data is defined in?
The kernel.
> 2. what is raw boot?
A modif
> Both of these appear to be in print currently, so you should be able to
> find them (or order them) through any reputbale book shop. Does
> Australia have a good on-line bookstore yet? This might be a good
> opportunity for some FreeBSD hackers with ecommerce skills and a few
> million dollar
Hi folks,
I am trying to set the time zone to GMT on some 2.2.8 machines. This
is trivial on a 3.x system (cd /usr/share/zoneinfo && tzsetup GMT), but
on 2.x, tzsetup(8) doesn't take a time zone argument. Is there another
interface I can use? Or is it safe to copy a -stable tzsetup(8) over
and
>
> We've encountered a situation where mbuf allocations inside a device
> interrupt handler fails occasionally...and it always seems to happen when
> rtalloc() is interrupted. Is this due to some sort of locking (rtalloc is
> run at splnet())...should it perhaps be run at splimp() to avoid this p
On Wed, 19 May 1999, G. Adam Stanislav wrote:
> It should be the constructor that allocates the memory; the
> destructor that frees it. That way you could rely on having exactly the
> amount of memory needed for each class no matter what version of the class
> library you use.
Allowing the constru
> > Hi!
> >
> > Some days ago I've faced with the following problem:
> > I need some kind of action (while coding user space
> > program actively handling the serial port) to get
> > sure all the bytes I've wrote to it are _transmitted_.
> > I know about "ioctl(fd, TIOCDRAIN)", but this ioctl
> >
>I am trying to set the time zone to GMT on some 2.2.8 machines. This
>is trivial on a 3.x system (cd /usr/share/zoneinfo && tzsetup GMT), but
>on 2.x, tzsetup(8) doesn't take a time zone argument. Is there another
>interface I can use? Or is it safe to copy a -stable tzsetup(8) over
>and use t
hi, there!
Are there any projects to implement NSS under FreeBSD (or other *BSDs)?
/fjoe
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
At 12:26 PM 5/27/99 -0700, you wrote:
>>
>> We've encountered a situation where mbuf allocations inside a device
>> interrupt handler fails occasionally...and it always seems to happen when
>> rtalloc() is interrupted. Is this due to some sort of locking (rtalloc is
>> run at splnet())...should it
On Thu, 27 May 1999, Dennis wrote:
> At 12:26 PM 5/27/99 -0700, you wrote:
> >>
> >> We've encountered a situation where mbuf allocations inside a device
> >> interrupt handler fails occasionally...and it always seems to happen when
> >> rtalloc() is interrupted. Is this due to some sort of loc
At 02:57 PM 5/27/99 -0700, you wrote:
>
>
>On Thu, 27 May 1999, Dennis wrote:
>
>> At 12:26 PM 5/27/99 -0700, you wrote:
>> >>
>> >> We've encountered a situation where mbuf allocations inside a device
>> >> interrupt handler fails occasionally...and it always seems to happen
when
>> >> rtalloc()
On Fri, 28 May 1999, Max Khon wrote:
> hi, there!
>
> Are there any projects to implement NSS under FreeBSD (or other *BSDs)?
Might be courteous of you, if you could at least include *some* kind of
definition of what NSS is (like maybe a web pointer?)
+--
hi, there!
On Thu, 27 May 1999, Chuck Robey wrote:
> > Are there any projects to implement NSS under FreeBSD (or other *BSDs)?
>
> Might be courteous of you, if you could at least include *some* kind of
> definition of what NSS is (like maybe a web pointer?)
ah, I'm sorry. NSS stands for "Name
NetBSD has had this for a while.
- ad
On Fri, 28 May 1999, Max Khon wrote:
> hi, there!
>
> On Thu, 27 May 1999, Chuck Robey wrote:
>
> > > Are there any projects to implement NSS under FreeBSD (or other *BSDs)?
> >
> > Might be courteous of you, if you could at least include *some* kind of
>
Well, it took me one more day to get it working (I had a bogus bit-shift in
there), and I did some cleaning (also made probing work). The K6-2 MTRR code
works fine.
It should be ready to be committed now, so I'll attach
it to this message. (it is a required by files.i386, BTW)
I'd like a way to te
Hello all,
I am new to FreeBSD and have been instructed to keep my ports up to date
using CVSup. I have carefully studied the Handbook page on how to setup the
process and have checked out the CVSup web site; however, I am having a bit
of a problem. When I attempt to start CVSup I get an error sta
On Fri, May 28, 1999, Jeff Lush wrote:
> Hello all,
>
> I am new to FreeBSD and have been instructed to keep my ports up to date
> using CVSup. I have carefully studied the Handbook page on how to setup the
> process and have checked out the CVSup web site; however, I am having a bit
> of a proble
In article <199905270619.qaa09...@cheops.anu.edu.au>,
Darren Reed wrote:
> In some mail from Wes Peters, sie said:
> [...]
> > PC-Card Intel 82365 (5 mem & 2 I/O windows)
> > pcic: controller irq 3
> > ^^
> > Initializing PC-card drivers: sio
>
> Why does it list "sio" here ?
"Michael R. Wayne" wrote:
>Long ago, back when disks were small, slow and expensive, someone
>wrote a program that properly defragged a Unix filesystem.
If it was that long ago, chances are it is pre-FFS - the System 5
File System and its predecessors. I remember using a Motorola
SysVR3 system t
51 matches
Mail list logo
