Hi, can you help me with problem with Aladdin V chipset and UDMA.
Here is my dmesg when UDMA in bios is off:
FreeBSD 3.2-STABLE #0: Thu May 20 10:00:54 EEST 1999
ako...@gw.physics.franko.lviv.ua:/usr/src/sys/compile/Firewall
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequen
Hi,
> Well maybe FreeBSD is transmitting packets much faster than Linux. :)
> You still haven't actually measured the transfer speed, so there's
> no way for us to know.
Well, I'll do and report the results to you.
> Grrr. I'm sorry, but I really don't think you're putting the pieces
> together
1. I try to learn something about boot code with version 3.0. I
wander whether I can begin with biosboot?(/usr/src/sys/i386/
boot/biosboot)
2. The initialized data will be loaded into memory after kernel
text during boot stage. And where is the file that the
initialized data is de
On Mon, 31 May 1999 17:47:45 MST, Nick Popoff wrote:
> Sorry if this is off topic for this list, but I'm about to dive head
> first into more advanced FreeBSD and I'm badly in need of a good
> reference book.
Hi Nick,
If "more adva
> Has anyone done any performance benchmarking on the TIGON Gigabit
> Ethernet drivers? Curious to see what sort of link saturation can be
> achieved with various boxen/applications...
470 Mbps application to application using ttcp, on a PII-350 back to
back with a Celeron 300A overclocked to 337
1. I try to learn something about boot code with
version 3.0. I wander whether I can begin with
biosboot?(/usr/src/sys/i386/boot/biosboot)
2. The intialized data will be loaded into memory
after kernel text during boot stage, and where
is the file that the initialized data is defined
At 31/05/99, you wrote:
>
>Sorry if this is off topic for this list, but I'm about to dive head first
>into more advanced FreeBSD and I'm badly in need of a good reference book.
>I was tempted by the Walnut Creek FreeBSD book, but it looks like it only
>covers 2.2.8 and I was concerned that eno
On Tue, Jun 01, 1999 at 12:28:11AM -0500, David Scheidt wrote:
> On Tue, 1 Jun 1999, Eivind Eklund wrote:
>
> > (3) Hit jkh with a baseball bat until he stops refusing to use soft
> > updates on the boot floppy during install (due to "making a point")
>
> What exactly is the point? We clearl
(CCs snipped)
On Tue, 1 Jun 1999, Eivind Eklund wrote:
> (3) Hit jkh with a baseball bat until he stops refusing to use soft
> updates on the boot floppy during install (due to "making a point")
What exactly is the point? We clearly wouldn't be distributing a
kernel withoutthe whole sources,
On Mon, May 31, 1999 at 02:06:22PM +0200, Luigi Rizzo wrote:
> > Now, the problems are:
> >
> > @ It takes a long time to...what? cvsup the tree? That's already
>
> to install the port distribution. it's the slowest part of the install
> process. developers may not experience that, but all ot
In the last episode (Jun 01), Max Khon said:
> hi, there!
>
> On Mon, 31 May 1999, Bill Fumerola wrote:
> > Not really.
> >
> > > E.g.: try to check out port for samba 1.9.18p10
> >
> > $ cvs co -D 08/29/98 samba
> >
> > works for me on freefall.
>
> I have very (VERY!) bad link to anoncvs.fre
Matthew Dillon said:
>
> Alan and I are working on it. We are testing a fix for pipe_read() now
> and I'm working on one for pipe_write(). The fixes basically involve
> holding the pipe's lock throughout all calculations and I/O ops except
> when the code needs to explicitly tsl
hi, there!
On Mon, 31 May 1999, Bill Fumerola wrote:
> > It's hard to check out the port for an arbitrary version of program.
>
> Not really.
>
> > E.g.: try to check out port for samba 1.9.18p10
>
> $ cvs co -D 08/29/98 samba
>
> works for me on freefall.
I have very (VERY!) bad link to ano
On Mon, May 31, 1999 at 04:18:19PM -0700, Matthew Hunt wrote:
> > It will work. Trust me :-)
> >
> > /usr/src/contrib/perl5/hints/freebsd.sh:
>
> I'm not sure I understand. If "-export-dynamic" is supposed to be
> there, then why isn't it? If it's not supposed to be there, then why
> do I need
Sorry if this is off topic for this list, but I'm about to dive head first
into more advanced FreeBSD and I'm badly in need of a good reference book.
I was tempted by the Walnut Creek FreeBSD book, but it looks like it only
covers 2.2.8 and I was concerned that enough had changed since then th
On 31-May-99 Bill Fumerola wrote:
> Not really.
>
> > E.g.: try to check out port for samba 1.9.18p10
>
> $ cvs co -D 08/29/98 samba
>
> works for me on freefall.
Hmm... anon cvs anyone? :)
I have a copy of the src repo but not the ports one..
---
Daniel O'Connor software and network e
I do agree that the current approach is fairly wasteful. Currently,
an unpacked ports tree contains 61767 inodes and occupies 79967
1K-blocks (35184 inodes and 35215 blocks are CVS-related metadata).
This covers 2374 ports in 41 categories. An average user probably
builds 1-2% of these.
How abou
On Mon, May 31, 1999 at 11:41:13PM +0200, Ollivier Robert wrote:
> > I've noticed that dynamic linking in Perl also doesn't work for me,
> > likely for the same reason. I haven't tried rebuilding perl with
> > "-export-dynamic" yet, though.
>
> It will work. Trust me :-)
>
> /usr/src/contrib/pe
David Scheidt wrote:
> On Sun, 30 May 1999, Bill Huey wrote:
>
> > That's fundamentally disturbing especially coming from other fellow
> > Unix variant folks.
>
> Inter-UNIX rivalries are one of things that has kept unix healthy for so
> long. Linux tends to pick up most of the 3L1t3 dudez, wh
Well, after a bit of head scratching, I finally think I've gotten the
hang of the new bus architecture stuff (in general that is, not just
the new ISA and PCI stuff). I'm trying to create an miibus framework so
that I can have an miibus attached to those PCI ethernet drivers which
support MII-base
> Inter-UNIX rivalries are one of things that has kept unix healthy for so
> long. Linux tends to pick up most of the 3L1t3 dudez, who don't know
You must be joking me. Just about every other systems person I've talked
to in past 5 years, (including me) would highly disagree with that citing
tha
According to Matthew Hunt:
> I've noticed that dynamic linking in Perl also doesn't work for me,
> likely for the same reason. I haven't tried rebuilding perl with
> "-export-dynamic" yet, though.
It will work. Trust me :-)
/usr/src/contrib/perl5/hints/freebsd.sh:
-=-=-
# Original based on info
Of all the gin joints in all the towns in all the world, Alexander Maret
had to walk into mine and say:
> Hmm,
>
> I'm no expert and this all sounds reasonable to me, but there are
> things I haven't mentioned yet:
Grrr. What were you waiting for. You should have mentioned them to
start with.
Has anyone done any performance benchmarking on the TIGON Gigabit
Ethernet drivers? Curious to see what sort of link saturation can be
achieved with various boxen/applications...
-marc
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the mess
On Tue, Jun 01, 1999 at 01:21:46AM +1000, Andrew Kenneth Milton wrote:
> 'Harder' is an awkward word, it has too many meanings in this context.
> One meaning says that any extra exertion required rules out the change,
> one meaning says that extra complexity rules out the change. I'm not
> sure whi
On Mon, May 31, 1999 at 01:35:48PM -0700, Mike Smith wrote:
> > Either soft updates or async mounts should be used when initially
> > installing the system.
>
> Maybe you should do an install one of these days.
Should I take that to mean that async mounts are now used during the
installation?
S
> > installing the ports. FreeBSD also seems a bit slow when dealing with
> > lots of small files.
This was discussed a while back; the causes are widely known (and have
nothing to do with "lots of small files").
> Either soft updates or async mounts should be used when initially
> installing t
On Mon, May 31, 1999 at 09:23:34PM +0100, Dean Lombardo wrote:
> occupies at least 512 bytes on disk. So is 44Mb the _actual_ size of
> the whole thing, as stored on disk, or just the sum of individual file
> sizes?
I would expect that Satoshi measured with du (or maybe df if he
has a partition
Satoshi - Ports Wraith - Asami wrote:
>
> @ It is large. Ok, so it's 44MB (the first poster had the size
> completely wrong -- probably had some distfiles or work/ subdirs
> lying around). That's less than 20KB per port. Ok, so you can
> keep only the Makefile, or even less, and le
On Mon, 31 May 1999, Luigi Rizzo wrote:
> I am primarily concerned with that, and secondly with mainteinance
> issues when you have a new/updated port, you generally need to touch
> the Makefile and one or more files in pkg, and the info in pkg/* is
> often the same comments you would put at the b
On Mon, 31 May 1999, Max Khon wrote:
> > @ Version control. Can you check out an arbitrary version of any
> > file? I want to do something like "give me the changes in
> > Makefile between yesterday and today".
>
> It's hard to check out the port for an arbitrary version of program.
On Mon, 31 May 1999, Satoshi - Ports Wraith - Asami wrote:
> It seems to me that you guys are arguing about a problem that doesn't
> really exist. Or at least all ideas proposed so far seem to hurt more
> than help. ;)
Agreed. This whole discussion, I feel, is silly.
This is change for the sak
On Tue, Jun 01, 1999 at 01:04:43AM -1430, Mark Newton wrote:
>
> The bsd.ports.mk file would begin by checking for the existence of
> /usr/ports/buildenv/category/application. If it doesn't exist,
> go looking for it in /cdrom, or on ftp.freebsd.org. If it does
The portcheckout script can easi
On Tue, Jun 01, 1999 at 01:21:46AM +1000, Andrew Kenneth Milton wrote:
>
> How about optionally tarring the 'files' and 'patches' subdirs
> (into seperate tarfiles or as one tarfile) to be extracted when the port
> is needed. This would make cvsupping ports 'harder' I would imagine,
Has anyone i
On Sun, May 30, 1999 at 06:11:51PM -0700, John Polstra wrote:
> > My problem is that login fails, due to undefined symbols in the PAM
> > modules:
>
> I don't know what's going on with your system, but something is messed
> up. Maybe you're trying to mix and match a.out and ELF files. Try
> run
Take 2: I've added a few pictures of a converted board to the web page. I
hope this helps people to figure out if it is do-able for them.
See: http://www.tcja.nl/~wilko/ncr_hack.html
| / o / / _ Arnhem, The Netherlands- Powered by FreeBSD -
|/|/ / / /( (_) BulteWWW : htt
Thus spake Mark Newton (new...@internode.com.au):
> but for most people who just want to build a handful of ports,
> browse the tree to see if there's anything cool they want, and
> then forget the ports tree 'til the next upgrade, it'll cut
How do you want to find out if the port fits your needs
I write a small program to read/write each FreeBSD partition via special
device file names, e.g. /dev/wd0s2e, /dev/rwd0s2e, etc. I have two
questions about doing this:
(1) If I try to read() on these files, the buffer size must be given in
multiples of 512 (sector size). Otherwise, I will get an
:While I really doubt that this is related, I discovered today that I'm able
:to repeatably lock up my -current machine with:
:
:find /home -print | afio -T 3k -G 6 -Z -z -v -o - | tee /scratch/backup.afio
>/dev/rsa0
:
:It runs for about 5 minutes, then hangs completely. Removing the tee and
:writ
On Sun, 30 May 1999 21:28:31 -0700 (PDT)
Bill Huey wrote:
> Possibly, but the thing that bothers me is that I've heard more
> derogatory comments directed against Linux user on this list
> than I have seen come from Microsoft.
...because Microsoft isn't Unix, so being displeased with its ap
On Mon, 31 May 1999, Robert Huff wrote:
: How often _do_ people rebuild their kernels? (On non-testing
:machines.)
: I rebuild/reinstall every two weeks, plus or minus a day or
:two.
I only run -RELEASE. Usually the latest. I build a kernel customized for
my machine with every new
Well, I have a debuging kernel compiled with DEBUG_LOCKS turned on, below is
the result. This was cvsup-ed and built about May 27, 14:00 EDT.
gdb -k /usr/src/sys/compile/STAGGER/kernel.debug vmcore.10 (yes, that's right,
#10 in a little over one week)
GNU gdb 4.18
Copyright 1998 Free Software Fo
> > I'm having serious problems with my 3COM Card too. The problem is
> > that there are many many collisions on the network. If i for
> > example transfer 30MB via samba from one computer to the other i get
> > about 900 collisions.
Leaving busy networks etc. aside, this is purely a characterist
Mark Newton wrote:
> /usr/ports/buildenv would contain everything that the non-special-case
> /usr/ports directories currently contain, except the Makefiles. They'd
> continue to live in their present location.
I thought of another advantage of this approach: You can upgrade
existing ports
Andrew Kenneth Milton wrote:
> How about optionally tarring the 'files' and 'patches' subdirs
> (into seperate tarfiles or as one tarfile) to be extracted when the port
> is needed. This would make cvsupping ports 'harder' I would imagine,
> although not impossible, given the .uu files I've s
Of all the gin joints in all the towns in all the world, Alexander Maret
had to walk into mine and say:
> Hi,
>
>
> > If you have a real, detailed and accurate bug report to
> > submit, then fine:
> > let's hear it. But if you just want to make vague and unsubstantiated
> > complaints, do me
On Mon, May 31, 1999 at 09:22:23PM +0700, Max Khon wrote:
>
> It's hard to check out the port for an arbitrary version of program.
> E.g.: try to check out port for samba 1.9.18p10
Well, samba was upgraded from 1.9.18p10 to 2.0.0 at Mon Jan 18 2:34:03
1999 UTC, so to checkout 1.9.18p10,
$ cvs co
+[ Eivind Eklund ]-
| On Mon, May 31, 1999 at 01:02:50PM +0200, Andrzej Bialecki wrote:
| > Folks, how about _admitting_ finally that our ports collection is a
| > database? We wouldn't need anything else than standard system tools to
| > maintain a p
Luigi Rizzo writes:
> in fact i think the biggest problem, performancewise, is the presence
> of multiple subdirs per port.
Well, if we are going to change the ports mechanism, may I suggest
that we make it easy to create `foreign' packages? Let me explain.
In an ideal world, I'd like to use
c
> Now, the problems are:
>
> @ It takes a long time to...what? cvsup the tree? That's already
to install the port distribution. it's the slowest part of the install
process. developers may not experience that, but all other
users (who buy the cd) do.
I am primarily concerned with that, and s
hi, there!
On Mon, 31 May 1999, Satoshi - Ports Wraith - Asami wrote:
> @ Version control. Can you check out an arbitrary version of any
> file? I want to do something like "give me the changes in
> Makefile between yesterday and today".
It's hard to check out the port for an arbitra
hi, there!
On Mon, 31 May 1999, Satoshi - Ports Wraith - Asami wrote:
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
* From: Ladavac Marino
I don't really have time to butt in (I have to hop on a plane in a few
hours and I haven't finished the presentation slides) but I'd like to
throw in my two cents before this gets out of hand.
* [ML] This would offer an advantage over the existing system
* only if
On Mon, May 31, 1999 at 01:02:50PM +0200, Andrzej Bialecki wrote:
> Folks, how about _admitting_ finally that our ports collection is a
> database? We wouldn't need anything else than standard system tools to
> maintain a ports.db file containing all that we want as DB records.
Rule #1: Any change
> -Original Message-
> From: Luigi Rizzo [SMTP:lu...@labinfo.iet.unipi.it]
> Sent: Monday, May 31, 1999 12:39 PM
> To: mlada...@metropolitan.at
> Cc: ta...@uninet.ee; mlada...@metropolitan.at; nick.hi...@jrc.it;
> freebsd-po...@freebsd.org; freebsd-hackers@FreeBSD.ORG
> Subject: Re
zzh...@cs.binghamton.edu (Zhihui Zhang) writes:
> It seems to me that we can lock at the vnode layer AND at the inode layer.
No, the inode lock is, in most cases, the vnode layer lock. It isn't
obvious because the code assumes that any filesystem using vop_stdlock
has a 'struct lock' as the fi
Chris D. Faulhaber writes:
> I somewhat agree. A custom kernel is useful for setting up and
> tuning parameters (e.g. softupdates); however, unlike Linux, we
> don't have a new kernel every week to reconfigure.
How often _do_ people rebuild their kernels? (On non-testing
machines.)
> > With one big file it is next to impossible to build version 1.1.1 of
> > one
> > port and 1.1.2 of another.
> >
> > With current model i can check out specific branch for
> > all files/ports separately.
> >
> [ML] You have a point there :)
> Of course, you could check out the 1.1
> -Original Message-
> From: Taavi Talvik [SMTP:ta...@uninet.ee]
> Sent: Monday, May 31, 1999 2:38 PM
> To: Ladavac Marino
> Cc: 'Nick Hibma'; freebsd-po...@freebsd.org;
> freebsd-hackers@FreeBSD.ORG
> Subject: RE: a two-level port system? (fwd)
>
> On Mon, 31 May 1999, Ladavac M
On Mon, 31 May 1999, Ladavac Marino wrote:
Disadvantage:
With one big file it is next to impossible to build version 1.1.1 of one
port and 1.1.2 of another.
With current model i can check out specific branch for
all files/ports separately.
best regards,
taavi
> Basically the format will b
> -Original Message-
> From: Nick Hibma [SMTP:nick.hi...@jrc.it]
> Sent: Monday, May 31, 1999 2:05 PM
> To: freebsd-po...@freebsd.org; freebsd-hackers@FreeBSD.ORG
> Subject: Re: a two-level port system? (fwd)
>
> > Folks, how about _admitting_ finally that our ports collection is
jo...@gnu.org (Joel Ray Holveck) writes:
> As we all know, tunefs -o space will hurt write performance. Will it
> hurt read performance? If I don't care about install-time speed, but
> do care about run-time speed and free space, should I populate my
> filesystems at install time with space tun
> > Moving these files to ftp requires good automatic means to keep
> > ftp servers updated. However as of today there are no such means
> > available.
> >
> > CVSup is definitely easiest way to keep well defined collection
> > of files up to date.
>
> Folks, how about _admitting_ finall
On Mon, 31 May 1999, Chris Costello wrote:
> On Sun, May 30, 1999, Nik Clayton wrote:
> > Cheers, committed.
>
>Already? As the CVS tree (at least the one on
> anoncvs.freebsd.org) has it, the so_cred changes haven't been
> committed yet.
*Laugh* I think that the doc was the only thing that
On Mon, 31 May 1999, Taavi Talvik wrote:
> On Mon, 31 May 1999, Rasmus Kaj wrote:
>
> > RW> Alternatively, is it possible to have the port tree be essentially
> > RW> empty (perhaps just the makefile and category directories) and then
> > RW> just have it fetch the makefiles and make the direc
On Mon, 31 May 1999, Rasmus Kaj wrote:
> RW> Alternatively, is it possible to have the port tree be essentially
> RW> empty (perhaps just the makefile and category directories) and then
> RW> just have it fetch the makefiles and make the directories on demand, for
> RW> the individal ports?
>
> "RW" == Robert Withrow writes:
RW> Alternatively, is it possible to have the port tree be essentially
RW> empty (perhaps just the makefile and category directories) and then
RW> just have it fetch the makefiles and make the directories on demand, for
RW> the individal ports?
May I sugg
On Sun, May 30, 1999, Nik Clayton wrote:
> Cheers, committed.
Already? As the CVS tree (at least the one on
anoncvs.freebsd.org) has it, the so_cred changes haven't been
committed yet.
--
Chris Costello
Exclusive: We're the only ones who have the documentation
> A friend of mine upgraded one of his machines to a duel-cpu
> box and upgraded the OS to -STABLE, and he noticed that his
> backups were being corrupted. The corruption appears to occur when
> he transfers huge gzip'd tar files over a 100BaseTX network:
>
> I believe that t
+[ Spike ]-
|
| a good enough job. I think this because in the end FreeBSD is going to
| lose to Linux if only from the sheer momentum of twenty million rabid
| Linux fanatics. And realistically, we aren't doing a damn thing about it.
Technical disc
70 matches
Mail list logo
