Re: More PCI->PCMCIA bridge stuff

[Warner Losh]

In message <[EMAIL PROTECTED]> Peter Pentchev writes:
: Yes, I had the same problem with my PCMCIA->PCI bridge.  I solved it with
: the following patch, which adds a new option to pccardd: -S maxslot.
: Then, add -S 1 to pccardd_flags in your /etc/rc.conf, and you're all set.

On current, without any patches, I hang just when I go to try to mount
/.  So changes to userland won't help much :-)  I have some patches
that should help, but I'm not quite ready to commit them.

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: x86-64 Hammer and IA64 Itainium

[Leif Neland]

- Original Message - 
From: "Sergey Babkin" <[EMAIL PROTECTED]>
To: "Michael C . Wu" <[EMAIL PROTECTED]>
Cc: "Jeremiah Gowdy" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, April 27, 2001 4:09 AM
Subject: Re: x86-64 Hammer and IA64 Itainium

> Anothing interesting point is that the optimisation for IA-64
> seems to be highly processor-specific: the code optimized for
> Itanium won't be optimal for McKinley and vice versa.  I've heard
> an estimation of about 1.5 times speed increase due to the
> model-specific optimisation.
> 
Perhaps commercial software will need to come in (encrypted) source and be compiled to 
the the current processor...

Leif


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: NAT and IPFiltering

[Sverre Valgeirsson]

On Fri, Apr 27, 2001 at 12:07:47AM +0200, Jesús Arnáiz wrote:
> Hi!
> 
> I'm configuring a server able to do NAT and IP FILTERING (IPF).
> What are the required options that I should set to the kernel?
> 
> I have this:
> 
> --
> options IPFILTER
> options IPFILTER_LOG
> options IPFIREWALL
> options IPDIVERT
> ---
> 
> but I'm not sure if IPFIREWALLING should be (I'm not going to use ipfw).

If you just want IPFILTER then you can skip the IPFIREWALL and IPDIVERT. 

/sverre
-- 
If you're happy, you're successful.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: BSDI and Marketing 101

[Mark Sergeant]

Then again you could also download an iso of 4.3 for free, go to BSD Mall and
get a 4 CD set for 39.95 etc. The thing you pay for when you are buying these
box sets is usually the manual, some also include a certain amount of telephone
support etc. So while one may be 29.95 and the other another 100 dollars more
you may not get a book / as good a book with the 29.95 version. Also you may or
may not get phone support etc with the one you pay 100 for, I know many
companies that would pay 129.95 for an OS that you get a book, support n cd's
for, hell I know companies that buy Windows 98 / 2000 :P

Cheers,

Mark

On Thu, 26 Apr 2001 21:47:52 -0700, Julian Elischer said:

:: Dennis wrote:
::  > 
::  > At 08:12 PM 04/26/2001, David O'Brien wrote:
::  > >On Thu, Apr 26, 2001 at 07:03:47PM -0400, Dennis wrote:
::  > > > I saw BSDIs retail product of FreeBSD in a local bookstore the other day,
::  > > > and it became sadly clear why LINUX, although highly inferior, is so much
::  > > > more widely used. Right next to Freebsd (priced at $129.95) was Mandrake
::  > > > LINUX for $29.95.
::  > >
::  > >I should use your quote from this morning... but I won't.
::  > >You don't understand channel marketing.  And I'll just leave it at that.
::  > 
::  > Actually I do. Channel marketing requires a marketing base, which they dont
::  > have. You have to establish a base before you can gouge.
::  > 
::  > I know that 0 X 129. < anything X 29.
::  
::  Denis is certainly right about this..
::  

-- 
Mark Sergeant
Unix Systems Administrator

Fortune follows...

Don't believe everything you hear or anything you say.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: BSDI and Marketing 101

[Julian Elischer]

Dennis wrote:
> 
> At 08:12 PM 04/26/2001, David O'Brien wrote:
> >On Thu, Apr 26, 2001 at 07:03:47PM -0400, Dennis wrote:
> > > I saw BSDIs retail product of FreeBSD in a local bookstore the other day,
> > > and it became sadly clear why LINUX, although highly inferior, is so much
> > > more widely used. Right next to Freebsd (priced at $129.95) was Mandrake
> > > LINUX for $29.95.
> >
> >I should use your quote from this morning... but I won't.
> >You don't understand channel marketing.  And I'll just leave it at that.
> 
> Actually I do. Channel marketing requires a marketing base, which they dont
> have. You have to establish a base before you can gouge.
> 
> I know that 0 X 129. < anything X 29.

Denis is certainly right about this..

-- 
  __--_|\  Julian Elischer
 /   \ [EMAIL PROTECTED]
(   OZ) World tour 2000-2001
---> X_.---._/  
v

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

°í±Þ¾×¼¼¼­¸®¸¦ Á¤¸» ±âºÐÁÁÀº °¡°Ý¿¡

[kim]

Title: 



 
Çã¶ô¾øÀÌ ¸ÞÀÏÀ» µå·Á Á˼ÛÇÕ´Ï´Ù.
°í±Þ¾×¼¼¼­¸®¸¦ Á¤¸» ±âºÐÁÁÀº °¡°Ý¿¡ °øÀå¿¡¼­ Á÷Á¢ 
ÆǸÅÇÕ´Ï´Ù.
¸Ó¸®ÇÉ,¸ñ°ÉÀÌ,ÆÈÂîµî 100¿©°¡Áö ÀÌ»óÀÇ ¼±¸íÇÑ »çÁø°ú ÃÖÀú 
°¡°ÝÇ¥
http://www.vivi.co.kr/
¡¡** 10.000¿ø ÀÌ»ó ±¸¸Å½Ã ¼±¹°À» µë»Ò µå¸³´Ï´Ù.
  ½ÃÁßÆǸŰ¡ÀÇ 
¹Ý°ª~30% 
°¡°ÝÀÔ´Ï´Ù.
»çÁøÀ» Ŭ¸¯Çϼ¼¿ä
¡¡


  
  

  

  
  
3001-7700¿ø(¼Û·áÆ÷ÇÔ)
3006-8500¿ø(¼Û·áÆ÷ÇÔ)
  


  
2003-15000¿ø(¼Û·áÆ÷ÇÔ)
4010-3700¿ø(¼Û·áÆ÷ÇÔ)
  


  
8024-6000¿ø(¼Û·áÆ÷ÇÔ)
8039-3000¿ø(¼Û·áÆ÷ÇÔ)
¿À½ºÆ®¸®¾Æ ¼öÀÔ ¶óÀνºÅæÀ» »ç¿ëÇÕ´Ï´Ù.
ÀÌ-¸ÞÀÏ
º»»ç,°øÀå : °æ±âµµ Æ÷õ±º °¡»ê¸é °¨¾Ï¸® 515-1
ÀüÈ­: 031-535-6995
Æѽº: 031-535-6994
»ç¾÷ÀÚµî·Ï¹øÈ£: 
112-03-23802


èR{.nÇ+‰·¬zwfj)m¢f£¢·hškyàRŠàÂ+aº{.nÇ+‰·Ÿ­ç›±ØZrG«²)í…æèw*¶¦zˁ

Re: x86-64 Hammer and IA64 Itainium

[Jeremiah Gowdy]

> IIRC, KA-64 does not even have an emulator yet.  Rest assured that
> there will be a lot of people in and out of this project interested
> in supporting a KA-64 port of FreeBSD.  

What's KA-64 ?



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: x86-64 Hammer and IA64 Itainium

[Sergey Babkin]

"Michael C . Wu" wrote:
> 
> With the branch prediction, cache tracing, and EPIC instructions,
> you really want to use an ILP compiler.  Without a compiler that
> can decide on good ways to output binaries that run with all the IA-64
> innovations^Wreinvention-of-the-wheels.

Anothing interesting point is that the optimisation for IA-64
seems to be highly processor-specific: the code optimized for
Itanium won't be optimal for McKinley and vice versa.  I've heard
an estimation of about 1.5 times speed increase due to the
model-specific optimisation.

-SB

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: x86-64 Hammer and IA64 Itainium

[David O'Brien]

On Thu, Apr 26, 2001 at 05:59:06PM -0500, Michael C . Wu wrote:
> IIRC, KA-64 does not even have an emulator yet.

Are you making a distinction between emulator and simulator?  Such that
SimNow! and VirtuHammer don't fall into what you are speaking of?

-- 
-- David  ([EMAIL PROTECTED])

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: BSDI and Marketing 101

[Drew Eckhardt]

In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
 writes:
>
>I saw BSDIs retail product of FreeBSD in a local bookstore the other day, 
>and it became sadly clear why LINUX, although highly inferior, is so much 
>more widely used. 

Linux was much more widely used because the Jolitzes felt their i86 unix
port was a "research system" which didn't need to run on arbitrary hardware
or do what people wanted while Linus was initially working on a Minix clone
that would run on his hardware and maintained that "practical" attitude 
throughout the project.  

Linux also provided substantially better interactive performance under load,
which was the normal operating state for starving students.  Who in turn
wrote drivers.

Finally, Linux was not endangered by the AT&T lawsuit.

Combine these factors, and Linux was more rapidly accepted by starving 
hackers, enough of whom contributed drivers for their hardware rather
than buying something which would work.

The larger hacker community rubbed off on more hobbiests than
the smaller in BSD.  More hobbiests could actually run linux on
their systems because of both hardware support and Wintel coexistance
(things like non-destructive repartitioning, the unix semantics on 
msdos file systems, etc. really helped).  

IOW, Linux was useful to more people sooner.  Even if BSD can match 
Linux's growth rate, that head start means BSD won't catch up in numbers.

Of course, this is irrelevant.  I run BSD on my black (actually,
they're purple) boxes and servers.  I can get jobs doing BSD 
professionally.  If people want to use Linux where BSD works better,
that's their perogative as long as I don't have to hold their hand
or clean up after them.

>What they dont seem to realize is that people who know its worth more than 
>linux also know they dont have to pay $129. for free software with fancy 
>packaging and paid support.

Joe Average (where the numbers come from and perhaps venture capital) is 
going to go with Linux because of name recognition, it works well enough
(which is even better than BSD) for his purposes (Installing some Linux
binaries on BSD requires finding the corresponding Linux libraries, which
is easier said than done.  Installing them on Linux just works.  Linux also
has more complete driver support.  It can coexist easier with Wintel.).

Personally, I'm now running BSD exclusively because it was more flood 
resistant than Linux (my Linux mail server & DNS machine did not survive
the catastrophic water heater failure, while the robust BSD box was more
water tight).

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: BSDI and Marketing 101

[David O'Brien]

On Thu, Apr 26, 2001 at 08:00:35PM -0400, Dennis wrote:
> At 08:12 PM 04/26/2001, David O'Brien wrote:
> >On Thu, Apr 26, 2001 at 07:03:47PM -0400, Dennis wrote:
> > > I saw BSDIs retail product of FreeBSD in a local bookstore the other day,
> > > and it became sadly clear why LINUX, although highly inferior, is so much
> > > more widely used. Right next to Freebsd (priced at $129.95) was Mandrake
> > > LINUX for $29.95.
> >
> >I should use your quote from this morning... but I won't.
> >You don't understand channel marketing.  And I'll just leave it at that.
> 
> Actually I do. Channel marketing requires a marketing base, which they dont 
> have. You have to establish a base before you can gouge.

What you fail to realize is computer stores and bookstores *want* and
have requested the $129.95 product.  They want even more expensive ones
than that.   The really don't care for $29.95 products as the margins are
too low for their liking -- unless they feel the product is a "leader"
one.
 
-- 
-- David  ([EMAIL PROTECTED])

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: BSDI and Marketing 101

[George Reid]

On Thu, 26 Apr 2001, Dennis wrote:

> Your need to continuously criticize me no matter how trivial the subject is 
> very satisfying to me. Makes you look like even more of a loser than you are.

Actually, it's the first time I've replied to one of your troll posts
before. Seeing (from both current and previous postings) that you're
clearly not capable of holding a reasonable discussion, it'll be the last.

Further messages on the subject will be ignored by me, but I expect you'll
post them to bolster your own ego anyway.

greid


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: BSDI and Marketing 101

[Dennis]

At 08:24 PM 04/26/2001, George Reid wrote:
>On Thu, 26 Apr 2001, Dennis wrote:
>
> > >This is relevant to -hackers in what way?
> >
> >
> > well you copied hackers, so you either think so also or you are just an
> > ass. Learn to ignore things you dont care about, you'll live longer.
>
>I "either think so" w.r.t what? I didn't make a definite statement.
>
>Learn to read properly, you'll make yourself look like less of a dickhead.

You asked if it was relevent, and I said you much think so also. Its not 
brain surgery

Your need to continuously criticize me no matter how trivial the subject is 
very satisfying to me. Makes you look like even more of a loser than you are.

db


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: BSDI and Marketing 101

[Dennis]

At 08:12 PM 04/26/2001, David O'Brien wrote:
>On Thu, Apr 26, 2001 at 07:03:47PM -0400, Dennis wrote:
> > I saw BSDIs retail product of FreeBSD in a local bookstore the other day,
> > and it became sadly clear why LINUX, although highly inferior, is so much
> > more widely used. Right next to Freebsd (priced at $129.95) was Mandrake
> > LINUX for $29.95.
>
>I should use your quote from this morning... but I won't.
>You don't understand channel marketing.  And I'll just leave it at that.

Actually I do. Channel marketing requires a marketing base, which they dont 
have. You have to establish a base before you can gouge.

I know that 0 X 129. < anything X 29.

do you?

DB


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: x86-64 Hammer and IA64 Itainium

[Andrew Hesford]

On Thu, Apr 26, 2001 at 06:08:36PM -0500, Michael C . Wu wrote:
> | and a bunch of ARMs for low-level I/O tasks. Back to imagination. (Take
> | a look at 0.15um copper process FPGAs with embeded ARM at Altera, for
> | example, and you will see why no one, in the futur, will never ever need
> | a proprietary and undocumented 'server class' SCSI or network card).

Do you mean to say that, in the future, we will all blow our own FPGAs
at home? That to get the next processor upgrade, you download the
schematics and use Xilinx Foundation Series to build a chip? FPGAs are
not the answer... they can never be as fast as custom-fab chips. It may
be, in the future, we get circuits to run fast enough that we wouldn't
notice given today's speeds, but remember, if FPGAs get that fast,
custom-fab chips will be even faster. 

The future isn't FPGAs; it's GaAs BJT circuitry, designed and built by
the guys who have money to set up a fab and roll out millions of chips.
It will be a long, long time before anything changes about how we get
our chips; the only thing that will change is how they are made.

> Please make Altera/Xilinx make their FPGA programming software
> freely available.

Ugh. I think we need a better solution than the Xilinx software. It's
absolutely horrible. They should stick to electronics and leave the
software design to those who know what they're doing.

-- 
Andrew Hesford
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: BSDI and Marketing 101

[David O'Brien]

On Thu, Apr 26, 2001 at 07:03:47PM -0400, Dennis wrote:
> I saw BSDIs retail product of FreeBSD in a local bookstore the other day, 
> and it became sadly clear why LINUX, although highly inferior, is so much 
> more widely used. Right next to Freebsd (priced at $129.95) was Mandrake 
> LINUX for $29.95.

I should use your quote from this morning... but I won't.
You don't understand channel marketing.  And I'll just leave it at that.
 
-- 
-- David  ([EMAIL PROTECTED])

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: BSDI and Marketing 101

[George Reid]

On Thu, 26 Apr 2001, Dennis wrote:

> What they dont seem to realize is that people who know its worth more than 
> linux also know they dont have to pay $129. for free software with fancy 
> packaging and paid support.

This is relevant to -hackers in what way?

greid


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

BSDI and Marketing 101

[Dennis]

I saw BSDIs retail product of FreeBSD in a local bookstore the other day, 
and it became sadly clear why LINUX, although highly inferior, is so much 
more widely used. Right next to Freebsd (priced at $129.95) was Mandrake 
LINUX for $29.95.

What they dont seem to realize is that people who know its worth more than 
linux also know they dont have to pay $129. for free software with fancy 
packaging and paid support.

Of course they are building systems now..

db


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: NAT and IPFiltering

[Matt Dillon]

:Hi!
:
:I'm configuring a server able to do NAT and IP FILTERING (IPF).
:
:What are the required options that I should set to the kernel?
:
:I have this:
:...
:Jesús Arnáiz

I think all you need is:

options IPFIREWALL
options IPDIVERT

I usually also have (because it is useful):

options IPFILTER
options IPFIREWALL_FORWARD

--

For my firewall configuration

firewall_enable="YES"
firewall_type="/etc/ipfw.conf"
ip_portrange_first=4000
ip_portrange_last=5000

My /etc/ipfw.conf file contains:

# do not allow an outside entity to spoof our internal network
# IPs
add 00300 deny all from 10.0.0.0/8 in via fxp0

# NATD diversions
#
add 00400 divert 8668 ip from 10.0.0.0/8 to not 10.0.0.0/8
add 00400 divert 8668 ip from not 10.0.0.0/8 to 208.161.114.67

# allow data related to already-established TCP connections
# (near the top of the ruleset to packet switch efficiently)
#
add 01000 allow tcp from any to any established

# all all outgoing packets
#
add 01001 allow all from any to any out via fxp0
add 01001 allow all from any to any out via fxp1

# allow all strictly internal network traffic
add 01010 allow all from 10.0.0.0/8 to 10.0.0.0/8

# allow temporary ports and specific UDP services 
#
add 02000 allow udp from any to any 4000-65535,domain,ntalk,ntp
add 02500 allow udp from any to any frag

# allow temporary ports and specific TCP services.  Note that
# TCP packet fragments are not allowed.
#
add 03000 allow tcp from any to any http,https
add 03000 allow tcp from any to any 4000-65535,ssh,smtp,domain,ntalk
add 03000 allow tcp from any to any auth,pop3,ftp,ftp-data

# allow certain icmp types through for ping, routing errors, and
# tcp mtu path negotiation.
#
add 04000 allow icmp from any to any icmptypes 0,3,5,8,11,12,13,14

# log any remaining fragments that get through and deny the rest
#
add 05000 deny log ip from any to any frag
add 65000 deny ip from any to any

The rc.conf setup for my ethernet port is roughly:

# Exposed network
#
ifconfig_fxp0="inet 208.161.114.65 netmask 255.255.255.192"

# Exposed for NAT
#
ifconfig_fxp0_alias1="inet 208.161.114.67 netmask 255.255.255.192"

# Internal network
#
ifconfig_fxp1="inet 10.0.0.2 netmask 255.255.255.0"

And I run natd from /etc/rc.local using:

natd -s -u -a 208.161.114.67

*ALL* exposed services run from this machine are tied to the machine's
exposed IP address, in my case 208.161.114.65.  It requires some work
in named, sendmail.cf, and so forth to the services bound to the
correct IP address (you don't want to bind services to your NAT address).

The .67 address in my case is only used for NAT traffic.

The 4000-65535 junk is only really necessary for programs which use
UDP (like DNS) and expect replies via UDP.  I don't run any internal
TCP or UDP services on higher numbered ports but I like having
the flexibility.  With some care and hardwiring of UDP ports for the
services that need them, you can rip out the 4000-65535 stuff
entirely.  I use it because it's reasonably secure and a 'file and forget'
type of setup.

If you are using NAT, your internal network should be in the 10.x.x.x
space, and your external network should of course be in your
internet-visible space.

-Matt


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: gcc -O bug

[Dennis]

At 05:51 PM 04/26/2001, Peter Seebach wrote:
>In message <[EMAIL PROTECTED]>, Dennis writes:
> >Don't try to argue this ridiculous point on this list. You are badly
> >overmatched. You are so wrong that its not worthy of debate.
>
>Which is presumably why you offered no arguments.
>
>Actually, this is a fairly well-demonstrated result.  Anything that depends
>mostly on the operation of, say, regexp code, and doesn't spend most of its
>time doing flow control will be fairly comparable in C and perl.  Slower?
>Quite possibly.  *much* slower?  Not normally.  I think the standing estimate
>is that competently-written perl will take no more than three times as long as
>carefully-written C for most perl-ish tasks.  Matrix multiplies are an obvious
>exception.
>
>In practice, perl is likely to beat C substantially on most
>exrpession-matching code, because most C programmers write very inefficient
>matching code, and perl is good at it.
>
>(Go ahead, dismiss me as being unfairly biased against C.)


Done. Like I said, its not worthy of debate.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: x86-64 Hammer and IA64 Itainium

[Michael C . Wu]

On Wed, Apr 18, 2001 at 04:24:18PM +0200, Remy Nonnenmacher scribbled:
| On 17 Apr, Andrew Hesford wrote:
| > On Tue, Apr 17, 2001 at 12:49:04PM -0700, Jeremiah Gowdy wrote:
| For sure. Look at how it's pretty more easy to use an ARM or MIPS core
| to handle gluelessly the PCI, SDRAM, Flash etc... and just add specific
| components for the analogic interface side.

And what happens to the overhead of intercommunication between these
devices? :)  

...
Infiniband
...
PCI-X

Btw, we already use ARM/MIPS stuff in many PCI applications...
NIC chipsets are essentially specialized processors.
Think about about the new Intel NIC's with i960 built-in

| X86 (and -64) is going to be just die hard PC and workstations where
| deadly wrong past must be taken into account at the price of wasted
| power. Futur is more than probably Itanium and alike for servers CPUs

And what's so deadly wrong about all the new features of Itanium
and KA-64?

| and a bunch of ARMs for low-level I/O tasks. Back to imagination. (Take
| a look at 0.15um copper process FPGAs with embeded ARM at Altera, for
| example, and you will see why no one, in the futur, will never ever need
| a proprietary and undocumented 'server class' SCSI or network card).

Please make Altera/Xilinx make their FPGA programming software
freely available.

| It would be really interesting to have a server-class FreeBSD SMPng
| version and, in conjonction, an highly portable and small Pico-bsd like
| one to animate the embeded processors.

Please define "server-class" SMPng :)
You do realize that, in the embedded systems world, sometimes
we use SMP, right?  For example, multiple DSP ASIC's in the same
router.

-- 
+---+
| [EMAIL PROTECTED] | [EMAIL PROTECTED]   |
| http://iteration.net/~keichii | Yes, BSD is a conspiracy. |
+---+

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: x86-64 Hammer and IA64 Itainium

[Michael C . Wu]

On Tue, Apr 17, 2001 at 12:49:04PM -0700, Jeremiah Gowdy scribbled:
| I'd like to know if anyone's considering support for the new AMD
| Sledgehammer/Clawhammer/*hammer with x86-64 architecture.  I know the new
| hammer cpus will run as _very_ fast x86-32 processors, and FreeBSD would run
| happily under that, however, the x86-64 architecture offers major advantages
| over the 32bit architecture.  More than simply 64bit integers.  Like the
| Itainium, the Hammer has more registers.  Not as many as Itainium's 128
| 64bit general purpose registers, but a good 16 64bit registers rather than

| I'm studying the AMD architecture in an effort to port my x86 assembly
| skills to x86-64.  Learning IA64 assembly seems pointless since they want

With the branch prediction, cache tracing, and EPIC instructions,
you really want to use an ILP compiler.  Without a compiler that
can decide on good ways to output binaries that run with all the IA-64
innovations^Wreinvention-of-the-wheels.

I will reserve my opinions on whether Intel will succeed in 
implementing the EPIC stuff well. ;-)

IIRC, KA-64 does not even have an emulator yet.  Rest assured that
there will be a lot of people in and out of this project interested
in supporting a KA-64 port of FreeBSD.  


| everything done with an ILP capable compiler for maximum performance.
| Although my kernel programming skills are in their infancy, I am a good C
| and assembly language programmer.  Perhaps I could contribute to the FreeBSD
| x86-64 project, if and when there was one.

When Sledgehammer comes out, we will see what we can do. :)
-- 
+---+
| [EMAIL PROTECTED] | [EMAIL PROTECTED]   |
| http://iteration.net/~keichii | Yes, BSD is a conspiracy. |
+---+

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: More PCI->PCMCIA bridge stuff

[Warner Losh]

In message <[EMAIL PROTECTED]> Lists Account 
writes:
: Any suggestions?

Be patient.

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

NAT and IPFiltering

[Jesús Arnáiz]

Hi!

I'm configuring a server able to do NAT and IP FILTERING (IPF).

What are the required options that I should set to the kernel?

I have this:

--
options IPFILTER
options IPFILTER_LOG
options IPFIREWALL
options IPDIVERT
---

but I'm not sure if IPFIREWALLING should be (I'm not going to use ipfw).

On the other hand, I put this lines in /etc/rc.conf

--
firewall_type="open"
firewall_enable="NO"
--

But everytime I boot I have to do:

# ipfw -f flush
# ipfw add pass all from any to any

if I want to see other machines of my net.

As I say, I wan to use IPFILTER but not ipfw, so what I'm supposed to do?

Thanks in advance!


--
Jesús Arnáiz
0z0ne Inc I+D/IT Manager
http://www.0z0ne.com
mailto:[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: gcc -O bug

[Peter Seebach]

In message <[EMAIL PROTECTED]>, Dennis writes:
>Don't try to argue this ridiculous point on this list. You are badly 
>overmatched. You are so wrong that its not worthy of debate.

Which is presumably why you offered no arguments.

Actually, this is a fairly well-demonstrated result.  Anything that depends
mostly on the operation of, say, regexp code, and doesn't spend most of its
time doing flow control will be fairly comparable in C and perl.  Slower?
Quite possibly.  *much* slower?  Not normally.  I think the standing estimate
is that competently-written perl will take no more than three times as long as
carefully-written C for most perl-ish tasks.  Matrix multiplies are an obvious
exception.

In practice, perl is likely to beat C substantially on most
exrpession-matching code, because most C programmers write very inefficient
matching code, and perl is good at it.

(Go ahead, dismiss me as being unfairly biased against C.)

-s

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: VPN

[Rick Duvall]

This is cool!

Now, is there a way to use MS_DUN VPN support to dial into such a private
network made with FreeBSD so that people can telecommute?

On Thu, 26 Apr 2001, John J. Rushford Jr wrote:

> On Thu, 26 Apr 2001, you wrote:
> > I've just been going through this stuff for the past week.
> > None of the things come with adequate documentation
> > so you need to rely heavily on mailing list support.
> > Thankfully a few people have been giving me
> > some assistance but looks like at least few days more
> > messing around will be involved before its working..
> > 
> > There is a basic HOWTO on one application at
> > freebsddiary, but its quite dated now.  The only other apps
> > I've been able to find are vtund & poptop (both from ports)
> > Judging from feedback I received to a similar question, the
> > few FreeBSD users who use VPN prefer vtund.
> > 
> > I did look at poptop (which reportedly has some security
> > "features") in the hope it might be more straightforward to
> > configure. You need to hack the makefile (its flagged
> > "forbidden") to install, then theres a few compatibility issues
> > to contend with (due to the linux heritage)  I gave up with
> > it at that stage.
> > 
> > I think there may be other applications available if you can
> > compile support into the kernel  thats not practical for my
> > present situation as I can't take the server end offline in the
> > immediate future.
> > 
> 
> Greetings,
> 
> I just recently setup a vpn between two sites and have documented
> my work at http://www.alisa.org/~jjr/vpn
> 
> Have a look at it, I hope this proves useful to others
> -- 
> John J. Rushford
> [EMAIL PROTECTED]
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: VPN

[Doug Young]

> * Doug Young <[EMAIL PROTECTED]> [010426 04:59] wrote:
> > no vpn or sloop labels in my 4.1 system ... when were they introduced ??
>
> you can use cvsweb to read the most recent versions:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/share/examples/ppp

OK thanks Alfred. I wasn't aware of that as I haven't used CVS anything fo
rsome time (gave more "features" than leaving the system alone between
RELEASE versions, but at least being able to read the example files would
help
>
> btw, can you fix or get your mailer to quote messages properly?

probably not . its already got the "correct" settings but I dunno that
OE has ever observed "correct". To make matters worse its OE6b that got
installed automatically when I wasn't here (h) I think I've got pine to
work with this stupid Tel$tra / ADSL routing so maybe that will make a few
people happy :)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: pax(1) gzip functionality

[Kris Kennaway]

On Thu, Apr 26, 2001 at 04:42:44PM +0100, Brian Somers wrote:
> > On Thu, Apr 26, 2001 at 02:54:25AM -0700, Kris Kennaway wrote:
> > > Please review the following code from OpenBSD; it adds -z and -Z
> > > options to pax(1) to gzip(1) the archives created.
> > 
> > Sigh.  They could have generalized this just a little and supported Bzip2
> > at the same time.  Please let me know after you commit this so I can do
> > this.
> 
> Is this necessary ?  What's the problem with using a pipe ?  Isn't 
> this the same argument as the xargs one we've just gotten through ?
> 
> Maybe I'm missing something...

This is useful in tar compatibility mode, and therefore it may as well
be used for pax mode too.

Kris

 PGP signature

Re: pax(1) gzip functionality

[Kris Kennaway]

On Thu, Apr 26, 2001 at 07:23:30PM +0100, Brian Somers wrote:
> > On Thu, Apr 26, 2001 at 04:42:44PM +0100, Brian Somers wrote:
> > > > On Thu, Apr 26, 2001 at 02:54:25AM -0700, Kris Kennaway wrote:
> > > > > Please review the following code from OpenBSD; it adds -z and -Z
> > > > > options to pax(1) to gzip(1) the archives created.
> > > > 
> > > > Sigh.  They could have generalized this just a little and supported Bzip2
> > > > at the same time.  Please let me know after you commit this so I can do
> > > > this.
> > > 
> > > Is this necessary ?  What's the problem with using a pipe ?  Isn't 
> > > this the same argument as the xargs one we've just gotten through ?
> > 
> > What's wrong with:
> > tar cf - foo | gzip >foo.tar.gz
> > gzip -dc foo.tar.gz | tar xf -
> > 
> > Someone deemed them too inconvient for the number of times they are
> > invoked.  I'm not going to enter that discussion, but _if_ gzip support
> > is added, I feel bzip2 support should be added to be orthogonal with
> > today's uses.
> 
> Agreed.

Fair enough; would be a trivial thing to do.  Increased compatibility
with tar and cpio seems to have been one of the goals of OpenBSD's
work on pax(1); I'm intending to go through and pull over the other
bugfixes and extensions too.

Kris

 PGP signature

Re: VPN

[John J. Rushford Jr]

On Thu, 26 Apr 2001, you wrote:
> I've just been going through this stuff for the past week.
> None of the things come with adequate documentation
> so you need to rely heavily on mailing list support.
> Thankfully a few people have been giving me
> some assistance but looks like at least few days more
> messing around will be involved before its working..
> 
> There is a basic HOWTO on one application at
> freebsddiary, but its quite dated now.  The only other apps
> I've been able to find are vtund & poptop (both from ports)
> Judging from feedback I received to a similar question, the
> few FreeBSD users who use VPN prefer vtund.
> 
> I did look at poptop (which reportedly has some security
> "features") in the hope it might be more straightforward to
> configure. You need to hack the makefile (its flagged
> "forbidden") to install, then theres a few compatibility issues
> to contend with (due to the linux heritage)  I gave up with
> it at that stage.
> 
> I think there may be other applications available if you can
> compile support into the kernel  thats not practical for my
> present situation as I can't take the server end offline in the
> immediate future.
> 

Greetings,

I just recently setup a vpn between two sites and have documented
my work at http://www.alisa.org/~jjr/vpn

Have a look at it, I hope this proves useful to others
-- 
John J. Rushford
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: gcc -O bug

[Jason Andresen]

Dennis wrote:
> 
> At 09:11 AM 04/26/2001, you wrote:
> >On Thu, Apr 26, 2001 at 11:00:15PM +1000, Greg Black wrote:
> >Nope.  The real nonsense is what you say.  Perl core is written in a
> >highly optimized C using very polished algorithms.  As long as the Perl
> >script is written in such a way as to minimize the number of OPCODEs
> >executed and maximize the time spent inside the OPCODE executor engine,
> >it is not exactly trivial to beat it in C, unless you are willing to
> >spent a considerable time polishing your code (which is not worth it for
> >your typical log analyzer).
> 
> Don't try to argue this ridiculous point on this list. You are badly
> overmatched. You are so wrong that its not worthy of debate.

Youch!  I think most people on this list can see where this is going. 
Please take this thread to email before it becomes a full fledged
inferno.

Remember kids: Only YOU can prevent troll fires.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Is 3COM 3C996-T supported via Alteon Driver?

[Bill Paul]

> > Hello All:
> > 
> > I'm in the process of configuring a cluster and noticed that 3COM
> > had recently purchased Alteon and was making a 3C996-T 10/100/1000 BaseT
> > cards.  Can the Alteon Tigon drivers support this card?
> 
> After a bit of poking around, and discussion with 3Com's tech support,
> they have confirmed that this card is NOT Alteon based.  In fact,
> most of the current crop of 10/100/1000 BaseT cards are based on
> broadcom's recent chipset, (I'm not sure which chip, possibly
> the BMC5401 or the BMC5402).  I don't think that there are FreeBSD
> drivers for these cards (due in some part to reasons discussed below).
> 
> Other FreeBSD friendly vendors (I'm not sure if I'm allowed to give names
> here) have confirmed that they too are preparing cards with the same
> technology.  I've heard rumors that the chip supplies are currently limited,
> so that card availability might be limited until late May.

The 3c996 uses the Broadcom BCM5700, also known as the Tigon 3. Apparently,
Alteon 'outsourced' the development of the Tigon 3 to Broadcom, and
3Com has some right to it now that they own Alteon's NIC division. The
BCM5400 and 5401 are PHY (transceiver) chips, not MACs. I have been
trying to get Broadcom to give me a copy of the BCM5700 programming
manual, but have been left somewhat out if left field. My last contact
with them was a few weeks ago, when they told me they needed approval
from yet another management droid of some kind, who hasn't responded to
either my phone messages or my e-mail.

The Tigon 3 doesn't look *too* different from the Tigon 2, based on
what I've seen in the Linux driver. (Yes, they wrote a Linux driver,
but not a BSD driver.) One major difference is that the firmware seems
to now reside in the chip itself, which saves you from having to load
it from the driver.

In the meantime, I'm currently working on drivers for the National
Semiconductor DP83820 and Level 1 LXT1001 gigabig MAC chips. The Level 1
part can be found on the D-Link DGE-500SX and a couple of SMC cards.
The NatSemi chip is being used on cards by D-Link (DGE-500T), Asante
and Addtron. Getting the DP83820 manual was easy (it's on National's
web site). Getting the LXT1001 manual took some arm twisting, but Intel
(who now owns Level 1) finally agreed to let D-Link release it to me
without NDA.

Unfortunately, the BSDi/Wind River deal still hasn't quite closed yet,
which is preventing me from ordering hardware. I'm doing as much of the
gruntwork as I can, but I can't do actual testing until I can get some
sample NICs. Everyone will know once I'm done.

-Bill

=
-Bill Paul(925) 691-2800 | Systems Programmer, Master of Unix-Fu
  [EMAIL PROTECTED] | BSDi Open Source Solutions
=
"I like zees guys. Zey are fonny guys. Just keel one of zem." -- The 3 Amigos
=

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: pax(1) gzip functionality

[Brian Somers]

> On Thu, Apr 26, 2001 at 04:42:44PM +0100, Brian Somers wrote:
> > > On Thu, Apr 26, 2001 at 02:54:25AM -0700, Kris Kennaway wrote:
> > > > Please review the following code from OpenBSD; it adds -z and -Z
> > > > options to pax(1) to gzip(1) the archives created.
> > > 
> > > Sigh.  They could have generalized this just a little and supported Bzip2
> > > at the same time.  Please let me know after you commit this so I can do
> > > this.
> > 
> > Is this necessary ?  What's the problem with using a pipe ?  Isn't 
> > this the same argument as the xargs one we've just gotten through ?
> 
> What's wrong with:
> tar cf - foo | gzip >foo.tar.gz
> gzip -dc foo.tar.gz | tar xf -
> 
> Someone deemed them too inconvient for the number of times they are
> invoked.  I'm not going to enter that discussion, but _if_ gzip support
> is added, I feel bzip2 support should be added to be orthogonal with
> today's uses.

Agreed.

> -- 
> -- David  ([EMAIL PROTECTED])

-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: gcc -O bug

[Dennis]

At 09:11 AM 04/26/2001, you wrote:
>On Thu, Apr 26, 2001 at 11:00:15PM +1000, Greg Black wrote:
> > Anton Berezin wrote:
> >
> > | Could you provide the Perl script as well?
> >
> > That would be pointless.  The issue is with the C ...
>
>I know that.
>
> > | I am quite sure it can be
> > | made to run faster.  In fact, it is almost always possible in Perl to
> > | closely match the perfomance of a C program for this kind of
> > | application.
> >
> > Nonsense (unless the C program is written by an idiot).
>
>Nope.  The real nonsense is what you say.  Perl core is written in a
>highly optimized C using very polished algorithms.  As long as the Perl
>script is written in such a way as to minimize the number of OPCODEs
>executed and maximize the time spent inside the OPCODE executor engine,
>it is not exactly trivial to beat it in C, unless you are willing to
>spent a considerable time polishing your code (which is not worth it for
>your typical log analyzer).


Don't try to argue this ridiculous point on this list. You are badly 
overmatched. You are so wrong that its not worthy of debate.

Dennis



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

LCD driver port (Linux -> FreeBSD) needed for car-mp3 player

[Shaun Dwyer]

Hi everyone..

I have a PC in the boot of my car running Linux (yuck) to play mp3s.
I would love to use FreeBSD instead of Linux for many reasons.
The only thing stopping me using FreeBSD is the lack of a driver in the
style
implemented for Linux (provides a /dev/lcd that u just throw data at).

The reason I need this driver to be ported is so I can use Cajun
(cajun.sourceforge.net)
with little or no modifications on FreeBSD.

If I knew C, i would port the driver myself, and If i knew perl, I would
mod
cajun to use  /usr/share/examples/ppi/ppilcd.c's stuff.

The linux driver is available at:
http://www4.infi.net/~cpinkham/cajun/code/lcd-0.2c.tar.gz

If you want to see some photos and a bit of a description of my mp3
player, goto
http://members.nbci.com/mp3zeus/

BTW, please email me directly, as I am not subscribed to the mailing
list.

Thanks in advance,

Shaun


-- 
--
Shaun Dwyer
[EMAIL PROTECTED]
--

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: pax(1) gzip functionality

[David O'Brien]

On Thu, Apr 26, 2001 at 04:42:44PM +0100, Brian Somers wrote:
> > On Thu, Apr 26, 2001 at 02:54:25AM -0700, Kris Kennaway wrote:
> > > Please review the following code from OpenBSD; it adds -z and -Z
> > > options to pax(1) to gzip(1) the archives created.
> > 
> > Sigh.  They could have generalized this just a little and supported Bzip2
> > at the same time.  Please let me know after you commit this so I can do
> > this.
> 
> Is this necessary ?  What's the problem with using a pipe ?  Isn't 
> this the same argument as the xargs one we've just gotten through ?

What's wrong with:
tar cf - foo | gzip >foo.tar.gz
gzip -dc foo.tar.gz | tar xf -

Someone deemed them too inconvient for the number of times they are
invoked.  I'm not going to enter that discussion, but _if_ gzip support
is added, I feel bzip2 support should be added to be orthogonal with
today's uses.

-- 
-- David  ([EMAIL PROTECTED])

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Unixgamers.com

[Jeremiah Gowdy]

Our site, unixgamers.com will hopefully be launching soon.  As I've
mentioned before, we will be giving full instructions on how to setup Linux
compatible games under BSD and any other Unix-like operating system.  We
need contributors with experience on how to setup FreeBSD to run games via
Linux compatibility mode with OpenGL or DirectX via Wine emulation.  We need
URLs, Howtos, FAQs, etc.  We need your help to promote the gaming scene on
FreeBSD.  With Loki Games recent commitment to FreeBSD compatibility, it
makes us believe our site really will have a place in the BSD/Linux Gaming
community.  If you have any good links, please mail them to me.  If you are
interested in writing an article for our site, either about playing games or
serving games under FreeBSD (or even Linux or any other Unix-like OS),
please do so and contact me.  Unixgamers.com is going to be a community site
and therefore we need community support to make this happen.  Thanks.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: VPN

[Alfred Perlstein]

> > > > Actually ppp shouldn't be that hard to set up as a vpn server.
> > >
> > > exactly where to find  config information suitable for a non-expert ??
> >
> > /usr/share/examples/ppp - have a look at the vpn* and sloop* labels.

* Doug Young <[EMAIL PROTECTED]> [010426 04:59] wrote:
> no vpn or sloop labels in my 4.1 system ... when were they introduced ??

you can use cvsweb to read the most recent versions:

http://www.freebsd.org/cgi/cvsweb.cgi/src/share/examples/ppp

btw, can you fix or get your mailer to quote messages properly?

-- 
-Alfred Perlstein - [[EMAIL PROTECTED]]
http://www.egr.unlv.edu/~slumos/on-netbsd.html

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: pax(1) gzip functionality

[Brian Somers]

> On Thu, Apr 26, 2001 at 02:54:25AM -0700, Kris Kennaway wrote:
> > Please review the following code from OpenBSD; it adds -z and -Z
> > options to pax(1) to gzip(1) the archives created.
> 
> Sigh.  They could have generalized this just a little and supported Bzip2
> at the same time.  Please let me know after you commit this so I can do
> this.

Is this necessary ?  What's the problem with using a pipe ?  Isn't 
this the same argument as the xargs one we've just gotten through ?

Maybe I'm missing something...

> -- 
> -- David  ([EMAIL PROTECTED])

-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: pax(1) gzip functionality

[David O'Brien]

On Thu, Apr 26, 2001 at 02:54:25AM -0700, Kris Kennaway wrote:
> Please review the following code from OpenBSD; it adds -z and -Z
> options to pax(1) to gzip(1) the archives created.

Sigh.  They could have generalized this just a little and supported Bzip2
at the same time.  Please let me know after you commit this so I can do
this.
 
-- 
-- David  ([EMAIL PROTECTED])

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: gcc -O bug

[David O'Brien]

On Thu, Apr 26, 2001 at 09:44:36AM -0400, Jason Andresen wrote:
> Er, isn't this the kind of problem the GCC folks are more likly to be
> able to fix?

In general yes.  But it doesn't hurt to double check here to make sure
you your ducks in row before going to the GCC lists.  I see later in this
thread DES found it was a coding problem, not GCC optimizer problem.
 
> At least in GCC 2.9.5 (not the latest mind you) this problem still
  ^
  2.95[.3]

-- 
-- David  ([EMAIL PROTECTED])

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: gcc -O bug

[Dag-Erling Smorgrav]

Jason Andresen <[EMAIL PROTECTED]> writes:
> Dag-Erling Smorgrav wrote:
> > I ran into this bug while analyzing a customer's logs to determine the
> > best time of day for an upgrade.  The original script was in Perl, but
> > I rewrote it in C because it was too slow.  The C version produces
> > incorrect results when compiled with -O.  Note that the log starts at
> > 16:27.
> Er, isn't this the kind of problem the GCC folks are more likly to be
> able to fix?

Sure, but I thought people on this list (especially David O'Brien)
might have some insights.

Anyway, I found the bug - it's not a compiler bug, it's simply a
matter of passing a partially uninitialized struct tm to mktime().

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: More PCI->PCMCIA bridge stuff

[Peter Pentchev]

On Thu, Apr 26, 2001 at 02:02:40PM +0200, Lists Account wrote:
> Hi All
> 
> Ok, the newcard stuff under version 5 picks up my bridge fine, and it
> finds my wi0 (orinoco gold card) perfectly, this is all great and I was
> rather ecstatic as I watched it boot and tell me all this...
> 
> However the problem comes in the fact that it tries to probe pccard1 after
> finishing with pccard0, and the moment it does this (there is only one
> bridge, and only space for one card), it hangs the machine solid, not even
> a numlock, says something about printing cis tuplets and *boom* nothing
> left.

Yes, I had the same problem with my PCMCIA->PCI bridge.  I solved it with
the following patch, which adds a new option to pccardd: -S maxslot.
Then, add -S 1 to pccardd_flags in your /etc/rc.conf, and you're all set.

The patch is against -current; I can provide one against -stable if
somebody is interested.

G'luck,
Peter

-- 
What would this sentence be like if pi were 3?

Index: src/usr.sbin/pccard/pccardd/cardd.c
===
RCS file: /home/ncvs/src/usr.sbin/pccard/pccardd/cardd.c,v
retrieving revision 1.65
diff -u -r1.65 cardd.c
--- src/usr.sbin/pccard/pccardd/cardd.c 2000/12/24 15:30:36 1.65
+++ src/usr.sbin/pccard/pccardd/cardd.c 2001/04/26 13:47:46
@@ -51,6 +51,7 @@
 static void read_ether_attr2(struct slot *sp);
 
 struct slot *slots;
+intslot_max = MAXSLOT;
 
 /*
  * Dump configuration file data.
@@ -112,7 +113,7 @@
struct slot *sp;
 
slots = NULL;
-   for (i = 0; i < MAXSLOT; i++) {
+   for (i = 0; i < slot_max; i++) {
sprintf(name, CARD_DEVICE, i);
fd = open(name, O_RDWR);
if (fd < 0)
Index: src/usr.sbin/pccard/pccardd/cardd.h
===
RCS file: /home/ncvs/src/usr.sbin/pccard/pccardd/cardd.h,v
retrieving revision 1.27
diff -u -r1.27 cardd.h
--- src/usr.sbin/pccard/pccardd/cardd.h 2000/10/20 13:08:18 1.27
+++ src/usr.sbin/pccard/pccardd/cardd.h 2001/04/26 13:47:46
@@ -141,6 +141,7 @@
 
 EXTERN struct slot *slots, *current_slot;
 EXTERN int slen;
+EXTERN int slot_max;
 
 EXTERN struct allocblk *pool_ioblks;/* I/O blocks in the pool */
 EXTERN struct allocblk *pool_mem;   /* Memory in the pool */
Index: src/usr.sbin/pccard/pccardd/pccardd.8
===
RCS file: /home/ncvs/src/usr.sbin/pccard/pccardd/pccardd.8,v
retrieving revision 1.22
diff -u -r1.22 pccardd.8
--- src/usr.sbin/pccard/pccardd/pccardd.8   2000/12/27 15:30:15 1.22
+++ src/usr.sbin/pccard/pccardd/pccardd.8   2001/04/26 13:47:47
@@ -39,6 +39,7 @@
 .Op Fl i Ar IRQ
 .Op Fl I 
 .Op Fl f Ar configfile
+.Op Fl S Ar maxslot
 .Sh DESCRIPTION
 .Nm Pccardd
 is normally started at boot time, and manages the insertion
@@ -153,6 +154,12 @@
 .Nm ,
 and the kernel drivers and devices that are used to
 interface to the card.
+.It Fl S Ar maxslot
+Specifies the maximum number of slots to probe (default 16).
+This may be useful with e.g. some PCMCIA->PCI bridges, when probing
+the second slot causes
+.Nm
+to enter an infinite loop.
 .El
 .Sh FILES
 .Bl -tag -width /etc/defaults/pccard.conf -compact
Index: src/usr.sbin/pccard/pccardd/pccardd.c
===
RCS file: /home/ncvs/src/usr.sbin/pccard/pccardd/pccardd.c,v
retrieving revision 1.12
diff -u -r1.12 pccardd.c
--- src/usr.sbin/pccard/pccardd/pccardd.c   2000/10/20 13:08:18 1.12
+++ src/usr.sbin/pccard/pccardd/pccardd.c   2001/04/26 13:47:47
@@ -161,7 +161,7 @@
int irq_specified = 0;
int i;
struct sockaddr_un sun;
-#defineCOM_OPTS":Idvf:s:i:z"
+#defineCOM_OPTS":Idvf:S:s:i:z"
 
bzero(irq_arg, sizeof(irq_arg));
use_kern_irq = 1;
@@ -192,6 +192,13 @@
}
irq_arg[i] = 1;
irq_specified = 1;
+   break;
+   case 'S':
+   if (sscanf(optarg, "%d", &i) != 1) {
+   fprintf(stderr, "%s: -S number\n", argv[0]);
+   exit(1);
+   }
+   slot_max = i;
break;
case 's':
sock = optarg;

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: vmware on freebsd for fast booting for devel.

[Sven Huster]

At 03:38 PM 4/25/01, Andrew Gallatin wrote:
>*This message was transferred with a trial version of CommuniGate(tm) Pro*
>
>Sven Huster writes:
>
>  > OT FYI:
>  >
>  > Check the ISP1100 from Intel if you like
>  > support for PIII up to 850
>  > 2GB RAM
>  > 2 x Intel Network onboard (includes pxe boot, possible on both)
>  > full serial console (even for access to bios setup)
>
>Hmm.. We have some Dell PowerEdge 1550s that do this (nice machines,
>but horribleb bootstones).  But I've got a basic problem with console
>redirection on PCs that we don't see on Alphas or Suns.
>
>The problem is that I cannot figure out how in the hell to hit "F2" in
>my environment.  My environment is essentially telnet'ing into a
>console server from an xterm.  Hitting "Ctrl-A" for the scsi bios
>works just fine & dandy..
>
>Anybody know how to make ansi function keys work from an xterm?

As far as i remember:
Worked for me with the ISP1100 with xterm.
Also TERM set to xterm.


Sven Huster
Senior IT Systems Administrator
*BSD, Linux, Solaris


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: gcc -O bug

[Jason Andresen]

Dag-Erling Smorgrav wrote:
> 
> I ran into this bug while analyzing a customer's logs to determine the
> best time of day for an upgrade.  The original script was in Perl, but
> I rewrote it in C because it was too slow.  The C version produces
> incorrect results when compiled with -O.  Note that the log starts at
> 16:27.
> 
> The warning about "time" being possibly uninitialized is safe to
> ignore; this can only happen if the log is empty.
> 
> The C source and a truncated log that reproduces the bug are attached
> at the end of this message.

Er, isn't this the kind of problem the GCC folks are more likly to be
able to fix?

At least in GCC 2.9.5 (not the latest mind you) this problem still
exists.  I'm sure the GNU project would love to hear about this bug,
especially since it happens at such a low -O level (people expect bugs
with -O2 or -O3, but -O bugs can be surprising to some).


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: gcc -O bug

[Anton Berezin]

On Thu, Apr 26, 2001 at 11:00:15PM +1000, Greg Black wrote:
> Anton Berezin wrote:
> 
> | Could you provide the Perl script as well? 
> 
> That would be pointless.  The issue is with the C ...

I know that.

> | I am quite sure it can be
> | made to run faster.  In fact, it is almost always possible in Perl to
> | closely match the perfomance of a C program for this kind of
> | application.
> 
> Nonsense (unless the C program is written by an idiot).

Nope.  The real nonsense is what you say.  Perl core is written in a
highly optimized C using very polished algorithms.  As long as the Perl
script is written in such a way as to minimize the number of OPCODEs
executed and maximize the time spent inside the OPCODE executor engine,
it is not exactly trivial to beat it in C, unless you are willing to
spent a considerable time polishing your code (which is not worth it for
your typical log analyzer).

Cheers,
+Anton.
-- 
May the tuna salad be with you.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: gcc -O bug

[Greg Black]

Anton Berezin wrote:

| Could you provide the Perl script as well? 

That would be pointless.  The issue is with the C ...

| I am quite sure it can be
| made to run faster.  In fact, it is almost always possible in Perl to
| closely match the perfomance of a C program for this kind of
| application.

Nonsense (unless the C program is written by an idiot).

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: gcc -O bug

[Dag-Erling Smorgrav]

Anton Berezin <[EMAIL PROTECTED]> writes:
> Could you provide the Perl script as well?  I am quite sure it can be
> made to run faster.  In fact, it is almost always possible in Perl to
> closely match the perfomance of a C program for this kind of
> application.

I doubt it - and in any case, this is irrelevant.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: gcc -O bug

[Anton Berezin]

On Thu, Apr 26, 2001 at 02:23:49PM +0200, Dag-Erling Smorgrav wrote:
> I ran into this bug while analyzing a customer's logs to determine the
> best time of day for an upgrade.  The original script was in Perl, but
> I rewrote it in C because it was too slow.

Could you provide the Perl script as well?  I am quite sure it can be
made to run faster.  In fact, it is almost always possible in Perl to
closely match the perfomance of a C program for this kind of
application.

Cheers,
\Anton.
-- 
May the tuna salad be with you.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

gcc -O bug

[Dag-Erling Smorgrav]

I ran into this bug while analyzing a customer's logs to determine the
best time of day for an upgrade.  The original script was in Perl, but
I rewrote it in C because it was too slow.  The C version produces
incorrect results when compiled with -O.  Note that the log starts at
16:27.

The warning about "time" being possibly uninitialized is safe to
ignore; this can only happen if the log is empty.

The C source and a truncated log that reproduces the bug are attached
at the end of this message.

des@aes ~/ts/projects/MGW/misc% uname -a
FreeBSD aes.thinksec.com 5.0-CURRENT FreeBSD 5.0-CURRENT #23: Fri Apr 13 00:35:50 CEST 
2001 [EMAIL PROTECTED]:/usr/src/sys/compile/AES  i386
des@aes ~/ts/projects/MGW/misc% gcc --version
2.95.3
des@aes ~/ts/projects/MGW/misc% cc -Wall -pedantic logalyze.c
logalyze.c: In function `main':
logalyze.c:28: warning: unused variable `j'
des@aes ~/ts/projects/MGW/misc% head -1 ../ldalog | ./a.out
9412 messages accepted, 588 rejected
log spans 6.98 hours
average throughput: 1347.73 msg/h

Breakdown per hour:

00 | 0
01 | 0
02 | 0
03 | 0
04 | 0
05 | 0
06 | 0
07 | 0
08 | 0
09 | 0
10 | 0
11 | 0
12 | 0
13 | 0
14 | 0
15 | 0
16 | 1009
17 |### 2329
18 |## 1274
19 |## 712
20 | 816
21 |## 2446
22 |## 500
23 |## 326
des@aes ~/ts/projects/MGW/misc% cc -O -Wall -pedantic logalyze.c
logalyze.c: In function `main':
logalyze.c:28: warning: unused variable `j'
logalyze.c:27: warning: `time' might be used uninitialized in this function
des@aes ~/ts/projects/MGW/misc% head -1 ../ldalog | ./a.out
9412 messages accepted, 588 rejected
log spans 7.98 hours
average throughput: 1178.92 msg/h

Breakdown per hour:

00 | 0
01 | 0
02 | 0
03 | 0
04 | 0
05 | 0
06 | 0
07 | 0
08 | 0
09 | 0
10 | 0
11 | 0
12 | 0
13 | 0
14 | 0
15 | 1
16 | 1008
17 |### 2329
18 |## 1274
19 |## 712
20 | 816
21 |## 2446
22 |## 500
23 |## 326
des@aes ~/ts/projects/MGW/misc% head -1 ../ldalog | ./logalyze.pl
9412 messages accepted, 588 rejected
log spans 6.98 hours
average throughput: 1347.73 msg/h

Breakdown per hour:

00 | 0
01 | 0
02 | 0
03 | 0
04 | 0
05 | 0
06 | 0
07 | 0
08 | 0
09 | 0
10 | 0
11 | 0
12 | 0
13 | 0
14 | 0
15 | 0
16 | 1009
17 |### 2329
18 |## 1274
19 |## 712
20 | 816
21 |## 2446
22 |## 500
23 |## 326

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]



/*
 * Copyright (c) 2001 ThinkSec AS.  All rights reserved.
 *
 * $ThinkSec$
 */

#include 
#include 
#include 
#include 

static int   accepted, rejected;
static time_tfirst, last;
static doubleduration;
static int   hour[24];
static int   week[7][25];

static const char hashes[] =
"##!";

int
main(void)
{
char *line;
size_t len;
struct tm tm;
time_t time;
int i, j, max;
double scale;

setbuf(stdout, NULL);
while ((line = fgetln(stdin, &len)) != NULL) {
if (len < 20 || line[4] != '-' || line[7] != '-' || line[10] != '-'
|| line[13] != ':' || line[16] != ':' || line[19] != ':') {
warn("malformed line: %.*s\n", (int)len, line);
continue;
}
if (line[20] == '-') {
++rejected;
continue;
}
tm.tm_year = atoi(line) - 1900;
tm.tm_mon = atoi(line + 5) - 1;
tm.tm_mday = atoi(line + 8);
tm.tm_hour = atoi(line + 11);
tm.tm_min = atoi(line + 14);
tm.tm_sec = atoi(line + 17);
time = mktime(&tm);
if (!first)
first = time;
++hour[tm.tm_hour];
++week[tm.tm_wday][tm.tm_hour];
++week[tm.tm_wday][24];
if (++accepted % 1000 == 0)
printf("\r%d", accepted);
}
last = time;
printf("\r%d messages accepted, %d rejected\n", accepted, rejected);
duration = (last - first + 1) / 3600.0;
printf("log spans %.2f hours\n", duration);
printf("average throughput: %.2f msg/h\n", accepted / duration);

printf("\nBreakdown per hour:\n\n");
for (i = max = 0; i < 24; ++i)
if (hour[i] > max)
max = hour[i];
scale = max / 50.0;
for (i = 0; i < 24; ++i) {
printf("%02d |%.*s %d\n", i, (int)(hour[i] / scale), hashes, hour[i]);
}

exit(0);
}


2001-01-05-16:27:23:N
2001-01-05-16:27:24:N
2001-01-05-16:27:25:N
2001-01-05-16:27:25:N
2001-01-05-16:27:25:N
2001-01-05-16:27:26:N
2001-01-05-16:27:26:N
2001-01-05-16:27:26:N
2001-01-05-16:27:27:N
2001-01-05-16:27:28:N
2001-01-05-16:27:28:N
2001-01-05-16:27:29

Re: VPN

[Doug Young]

> There is also vpnd in ports now, which I maintain. It has worked quite
> stable for me, is easy to set up, has rather high performance, uses
Blowfish, etc.

I just found it in security (was looking in "net" previously where all the
other VLAN / VPN applications seem to be)

Is there anything in the way of documentation (always a major problem with
open source software) ?? I'm trying to find config info at the homepage but
nothing obvious



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: VPN

[Brian Somers]

> no vpn or sloop labels in my 4.1 system ... when were they introduced ??

They were MFC'd on December 18 '00, 4.1 was released the August 
before.
-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

More PCI->PCMCIA bridge stuff

[Lists Account]

Hi All

Ok, the newcard stuff under version 5 picks up my bridge fine, and it
finds my wi0 (orinoco gold card) perfectly, this is all great and I was
rather ecstatic as I watched it boot and tell me all this...

However the problem comes in the fact that it tries to probe pccard1 after
finishing with pccard0, and the moment it does this (there is only one
bridge, and only space for one card), it hangs the machine solid, not even
a numlock, says something about printing cis tuplets and *boom* nothing
left.

Any suggestions?

Andrew


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: VPN

[Doug Young]

no vpn or sloop labels in my 4.1 system ... when were they introduced ??


- Original Message -
From: "Brian Somers" <[EMAIL PROTECTED]>
To: "Doug Young" <[EMAIL PROTECTED]>
Cc: "Alfred Perlstein" <[EMAIL PROTECTED]>; "Jesús Arnáiz"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, April 26, 2001 9:54 PM
Subject: Re: VPN


> >
> > > Actually ppp shouldn't be that hard to set up as a vpn server.
> >
> > exactly where to find  config information suitable for a non-expert ??
>
> /usr/share/examples/ppp - have a look at the vpn* and sloop* labels.
>
> --
> Brian <[EMAIL PROTECTED]>
>      
> Don't _EVER_ lose your sense of humour !
>
>
>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: VPN

[Anders Nordby]

On Thu, Apr 26, 2001 at 06:00:36PM +1000, Doug Young wrote:
> There is a basic HOWTO on one application at
> freebsddiary, but its quite dated now.  The only other apps
> I've been able to find are vtund & poptop (both from ports)
> Judging from feedback I received to a similar question, the
> few FreeBSD users who use VPN prefer vtund.

There is also vpnd in ports now, which I maintain. It has worked quite
stable for me, is easy to set up, has rather high performance, uses Blowfish,
etc.

Cheers,

-- 
Anders.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: VPN

[Brian Somers]

>  
> > Actually ppp shouldn't be that hard to set up as a vpn server.
> 
> exactly where to find  config information suitable for a non-expert ??

/usr/share/examples/ppp - have a look at the vpn* and sloop* labels.

-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Getting a list of users logged in at a certain time (patch)

[Michael Lyngbøl]

On 25.04.2001 23:34:36 +, Dima Dorfman wrote:
> OpenBSD's last(1) has a nice snapshot feature which allows one to get
> a list of users logged in at a certain date and time.  This is very
> useful, e.g., for security auditing: you see a message in a log, and
> want to know who could've caused it.  Assuming that it was something
> that must've been done locally, using this feature you can narrow the
> list down to a the users that were logged in.  It isn't perfect, but
> it's a start.
> 
> Attached is a patch which implements this feature in FreeBSD's
> last(1).  I copied most of the "meat" from OpenBSD, but our last(1)
> still looks nothing like theirs, and the delta is larger than it
> should've been: surprisingly, our last(1) is quite a bit more mature
> (e.g., internationalization).
> 
> Comments?  Suggestions?

It's a feature I'd appriciate.

I'm no C-meistro but it looks fine to me.

Best regards
/Michael


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

pax(1) gzip functionality

[Kris Kennaway]

Hi all,

Please review the following code from OpenBSD; it adds -z and -Z
options to pax(1) to gzip(1) the archives created.

Kris

Index: ar_io.c
===
RCS file: /home/ncvs/src/bin/pax/ar_io.c,v
retrieving revision 1.14
diff -u -r1.14 ar_io.c
--- ar_io.c 2001/04/26 09:22:27 1.14
+++ ar_io.c 2001/04/26 09:52:32
@@ -44,16 +44,18 @@
 #endif /* not lint */
 
 #include 
-#include 
 #include 
 #include 
-#include 
-#include 
+#include 
+#include 
+#include 
+#include 
 #include 
-#include 
+#include 
 #include 
-#include 
+#include 
 #include 
+#include 
 #include "pax.h"
 #include "extern.h"
 
@@ -79,9 +81,12 @@
 static int wr_trail = 1;   /* trailer was rewritten in append */
 static int can_unlnk = 0;  /* do we unlink null archives?  */
 char *arcname; /* printable name of archive */
+const char *gzip_program;  /* name of gzip program */
+static pid_t zpid = -1;/* pid of child process */
 
 static int get_phys __P((void));
 extern sigset_t s_mask;
+static void ar_start_gzip __P((int, const char *, int));
 
 /*
  * ar_open()
@@ -121,6 +126,8 @@
arcname = STDN;
} else if ((arfd = open(name, EXT_MODE, DMOD)) < 0)
syswarn(0, errno, "Failed open to read on %s", name);
+   if (arfd != -1 && gzip_program != NULL)
+   ar_start_gzip(arfd, gzip_program, 0);
break;
case ARCHIVE:
if (name == NULL) {
@@ -130,6 +137,8 @@
syswarn(0, errno, "Failed open to write on %s", name);
else
can_unlnk = 1;
+   if (arfd != -1 && gzip_program != NULL)
+   ar_start_gzip(arfd, gzip_program, 1);
break;
case APPND:
if (name == NULL) {
@@ -335,6 +344,16 @@
can_unlnk = 0;
}
 
+   /*
+* for a quick extract/list, pax frequently exits before the child
+* process is done
+*/
+   if ((act == LIST || act == EXTRACT) && nflag && zpid > 0) {
+   int status;
+   kill(zpid, SIGINT);
+   waitpid(zpid, &status, 0);
+   }
+
(void)close(arfd);
 
if (vflag && (artyp == ISTAPE)) {
@@ -1286,4 +1305,47 @@
continue;
}
return(0);
+}
+
+/*
+ * ar_start_gzip()
+ * starts the gzip compression/decompression process as a child, using magic
+ * to keep the fd the same in the calling function (parent).
+ */
+void
+ar_start_gzip(int fd, const char *gzip_program, int wr)
+{
+   int fds[2];
+   char *gzip_flags;
+
+   if (pipe(fds) < 0)
+   err(1, "could not pipe");
+   zpid = fork();
+   if (zpid < 0)
+   err(1, "could not fork");
+
+   /* parent */
+   if (zpid) {
+   if (wr)
+   dup2(fds[1], fd);
+   else
+   dup2(fds[0], fd);
+   close(fds[0]);
+   close(fds[1]);
+   } else {
+   if (wr) {
+   dup2(fds[0], STDIN_FILENO);
+   dup2(fd, STDOUT_FILENO);
+   gzip_flags = "-c";
+   } else {
+   dup2(fds[1], STDOUT_FILENO);
+   dup2(fd, STDIN_FILENO);
+   gzip_flags = "-dc";
+   }
+   close(fds[0]);
+   close(fds[1]);
+   if (execlp(gzip_program, gzip_program, gzip_flags, NULL) < 0)
+   err(1, "could not exec");
+   /* NOTREACHED */
+   }
 }
Index: extern.h
===
RCS file: /home/ncvs/src/bin/pax/extern.h,v
retrieving revision 1.10
diff -u -r1.10 extern.h
--- extern.h2001/04/26 08:37:00 1.10
+++ extern.h2001/04/26 09:52:32
@@ -48,6 +48,7 @@
  * ar_io.c
  */
 extern char *arcname;
+extern const char *gzip_program;
 int ar_open __P((char *));
 void ar_close __P((void));
 void ar_drain __P((void));
Index: options.c
===
RCS file: /home/ncvs/src/bin/pax/options.c,v
retrieving revision 1.17
diff -u -r1.17 options.c
--- options.c   2001/04/26 09:22:28 1.17
+++ options.c   2001/04/26 09:52:32
@@ -78,6 +78,9 @@
 static void cpio_usage __P((void));
 #endif
 
+#define GZIP_CMD   "gzip"  /* command to run as gzip */
+#define COMPRESS_CMD   "compress"  /* command to run as compress */
+
 /*
  * Format specific routine table - MUST BE IN SORTED ORDER BY NAME
  * (see pax.h for description of each function)
@@ -192,7 +195,7 @@
/*
 * process option flags
 */
-   while ((c=getopt(argc,argv,"ab:cdf:iklno:p:rs:tuvwx:B:DE:G:HLPT:U:XYZ"))
+   while ((c=getopt(argc,argv,"ab:cdf:ikl

Re: Question about Posix Threads

['[EMAIL PROTECTED]']

* PETIT Sebastien <[EMAIL PROTECTED]> [010426 01:43] wrote:
> Hi,
> 
> Is it the same limitation problem about the performance under mysql with a
> lot of IO ?

Yes, basically most of the performance problems you're seeing on FreeBSD
should be because of the threads libraries, nothing else.

You might want to see if you can link mysql against the linuxthreads
port to gain more peformance wrt IO.

-Alfred

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

RE: VPN

[Koster, K.J.]

Dear Thomas,

> 
> > Any advantages or disadvantages of using one or other?. 
> > What is better (is the first
> > time I set VPN on a UNIX system).?
> 
> If your requirements are not too complicated, you can use pipsecd
> (from ports/net), which is an implementation of ipsec that requires
> only very limited setup. Besides, pipsecd has been successfully
> tested for interoperation with other ipsec products.
>
Does "other ipsec products" include stuff from Microsoft?

Kees Jan


 You are only young once,
   but you can stay immature all your life.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: VPN

[Thomas Quinot]

Le 2001-04-26, Jesús Arnáiz écrivait :

> I want to set VPN on my system, I see there is many programs created to do it.
> 
> Any advantages or disadvantages of using one or other?. What is better (is the first
> time I set VPN on a UNIX system).?

If your requirements are not too complicated, you can use pipsecd
(from ports/net), which is an implementation of ipsec that requires
only very limited setup. Besides, pipsecd has been successfully
tested for interoperation with other ipsec products.

Thomas.

-- 
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

RE: Question about Posix Threads

[PETIT Sebastien]

Hi,

Is it the same limitation problem about the performance under mysql with a
lot of IO ?
I test FreeBSD-4.3 pthread and linux 2.2.16 pthread under same servers (ram,
dd etc...) with mysql and same databases exactly. When I doing a request of
about 57000 rows on a 400 rows database under linux I can have 1,70s of
elapsed time and under FreeBSD, I have 2.89s for the same request. I see
that Linux doing a lot of IO cache (buffered = 502556K and cached = 335160K,
servers have 1 Go of memory) but FreeBSD limits to a little cache and 112 Mo
buffered, the rest of memory is Free. I'm a FreeBSD fan, but I see that I
cannot use FreeBSD for a mysql box production that do a lot of selects
(index on memory doesn't change anything). I try to use softupdates but
there is a little amelioration. Sinisa of mysql dev team says to me that
reason lies in much more efficient context-switching, more efficient file
system and much better buffering. So what is the difference about linux
caching and FreeBSD ? is the vfs_bio architecure responsible of this lack of
performance ?
If someone can tell me how can I boost performance of caching under FreeBSD
to have the same performance, please tell me :)
If this problem is due to another problem and You know what is this problem
tell me how too.
I hope that FreeBSD can run mysql thread native as faster as possible in the
future.

Thank you for any clues.
Regards,
Sebastien Petit.
-- 
[EMAIL PROTECTED]

> How is performance dismal under redhat?  FreeBSD should do a really
> good job of running thousands of threads as long as you don't have
> too much disk IO since all the threads are multiplexed into a single
> process, if you have an IO intensive program FreeBSD threads will
> probably not help you all that much.  There are plans on replacing
> the FreeBSD threads library with a multiplexed userland<->kernel
> scheme in the near future.
> 
> 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: VPN

[Doug Young]

 
> Actually ppp shouldn't be that hard to set up as a vpn server.

exactly where to find  config information suitable for a non-expert ??


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: VPN

[Alfred Perlstein]

* Doug Young <[EMAIL PROTECTED]> [010426 01:01] wrote:
> I've just been going through this stuff for the past week.
> None of the things come with adequate documentation
> so you need to rely heavily on mailing list support.
> Thankfully a few people have been giving me
> some assistance but looks like at least few days more
> messing around will be involved before its working..


Actually ppp shouldn't be that hard to set up as a vpn server.

-Alfred

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: VPN

[Doug Young]

I've just been going through this stuff for the past week.
None of the things come with adequate documentation
so you need to rely heavily on mailing list support.
Thankfully a few people have been giving me
some assistance but looks like at least few days more
messing around will be involved before its working..

There is a basic HOWTO on one application at
freebsddiary, but its quite dated now.  The only other apps
I've been able to find are vtund & poptop (both from ports)
Judging from feedback I received to a similar question, the
few FreeBSD users who use VPN prefer vtund.

I did look at poptop (which reportedly has some security
"features") in the hope it might be more straightforward to
configure. You need to hack the makefile (its flagged
"forbidden") to install, then theres a few compatibility issues
to contend with (due to the linux heritage)  I gave up with
it at that stage.

I think there may be other applications available if you can
compile support into the kernel  thats not practical for my
present situation as I can't take the server end offline in the
immediate future.

- Original Message -
From: "Jesús Arnáiz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, April 26, 2001 12:56 PM
Subject: RV: VPN


>
>
> -Mensaje original-
> De: Jesús Arnáiz [mailto:[EMAIL PROTECTED]]
> Enviado el: jueves, 26 de abril de 2001 4:36
> Para: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Asunto: VPN
>
>
> Hi!
>
> I want to set VPN on my system, I see there is many programs created to do
it.
>
> Any advantages or disadvantages of using one or other?. What is better (is
the first
> time I set VPN on a UNIX system).?
>
>
> Thanks in advance.
>
>
> --
> Jesús Arnáiz
> 0z0ne Inc I+D/IT Manager
> http://www.0z0ne.com
> mailto:[EMAIL PROTECTED]
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message