at 07:23:07PM -0700, Joesh Juphland wrote:
Hello,
I have a machine whose primary IDE controller is blown. Only the
secondary
works. So, I connected my single IDe drive as the secondary master, and
proceeded to install FreeBSD.
The install went flawlessly. I installed
Hello,
I have a machine whose primary IDE controller is blown. Only the secondary
works. So, I connected my single IDe drive as the secondary master, and
proceeded to install FreeBSD.
The install went flawlessly. I installed with the FreeBSD boot manager(the
first choice on that screen of
Vanilla x86 system with two identical scsi disks attached to a single 2940.
Installation is flawless - in custom install, I choose da0 and then da1, one
after the other, to partition. Again, I say, installation goes flawlessly.
When the system boots though, it cannot get past the boot
One thing I would like to do as a hobby is start a classic multi-user unix
system and giving out shell accounts to whoever wants one. Not a money
maker, of course, but it would be fun.
My question: does anyone have any comments on using `jail` in a public
environment like this - that is,
I am going to be setting up four freeBSD servers as a test environment -
they need to be totally isolated machines. However, I would like to see if
I can do all of this on one server. The choice that comes to mind
immediately is vmware, but since I am required to use all freeBSD, I would
I am planning on building a true multi-user system (as opposed to a NFS
server, or a web server, or a mail server) - many people with many shells
will be doing many things.
Two things have been decided:
- it will run freeBSD
- it will be dual processor
-
So what two processors should I
I have two 3com 3c589 10BT pc cards. As vanilla as they come.
In a previous thread, I described how a bit of pccard.conf mumbo jumbo made
it possible for me to get both cards up and running in 4.3-RELEASE. It was
explained to me that pccard.conf is deprecated, and that two pcmcia nics
I cannot mount any of the NFS shares that I share from my server due to a
problem with mountd and RPC.
rc.conf looks like this:
network_interfaces=lo0
removable_interfaces=wi0
nfs_server_enable=YES
nfs_server_flags=-t -u -n 4
/etc/exports looks like this:
/mp3 myclient
I have the
I am trying to get two identical 3C589 pc cards working simultaneously on my
laptop. This was accomplished with FreeBSD 4.3 by adding lines like this to
/etc/defaults/pccard.conf :
config auto ep0 10
config auto ep1 15
(everything else for that cards entry is left the same)
However, this
Ok, so I finally got two identical ep cards to come up at the same time
and both work. Thanks.
But when I run:
sysctl -w net.link.ether.bridge=1
Nothing happens. They don't get put in promiscuous mode, and bridging does
not get turned on, even though I have bridging in my kernel.
Can
/etc/rc.conf looks like this:
pccard_enable=YES
pccard_mem=DEFAULT
pccardd_flags= -i 10 -i 15
removable_interfaces=ep0 ep1
network_interfaces=lo0
(I have tried with and without that last lo0 line)
and /etc/defaults/pccard.conf looks like this:
config auto ep0 10
config auto ep1 15
so
/etc/rc.conf looks like this:
pccard_enable=YES
pccard_mem=DEFAULT
pccardd_flags= -i 10 -i 15
removable_interfaces=ep0 ep1
/etc/defaults/pccard.conf has this:
io 0x240-0x360
irq 10 15
memory 0xd4000 96k
and I added a second config line to the ep0 line like this:
config auto ep 10
You mean in /etc/defaults/pccard.conf ? or in /etc/rc.conf ?
thanks.
: hostname pccardd[87]: No free configuration for card 3Com Corporation
You need a second config line to the 3com entry.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe
freebsd-hackers in the body
I am trying to run two 3com 3c589 pc-cards in one system. Technically one
is a straight 3c589 and one is 3c589c.
irqs are good, since I can put any one of the two 3c589's into the laptop
along with a wavelan (wi) and both cards show up fine and work.
But when I put two 3c589's in, the first
thank you - this was helpful. One last question - when you say that
bridging cannot work with wi cards because they do not support promiscuous
transmission, this makes me wonder two things:
1. Do you mean the wi driver does not support this, or you mean the actual
physical card itself is
Recently on this list someone mentioned that you cannot bridge with the 'wi'
driver. This interests me and I have some questions:
(I am running strictly 4.3-RELEASE, btw)
1. is this just temporary - or will we _never_ be able to bridge with 'wi'
?
2. can I bridge with 'an' (cisco aironet
Great.
Can I already bridge with an* ? And does this mean that bridging in
general with pc cards is a-ok ?
thanks.
you WILL be able to bridge with WI cards
no time estimates though..
On Tue, 26 Jun 2001, Joesh Juphland wrote:
Recently on this list someone mentioned that you cannot
Many pcmcia cards that I use have user-updateable firmware - basically a
flash region of some kind that you can update with newer firmwares.
When I want to update these items, I generally stick them in a windows
machine and get the new firmware from the manufacturer and use whatever
program
18 matches
Mail list logo
