Re: network traffic

[Oscar Ricardo Silva]

At 02:41 PM 5/18/2004, you wrote:
any one know were I can get a netwrk testing tool that can sit on a
server and test the speed of a network connection.. I have a small
network ot work and I get computers that just disappear off the
net..different computer at different times. but most of the time they
are on the net and just are so slow. I have check for virus's and adware
and changed the switching hub out..I have even replaced every network
cable in the place
I would like two programs that sit on two computer and just talk to each
other and tell what the speed they are talking and if there is a packet
loss

iperf or netperf?

Oscar
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re[2]: True IMAP Trash Folder

[Oscar Ricardo Silva]

At 09:33 AM 2/2/2004, you wrote:
Hi Matt,

On Mon, 02 Feb 2004 10:27:41 -0500 UTC (2/2/2004, 9:27 AM -0600 UTC my
time), Matt Juszczak wrote:
>>There is no trash folder in the IMAP protocol itself.. Removing mail is a
>>two step process, first of deleting it, and second of purging the deleted
>>mail.
>>
>>
>>
M> I understand now.  Thanks.  So do you know of a mail client that
M> supports "Deleting Items" to a folder called "Trash" on the IMAP
M> server?
No, because it is not part of the IMAP protocol.

M> Right now I have evolution and if I delete mail it puts it into
M> a local trash folder, but I dont see an option to "Copy deleted mail to
M> folder  on mail server" or something like that.
Right, not part of the protocol, so there would be no option for that. You
can either manually drag-N-drop deleted mail, before you purge it, to a new
folder you create on the server, called Trash, or whatever. Or... perhaps
you can set up a filter to move/copy deleted mail to your new Trash folder,
etc... this might work.


Which leads me to ask/comment/point out, a bit off topic perhaps ... if you 
do take the filter path, and are checking mail on different machines, 
perhaps with different applications and operating systems ... how do you 
sychronize your filters?  I believe there's not a centralized universal way 
of filtering messages.  Do you have create them on each app you use?

Oscar

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD Security Advisory FreeBSD-SA-03:04.sendmail

[Oscar Ricardo Silva]

Anybody know how we should approach this for older versions of FreeBSD?  Is 
upgrading source and rebuilding the only way?  I was wondering if there 
were binary versions or patches for older versions so we don't have 
upgrade, rebuild and reboot.



At 09:11 AM 3/3/2003 -0800, FreeBSD Security Advisories, you wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-03:04.sendmail   Security Advisory
  The FreeBSD Project
Topic:  sendmail header parsing buffer overflow

Category:   contrib
Module: contrib_sendmail
Announced:  2003-03-03
Credits:Mark Dowd (ISS)
Affects:All releases prior to 4.8-RELEASE and 5.0-RELEASE-p4
FreeBSD 4-STABLE prior to the correction date
Corrected:  2003-03-03
FreeBSD only:   NO
I.   Background

FreeBSD includes sendmail(8), a general purpose internetwork mail
routing facility, as the default Mail Transfer Agent (MTA).
II.  Problem Description

ISS has identified a buffer overflow that may occur during header
parsing in all versions of sendmail after version 5.79.
In addition, Sendmail, Inc. has identified and corrected a defect in
buffer handling within sendmail's RFC 1413 ident protocol support.
III. Impact

A remote attacker could create a specially crafted message that may
cause sendmail to execute arbitrary code with the privileges of the
user running sendmail, typically root.  The malicious message might be
handled (and therefore the vulnerability triggered) by the initial
sendmail MTA, any relaying sendmail MTA, or by the delivering sendmail
process.  Exploiting this defect is particularly difficult, but is
believed to be possible.
The defect in the ident routines is not believed to be exploitable.

IV.  Workaround

There is no workaround, other than disabling sendmail.

V.   Solution

Do one of the following:

1) Upgrade your vulnerable system to 4-STABLE; or to the RELENG_5_0,
RELENG_4_7, or RELENG_4_6 security branch dated after the correction
date (5.0-RELEASE-p4, 4.7-RELEASE-p7, or 4.6.2-RELEASE-p10,
respectively).
[NOTE: At the time of this writing, the FreeBSD 4-STABLE branch is
 labeled `4.8-RC1'.]
2) To patch your present system:

The following patch has been verified to apply to FreeBSD 5.0, 4.7,
and 4.6 systems.
a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail.patch
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail.patch.asc
b) Execute the following commands as root:

# cd /usr/src
# patch < /path/to/patch
# cd /usr/src/lib/libsm
# make obj && make depend && make
# cd /usr/src/lib/libsmutil
# make obj && make depend && make
# cd /usr/src/usr.sbin/sendmail
# make obj && make depend && make && make install
3) For i386 systems only, a patched sendmail binary is available.
Select the correct binary based on your FreeBSD version and whether or
not you want STARTTLS support.  If you want STARTTLS support, you must
have the crypto distribution installed.
a) Download the relevant binary from the location below, and verify
the detached PGP signature using your PGP utility.
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail-4.6-i386-crypto.bin.gz
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail-4.6-i386-crypto.bin.gz.asc
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail-4.6-i386-nocrypto.bin.gz
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail-4.6-i386-nocrypto.bin.gz.asc
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail-4.7-i386-crypto.bin.gz
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail-4.7-i386-crypto.bin.gz.asc
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail-4.7-i386-nocrypto.bin.gz
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail-4.7-i386-nocrypto.bin.gz.asc
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail-5.0-i386-crypto.bin.gz
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail-5.0-i386-crypto.bin.gz.asc
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail-5.0-i386-nocrypto.bin.gz
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:04/sendmail-5.0-i386-nocrypto.bin.gz.asc
b) Install the binary.  Execute the following commands as root.
Note that these examples utilizes the FreeBSD 4.7 crypto binary.
Substitute BINARYGZ with the file name which you downloaded in
step (a).
# BINARYGZ=/path/to/sendmail-4.7-i386-crypto.bin.gz
# gunzip ${BINARYGZ}
# install -s -o root -g smmsp -m 2555 ${BINARYGZ%.gz} 
/usr/libexec/sendmail/sendmail

c) Restart sendmail.  Execute the following command as root.

# /bin/sh /etc/rc.sendmail restart

VI.  Correction details

The following list contains the revision numbers of each file that was
correc

Re: filesystem disappeared following 4.2 -> 4.7 upgrade

[Oscar Ricardo Silva]

At 08:23 PM 2/2/2003 -0600, Mike Meyer, you wrote:

In <[EMAIL PROTECTED]>, Brent Kearney <[EMAIL PROTECTED]> 
typed:
> What if this system were an all-IDE system?  I was planning to update
> one soon, and will no doubt run into this problem.  The root
> filesystem device node will change names, and according to this
> thread:
> 
http://www.freebsd.org/cgi/getmsg.cgi?fetch=2388792+2394647+/usr/local/www/db/text/2003/freebsd-questions/20030112.freebsd-questions

No, devices *may* change names. They don't have to. The article you
quoted changed names drastically because he wasn't using the onboard
IDE controller, but had all his drives on the Promise card (would you
verify that for me, Oscar)? One solution to the question asked in that
message is to disable the IDE on the motherboard so that the Promise
controller becomes ata0, and the first drive on it becomes ad0. That
also frees up a couple of IRQs, and may be worth doing in any
case. It's probably better to try changing /boot/loader.conf to set
root_disk_unit to solve the problem, though.


Wel ... yes and no.  I wasn't putting the drive on the first and second 
IDE controllers.  The motherboard had two additional IDE controllers, 
Promise ATA66, on it.

On some BIOS, you can direct the machine to look at slot devices before 
onboard devices, that might help your situation.

Not that it's any kind of solution, but in the end, while attempting to do 
another install on the system, I accepted the default sizes for the 
filesystems and it worked.  Creating a / filesystem of 128MB ... and from 
there it booted fine.




Oscar


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

Re: Making the all-important switch

[Oscar Ricardo Silva]

top posting is placing your reply at the top of a message, as I'm doing now 
(please, no flames, this is a deliberate example).  On this and many other 
mailing lists I belong to, the preferred way of replying is at the end of 
the message.  This way, your reply and any other previous messages can be 
read chronologically, usually with the original message first.  The benefit 
is that you can get an idea of what the original message was and what 
subsequent replies there have been (if any).


As for other things to keep in mind:
1.  Don't edit/truncate logs and/or error messages.  Sometimes you may 
think a particular section is not relevant when in reality that might give 
a clue to the real problem.

2.  Ignore anyone trying to bait you (you'll probably get some of these 
regarding your Windows comment).  I agree with what you said but on a more 
general level.  There are times and places for different operating systems 
depending on the user and the job that needs to be done.  Of course 
sometimes my take on different operating systems is a choice between 
FreeBSD and a Linux distribution, not Windows ("That's a joke son" - 
Foghorn Leghorn)

3.  Be generous with your suggestions, experiences and/or questions.  I 
don't know how many times I've posted a question, received private replies 
and later received a message asking whether I had resolved the problem 
because that person is also experiencing it.



Oscar


At 11:01 AM 1/25/2003 -0600, jshowatt, you wrote:
This is my first ever post to a FBSD mailing list so can someone explain
what "top posting" is and why it's not well received?  What other
formatting/etiquette rules should I keep in mind?

> > > > I'm about ready to ditch Windoze for good and I'm spending what
little
> > > > free time I can find to prepare by researching FreeBSD. Currently, I
run

> Choosing the right OS for a computer with a specific use is like choosing
> the right tool for the job; it's essential.

So why the derogatory 'Windoze' rather than simply 'Windows'?  I would argue
that Windows is the 'right OS' for many uses.  Try running AutoCAD on any
other operating system.  Remove Windows from the desktops of every
architecture firm in the US and you would cripple the industry.  Windows is,
in short, essential in this context.

I've been following -questions for awhile and read a very well reasoned and
succinct argument against using such negative terms to describe other
platforms.  I've chosen to adopt this view myself.  Don't get me wrong, I'm
actually envious of your ability and openness to trying different OSes.
Just putting in my two cents.

Good luck with FreeBSD and keep -newbies posted of your progress.  I for one
would be interested in knowing what differences (or lack thereof) you
discover.

Steve


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



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

Re: Mount root fails after clean install of FreeBSD 4.7

[Oscar Ricardo Silva]

I wonder if I scared anybody off with all the detail.  The short of it is 
that I have a Seagate 80GB drive on a motherboard, the drive on the 3rd of 
four IDE controllers (3rd and 4th are Promise ATA66).  The install goes 
fine but after reboot, I get the boot2 prompt, which if I interrupt with 
the correct entry instead of the default:

>>FreeBSD/i386 BOOT
Default:  0:ad(0,a)/kernel
boot:

the boot continues properly.  If I don't interrupt it, I get the "Manual 
root filesystem specification" screen and am given the mountroot 
prompt.  If I give the correct entry ofufs:/dev/ad4s1a   everything 
goes well, otherwise the boot procedure is stopped.  Is there a way to 
change the default boot2 so that it boots off of ad4 instead of ad0?




At 11:45 AM 1/9/2003 -0600, Oscar Ricardo Silva, you wrote:
I have a motherboard with two onboard Promise ATA66 controllers.  The hard 
drive is a Seagate ST380021A, connected as the master on the first Promise 
controller, referenced as ad4.  I have attempted to do a clean install, 
creating one FreeBSD slice on the entire disk.  I set the slice bootable 
and I install a Standard MBR on it.  After this I do a full install of 
4.7, do the post-install configuration, but when the machine reboots I get 
prompted to mount the root.  For some reason, the machine is attempting to 
mount the root from ad0s1a instead of ad4s1a.  At the mountroot prompt I 
do enter:

mountroot> ufs:/dev/ad4s1a

and the machine continues booting without problem.  Here is the dmesg output:


atapci1:  port 
0xe800-0xe83f,0xe400-0xe403,0xe000-0xe007,0xdc00-0xdc03,0xd800-0xd807 mem 
0xe000-0xe001 irq 9 at device 14.0 on pci0
ata2: at 0xd800 on atapci1
ata3: at 0xe000 on atapci1
...
lpt0: Interrupt-driven port
ppi0:  on ppbus0
ad4: 76319MB  [155061/16/63] at ata2-master UDMA66
acd0: CDROM  at ata1-master PIO4
Mounting root from ufs:ad0s1a
Root mount failed: 6
Mounting root from ufs:ad0a
Root mount failed: 6

Manual root filesystem specification:
  :  Mount  using filesystem 
   eg. ufs:/dev/da0s1a
  ?  List valid disk boot devices
 Abort manual input

mountroot> ufs:/dev/ad4s1a
Mounting root from ufs:/dev/ad4s1a




There is only the Seagate hard drive in the computer, no others.  I don't 
know why it's looking for anything on ad0.  There are the correct devices 
listed in  /dev :

/dev/ad4
/dev/ad4s1
/dev/ad4s1a
/dev/ad4s1b
/dev/ad4s1c
/dev/ad4s1d
/dev/ad4s1e
/dev/ad4s1f
/dev/ad4s1g
/dev/ad4s1h



and /etc/fstab references all the right devices:

# See the fstab(5) manual page for important information on automatic mounts
# of network filesystems before modifying this file.
#
# DeviceMountpoint  FStype  Options DumpPass#
/dev/ad4s1b noneswapsw  0   0
/dev/ad4s1a /   ufs rw  1   1
/dev/ad4s1e /boot   ufs rw  2   2
/dev/ad4s1h /home   ufs rw  2   2
/dev/ad4s1g /tmpufs rw  2   2
/dev/ad4s1d /usrufs rw  2   2
/dev/ad4s1f /varufs rw  2   2
/dev/acd0c  /cdrom  cd9660  ro,noauto   0   0
proc/proc   procfs  rw  0   0



In case it helps, here is how I labeled and sized the filesystems (listed 
in order of creation during the install):

/boot   50M
/   1500M
swap1024M
/var5000M
/tmp1000M
/home   5000M
/usr6M



Any information would be appreciated.



Oscar


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-questions" in the body of the message

Mount root fails after clean install of FreeBSD 4.7

[Oscar Ricardo Silva]

I have a motherboard with two onboard Promise ATA66 controllers.  The hard 
drive is a Seagate ST380021A, connected as the master on the first Promise 
controller, referenced as ad4.  I have attempted to do a clean install, 
creating one FreeBSD slice on the entire disk.  I set the slice bootable 
and I install a Standard MBR on it.  After this I do a full install of 4.7, 
do the post-install configuration, but when the machine reboots I get 
prompted to mount the root.  For some reason, the machine is attempting to 
mount the root from ad0s1a instead of ad4s1a.  At the mountroot prompt I do 
enter:

mountroot> ufs:/dev/ad4s1a

and the machine continues booting without problem.  Here is the dmesg output:


atapci1:  port 
0xe800-0xe83f,0xe400-0xe403,0xe000-0xe007,0xdc00-0xdc03,0xd800-0xd807 mem 
0xe000-0xe001 irq 9 at device 14.0 on pci0
ata2: at 0xd800 on atapci1
ata3: at 0xe000 on atapci1
...
lpt0: Interrupt-driven port
ppi0:  on ppbus0
ad4: 76319MB  [155061/16/63] at ata2-master UDMA66
acd0: CDROM  at ata1-master PIO4
Mounting root from ufs:ad0s1a
Root mount failed: 6
Mounting root from ufs:ad0a
Root mount failed: 6

Manual root filesystem specification:
  :  Mount  using filesystem 
   eg. ufs:/dev/da0s1a
  ?  List valid disk boot devices
 Abort manual input

mountroot> ufs:/dev/ad4s1a
Mounting root from ufs:/dev/ad4s1a




There is only the Seagate hard drive in the computer, no others.  I don't 
know why it's looking for anything on ad0.  There are the correct devices 
listed in  /dev :

/dev/ad4
/dev/ad4s1
/dev/ad4s1a
/dev/ad4s1b
/dev/ad4s1c
/dev/ad4s1d
/dev/ad4s1e
/dev/ad4s1f
/dev/ad4s1g
/dev/ad4s1h



and /etc/fstab references all the right devices:

# See the fstab(5) manual page for important information on automatic mounts
# of network filesystems before modifying this file.
#
# DeviceMountpoint  FStype  Options DumpPass#
/dev/ad4s1b noneswapsw  0   0
/dev/ad4s1a /   ufs rw  1   1
/dev/ad4s1e /boot   ufs rw  2   2
/dev/ad4s1h /home   ufs rw  2   2
/dev/ad4s1g /tmpufs rw  2   2
/dev/ad4s1d /usrufs rw  2   2
/dev/ad4s1f /varufs rw  2   2
/dev/acd0c  /cdrom  cd9660  ro,noauto   0   0
proc/proc   procfs  rw  0   0



In case it helps, here is how I labeled and sized the filesystems (listed 
in order of creation during the install):

/boot		50M
/		1500M
swap		1024M
/var		5000M
/tmp		1000M
/home		5000M
/usr		6M



Any information would be appreciated.



Oscar


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

Re: Wondering about mail clients (specific features)

[Oscar Ricardo Silva]

>I see there are already a few mutt recommendations, so I'll just quote
>the mutt.org site:  'All mail agents suck.  This one just sucks less.'
>And that is true.  Mutt is by far the most flexible and malleable MUA
>I've found, and I've actually started forgetting the little details
>about Netscapes MUA that you learn little by little over years of use.
>
>I use cyrus imapd as my server, procmail to filter crap, and just
>create a mailbox for each list or account I want to manage.  I have
>one for my work email, which I then fetch from my employers pop server
>using fetchmail, same with attbi email.  I also create a box for each
>mail list I subscribe to, then just subscribe as
>leblanc+@keyslapper.org.  When a message comes in, cyrus
>puts it into the folder with that name.  Mutt simply handles it as a
>series of folders, and as a previous poster mentioned, you can
>configure mutt to tell you which folders to monitor for new messages.
>You can also tell mutt which email addresses you consider lists, so it
>can handle a list reply properly.  With the correct patches, mutt can
>also read newsgroups, though I've recently fallen off the NGs and
>stopped building with them.
>
>I also use gbuffy (similar to xbiff, found in the ports) to create a
>little bar at the bottom of my screen.  Create one entry for each
>folder I want to monitor, and as mail comes in, it tells me how many
>unseen messages are in each.  Pretty slick.
>
>Mutt will also connect to cyrus via imaps (secure imap connection).
>Gbuffy won't, but it only reads the From: and Subject: headers.
>
>Ok, I did a little more than just quote the mutt.org site, but you get
>the picture.  Some of the stuff I do just can't be done on Windoze -
>without a whole lot more work porting recent versions to cygwin and
>jumping through twice as many hoops.
>
>Good luck, HTH
>Lou
>--
>Louis LeBlanc   [EMAIL PROTECTED]
>Fully Funded Hobbyist, KeySlapper Extrordinaire :)
>http://www.keyslapper.org ԿԬ




Thanks for the information.  From all the responses I received looks like 
I'll be going with mutt.



Oscar



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

Wondering about mail clients (specific features)

[Oscar Ricardo Silva]

It is not my intention to start any religious wars about mail clients.  I'm 
currently using Eudora (stop, drop, roll and duck incoming slings and 
arrows) on Windows.  One feature I like is that when mail is received and 
filtered into different mailboxes, you are told there is new mail in those 
mailboxes.  I subscribe to many different mailing lists and for the sake of 
my sanity I filter incoming mail from each list into its own mailbox.  I've 
tried using pine with procmail and mail is filtered properly but I don't 
know that there is new mail in mailboxes other than "In".

Is there something I'm missing in pine that will do this?  Are there other 
mail clients that will notify you when new mail has been received and 
placed in a mailbox other than "IN" ?


Oscar


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

Re: NTPD

[Oscar Ricardo Silva]

How soon after you start ntpd do you try checking time?  I've found that 
synchronization with the servers in ntp.conf takes quite a bit of 
time.  Start up the daemon, leave it alone for at least 15 minutes (more is 
better) and then check time.  In case it helps, here is my /etc/ntp.conf file:

driftfile   /etc/ntp.drift

disable auth monitor

server  tick.uh.edu prefer
server  tick.greyware.com



Oscar

At 05:32 PM 7/24/2002 -0400, Brian McCann, you wrote:
>Ok...I've tried reading the NTPD pagesbut they are a bit cryptic for 
>me.  I'm trying to set up an NTP server.  I tried just running "ntpd -A", 
>and when I try to query it, my client returns "no server suitable for 
>sync. found".  Is there a howto someplace on setting up a NTPD server?  Or 
>could someone tell me how?
>
>Thanks,
>--Brian


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

Re: "^L" File, needs to be Removed

[Oscar Ricardo Silva]

This might help:



UNIX: How To Deal With Filenames Containing Unprintable/Special Characters



Oscar

At 05:30 PM 7/17/2002 -0400, [EMAIL PROTECTED], you wrote:
>server /etc/namedb/ # ls -la |more
>total 970
>-rw-r--r--   1 bind  bind   -552 Aug  8  2000 ^L
>drwxr-xr-x   2 bind  wheel  -  10240 Jul 17 17:06 ./
>drwxr-xr-x  19 root  wheel  -   2560 Jul 17 17:20 ../
>
>Can only be opened via (editor of choice) ?, e.g. pico ?
>
>The file contains a zone file, from ages ago, but the original zone file 
>is fine and
>is still there.
>
>Even after a quick secondary backup of the whole directory, I am hesitant to
>perform a rm ? because the directory contains 100's of critical zone files.
>
>Any safe way to remove it and why sometimes after an ls -la the file comes up
>as ^L and other times ? and only can be opened when you specify ?
>
>Thank you! :)
>
>
>
>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-questions" in the body of the message

Re: Adding disks via an expansion card

[Oscar Ricardo Silva]

At 08:16 AM 7/17/2002 -0700, David, you wrote:
>- Original Message -
>From: "David" <[EMAIL PROTECTED]>
>
>
> > I've looked through what I can of the Handbook and FAQ but can't seem to
> > find an answer.
> >
> > I have added a Maxtor UltraATA/100 PCI Adaptor Card to one of my machines
> > (to replace failing on-board IDE controllers).  On boot, I see that it is
> > detected and it detects the hard drive attached to it.  However, I have
>two
> > problems.
> >
> > 1) The CD-ROM attached to the card is not detected.
> > 2) The devices don't exist in /dev to do anything with it.
> >
> > I have tried to use 'MAKEDEV all' to get the devices to appear there, but
>it
> > doesn't seem to do it.  Do I have to add the devices manually?
> >
> > exerpt from dmesg:
> >
> > atapci1:  port
> > 0xec00-0xec3f,0xe800-0xe803,0xe400-0xe407,0xe000-0xe003,0xdc00-0xdc07 mem
> > 0xee00-0xee01 irq 11 at device 10.0 on pci0
> > ata2: at 0xdc00 on atapci1
> > ata3: at 0xe400 on atapci1
> > 
> > ad2: 2014MB  [4092/16/63] at ata1-master UDMA33
> > ad3: 12416MB  [25228/16/63] at ata1-slave UDMA33
> > ad4: 4121MB  [8374/16/63] at ata2-master UDMA33
> >
> >
>
>Well, I found a way to do this, though I'm wondering if there's an easier
>way.  I ended up removing an option in the kernel conf for static IDE
>numbering.  I recompiled that and rebooted.  On the way up I disabled the
>first IDE controller on the board.  When the rest of the machine came up the
>secondary master and secondary became ad0 and ad1, respectively, while the
>new controller's master and secondary became ad2 and ad3.
>
>While this works, it also means that I can't use the secondary controller on
>the add-on card I have.
>
>I found these lines in the kernel conf:
>
>device  ata0at isa? port IO_WD1 irq 14
>device  ata1at isa? port IO_WD2 irq 15
>
>Can I just add another line like this?   A friend also suggested I use the
>wd driver, but it appears to be mutually exclusive with the ata driver.
>Anyone know what the best way to do this would be or suggestions on what I
>could do?
>
>David


Have you tried going into /dev and issuing the MAKEDEV commands to make the 
individual devices?  How about going through /stand/sysinstall and seeing 
if you can manipulate the new drives from there?

I ran into the same problem with you after adding an ATA/66 card.  I had to 
add the create the devices /dev/ad6s1, etc. using MAKEDEV and that worked 
without a problem.


Oscar


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

VLAN experiences with FreeBSD?

[Oscar Ricardo Silva]

I would like to find out what kind of experiences people have had 
implementing VLANs in FreeBSD.  We're currently running some Red Hat Linux 
machines and have created VLANs on them but are considering moving this to 
FreeBSD.  The Linux machines will sometimes completely stop responding, and 
I mean nothing, no video, no keyboard, no network, no response at 
all.  These machines are all connected to various models of Cisco ethernet 
switches, all of which support 802.1q VLANs, but we use the machines for 
authenticating public users.  We believe that FreeBSD would provide a more 
stable environment but have no experience using/creating/managing 802.1q 
VLANs on FreeBSD.

Any information would be appreciated.


Oscar


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

Re: Enabling Telnet capabilities

[Oscar Ricardo Silva]

Have you looked at and edited the /etc/inetd.conf file?  As far as telnet I 
would strongly discourage you from using telnet to gain access to your 
computer.  How about using ssh?  This way passwords and traffic are encrypted.


Oscar

At 06:23 PM 7/12/2002 +, Jed Sargent, you wrote:


>Been trying to add the capability to Telnet into my Box, but have been 
>unable to so far.  All of the reference material is for doing a serial 
>connection, which I can do, just not an ethernet connection.  I believe my 
>problem is in the TTYS file, not using the right line entry on the ttyp0.
>Thanks, Jed
>
>_
>Send and receive Hotmail on your mobile device: http://mobile.msn.com
>
>
>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-questions" in the body of the message