In message <19990513003507.cda7015...@hub.freebsd.org> "Jonathan M. Bresler"
writes:
: how about gelfi'll bring a handkerchief so that everyone
: stays dry. ;P
What? No spoo?
Warner
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of
Whoa ... can anyone substantiate that this poor performance is typical
or atypical of DPT SCSI RAID controllers?
I was just about to drop $6000 on a DPT SmartRAID IV 64MB. . .
Chuck Youse
Director of Systems
cyo...@cybersites.com
On Thu, 13 May 1999, Greg Lehey wrote:
> On Wednesday, 12 May
Jonathan M. Bresler wrote:
>
> >
> > How about Klingon? I doubt anyone would question how authentic your accent
> > is ;-)
>
> how about gelfi'll bring a handkerchief so that everyone
> stays dry. ;P
Will people please stop posting this stuff to -hackers.
--
John Birrell - j...@cim
>
> How about Klingon? I doubt anyone would question how authentic your accent
> is ;-)
how about gelfi'll bring a handkerchief so that everyone
stays dry. ;P
jmb
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
On Wednesday, 12 May 1999 at 15:18:22 -0400, Mark J. Taylor wrote:
> On 12-May-99 Matthew Jacob wrote:
>>
>>
I was wondering if anyone has done any work on fsck and very large
file
systems. We have a system that has 126 GB RAID Array. As you can
imagine,
fsck ch
On Wed, May 12, 1999 at 01:38:00PM -0400, a little birdie told me
that Jim Carroll remarked
>
> I was wondering if anyone has done any work on fsck and very large file
> systems. We have a system that has 126 GB RAID Array. As you can imagine,
> fsck chokes trying to alloc enough bl
>
> and all was dandy. However, I'de like to see this actually have a chance
> is h*ll of getting into FreeBSD so I figured that since it is fairly
> useless to most people (I've got some plans for it) that the best thing to
> do would be to make a KLD (like vesa.ko).
I don't think so. Your code
On Wed, May 12, 1999 at 02:24:10PM -0700, Mike Smith wrote:
> > >
> > > As long as you don't insist on trying your ?Irish? (Not) accent out
> > > like last time...
> >
> > no problem, mate, got a new one fer you this year.
>
> I'd avoid that one, since there will be plenty of the authentic
> >
> > I've been doing 120GB+ filesystems for FreeBSD for quite some time. The
> > real fun will be the 1TB filesystems.
>
> How much Swap disk space have you allocated on machines that you fsck'ed
> that were this large ?
Well, here's a current FreeBSD machine that has a couple 60GB raid bo
> >
> > As long as you don't insist on trying your ?Irish? (Not) accent out
> > like last time...
>
> no problem, mate, got a new one fer you this year.
I'd avoid that one, since there will be plenty of the authentic article
around to show up your shabby impersonation.
Pick something m
On Tue, 11 May 1999, Tomas TPS Ulej wrote:
> I saw bounce package and also linux redir. More information about trasparent
> proxy I found at http://www.pdos.lcs.mit.edu/~cananian/Projects/IPfwd/ is
> there solution for FreeBSD? I need this:
>
> BOX A (195.168.11.1) -> REDIR (195.168.11.5) -> DEST
> > > I was wondering if anyone has done any work on fsck and very large
> > > file
> > > systems. We have a system that has 126 GB RAID Array. As you can
> > > imagine,
> > > fsck chokes trying to alloc enough blocks to store it's internal
> > > data
> > > structures (128 MB RAM
:
:
: I was wondering if anyone has done any work on fsck and very large file
: systems. We have a system that has 126 GB RAID Array. As you can imagine,
: fsck chokes trying to alloc enough blocks to store it's internal data
: structures (128 MB RAM, 128 MB Swap)
:
: We would like to
The problem that we ran into in a system with several 130 MB RAID5 arrays
is that the fsck was running out of RAM+swap. We had to add a vnode to swap
to before the fsck would complete (basically added more swap space).
We had to have over 100 MB swap space to fsck the 130 MB volume, and the
syste
> > I was wondering if anyone has done any work on fsck and very large file
> > systems. We have a system that has 126 GB RAID Array. As you can imagine,
> > fsck chokes trying to alloc enough blocks to store it's internal data
> > structures (128 MB RAM, 128 MB Swap)
Huh- I reme
> I was wondering if anyone has done any work on fsck and very large file
> systems. We have a system that has 126 GB RAID Array. As you can imagine,
> fsck chokes trying to alloc enough blocks to store it's internal data
> structures (128 MB RAM, 128 MB Swap)
Might not the use of
I was wondering if anyone has done any work on fsck and very large file
systems. We have a system that has 126 GB RAID Array. As you can imagine,
fsck chokes trying to alloc enough blocks to store it's internal data
structures (128 MB RAM, 128 MB Swap)
We would like to treat this
> I'd really rather have the cross-compilers.
Me too, but for other reasons.
If you are using CVS then the problems you mention of working
between systems will be greatly minimized. Besides, we'd
really like to see you try FreeBSD :-)
My major problem with the approach you are considering rea
On Thu, 13 May 1999, Masachika ISHIZUKA wrote:
>>> The only reason some of the linux codecs are not useable on FreeBSD is
>>> the reference of symbol __IO_stderr, it should be quite easy to convert
>>> them to references to &__sF[2].
>>
>> Compile this little program, use it to process the linux .
>> The only reason some of the linux codecs are not useable on FreeBSD is
>> the reference of symbol __IO_stderr, it should be quite easy to convert
>> them to references to &__sF[2].
>
> Compile this little program, use it to process the linux .xa files, and they
> should be useable on FreeBSD.
Zhihui Zhang wrote:
> By the way, all other metablocks seem to be delay-written. In other words,
> they are not written synchronously. What happens if the system crashes
> before their updates go to disk. I read in the mailinglist that FreeBSD
> metadata I/O are conservative. Can anyone descri
It seems to me that metablocks such as filesystem superblock and cylinder
group control blocks are associated with the device vnode. The indirect
blocks are associated with the file using them to find data blocks. These
indirect blocks are identified by negative block numbers. This makes the
ma
> I'd really rather have the cross-compilers. One for ELF and one for
> the older freebsd object file format(A.OUT?). That way every time
> I make a change I can just type "make freebsdELF" and "make freebsd"
> right afterwards.
...
> The problem with a separate machine(or OS partition) is the time
Luigi Rizzo wrote:
>
> [I am Bcc-ing Mark Podlipec since he might give us some input -- Mark,
> we were discussing about FreeBSD versions of the DLL's]
>
> > > but the xanim author won't go that route. See
> > > http://xanim.va.pubnix.com/xa_dlls.html . The short form is that the
> > > NDA he's
On Wed, 12 May 1999, Kazutaka YOKOTA wrote:
> Hi,
>
> >Hmm. I sent this message a few days ago and it has been silently ignored.
> >Should I consider that an OK to extern the get_mode_param function in
> >vga_isa.c? Or should I take that as a mass "go ahead, we're not going to
> >commit the code
On Wed, 12 May 1999 07:24:55 -0400, John Baldwin wrote:
> Nope, the WANT_AOUT forces them to be compiled as part of the world
> build. That is they only way I know of thus far to build crt0.o and
> friends which are needed for linking aout executables.
Ah, gotcha. Seems like crt0.o and its bud
On 12-May-99 Sheldon Hearn wrote:
>
>
> On Wed, 12 May 1999 00:46:25 -0400, John Baldwin wrote:
>
>> If you are doing it with current -stable sources, you need to define
>> WANT_AOUT
>> (sp?) to true in /etc/make.conf and make world again. That oughta get you
>> the
>> aout bits you need in /u
With 3.1-R the default is to build and aout and elf world. Make sure you don't
have NO_AOUT uncommented in your /etc/make.conf as that turns aout off.
On 12-May-99 Josh2 Lists wrote:
>
> Is it the same for 3.1-Release? That is what I am running.
> I hope so!
>
> Josh
>
> On 12-May-99 John Bald
On Fri, 7 May 1999, Hellmuth Michaelis wrote:
> The cursor keys generate 2 different sequences depending on wether they
> are in "normal" mode or "application mode": normal sends "CSI A" (where
> CSI is 0x9b in 8-bit mode or "ESC [" in 7-bit mode) and application sends
> "SS3 A" (where SS3 is 0x
On Wed, 12 May 1999 00:46:25 -0400, John Baldwin wrote:
> If you are doing it with current -stable sources, you need to define WANT_AOUT
> (sp?) to true in /etc/make.conf and make world again. That oughta get you the
> aout bits you need in /usr/lib/aout.
I take it the aout bits installed will
30 matches
Mail list logo
