Re: freebsd Wireless
You can use the madwifi driver, resident in the standard 5.2.1 distribution. kldload ath_hal kldload if_ath You will be able to tell if the madwifi driver sees your atheros-based card by looking at the output of the second module load. If it does, you can use ifconfig (man ifconfig) to configure your wireless environment. Example: ifconfig ath0 up ifconfig ath0 inet 192.168.X.Y/24 ifconfig ath0 wepmode on wepkey MYKEY ifconfig ath0 ssid MYSSID MYKEY and MYSSID must jive with your AP configuration. MST Dan wrote: Looking for setup help on wireless Atheros chip set. Telesat International Ltd. Dan Berge ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Serial Port Boot Configuration
I am trying to remotely debug a FreeBSD kernel, and it appears that the baud rate and other stty settings are being modified during system boot. I have modified the /dev/ttyid0 device and the /dev/ttyld0 device, yet their settings are being reset somewhere during reboot as well. I have looked at the handbook, which states that initial settings are found in /etc/rc.serial, but there is no such file and no reference to it in man rc.serial. Where are boot serial parameters configured and by what are they set? I need to set my ttyd0 port up to allow brkint, 115200 baud etc. TIA, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: two questions
Here is a script I use to backup my linux system: #!/bin/sh MEDIUM=/mnt/dmzserv/share/mark/BACKUP/webserver echo Creating system backup on $MEDIUM as dmz2-sys-backup-date.tar.gz... tar -zcvpf $MEDIUM/dmz2-sys-backup-`date '+%d-%B-%Y'`.tar.gz \ --directory / --exclude=mnt --exclude=proc --exclude=share . echo ...done This creates a system backup starting in /, excluding mnt, proc and share, with the file name including the date. MST Michael Sharp wrote: I'm having a brain freeze tonight and apparently forgot some basic UNIX commands.. what is the command to remove the file --directory rm *directory* = nope rm *directory* = nope rm \-\-\directory = nope rm -i * = nope and dosent even see the file Also, if I'm in / and want to tar the entire filesystem EXCLUDING the directory jail ( /jail ) what would be the switches to tar? Dana ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with Remote Kernel Debugging on the 5.2.1 Kernel
It is serial debugging, as described in the Developer's Handbook. I have set up the same remote debugging environment in linux using gdb/ddd with success. Further, the Interrupt button in ddd is ^C, and in gdb ^C is what is used to break execution, at least in past experience in linux. How would I send a BREAK, and how would one setup ddd to use that instead of ^C? That should definitely be addressed in the developer's handbook if it is non-standard for FreeBSD. Thanks, Mark John E Hein wrote: Mark Teel wrote at 19:48 -0500 on Jun 22, 2004: I have configured remote kernel debugging as prescribed in the developer's handbook. I am able to step through code, but once I enter cont in gdb on the debug machine, I cannot ever interrupt or break the target kernel execution. It is as if the Ctrl-C character is being ignored on the target. The target kernel was built with the ddb and -g options set, using config -g as well. Has anyone seen such a problem? This is the last hurdle before I can start debugging my wireless device driver. If you mean serial debugging, you use the serial BREAK, not ctrl-c. If you are connecting using tip, you use ~# to send a break (man tip). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with Remote Kernel Debugging
Hello: I have configured remote kernel debugging as prescribed in the developer's handbook. I am able to step through code, but once I enter cont in gdb on the debug machine, I cannot ever interrupt or break the target kernel execution. It is as if the Ctrl-C character is being ignored on the target. The target kernel was built with the ddb and -g options set, using config -g as well. Has anyone seen such a problem? This is the last hurdle before I can start debugging my wireless device driver. Thanks in advance, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with Remote 5.2.1 Kernel Debugging
Hello: I have configured remote kernel debugging as prescribed in the developer's handbook. I am able to remotely connect to the target and step through code, but once I enter cont in gdb on the debug machine, I cannot ever interrupt or break the target kernel execution. It is as if the Ctrl-C character is being ignored on the target. The target kernel was built with the ddb and -g options set, using config -g. Has anyone seen such a problem? This is the last hurdle before I can start debugging my wireless device driver. Any advice would be appreciated. Thanks in advance, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cannot Login After Using Kuser to setup Accounts
On a fresh install of FreeBSD 5.2, after I add a user via kuser, when I logout I cannot log back in! I get a message stating that the accound has expired, even for the root user. Please help as this has rendered my system unusable. Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
