Re: Growisofs seg faults with DVD-RAM. Anybody else seen this?
On Friday, 29 July 2005 at 22:50:13 -0700, Carl Delsey wrote: I was trying to use growisofs to write to a DVD-RAM and it kept seg faulting. It worked fine with a DVD-R. I tracked the problem down to place in the code where growisofs tries to perform an operation on a file handle it has already closed. I've implemented a workaround already. The problem is, that by my reckoning, this should affect anybody who is trying to use a DVD-RAM (not DVD+RW) with FreeBSD, but I haven't found any references to the problem on the net. My guess is that DVD-RAM isn't popular enough, and that people who have had problems with it haven't had the understanding to track the bug down. I'm wondering if anybody else has seen this problem, and if you've found some other workaround for it? Or alternatively, you still have the problem and my patch would be useful to you. :-) Is this a workaround or a fix? The latter is obviously preferable. Also, does this only affect FreeBSD, or is it general? In the former case, contact the maintainer (mail address in the Makefile); in the latter, contact the project. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgpSLAfTK6V20.pgp Description: PGP signature
Shell script help
I'm working on a new port, and the one thing I can't seem to solve is the
man pages. They install fine, but they're not formatted right.
In the Makefile that is built from configure, this is the section that
handles the man pages:
@cd $(TOP_DIR)/doc; for i in *.n; \
do \
rm -f $(MAN_INSTALL_DIR)/`basename $$i`; \
rm -f $(MAN_INSTALL_DIR)/`basename iwidgets_$$i`; \
sed -e '/man\.macros/r man.macros' -e '/man\.macros/d' \
$$i $(MAN_INSTALL_DIR)/`basename iwidgets_$$i`; \
chmod 444 $(MAN_INSTALL_DIR)/`basename iwidgets_$$i`; \
done;
Running what I *thought* was the same sed command in the Makefile of the
port doesn't solve the problem of the formatting of the man pages, but it
doesn't generate any errors either:
@${SED} -e '/man\.macros/r man.macros' -e '/man\.macros/d'
${WRKSRC}/doc/${f} \
${WRKDIR}/${f}
Can someone explain what the sed command is doing? The man page isn't much
help.
Paul Schmehl ([EMAIL PROTECTED])
Adjunct Information Security Officer
University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shell script help
in message [EMAIL PROTECTED],
wrote Paul Schmehl thusly...
Running what I *thought* was the same sed command in the Makefile
of the port doesn't solve the problem of the formatting of the man
pages, but it doesn't generate any errors either:
@${SED} -e '/man\.macros/r man.macros' -e '/man\.macros/d'
${WRKSRC}/doc/${f} \
${WRKDIR}/${f}
Can someone explain what the sed command is doing? The man page
isn't much help.
In the 1st part, sed sends the output of file 'man.macros' to
standard out if it exists (otherwise no worries) when sed sees the
'man\.macros' pattern.
And the 2d part, just deletes that pattern.
There in the sed(1) man page all is. Or, line by line try this ...
rm -f q ; echo polka p
{ echo p ; echo q; echo p; } | sed -e '/p/r p' -e '/p/d'
{ echo p ; echo q; echo p; } | sed -e '/p/r q' -e '/p/d'
- Parv
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shell script help
in message [EMAIL PROTECTED], wrote Parv
thusly...
in message
[EMAIL PROTECTED], wrote
Paul Schmehl thusly...
@${SED} -e '/man\.macros/r man.macros'
...
In the 1st part, sed sends the output of file 'man.macros' to
^ ^ ^ ^ ^ ^ ^
^ ^ ^ ^ ^ ^ ^
standard out
[O]utput of file should have been contents of file.
- Parv
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Using a hard drive without partitions
What are the ramifications, good or bad, of not using partitions on a FreeBSD disk? What is wrong with just a slice? Drive: Dangerously dedicated /dev/da0s1 newfs -O2 -U I don't see the point of labeling the disk into partitions, but I can't find any info on why not to do this. I did managed to setup a test drive this way and then grow it (RAID 5 array) with OCE, resize it with fdisk, then make it bigger with bsdlabel, and finally use growfs to extend the filesystem by 10GB. I had no problems doing it like this but everything I've read tells me to partition the disk. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6
On 7/28/05, Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Jul 26, 2005 at 03:00:49PM -0500, Nikolas Britton wrote: The kernel build failed when it tired to compile the r128drm device. Show us the error. cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I../../.. -I../../../contrib/dev/acpica -I../../../contrib/altq -I../../../contrib/ipfilter -I../../../contrib/pf -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd -I../../../contrib/ngatm -I../../../dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror vnode_if.c touch hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c MAKE=make sh ../../../conf/newvers.sh GENERIC cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I../../.. -I../../../contrib/dev/acpica -I../../../contrib/altq -I../../../contrib/ipfilter -I../../../contrib/pf -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd -I../../../contrib/ngatm -I../../../dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror vers.c linking kernel r128_cce.o(.text+0x354): In function `r128_do_cleanup_cce': : undefined reference to `drm_free' r128_cce.o(.text+0x372): In function `r128_do_cleanup_cce': : undefined reference to `drm_irq_uninstall' r128_cce.o(.text+0x394): In function `r128_do_cleanup_cce': : undefined reference to `drm_ioremapfree' r128_cce.o(.text+0x3a8): In function `r128_do_cleanup_cce': : undefined reference to `drm_ati_pcigart_cleanup' r128_cce.o(.text+0x3d7): In function `r128_do_cleanup_cce': : undefined reference to `drm_ioremapfree' r128_cce.o(.text+0x3e3): In function `r128_do_cleanup_cce': : undefined reference to `drm_ioremapfree' r128_cce.o(.text+0x400): In function `r128_cce_init': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0x4ab): In function `r128_cce_init': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0x4bb): In function `r128_cce_init': : undefined reference to `drm_alloc' r128_cce.o(.text+0x504): In function `r128_cce_init': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0x575): In function `r128_cce_init': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0x7e2): In function `r128_cce_init': : undefined reference to `drm_order' r128_cce.o(.text+0x851): In function `r128_cce_init': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0x8e0): In function `r128_cce_init': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0xa1d): In function `r128_cce_init': : undefined reference to `drm_ioremap' r128_cce.o(.text+0xa2f): In function `r128_cce_init': : undefined reference to `drm_ioremap' r128_cce.o(.text+0xa41): In function `r128_cce_init': : undefined reference to `drm_ioremap' r128_cce.o(.text+0xab3): In function `r128_cce_init': : undefined reference to `drm_ati_pcigart_init' r128_cce.o(.text+0xc08): In function `r128_cce_start': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0xc87): In function `r128_cce_start': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0xd13): In function `r128_cce_stop': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0xe14): In function `r128_cce_reset': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0xea1): In function `r128_cce_reset': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0xedd): more undefined references to `drm_debug_flag' follow r128_drv.o(.text+0xc): In function `r128_probe': : undefined reference to `drm_probe' r128_drv.o(.text+0xca): In function `r128_attach': : undefined reference to `drm_attach' r128_drv.o(.data+0x48): undefined reference to `drm_devclass' r128_drv.o(.data+0x94): undefined reference to `drm_detach' r128_irq.o(.text+0x48): In function `r128_driver_irq_handler': : undefined reference to `drm_vbl_send_signals' r128_state.o(.text+0xb): In function `r128_emit_clip_rects': : undefined reference to `drm_debug_flag' r128_state.o(.text+0x2d0): In function `r128_cce_dispatch_flip': : undefined reference to `drm_debug_flag' r128_state.o(.text+0x523): In function `r128_cce_dispatch_indirect': : undefined reference to `drm_debug_flag' r128_state.o(.text+0x7e4): In function `r128_cce_clear': : undefined reference to `drm_debug_flag' r128_state.o(.text+0x906): In function `r128_cce_clear': : undefined reference to `drm_debug_flag' r128_state.o(.text+0xc0f): more
Re: onboard ethernet support
On 7/29/05, Antoine Solomon [EMAIL PROTECTED] wrote: Hello all, has anyone tried to get a marvell Yukon 88E8053 pci-e gigabit ethernet card working on fbsd 5.4? Is there any support for this? Not for 5.x, but I would try project evil and maybe it might be naively supported in 6.x http://www.pingwales.co.uk/tutorials/project-evil.html http://groups-beta.google.com/groups?q=group%3A*.freebsd.*+Marvell+Yukonqt_s=Search ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6
Nikolas Britton wrote: On 7/28/05, Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Jul 26, 2005 at 03:00:49PM -0500, Nikolas Britton wrote: The kernel build failed when it tired to compile the r128drm device. Show us the error. cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I../../.. -I../../../contrib/dev/acpica -I../../../contrib/altq -I../../../contrib/ipfilter -I../../../contrib/pf -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd -I../../../contrib/ngatm -I../../../dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror vnode_if.c touch hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c MAKE=make sh ../../../conf/newvers.sh GENERIC cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I../../.. -I../../../contrib/dev/acpica -I../../../contrib/altq -I../../../contrib/ipfilter -I../../../contrib/pf -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd -I../../../contrib/ngatm -I../../../dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror vers.c linking kernel r128_cce.o(.text+0x354): In function `r128_do_cleanup_cce': : undefined reference to `drm_free' r128_cce.o(.text+0x372): In function `r128_do_cleanup_cce': : undefined reference to `drm_irq_uninstall' r128_cce.o(.text+0x394): In function `r128_do_cleanup_cce': : undefined reference to `drm_ioremapfree' r128_cce.o(.text+0x3a8): In function `r128_do_cleanup_cce': : undefined reference to `drm_ati_pcigart_cleanup' r128_cce.o(.text+0x3d7): In function `r128_do_cleanup_cce': : undefined reference to `drm_ioremapfree' r128_cce.o(.text+0x3e3): In function `r128_do_cleanup_cce': : undefined reference to `drm_ioremapfree' r128_cce.o(.text+0x400): In function `r128_cce_init': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0x4ab): In function `r128_cce_init': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0x4bb): In function `r128_cce_init': : undefined reference to `drm_alloc' r128_cce.o(.text+0x504): In function `r128_cce_init': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0x575): In function `r128_cce_init': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0x7e2): In function `r128_cce_init': : undefined reference to `drm_order' r128_cce.o(.text+0x851): In function `r128_cce_init': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0x8e0): In function `r128_cce_init': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0xa1d): In function `r128_cce_init': : undefined reference to `drm_ioremap' r128_cce.o(.text+0xa2f): In function `r128_cce_init': : undefined reference to `drm_ioremap' r128_cce.o(.text+0xa41): In function `r128_cce_init': : undefined reference to `drm_ioremap' r128_cce.o(.text+0xab3): In function `r128_cce_init': : undefined reference to `drm_ati_pcigart_init' r128_cce.o(.text+0xc08): In function `r128_cce_start': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0xc87): In function `r128_cce_start': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0xd13): In function `r128_cce_stop': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0xe14): In function `r128_cce_reset': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0xea1): In function `r128_cce_reset': : undefined reference to `drm_debug_flag' r128_cce.o(.text+0xedd): more undefined references to `drm_debug_flag' follow r128_drv.o(.text+0xc): In function `r128_probe': : undefined reference to `drm_probe' r128_drv.o(.text+0xca): In function `r128_attach': : undefined reference to `drm_attach' r128_drv.o(.data+0x48): undefined reference to `drm_devclass' r128_drv.o(.data+0x94): undefined reference to `drm_detach' r128_irq.o(.text+0x48): In function `r128_driver_irq_handler': : undefined reference to `drm_vbl_send_signals' r128_state.o(.text+0xb): In function `r128_emit_clip_rects': : undefined reference to `drm_debug_flag' r128_state.o(.text+0x2d0): In function `r128_cce_dispatch_flip': : undefined reference to `drm_debug_flag' r128_state.o(.text+0x523): In function `r128_cce_dispatch_indirect': : undefined reference to `drm_debug_flag' r128_state.o(.text+0x7e4): In function `r128_cce_clear': : undefined reference to `drm_debug_flag' r128_state.o(.text+0x906): In function `r128_cce_clear': : undefined reference to
Re: FreeBSD 6
On 7/30/05, Subhro [EMAIL PROTECTED] wrote: -O2 is known to create broken binaries. Reduce it to -O and recompile. Report back if it still does not work. -O2 is the default now for 6.x. I just added device drm and am rebuilding it to see if that works, will post the results when it's done ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: burncd - verify burn
[EMAIL PROTECTED] (Gary W. Swearingen) wrote: Brian Henning [EMAIL PROTECTED] writes: I would like to know a process to verify that I my cd burner has burned an ISO file correctly with burncd. I know I can take some precautions like checking the md5sum of the iso during a transfer from the Internet. I also read on the Internet that burncd does puts some extra padding at the end of the cd. I am not sure if that is true or not. Could someone tell me how to verify a cd burn? Here's a crummy script I just used to burn and verify a CD, but I've only tested it with the cdrecord setup. Older versions of it worked with burncd on older OS versions, but I can tell you that the reason I'm using cdrecord is that my manual efforts to do this with burncd on 5.4-RELEASE (and maybe 5.4-STABLE a couple weeks ago) failed, because I couldn't dd a CD burned with burncd. (IE, I couldn't sucessfully dd /dev/acd0, while I could dd /dev/cd0). (Search this for diff to find the verify. ISO images generally get an extra two blocks of something on the CD for run-out. See -isosize description of cdrecord manpage.) Not generally, only if you burn in TAO mode. BTW you can use readcd -c2scan to check the burning quality at a deeper level and there even is a patch out there to make reading c1 error pointers possible. Haven't tested it though. Fabian -- http://www.fabiankeil.de/ pgphNPDzWKRES.pgp Description: PGP signature
Re: scanimage -L doesn't work as normal user
On Sat, 30 Jul 2005, cpghost wrote: Then as ordinary user: $ sane-find-scanner -q found USB scanner (vendor=0x04b8 [EPSON], product=0x0121 [EPSON Scanner]) at libusb:/dev/usb0:/dev/ugen0 $ scanimage -L No scanners were identified. This is normally a problem with permissions. You could set them to 0666 in /etc/devfs.conf, and [re]start devfs with # /etc/rc.d/devfs start This was also what I thought, but I can't seem to get it right: In my devfs.conf I have: # Allow all users to use the scanner permugen0 0666 permusb0666 permusb0 0666 permusb1 0666 But when I plugin the scanner, ugen0 and ugen0.* has permissions crw-r--r-- sane-find-scanner doesn't show any scanners. Then I manually set the permissions on ugen0 to give write permissions to all, and sane-find-scanner finds the scanner, but scanimage still doesn't work. I would expect either both or none to work. To investigate furhter, I ran sane-find-scanner verbose: This is sane-find-scanner from sane-backends 1.0.15 searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/scanner0... failed to open (Invalid argument) ... searching for USB scanners: checking /dev/uscanner... failed to open (Invalid argument) checking /dev/uscanner0... failed to open (Invalid argument) ... device 0x04b8/0x0121 is not configured that is when there is no write permissions to ugen0, setting write permissions on ugen0 the last device line becomes found USB scanner (vendor=0x04b8 [EPSON], product=0x0121 [EPSON Scanner]) at libusb:/dev/usb0:/dev/ugen0 Unfortunately, running scanimage verbose doesn't show anything about probing for devices. Thanks, Erik GnuPG: http://www.locolomo.org/home/norgaard/norgaard.gpg.asc pub 1024D/11D11F9E 2003-08-15 Erik Norgaard [EMAIL PROTECTED] Key fingerprint = C394 81C4 D137 EEE5 39BE 82D5 3E6B FB3E 11D1 1F9E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: onboard ethernet support
On 7/30/05, Subhro [EMAIL PROTECTED] wrote: Nikolas Britton wrote: On 7/29/05, Antoine Solomon [EMAIL PROTECTED] wrote: Hello all, has anyone tried to get a marvell Yukon 88E8053 pci-e gigabit ethernet card working on fbsd 5.4? Is there any support for this? Not for 5.x, but I would try project evil and maybe it might be naively supported in 6.x http://www.pingwales.co.uk/tutorials/project-evil.html http://groups-beta.google.com/groups?q=group%3A*.freebsd.*+Marvell+Yukonqt_s=Search ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I bet something is wrong somewhere. I remember seeing that chipset on Asus K8V-SE Deluxe. And that worked for me without any troubles with the sk0 driver. However Nikolas has to say that its not supported. Anyone would please correct? spectra# man sk | grep -i marv Also supported is the Marvell Semiconductor 88E1000* gigabit PHY. I don't no for a fact that it's not supported, just an edu. guess... his card is a 88E8 btw ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with IPFilter/IPNAT
I am using IPFilter and IPNat on several FreeBSD boxes. They are mostly configured the same. Each box has two interfaces, public and internal, and acts as a router to the LAN which is 'behind' it. The LAN machines use the FreeBSD as the gateway, as well as a DNS server. I run cache-only config. The problem I have is that when, for any reason, the public link goes down, the machines on the LAN timeout when communicating. I can simulate this by simply pulling out the connection from the $ext_iface (assume this is ADSL or something like that) which is connected to the ISP upstream. I don't know if it is my NAT configuration causing this. Here is the /etc/ipnat.rules that I use: I'd want a situation where network communications within the LAN should not be affected when the circuit to the ISP is down since it is only used for web traffic and for the mail server on the FreeBSD router to send outbound e-mails, not local e-mails. cut # rl0 is the internal interface. rl1 is external interface. # These redirection rules are to force users on the LAN # to go through Squid cache. # First we let this machine access itself because there is a web server # on it. # Redirect direct web traffic to local web server. rdr rl0 192.168.100.31/32 port 80 - 192.168.100.31 port 80 tcp rdr rl0 192.168.100.31/32 port 443 - 192.168.100.31 port 443 tcp # Transparently redirect all outgoing web traffic through squid on # port 3128 rdr rl0 0.0.0.0/0 port 80 - 127.0.0.1 port 3128 # Also all SMTP Connections must go via localhost rdr rl0 0.0.0.0/0 port 25 - 127.0.0.1 port 25 # Now do NAT, but only for packets that are NOT local. map rl1 from 192.168.100.0/24 ! to 192.168.100.0/24 - 0/32 portmap tcp/udp auto map rl1 from 192.168.100.0/24 ! to 192.168.100.0/24 - 0/32 /cut What am I missing or doing wrong here??? -Wash http://www.netmeister.org/news/learn2quote.html -- +==+ |\ _,,,---,,_ | Odhiambo Washington[EMAIL PROTECTED] Zzz /,`.-'`'-. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +==+ Due to lack of disk space, this fortune database has been discontinued. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scanimage -L doesn't work as normal user
On Sat, Jul 30, 2005 at 12:14:25PM +0200, Erik Nørgaard wrote: On Sat, 30 Jul 2005, cpghost wrote: Then as ordinary user: $ sane-find-scanner -q found USB scanner (vendor=0x04b8 [EPSON], product=0x0121 [EPSON Scanner]) at libusb:/dev/usb0:/dev/ugen0 $ scanimage -L No scanners were identified. This is normally a problem with permissions. You could set them to 0666 in /etc/devfs.conf, and [re]start devfs with # /etc/rc.d/devfs start This was also what I thought, but I can't seem to get it right: In my devfs.conf I have: # Allow all users to use the scanner permugen0 0666 permusb0666 permusb0 0666 permusb1 0666 But when I plugin the scanner, ugen0 and ugen0.* has permissions crw-r--r-- [...] You have to use uscanner not ugenX You should read the Handbook section related to the image scanners: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html Marc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
openssl 0.9.8 with 5.4-stable
I know this may not be supported, but I was wondering if anyone was successful in installing the src of openssl 0.9.8 into the base install of 5.4 (overwriting the originals) ? thanks- -- J.D. Bronson Information Services Aurora Health Care - Milwaukee, Wisconsin Office: 414.978.8282 // Fax: 414.314.8787 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scanimage -L doesn't work as normal user
On Sat, 30 Jul 2005, Marc Fonvieille wrote: On Sat, Jul 30, 2005 at 12:14:25PM +0200, Erik Nørgaard wrote: On Sat, 30 Jul 2005, cpghost wrote: Then as ordinary user: $ sane-find-scanner -q found USB scanner (vendor=0x04b8 [EPSON], product=0x0121 [EPSON Scanner]) at libusb:/dev/usb0:/dev/ugen0 $ scanimage -L No scanners were identified. This is normally a problem with permissions. You could set them to 0666 in /etc/devfs.conf, and [re]start devfs with # /etc/rc.d/devfs start This was also what I thought, but I can't seem to get it right: In my devfs.conf I have: # Allow all users to use the scanner permugen0 0666 permusb0666 permusb0 0666 permusb1 0666 But when I plugin the scanner, ugen0 and ugen0.* has permissions crw-r--r-- [...] You have to use uscanner not ugenX You should read the Handbook section related to the image scanners: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html Thanks, I did read it. But if that is the problem, then please explain why I can scan as root but not as ordinary user? When I create a link uscanner0 - ugen0 that link gets permissions lrwxr-xr-x and I can't change those. I then run as normal user $ sane-find-scanner -q found USB scanner (UNKNOWN vendor and product) at device /dev/uscanner0 found USB scanner (vendor=0x04b8 [EPSON], product=0x0121 [EPSON Scanner]) at libusb:/dev/usb0:/dev/ugen0 So you see, it's not that I can't find the scanner. It is beyond me to understand why sane-find-scanner works as documented but scanimage don't. According to documentation this scanner uses the snapscan backend, in snapscan.conf I have: firmware /usr/local/etc/sane.d/Esfw41.bin # If not automatically found you may manually specify a device name. # For USB scanners also specify bus=usb, e.g. # /dev/usb/scanner0 bus=usb #/dev/uscanner0 bus=usb usb /dev/uscanner0 I have tried specifying the usb-scanner, both as written in the handbook and as suggested in the file and without any entries. No change. I don't think this file is read, because that would probably require that scanimage first identify the backend. Thanks, Erik GnuPG: http://www.locolomo.org/home/norgaard/norgaard.gpg.asc pub 1024D/11D11F9E 2003-08-15 Erik Norgaard [EMAIL PROTECTED] Key fingerprint = C394 81C4 D137 EEE5 39BE 82D5 3E6B FB3E 11D1 1F9E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Command Not Found error message
When running 'portsclean' from CRON, this message is sent to the root mailbox. In fact, there are several of them in the mailbox. I do not know what it means. /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:31: command not found: uname -rm uname(1) could be broken - cannot parse the output: make: not found ** Error occured reading /usr/local/etc/pkgtools.conf: uninitialized constant PkgConfig::OS_PLATFORM When I run the 'uname -rm' command from the command line, it produces this output. 5.4-RELEASE I386 -- Gerard E. Seibert [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature
Re: scanimage -L doesn't work as normal user
On Sat, Jul 30, 2005 at 01:41:20PM +0200, Erik Nørgaard wrote: Thanks, I did read it. But if that is the problem, then please explain why I can scan as root but not as ordinary user? Wrong perms on ugen0, read carefully: 7.6.4 Allowing Scanner Access to Other Users if you want ugen0 appears with the right permissions once you plug your scanner. The current devfs scheme you use (Cf. your previous mail) should work if you boot directly with your scanner plugged and not if you plug it later. When I create a link uscanner0 - ugen0 that link gets permissions lrwxr-xr-x and I can't change those. I then run as normal user $ sane-find-scanner -q found USB scanner (UNKNOWN vendor and product) at device /dev/uscanner0 found USB scanner (vendor=0x04b8 [EPSON], product=0x0121 [EPSON Scanner]) at libusb:/dev/usb0:/dev/ugen0 [...] This is a problem, a USB scanner under FreeBSD should use uscanner(8) driver nothing else. I assume your scanner is not seen by uscanner(8), i.e. not supported or just not defined in uscanner.c Try to add an entry for your scanner in uscanner.c, rebuild uscanner.ko, etc. and retry. Marc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Active Directory Server
Has anyone any experience trying to make FreeBSD an Active Directory
Server? From my research and experiementation, I am under the impression
that it is possible, but I have yet to come up with any articles where it
has actual been done fully.
At the minute I have samba and ldap setup, the active directory dns
entries in (_ldap._tcp.dc._msdcs.{domain}). I am getting an error message
when trying to join my XP client to the domain - I think it is to do with
the ldap server. Any clues or points in the right direction would be
helpful - I am getting the impression that this may be a big project, if
it is even achieveable.
Cheers,
Martin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Command Not Found error message
On 7/30/05, Gerard Seibert [EMAIL PROTECTED] wrote:
When running 'portsclean' from CRON, this message is sent to the root
mailbox. In fact, there are several of them in the mailbox. I do not
know what it means.
/usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:31: command not found: uname -rm
uname(1) could be broken - cannot parse the output:
make: not found
** Error occured reading /usr/local/etc/pkgtools.conf:
uninitialized constant PkgConfig::OS_PLATFORM
When I run the 'uname -rm' command from the command line, it produces
this output.
5.4-RELEASE I386
--
Gerard E. Seibert
[EMAIL PROTECTED]
You might need to define your path in your crontab file with something
like this:
PATH=${PATH}:/usr/bin
(because uname is in /usr/bin)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
bsdlabel question..
# /dev/da0s1: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 2234 sectors/unit: 35889147 rpm: 15000 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 104857604.2BSD 2048 16384 8 b: 2097152 10485764.2BSD 2048 16384 28552 c: 358891470unused0 0 # raw part, don't edit d: 16777216 31457284.2BSD 2048 16384 28552 e: 8388608 199229444.2BSD 2048 16384 28552 f: 2097152 283115524.2BSD 2048 16384 28552 g: 2097152 304087044.2BSD 2048 16384 28552 h: 3383291 325058564.2BSD 2048 16384 28552 ...This is on a FreeBSD 5.4 machine with a Fuji 15K 18GB scsi drive. Does this disklabel look right? (28553 bps/cpg?) thanks! -- J.D. Bronson Information Services Aurora Health Care - Milwaukee, Wisconsin Office: 414.978.8282 // Fax: 414.314.8787 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with IPFilter/IPNAT
On Sat, Jul 30, 2005 at 01:41:52PM +0300, Odhiambo Washington wrote: I am using IPFilter and IPNat on several FreeBSD boxes. They are mostly configured the same. Each box has two interfaces, public and internal, and acts as a router to the LAN which is 'behind' it. The LAN machines use the FreeBSD as the gateway, as well as a DNS server. I run cache-only config. The problem I have is that when, for any reason, the public link goes down, the machines on the LAN timeout when communicating. It sound like there tying to lookup hostnames via DNS or something like this. Are you able to ping them with there ip addresses? Are you able to ping them with there host names? -- Alex Please copy the original recipients, otherwise I may not read your reply. Howto's based on my ppersonal use, including information about setting up a firewall and creating traffic graphs with MRTG http://www.kruijff.org/alex/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scanimage -L doesn't work as normal user
On Sat, 30 Jul 2005, Marc Fonvieille wrote: On Sat, Jul 30, 2005 at 01:41:20PM +0200, Erik Nørgaard wrote: Wrong perms on ugen0, read carefully: 7.6.4 Allowing Scanner Access to Other Users if you want ugen0 appears with the right permissions once you plug your scanner. The current devfs scheme you use (Cf. your previous mail) should work if you boot directly with your scanner plugged and not if you plug it later. According to the man-pages, this should be solved by adding the folowing rules to /etc/devfs.rules: # Allow any user to access uscanner and ugen devices rw add path 'usb0' mode 0666 add path 'ugen*' mode 0666 add path 'uscanner*' mode 0666 I restarted devfs but the devices were created with the wrong permissions when I plugged in the scanner? If I restart devfs after plugging in the scanner permissions are corrected. But I think this is rather annoying - is this intended? no problem report has been filed on this issue... $ sane-find-scanner -q found USB scanner (UNKNOWN vendor and product) at device /dev/uscanner0 found USB scanner (vendor=0x04b8 [EPSON], product=0x0121 [EPSON Scanner]) at libusb:/dev/usb0:/dev/ugen0 [...] This is a problem, a USB scanner under FreeBSD should use uscanner(8) driver nothing else. I assume your scanner is not seen by uscanner(8), i.e. not supported or just not defined in uscanner.c Try to add an entry for your scanner in uscanner.c, rebuild uscanner.ko, etc. and retry. OK, I will update usbdevs and uscanner.c and submit a patch if this makes it work. Yet, I still can't understand howcome I can successfully scan an image as root if scanning is only supposed to work with the uscanner device. Thanks, Erik GnuPG: http://www.locolomo.org/home/norgaard/norgaard.gpg.asc pub 1024D/11D11F9E 2003-08-15 Erik Norgaard [EMAIL PROTECTED] Key fingerprint = C394 81C4 D137 EEE5 39BE 82D5 3E6B FB3E 11D1 1F9E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scanimage -L doesn't work as normal user
On Sat, Jul 30, 2005 at 03:42:54PM +0200, Erik Nørgaard wrote: On Sat, 30 Jul 2005, Marc Fonvieille wrote: On Sat, Jul 30, 2005 at 01:41:20PM +0200, Erik Nørgaard wrote: Wrong perms on ugen0, read carefully: 7.6.4 Allowing Scanner Access to Other Users if you want ugen0 appears with the right permissions once you plug your scanner. The current devfs scheme you use (Cf. your previous mail) should work if you boot directly with your scanner plugged and not if you plug it later. According to the man-pages, this should be solved by adding the folowing rules to /etc/devfs.rules: # Allow any user to access uscanner and ugen devices rw add path 'usb0' mode 0666 add path 'ugen*' mode 0666 add path 'uscanner*' mode 0666 you should add a ruleset line before your lines. I restarted devfs but the devices were created with the wrong permissions when I plugged in the scanner? I don't understand the ? If I restart devfs after plugging in the scanner permissions are corrected. But I think this is rather annoying - is this intended? no problem report has been filed on this issue... [...] I think it's a ruleset issue as I said above. Another thing devfs.rules is for pluggable devices, devfs.conf for devices present at boot time. Marc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using a hard drive without partitions
Nikolas Britton [EMAIL PROTECTED] writes: Drive: Dangerously dedicated /dev/da0s1 newfs -O2 -U I think you're using dangerously dedicated wrongly. A DD disk is one which has no standard partition table in the MBR; the disklabel sectors (16) start at sector 0 (or with your no-secondary-partitions- either method, your filesystem would start there (newfs /dev/da0)). You've got a standard partition table with the s1 entry in use, which is not dangerous. The FAQ has an entry on DD disks. I can't say much about your main question; I've never heard of doing it. It sounds less dangerous than putting a FS in a file, like we do with ISO filesystems all the time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using a hard drive without partitions
On Jul 30, 2005, at 2:26 AM, Nikolas Britton wrote: What are the ramifications, good or bad, of not using partitions on a FreeBSD disk?. My understanding is that if you use partitions in a standard way, other operating systems that may be or in the future be on the system in question will not wipe out your FreeBSD installation on the dangerously dedicated disk. There is nothing inherent wrong with DD but it is more dangerous if other OSes may be involved. I have used both sorts of layouts and have never had any problems, yet again, my computers were servers that would never have another OS anywhere near them... Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
network info
What command can display all the network parameters assigned from dhcp, such DNS? I have looked at ifconfig and netstat but unless I missed a switch I do not see them as correct choices. Basically the equiv of ipconfig /all in Windows? Thanks Sean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: your data
[EMAIL PROTECTED] wrote:Please confirm the document. ** ** WARNING: WinProxy has detected a virus in file attached to this e-mail message! The attachment has been automatically removed to protect your network. WinProxy Administrator: [EMAIL PROTECTED] 07/31/05 02:35:22 WinProxy (Version 5.1 R1e (5.0.50.11)) - http://www.Ositis.com/ Antivirus Vendor: Panda Software Scan Engine Version: 4.7.0.2_4.1.6.408 Pattern File Version: 3.102014 (Timestamp: 2005/07/29 12:08:44) Machine name: MEMBERSERVER Machine IP address: 192.168.184.1 Server: 67.28.113.19 Client: 192.168.1.67 Protocol: SMTP Virus: W32/Netsky.P.worm found! Attachment: data.zip ** ** __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
JNC MP3 Player Synchronize cache failed
Hello, I am not able to use may SylverCrest mp3 player. When I connect the player I have this message on the console : da0 at umass-sim0 bus 0 target 0 lun 0 da0: JNC MP3 Player 1.00 Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 499MB (1023713 512 byte sectors: 64H 32S/T 499C) umass0: at uhub2 port 1 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x39, scsi status == 0x0 (da0:umass-sim0:0:0:0): removing device entry after removing the device and after many minutes a page fault in kernel mode (trap 12) : fault code = supervisor read, page not present instruction pointer = 0x8:0xc0a27883 ... panic: page fault. This is the same with 4.11, 5.4, 6 and 7 release. I found nothing on the net. Many thanks for a patch, a fix or a workaround. -- (° Dhénin Jean-Jacques / ) [EMAIL PROTECTED] ^^ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is Kern/Pr 58045 really fixed?
Ted Mittelstaedt [EMAIL PROTECTED] writes: One reason bugs get closed is that the submitters don't respond to requests from the developers for further info. A status of closed should not be interpreted to mean any bug was corrected. In this case, it *does* mean that the patch from the PR was committed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6
On Sat, Jul 30, 2005 at 02:23:54PM +0530, Subhro wrote: -O2 is known to create broken binaries. Reduce it to -O and recompile. Report back if it still does not work. No, only on 4.x and below. Kris pgp35Y2CiNXRi.pgp Description: PGP signature
Re: Acess 127.0.0.1 from FreeBSD jail
At 10:35 PM 7/29/2005, Chad Leigh -- Shire.Net LLC wrote: On Jul 29, 2005, at 11:25 PM, Chatchawan Wongsiriprasert wrote: Hi, I am now using chroot apache+php, and want to move to more secure FreeBSD jail. After read the FreeBSD handbook, I have been successfully created a jailed apache+php on my test server but there is a litle problem that need to be solved before I put it on my real server. I run mysql-server on this server and make it listen only to 127.0.0.1 (--bind-address option). How can I access mysql-server on this server from the jail without (1) make mysql-server listen to the real ip (I don't want to open another door to my server -- firewall can be employ but this add another complexity to my setup) Create a separate jail on the system and put mysql in that. Make the address of this mysql jail be 192.168.1.1 or something like that. The apache jail will be able to reach it but the outside won't. You should still have a firewall of some sort. or (2) using unix socket (a lot of code to change and test -- most are develop by another people). Using the socket option is better as it probably also performs better (I don't know this for sure -- am just guessing) Using the sockets in mysql is faster. The only code you should need to change is the code that open's the connection to the database, everything else will work just fine. -Glenn Chad Regards, Chatchawan Wongsiriprasert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: openssl 0.9.8 with 5.4-stable
On Sat, Jul 30, 2005 at 06:38:18AM -0500, J.D. Bronson wrote: I know this may not be supported, but I was wondering if anyone was successful in installing the src of openssl 0.9.8 into the base install of 5.4 (overwriting the originals) ? Use the port, which has such a knob. Kris pgpH9pzVHAO9C.pgp Description: PGP signature
Re: bsdlabel question..
At 05:59 AM 7/30/2005, J.D. Bronson wrote: # /dev/da0s1: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 2234 sectors/unit: 35889147 rpm: 15000 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 104857604.2BSD 2048 16384 8 b: 2097152 10485764.2BSD 2048 16384 28552 c: 358891470unused0 0 # raw part, don't edit d: 16777216 31457284.2BSD 2048 16384 28552 e: 8388608 199229444.2BSD 2048 16384 28552 f: 2097152 283115524.2BSD 2048 16384 28552 g: 2097152 304087044.2BSD 2048 16384 28552 h: 3383291 325058564.2BSD 2048 16384 28552 ...This is on a FreeBSD 5.4 machine with a Fuji 15K 18GB scsi drive. Does this disklabel look right? (28553 bps/cpg?) Yes, it's correct. The number that's liset in the bps/cpg column is not what it appears to be when you create a filesystem using newfs in 5.x. If I recall correctly, it's actually the number of frags in a cyliner group. -Glenn thanks! -- J.D. Bronson Information Services Aurora Health Care - Milwaukee, Wisconsin Office: 414.978.8282 // Fax: 414.314.8787 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: network info
At 08:08 AM 7/30/2005, Sean wrote: What command can display all the network parameters assigned from dhcp, such DNS? I have looked at ifconfig and netstat but unless I missed a switch I do not see them as correct choices. Not exactly one command, but you could do ifconfig cat /etc/resolv.conf If it's something you need to do frequently, you could make an alias for it, or a shell script. -Glenn Basically the equiv of ipconfig /all in Windows? Thanks Sean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: network info
Glenn Dawson wrote: At 08:08 AM 7/30/2005, Sean wrote: What command can display all the network parameters assigned from dhcp, such DNS? I have looked at ifconfig and netstat but unless I missed a switch I do not see them as correct choices. Not exactly one command, but you could do ifconfig cat /etc/resolv.conf Toss an extra sockstat -4 for even more info. If it's something you need to do frequently, you could make an alias for it, or a shell script. -Glenn Basically the equiv of ipconfig /all in Windows? Thanks Sean -- Best regards, Chris History repeats itself. that's one of the things wrong with history. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel question..
At 05:59 AM 7/30/2005, J.D. Bronson wrote:
# /dev/da0s1:
type: SCSI
disk: da0s1
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 2234
sectors/unit: 35889147
rpm: 15000
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
#size offsetfstype [fsize bsize bps/cpg]
a: 104857604.2BSD 2048 16384 8
b: 2097152 10485764.2BSD 2048 16384 28552
c: 358891470unused0 0 # raw part,
don't edit
d: 16777216 31457284.2BSD 2048 16384 28552
e: 8388608 199229444.2BSD 2048 16384 28552
f: 2097152 283115524.2BSD 2048 16384 28552
g: 2097152 304087044.2BSD 2048 16384 28552
h: 3383291 325058564.2BSD 2048 16384 28552
...This is on a FreeBSD 5.4 machine with a Fuji 15K 18GB scsi drive.
Does this disklabel look right? (28553 bps/cpg?)
I just checked the source for newfs, and my previous reply was
correct. Here's the relevant code that put's that number in the label:
if (pp != NULL) {
pp-p_fstype = FS_BSDFFS;
pp-p_fsize = sblock.fs_fsize;
pp-p_frag = sblock.fs_frag;
pp-p_cpg = sblock.fs_fpg;
}
The last line is the one that inserts that number. sblock.fs_fpg is the
number of frags per cylinder grounp.
-Glenn
thanks!
--
J.D. Bronson
Information Services
Aurora Health Care - Milwaukee, Wisconsin
Office: 414.978.8282 // Fax: 414.314.8787
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using a hard drive without partitions
On 7/30/05, Chad Leigh -- Shire.Net LLC [EMAIL PROTECTED] wrote: On Jul 30, 2005, at 2:26 AM, Nikolas Britton wrote: What are the ramifications, good or bad, of not using partitions on a FreeBSD disk?. My understanding is that if you use partitions in a standard way, other operating systems that may be or in the future be on the system in question will not wipe out your FreeBSD installation on the Don't you mean slice? In BSD land slice = IBM PC partition and partitions, in BSD, are divisions of a slice. Yes it's confusing dangerously dedicated disk. There is nothing inherent wrong with DD but it is more dangerous if other OSes may be involved. I have used both sorts of layouts and have never had any problems, yet again, my computers were servers that would never have another OS anywhere near them... Correct about DD... This array will NEVER be used with another OS and It will NEVER be booted from The disk array will never show it's self in DOS because it needs special drivers. In FreeBSD I want it to show up as one big disk and just mount it as /data or something to that effect. The equivalent in MS-DOS / PC World to what I want to do is make a primary partition that spans the whole drive. In BSD land this would be da0s1c but from what I've read the c partition (BSD partition) is reserved and can't be used. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
correct syntax for openssl 0.9.8 in port
I update my port tree on 5.4 to the latest and I am trying to figure out what steps I need to build openssl 0.9.8 in /usr/ports/security/openssl and end up overwriting any base files. This question comes up often, perhaps a comment can be put into the makefile? I have tried all the ideas on the archives and either it wont build or it keeps trying to build 0.9.7g !!! *ANY* advice will be greatly appreciated. I am able to compile the src code cleanly, but that install will place files in their own spot and obviously not overwrite base files. thanks! -- J.D. Bronson Information Services Aurora Health Care - Milwaukee, Wisconsin Office: 414.978.8282 // Fax: 414.314.8787 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using a hard drive without partitions
Hi, On Sat, Jul 30, 2005 at 12:38:57PM -0500, Nikolas Britton wrote: On 7/30/05, Chad Leigh -- Shire.Net LLC [EMAIL PROTECTED] wrote: On Jul 30, 2005, at 2:26 AM, Nikolas Britton wrote: What are the ramifications, good or bad, of not using partitions on a FreeBSD disk?. As far as my understanding goes, it is an artifact of ye olde days, and should not be used again. There are ramifications for 'tasting' the label on the disk etc, however I do not know what the impact is -- it might just work, or it might not. This array will NEVER be used with another OS and It will NEVER be booted from The disk array will never show it's self in DOS because it needs special drivers. In FreeBSD I want it to show up as one big disk and just mount it as /data or something to that effect. The equivalent in MS-DOS / PC World to what I want to do is make a primary partition that spans the whole drive. In BSD land this would be da0s1c but from what I've read the c partition (BSD partition) is reserved and can't be used. So just create one primary slice using fdisk, and then label the disk with disklabel -e and copy paste the 'c' line to an 'a' line. Then use da0s1a for newfs mount. The amount of space wasted is negligible nowadays (~10mb or so I guess) and it may just save you in the future if/when support for DD mode goes away (not that I know it will, but you never know...). HTH, --Stijn -- Apparently, 1 in 5 people in the world are Chinese. And there are 5 people in my family, so it must be one of them. It's either my mum or my dad.. or maybe my older brother John. Or my younger brother Ho-Cha-Chu. But I'm pretty sure it's John. pgpCWTaKEC5PU.pgp Description: PGP signature
Re: Growisofs seg faults with DVD-RAM. Anybody else seen this?
On Sat, Jul 30, 2005 at 03:54:25PM +0930, Greg 'groggy' Lehey wrote:
On Friday, 29 July 2005 at 22:50:13 -0700, Carl Delsey wrote:
I'm wondering if anybody else has seen this problem, and if you've
found some other workaround for it? Or alternatively, you still have
the problem and my patch would be useful to you. :-)
Is this a workaround or a fix? The latter is obviously preferable.
Also, does this only affect FreeBSD, or is it general? In the former
case, contact the maintainer (mail address in the Makefile); in the
latter, contact the project.
It's a fix ... just not as elegant as I would like. Looking through the
code some more, it looks like it's a general problem. I'll try to get ahold
of the maintainer and get this fixed in the distribution.
In the meantime, if anybody needs a solution now, I'm including the patch
here.
patch
--- growisofs.c Tue Aug 24 16:02:29 2004
+++ growisofs.c Sat Jul 30 10:35:45 2005
@@ -2043,7 +2044,9 @@
fcntl ((fd),F_SETFD,f|FD_CLOEXEC); } while (0)
CLOSEONEXEC(in_fd);
CLOSEONEXEC(out_fd);
-CLOSEONEXEC(ioctl_fd);
+if ((ioctl_handle) (ioctl_handle != INVALID_HANDLE)) /*the fd might
already have been closed*/
+{ CLOSEONEXEC(ioctl_fd);
+}
#undef CLOSEONEXEC
if (!dry_run (poor_man || next_session==0)) /* unmount media */
/patch
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
any backup utilities for ACLs?
I've enabled ACL support on a 5.4-RELEASE system and have no problems creating and modifying ACLs. However, I can't seem to find a backup program that will actually restore the ACLs. I've tried bsdtar, pax, and star. Has anyone had any success in backing up and restoring ACLs? If so, what was the magic incantation? Dru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SOLVED: scanimage -L doesn't work as normal user
Hi,
OK, I have solved the problem, as was originally assumed it boils
down to getting the permissions right.
To make Epson 2480 work, there is no need to patch the uscanner.c
or usbdevs files and rebuild that module. I did make that work
though - sort of, now, sane-find-scanner finds an unidentified
device on uscanner0, but scanimage correctly idenfies the scanner.
This is what to do: In /usr/src/sys/dev/usb edit the files usbdevs
and uscanner.c, in usbdevs add a line:
product EPSON 2480 0x0121 Perfection 2480 scanner
and in uscanner.c add the line
{{ USB_VENDOR_EPSON, USB_PRODUCT_EPSON_2480 }, 0 },
after the last EPSON scanner.
I don't know if there is any benefit from using the uscanner
device other than the ability to set permissions for the scanner
only.
Here's the trick:
Create a file /etc/devfs.rules with the following:
[devfsrules=10]
# Allow any user to access usb devices: uscanner and ugen
add path 'usb0' mode 0666
add path 'usb1' mode 0666
add path 'ugen*' mode 0666
add path 'uscanner*' mode 0666
The last line can be omitted if you don't use the uscanner device.
I think it is better to let others access rw the scanner device
than to add users to the operator group.
Alternatively, one can create a separate group eg scanner, then
append group scanner to each rule - this might be the best
instead of giving rw access to arbitrary ugen devices.
In /etc/rc.conf add the line:
devfs_system_ruleset=devfsrules
Then restart devfs. You can unplug and plugin the scanner as
much as you like.
Cheers, Erik
GnuPG: http://www.locolomo.org/home/norgaard/norgaard.gpg.asc
pub 1024D/11D11F9E 2003-08-15 Erik Norgaard [EMAIL PROTECTED]
Key fingerprint = C394 81C4 D137 EEE5 39BE 82D5 3E6B FB3E 11D1 1F9E
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: correct syntax for openssl 0.9.8 in port
On Sat, Jul 30, 2005 at 12:46:37PM -0500, J.D. Bronson wrote: I update my port tree on 5.4 to the latest and I am trying to figure out what steps I need to build openssl 0.9.8 in /usr/ports/security/openssl and end up overwriting any base files. This question comes up often, perhaps a comment can be put into the makefile? I have tried all the ideas on the archives and either it wont build or it keeps trying to build 0.9.7g !!! *ANY* advice will be greatly appreciated. I am able to compile the src code cleanly, but that install will place files in their own spot and obviously not overwrite base files. Read the makefile for the appropriate variables to set. Kris pgpQBPSn2pjou.pgp Description: PGP signature
Re: Using a hard drive without partitions
On 7/30/05, Gary W. Swearingen [EMAIL PROTECTED] wrote: Nikolas Britton [EMAIL PROTECTED] writes: Drive: Dangerously dedicated /dev/da0s1 newfs -O2 -U I think you're using dangerously dedicated wrongly. A DD disk is one which has no standard partition table in the MBR; the disklabel sectors (16) start at sector 0 (or with your no-secondary-partitions- either method, your filesystem would start there (newfs /dev/da0)). But in FreeBSD your disk needs a slice otherwise it's not compatable with fdisk / bsdlabel / growfs... I think. You've got a standard partition table with the s1 entry in use, which is not dangerous. The FAQ has an entry on DD disks. But it is dangerous because it starts at sector 0. I've read that FAQ as well as greg's book, Lucas's book, unix power tools, the man pages, handbook, etc. I will reread them again. I can't say much about your main question; I've never heard of doing it. It sounds less dangerous than putting a FS in a file, like we do with ISO filesystems all the time. Yea that's the problem ;-). I've never heard of doing it like that too but it does work. I'm going to be working on this server today and I'll post some of the details of fdisk, bsdlabel, etc. to see if I can help clarify things. Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: correct syntax for openssl 0.9.8 in port
At 12:57 PM 7/30/2005, Kris Kennaway wrote: On Sat, Jul 30, 2005 at 12:46:37PM -0500, J.D. Bronson wrote: I update my port tree on 5.4 to the latest and I am trying to figure out what steps I need to build openssl 0.9.8 in /usr/ports/security/openssl and end up overwriting any base files. This question comes up often, perhaps a comment can be put into the makefile? I have tried all the ideas on the archives and either it wont build or it keeps trying to build 0.9.7g !!! *ANY* advice will be greatly appreciated. I am able to compile the src code cleanly, but that install will place files in their own spot and obviously not overwrite base files. Read the makefile for the appropriate variables to set. Kris This is obviously my issue. I cannot figure out what variables to set. What I think it should be, it whines about. Can someone at least POST what we should use so this will at least be in the archives once and for all? thanks! -- J.D. Bronson Information Services Aurora Health Care - Milwaukee, Wisconsin Office: 414.978.8282 // Fax: 414.314.8787 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Growisofs seg faults with DVD-RAM. Anybody else seen this?
Greg 'groggy' Lehey wrote:
On Friday, 29 July 2005 at 22:50:13 -0700, Carl Delsey wrote:
I was trying to use growisofs to write to a DVD-RAM and it kept
seg faulting. It worked fine with a DVD-R.
I tracked the problem down to place in the code where growisofs
tries to perform an operation on a file handle it has already
closed.
I've implemented a workaround already. The problem is, that by my
reckoning, this should affect anybody who is trying to use a DVD-RAM
(not DVD+RW) with FreeBSD, but I haven't found any references to the
problem on the net.
My guess is that DVD-RAM isn't popular enough, and that people who
have had problems with it haven't had the understanding to track the
bug down.
dvd+rw-tools doesn't support -RAM as well as other formats, in part because the
{+,-}R(W) formats are much more common, in part because there are some pretty
serious quirks in the older drives, but improvements would be welcome.
I'm wondering if anybody else has seen this problem, and if you've
found some other workaround for it? Or alternatively, you still have
the problem and my patch would be useful to you. :-)
Is this a workaround or a fix? The latter is obviously preferable.
Also, does this only affect FreeBSD, or is it general? In the former
case, contact the maintainer (mail address in the Makefile); in the
latter, contact the project.
I'd be happy to review or test them first if you'd like, but any changes of
this sort really ought to go upstream to Andy Polyakov [EMAIL PROTECTED]
or to the cdwrite mailing list at cdwrite@other.debian.org.
--
-Chuck
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient and wpa_supplicant
Sam Leffler wrote:
Sam Leffler wrote:
Brooks fixed a bunch of bugs in dhclient and I just committed an
important fix to wpa_supplicant to work right when wireless cards are
ejected (previously it would loop).
I also tested that dhclient does the right thing for roaming between
ap's--switching causes dhclient to immediately collect a new lease.
I just ran tests with wpa_supplicant and found that it does appear to
handle open ap's properly.
Everything except the wpa_supplicant changes have been MFC'd to
RELENG_6 for the 6.0RC2 build that's going to happen soon (I'm hoping
to get re to approve the wpa_supplicant changes).
FWIW I just MFC'd the wpa_supplicant fix.
So the question is what are the outstanding issues with dhclient and
wpa_supplicant? I'm mostly concerned with wireless devices but feel
free to talk about wired interfaces too. If something doesn't work
right please try to give steps to reproduce the problem. Otherwise
please provide detailed info include ifconfig output. Remember that
dhclient logs info to /var/log/messages and you should also see link
state change msgs there too.
s/6.0RC2/6.0BETA2/.
Sam
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Hello,
I am very interested in getting wpa_supplicant dhclient to work.
Presently it does not work for me the way I would hope it would.
I would think that if it were setup properly on my machine I could turn
the machine on at home, and have it associate with my AP and then
acquire a lease. Then I could shut it down... go to the office... turn
it on and then have it associate with the AP there and acquire a lease.
However it does not seem to do this. It seems to only want to associate
with the last AP it ever associated with. I then have to down the
interface and manually ifconfig it.
I am fairly sure I do not have things setup properly, since others have
had much better results. Can you please point me to the most current
docs or a How To to push me in the right direction.
I have RELENG_6 as of last night. I have appended some conf files to
the bottom for your review.
Thanks,
rc.conf contains
===
network_interfaces=lo0 bfe0 ath0
ifconfig_ath0=WPA DHCP
ifconfig_bfe0=DHCP
dhclient.conf contains
===
interface ath0 {
#send option host-name myhost;
#send option domain-name nxdomain.org;
send dhcp-client-identifier myhost;
media
### Home
ssid home_ssid mode 11b channel 11 wepmode on weptxkey 1 wepkey
0xhome_wepkey,
### Office
ssid office_ssid mode 11b channel 6 wepmode on weptxkey 1 wepkey
0xoffice_wepkey;
request subnet-mask, broadcast-address, routers, domain-name-servers,
domain-name;
}
wpa_supplicant.conf
=
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
# Home Network
network={
ssid=home_ssid
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=home_wepkey
}
# Office Network
network={
ssid=office_ssid
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=office_wepkey
}
--
Regards,
Eric
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Growisofs seg faults with DVD-RAM. Anybody else seen this?
On Sat, Jul 30, 2005 at 02:16:17PM -0400, Chuck Swiger wrote: I'd be happy to review or test them first if you'd like, but any changes of this sort really ought to go upstream to Andy Polyakov [EMAIL PROTECTED] or to the cdwrite mailing list at cdwrite@other.debian.org. Thanks. I've just emailed Andy about this. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient and wpa_supplicant
Eric Schuele wrote:
Sam Leffler wrote:
Sam Leffler wrote:
Brooks fixed a bunch of bugs in dhclient and I just committed an
important fix to wpa_supplicant to work right when wireless cards are
ejected (previously it would loop).
I also tested that dhclient does the right thing for roaming between
ap's--switching causes dhclient to immediately collect a new lease.
I just ran tests with wpa_supplicant and found that it does appear to
handle open ap's properly.
Everything except the wpa_supplicant changes have been MFC'd to
RELENG_6 for the 6.0RC2 build that's going to happen soon (I'm hoping
to get re to approve the wpa_supplicant changes).
FWIW I just MFC'd the wpa_supplicant fix.
So the question is what are the outstanding issues with dhclient and
wpa_supplicant? I'm mostly concerned with wireless devices but feel
free to talk about wired interfaces too. If something doesn't work
right please try to give steps to reproduce the problem. Otherwise
please provide detailed info include ifconfig output. Remember that
dhclient logs info to /var/log/messages and you should also see link
state change msgs there too.
s/6.0RC2/6.0BETA2/.
Sam
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
[EMAIL PROTECTED]
Hello,
I am very interested in getting wpa_supplicant dhclient to work.
Presently it does not work for me the way I would hope it would.
I would think that if it were setup properly on my machine I could turn
the machine on at home, and have it associate with my AP and then
acquire a lease. Then I could shut it down... go to the office... turn
it on and then have it associate with the AP there and acquire a lease.
However it does not seem to do this. It seems to only want to associate
with the last AP it ever associated with. I then have to down the
interface and manually ifconfig it.
I am fairly sure I do not have things setup properly, since others have
had much better results. Can you please point me to the most current
docs or a How To to push me in the right direction.
I have RELENG_6 as of last night. I have appended some conf files to
the bottom for your review.
Thanks,
rc.conf contains
===
network_interfaces=lo0 bfe0 ath0
ifconfig_ath0=WPA DHCP
ifconfig_bfe0=DHCP
dhclient.conf contains
===
interface ath0 {
#send option host-name myhost;
#send option domain-name nxdomain.org;
send dhcp-client-identifier myhost;
media
### Home
ssid home_ssid mode 11b channel 11 wepmode on weptxkey 1 wepkey
0xhome_wepkey,
### Office
ssid office_ssid mode 11b channel 6 wepmode on weptxkey 1 wepkey
0xoffice_wepkey;
request subnet-mask, broadcast-address, routers, domain-name-servers,
domain-name;
}
Do not use media statements to setup wireless parameters; this does not
work. You need to run wpa_supplicant and let it identify the network
and setup the key parameters.
wpa_supplicant.conf
=
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
# Home Network
network={
ssid=home_ssid
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=home_wepkey
}
# Office Network
network={
ssid=office_ssid
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=office_wepkey
}
Not sure you need scan_ssid set, I'd leave it out.
If you have problems try disabling auto-startup of ath0 and run
wpa_supplicant by hand with the -d flag to see what it's doing. Once
that's going then enable startup in rc.conf. If you continue to have
problems provide the output wpa_supplicant -d -i ath0 -c
/etc/wpa_supplicant.conf (or similar) when you have trouble. There is
also a pending issue with locating some ap's that are setup to hide
their ssid. If one of the ap's is configured in this way contact me
directly--I've been trying to collect the info I need to identify what's
going on.
Sam
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Reading the volume-id/label of a cd/dvd ?
Warren Block [EMAIL PROTECTED] wrote: On Wed, 27 Jul 2005, FreeBsdBeni wrote: Is there an easy way to get to know the volume id or disclabel of a cd or dvd ? Mounting the cd/dvd just gives me the contents of the disc, but not its name. In k3b one can ask the info about a disc and get all the info about the inserted cd/dvd (disc type, tracks, sessions,...). But how do i get that info without k3b ? Is there an easy way/solution ? cdrecord can get some info from a CD; see the -toc and -atip options. To show the volume id one can use isoinfo, it's part of cdrtools as well. Fabian -- http://www.fabiankeil.de/ pgpcfJjtbfa6B.pgp Description: PGP signature
sunbird
Hmmm, it did not get through to the list it seems, try again. * Anyone successfully built Sunbird on FreeBSD4 or 5? I thought I'd start off trying but was sort of baffled by all the ./configure options... Thanks, Per olof ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sunbird
On Sat, 2005-07-30 at 20:41 +0200, Per olof Ljungmark wrote: Hmmm, it did not get through to the list it seems, try again. * Anyone successfully built Sunbird on FreeBSD4 or 5? I thought I'd start off trying but was sort of baffled by all the ./configure options... We have an experimental port of it at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/ports. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
bind CTRL-ALT+DEL action
Is it possible to bind any action to combinated keys such as CTRL+ALT+DEL? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with IPFilter/IPNAT
* On 30/07/05 15:20 +0200, Alex de Kruijff wrote: On Sat, Jul 30, 2005 at 01:41:52PM +0300, Odhiambo Washington wrote: I am using IPFilter and IPNat on several FreeBSD boxes. They are mostly configured the same. Each box has two interfaces, public and internal, and acts as a router to the LAN which is 'behind' it. The LAN machines use the FreeBSD as the gateway, as well as a DNS server. I run cache-only config. The problem I have is that when, for any reason, the public link goes down, the machines on the LAN timeout when communicating. It sound like there tying to lookup hostnames via DNS or something like this. Are you able to ping them with there ip addresses? Are you able to ping them with there host names? Ping by IP addresses works. However, I have not tried ping by hostname since I have not setup any DNS or host entries for the machines on the LAN. I did not think this is a REQUIREMENTS at all. Is it?? So is this a DNS problem that I can resolve by just using /etc/hosts entries, maybe? Does my ipnat rules look okay? -Wash http://www.netmeister.org/news/learn2quote.html -- +==+ |\ _,,,---,,_ | Odhiambo Washington[EMAIL PROTECTED] Zzz /,`.-'`'-. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +==+ It is said that the lonely eagle flies to the mountain peaks while the lowly ant crawls the ground, but cannot the soul of the ant soar as high as the eagle? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SOLVED: scanimage -L doesn't work as normal user
On Sat, Jul 30, 2005 at 07:54:36PM +0200, Erik Nørgaard wrote:
Hi,
OK, I have solved the problem, as was originally assumed it boils
down to getting the permissions right.
To make Epson 2480 work, there is no need to patch the uscanner.c
or usbdevs files and rebuild that module. I did make that work
though - sort of, now, sane-find-scanner finds an unidentified
device on uscanner0, but scanimage correctly idenfies the scanner.
This is what to do: In /usr/src/sys/dev/usb edit the files usbdevs
and uscanner.c, in usbdevs add a line:
product EPSON 2480 0x0121 Perfection 2480 scanner
and in uscanner.c add the line
{{ USB_VENDOR_EPSON, USB_PRODUCT_EPSON_2480 }, 0 },
after the last EPSON scanner.
Please submit a PR with these both lines.
I don't know if there is any benefit from using the uscanner
device other than the ability to set permissions for the scanner
only.
Using uscanner(4) is the FreeBSD way, ugen(4) is for USB devices
without specific driver.
For example you can remove device ugen from your kernel config and
your scanner will continue to run...
Here's the trick:
Create a file /etc/devfs.rules with the following:
[devfsrules=10]
# Allow any user to access usb devices: uscanner and ugen
add path 'usb0' mode 0666
add path 'usb1' mode 0666
add path 'ugen*' mode 0666
These 3 lines are useless since you're using uscanner, sane-find-scanner
or scanimage should only mention uscanner not ugen, etc. now.
add path 'uscanner*' mode 0666
The last line can be omitted if you don't use the uscanner device.
I think it is better to let others access rw the scanner device
than to add users to the operator group.
You have to use uscanner(4), period :)
Marc
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient and wpa_supplicant
Sam Leffler wrote:
Eric Schuele wrote:
big-snip
dhclient.conf contains
===
interface ath0 {
#send option host-name myhost;
#send option domain-name nxdomain.org;
send dhcp-client-identifier myhost;
media
### Home
ssid home_ssid mode 11b channel 11 wepmode on weptxkey 1 wepkey
0xhome_wepkey,
### Office
ssid office_ssid mode 11b channel 6 wepmode on weptxkey 1 wepkey
0xoffice_wepkey;
request subnet-mask, broadcast-address, routers,
domain-name-servers, domain-name;
}
Do not use media statements to setup wireless parameters; this does not
work. You need to run wpa_supplicant and let it identify the network
and setup the key parameters.
How do I tell wpa_supplicant about the network media? I had found an
older post of yours regarding NOT doing it in dhclient.conf but I've
found no other way to accomplish it.
wpa_supplicant.conf
=
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
# Home Network
network={
ssid=home_ssid
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=home_wepkey
}
# Office Network
network={
ssid=office_ssid
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=office_wepkey
}
Not sure you need scan_ssid set, I'd leave it out.
If you have problems try disabling auto-startup of ath0 and run
wpa_supplicant by hand with the -d flag to see what it's doing. Once
that's going then enable startup in rc.conf. If you continue to have
problems provide the output wpa_supplicant -d -i ath0 -c
/etc/wpa_supplicant.conf (or similar) when you have trouble. There is
also a pending issue with locating some ap's that are setup to hide
their ssid. If one of the ap's is configured in this way contact me
directly--I've been trying to collect the info I need to identify what's
going on.
Both my APs (home and office) hide their ssids. One is a wrt54g (home),
the other is linksys as well... though I forget the model at the moment
(FWIW its a/b/g). What can I do to provide the info you need?
Sam
--
Regards,
Eric
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shell script help
--On July 30, 2005 2:57:57 AM -0400 Parv [EMAIL PROTECTED] wrote:
in message [EMAIL PROTECTED],
wrote Paul Schmehl thusly...
Running what I *thought* was the same sed command in the Makefile
of the port doesn't solve the problem of the formatting of the man
pages, but it doesn't generate any errors either:
@${SED} -e '/man\.macros/r man.macros' -e '/man\.macros/d'
${WRKSRC}/doc/${f} \
${WRKDIR}/${f}
Can someone explain what the sed command is doing? The man page
isn't much help.
In the 1st part, sed sends the output of file 'man.macros' to
standard out if it exists (otherwise no worries) when sed sees the
'man\.macros' pattern.
And the 2d part, just deletes that pattern.
There in the sed(1) man page all is. Or, line by line try this ...
rm -f q ; echo polka p
{ echo p ; echo q; echo p; } | sed -e '/p/r p' -e '/p/d'
{ echo p ; echo q; echo p; } | sed -e '/p/r q' -e '/p/d'
Thanks! That was the answer. I had to fiddle with it for a while before I
understood what it was doing, but it does exactly what I need it to do now.
Paul Schmehl ([EMAIL PROTECTED])
Adjunct Information Security Officer
University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sunbird
Per olof Ljungmark wrote: Hmmm, it did not get through to the list it seems, try again. * Anyone successfully built Sunbird on FreeBSD4 or 5? I thought I'd start off trying but was sort of baffled by all the ./configure options... Its in the ports tree... /usr/ports/www/linux-sunbird just make install clean Works well enough for me (on RELENG_5 and RELENG_6). Though I very much wish it would send my 'ToDo' list to stdout given a switch (like ical). Thanks, Per olof ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Regards, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using a hard drive without partitions
Nikolas Britton [EMAIL PROTECTED] writes: But in FreeBSD your disk needs a slice otherwise it's not compatable with fdisk / bsdlabel / growfs... I think. One of the main reasons for using a DD disk is so you don't have to mess with those things; they are of no use on a DD disk (assuming that you cover the whole disk with the file system). You haven't said how you plan to use this disk. If you're going to use it for raw data, you don't need disk labels or file systems or anything, you just write (eg, ) and read (eg, ) from it, or tell your custom driver about it. Do you want to mount it for files? You've got a standard partition table with the s1 entry in use, which is not dangerous. The FAQ has an entry on DD disks. But it is dangerous because it starts at sector 0. I've read that FAQ as well as greg's book, Lucas's book, unix power tools, the man pages, handbook, etc. I will reread them again. WHAT is dangerous? Yes, a DD disk is (more) dangerous, but you don't have a DD disk. Your s1 doesn't start at sector 0 and so it isn't considered dangerous. Your s1 probably starts at the 64th sector. And I'll take a guess that your newfs /dev/ad0s1 (if it works at all) is starting the new filesystem at least 16 sectors further on, after the disk label area (which it probably assumes is there). The newfs manpage says that the disk must first be labeled. I'm going to be working on this server today and I'll post some of the details of fdisk, bsdlabel, etc. to see if I can help clarify things. Yeah, I'd like to see your bsdlabel ad0s1; I'm wondering if you have a disk label with c when you think you have no disk label. Can you mount /dev/ad0s1c? Can you mount dev/ad0s1? Seems to me you'd either want to be safe and use ad0s1a or live dangerously and use ad0a or even ad0 if it seems to work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel question..
Glenn Dawson [EMAIL PROTECTED] writes: pp-p_fstype = FS_BSDFFS; pp-p_fsize = sblock.fs_fsize; pp-p_frag = sblock.fs_frag; pp-p_cpg = sblock.fs_fpg; } The last line is the one that inserts that number. sblock.fs_fpg is the number of frags per cylinder grounp. Glenn, can you tell me which of those numbers, if any, can be changed after a newfs has been done and the file system well occupied with data? (The lousy sysinstall disk labeler wiped out several of my disk labels and I restored them with zeroes in those fields of the disk label. It worked OK, but I'm guessing it only worked because the bsdlabel defaults were the same as they were when I first did bsdlabel...; newfs If defaults had changed or I used non-default values the first time, I'd have been SOL, right? Or do those values just serve as optimization/tuning values for the kernel?) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient and wpa_supplicant
Eric Schuele wrote:
Sam Leffler wrote:
Eric Schuele wrote:
big-snip
dhclient.conf contains
===
interface ath0 {
#send option host-name myhost;
#send option domain-name nxdomain.org;
send dhcp-client-identifier myhost;
media
### Home
ssid home_ssid mode 11b channel 11 wepmode on weptxkey 1 wepkey
0xhome_wepkey,
### Office
ssid office_ssid mode 11b channel 6 wepmode on weptxkey 1 wepkey
0xoffice_wepkey;
request subnet-mask, broadcast-address, routers,
domain-name-servers, domain-name;
}
Do not use media statements to setup wireless parameters; this does
not work. You need to run wpa_supplicant and let it identify the
network and setup the key parameters.
How do I tell wpa_supplicant about the network media? I had found an
older post of yours regarding NOT doing it in dhclient.conf but I've
found no other way to accomplish it.
The above dhclient.conf lists media settings that are all handled by
wpa_supplicant so you don't specify any of them. Specifically you set
ssid, band, channel, and wep parameters; all these are handled by
wpa_supplicant.
The intent is that dhclient deal only with the dhcp protocol and stop
being involved in the discovery and selection of wireless networks (a
job wpa_supplicant is better equipped to handle).
wpa_supplicant.conf
=
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
# Home Network
network={
ssid=home_ssid
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=home_wepkey
}
# Office Network
network={
ssid=office_ssid
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=office_wepkey
}
Not sure you need scan_ssid set, I'd leave it out.
If you have problems try disabling auto-startup of ath0 and run
wpa_supplicant by hand with the -d flag to see what it's doing. Once
that's going then enable startup in rc.conf. If you continue to have
problems provide the output wpa_supplicant -d -i ath0 -c
/etc/wpa_supplicant.conf (or similar) when you have trouble. There is
also a pending issue with locating some ap's that are setup to hide
their ssid. If one of the ap's is configured in this way contact me
directly--I've been trying to collect the info I need to identify
what's going on.
Both my APs (home and office) hide their ssids. One is a wrt54g (home),
the other is linksys as well... though I forget the model at the moment
(FWIW its a/b/g). What can I do to provide the info you need?
These should work; I've had reports of problems with certain Cisco ap's.
Note however that configuring an ap to hide it's ssid adds no real
security.
Sam
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Growisofs seg faults with DVD-RAM. Anybody else seen this?
On Saturday, 30 July 2005 at 14:16:17 -0400, Chuck Swiger wrote:
Greg 'groggy' Lehey wrote:
On Friday, 29 July 2005 at 22:50:13 -0700, Carl Delsey wrote:
I was trying to use growisofs to write to a DVD-RAM and it kept
seg faulting. It worked fine with a DVD-R.
I tracked the problem down to place in the code where growisofs
tries to perform an operation on a file handle it has already
closed.
I've implemented a workaround already. The problem is, that by my
reckoning, this should affect anybody who is trying to use a DVD-RAM
(not DVD+RW) with FreeBSD, but I haven't found any references to the
problem on the net.
My guess is that DVD-RAM isn't popular enough, and that people who
have had problems with it haven't had the understanding to track the
bug down.
dvd+rw-tools doesn't support -RAM as well as other formats, in part because
the {+,-}R(W) formats are much more common, in part because there are some
pretty serious quirks in the older drives, but improvements would be
welcome.
Carl's report and patch suggest that the biggest reason that
dvd+rw-tools doesn't support -RAM is due a bug in the program, not in
the drives.
Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers.
pgpeIqFOm4wHy.pgp
Description: PGP signature
Re: Shell script help
in message [EMAIL PROTECTED],
wrote Paul Schmehl thusly...
--On July 30, 2005 2:57:57 AM -0400 Parv [EMAIL PROTECTED] wrote:
in message [EMAIL PROTECTED],
wrote Paul Schmehl thusly...
...
@${SED} -e '/man\.macros/r man.macros' -e '/man\.macros/d'
${WRKSRC}/doc/${f} \
${WRKDIR}/${f}
...
In the 1st part, sed sends the output of file 'man.macros' to
standard out if it exists (otherwise no worries) when sed sees
the 'man\.macros' pattern.
And the 2d part, just deletes that pattern.
...
Thanks! That was the answer. I had to fiddle with it for a while
before I understood what it was doing, but it does exactly what I
need it to do now.
Your welcome; i apologize if my reply was cryptic.
But then i was working direclty from the man page as my sed-fu is ok
but not great. (:
- Parv
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using a hard drive without partitions
At 10:58 AM 7/30/2005, Nikolas Britton wrote: On 7/30/05, Gary W. Swearingen [EMAIL PROTECTED] wrote: Nikolas Britton [EMAIL PROTECTED] writes: Drive: Dangerously dedicated /dev/da0s1 newfs -O2 -U I think you're using dangerously dedicated wrongly. A DD disk is one which has no standard partition table in the MBR; the disklabel sectors (16) start at sector 0 (or with your no-secondary-partitions- either method, your filesystem would start there (newfs /dev/da0)). But in FreeBSD your disk needs a slice otherwise it's not compatable with fdisk / bsdlabel / growfs... I think. bsdlabel will happily label a disk with no slices and give you /dev/ad0a etc. You've got a standard partition table with the s1 entry in use, which is not dangerous. The FAQ has an entry on DD disks. But it is dangerous because it starts at sector 0. I've read that FAQ as well as greg's book, Lucas's book, unix power tools, the man pages, handbook, etc. I will reread them again. The only danger in not having the slice table is that if you use non BSD tools, such as the ones that come with windows, they will potentially write over things that that you don't want them to. Also, without the slice table on your boot disk, the BIOS wont know what to do since it looks for the active slice and attempts to boot it. Another reason to have the slice table is if you want to share use of the disk with other operating systems, such as linux or windows or whatever. -Glenn I can't say much about your main question; I've never heard of doing it. It sounds less dangerous than putting a FS in a file, like we do with ISO filesystems all the time. Yea that's the problem ;-). I've never heard of doing it like that too but it does work. I'm going to be working on this server today and I'll post some of the details of fdisk, bsdlabel, etc. to see if I can help clarify things. Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel question..
At 02:39 PM 7/30/2005, Gary W. Swearingen wrote: Glenn Dawson [EMAIL PROTECTED] writes: pp-p_fstype = FS_BSDFFS; pp-p_fsize = sblock.fs_fsize; pp-p_frag = sblock.fs_frag; pp-p_cpg = sblock.fs_fpg; } The last line is the one that inserts that number. sblock.fs_fpg is the number of frags per cylinder grounp. Glenn, can you tell me which of those numbers, if any, can be changed after a newfs has been done and the file system well occupied with data? (The lousy sysinstall disk labeler wiped out several of my disk labels and I restored them with zeroes in those fields of the disk label. It worked OK, but I'm guessing it only worked because the bsdlabel defaults were the same as they were when I first did bsdlabel...; newfs If defaults had changed or I used non-default values the first time, I'd have been SOL, right? Or do those values just serve as optimization/tuning values for the kernel?) As far as I am aware, the values listed in the label (see my sample below) for fsize (frag size), bsize (block size) and bps/cpg (used to be cylinders per group in 4.x, but 5.x writes frags per group in that space now) are there only for reference. The numbers that the kernel cares about are the ones in the superblock. # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD 2048 16384 32776 b: 2042752 524288 swap c: 3907168020unused0 0 # raw part, don't edit d: 524288 25670404.2BSD 2048 16384 32776 e: 524288 30913284.2BSD 2048 16384 32776 f: 387101186 36156164.2BSD 2048 16384 28552 Another thing that's interesting to note, is that when you create a file system using newfs from 5.x, it always creates cylinder groups with only one cylinder. That one cylinder has the same amount of blocks as multiple cylinders would have had using older versions of newfs. I'm not really sure why that was done, but it seems to have happened when ufs2 support was added to newfs. I posted to one of the lists a while back to try and find out why, but I never got a response. -Glenn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Active Directory Server
On Sat, 30 Jul 2005 20:03:56 +0800, [EMAIL PROTECTED] wrote:
Has anyone any experience trying to make FreeBSD an Active Directory
Server? From my research and experiementation, I am under the impression
that it is possible, but I have yet to come up with any articles where it
has actual been done fully.
At the minute I have samba and ldap setup, the active directory dns
entries in (_ldap._tcp.dc._msdcs.{domain}). I am getting an error message
when trying to join my XP client to the domain - I think it is to do with
the ldap server. Any clues or points in the right direction would be
helpful - I am getting the impression that this may be a big project, if
it is even achieveable.
Cheers,
Martin
Samba has experimental components which support ADS, but not fully. See
http://www.samba.org/ and the Official Samba Howto.
In my experience it isn't currently capable to have FreeBSD run as a fully
functioning ADS server.
If you absolutely need ADS you may simply need to have a Windows server.
If you need Windows Domain logons and ACLs etc... Samba+LDAP works
beautifully, I have this implemented at my work, the only reference I
needed was the Official Samba Howto. Using LDAP Account Manager also helps
:) There are no problems with machines connecting to the domains, or
domain logons, user profiles, or ACL's.
Daniel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: network info
On Sat, 30 Jul 2005 11:08:42 -0400 Sean [EMAIL PROTECTED] wrote: What command can display all the network parameters assigned from dhcp, such DNS? I have looked at ifconfig and netstat but unless I missed a switch I do not see them as correct choices. Basically the equiv of ipconfig /all in Windows? I think that the file /var/db/dhclient.leases might hold the information you are looking for. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
question about dmesg output - acpi0
I'm trying to figure out my dmesg - I'm getting this in part: acpi0: IBM SERONYXP on motherboard acpi0: Power Button (fixed) acpi0: reservation of 460, 2 (4) failed Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0x488-0x48b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge on acpi0 pci0: ACPI PCI bus on pcib0 pci0: display, VGA at device 5.0 (no driver attached) atapci0: ServerWorks CSB5 UDMA100 controller port 0x700-0x70f, 0x376,0x170-0x17 7,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 can someone shed any light on this part: acpi0: reservation of 460, 2 (4) failed ? This is an IBM xSeries 345. I have read the acpi man and understand some generalities but am wondering if I could be building a different kernel and avoid the error message. This is on 5.3 and with GENERIC w/SMP kernel. Thanks in advance - d. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient and wpa_supplicant
Sam Leffler wrote:
Eric Schuele wrote:
Sam Leffler wrote:
Eric Schuele wrote:
big-snip
dhclient.conf contains
===
interface ath0 {
#send option host-name myhost;
#send option domain-name nxdomain.org;
send dhcp-client-identifier myhost;
media
### Home
ssid home_ssid mode 11b channel 11 wepmode on weptxkey 1 wepkey
0xhome_wepkey,
### Office
ssid office_ssid mode 11b channel 6 wepmode on weptxkey 1 wepkey
0xoffice_wepkey;
request subnet-mask, broadcast-address, routers,
domain-name-servers, domain-name;
}
Do not use media statements to setup wireless parameters; this does
not work. You need to run wpa_supplicant and let it identify the
network and setup the key parameters.
How do I tell wpa_supplicant about the network media? I had found an
older post of yours regarding NOT doing it in dhclient.conf but
I've found no other way to accomplish it.
The above dhclient.conf lists media settings that are all handled by
wpa_supplicant so you don't specify any of them. Specifically you set
ssid, band, channel, and wep parameters; all these are handled by
wpa_supplicant.
ok... I removed the lines from dhclient.conf. I reboot, and run
wpa_supplicant manually with -d. The output is attached. My AP shows
up as , while my neighbors ssids are not hidden ('linksys' and 'default').
The intent is that dhclient deal only with the dhcp protocol and stop
being involved in the discovery and selection of wireless networks (a
job wpa_supplicant is better equipped to handle).
wpa_supplicant.conf
=
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
# Home Network
network={
ssid=home_ssid
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=home_wepkey
}
# Office Network
network={
ssid=office_ssid
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=office_wepkey
}
Not sure you need scan_ssid set, I'd leave it out.
If you have problems try disabling auto-startup of ath0 and run
wpa_supplicant by hand with the -d flag to see what it's doing. Once
that's going then enable startup in rc.conf. If you continue to have
problems provide the output wpa_supplicant -d -i ath0 -c
/etc/wpa_supplicant.conf (or similar) when you have trouble. There is
also a pending issue with locating some ap's that are setup to hide
their ssid. If one of the ap's is configured in this way contact me
directly--I've been trying to collect the info I need to identify
what's going on.
Both my APs (home and office) hide their ssids. One is a wrt54g
(home), the other is linksys as well... though I forget the model at
the moment (FWIW its a/b/g). What can I do to provide the info you need?
These should work; I've had reports of problems with certain Cisco ap's.
Note however that configuring an ap to hide it's ssid adds no real
security.
I realize hidden ssids are of no real world use... but they keep *my*
neighbors out (you'll notice their ssids in the wpa_supp output).
Sam
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
Any idea why my machine will never associate with my AP using
wpa_supplicant? Anything else I can provide that may shed some light?
I am using WEP... not WPA... could that part of the problem. Since WPA
was not previously supported I had been using WEP... and figured I'd
move up to WPA one step at a time.
All help is appreciated.
--
Regards,
Eric
Script started on Sat Jul 30 15:38:44 2005
You have mail.
fangorn# wpa_supplicant -d -i ath0 -c /etc/wpa_supplicnt[K[K[Kcant.conf
Initializing interface 'ath0' conf '/etc/wpa_supplicant.conf' driver 'default'
Configuration file '/etc/wpa_supplicant.conf' - '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0 (from group name 'wheel')
Priority group 0
id=0 ssid='wLAN_WEP_Kx6L04o2'
id=1 ssid='laquinta-g'
Initializing interface (2) 'ath0'
Own MAC address: 00:0e:9b:53:31:9d
wpa_driver_bsd_set_wpa: enabled=1
wpa_driver_bsd_del_key: keyidx=0
wpa_driver_bsd_del_key: keyidx=1
wpa_driver_bsd_del_key: keyidx=2
wpa_driver_bsd_del_key: keyidx=3
wpa_driver_bsd_set_countermeasures: enabled=0
wpa_driver_bsd_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 10 usec
Starting AP scan (broadcast SSID)
Received 0 bytes of scan results (3 BSSes)
Scan results: 3
Selecting BSS from priority group 0
0: 00:13:10:94:f4:07 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0
skip - no WPA/RSN IE
1: 00:11:95:07:be:ec ssid='default' wpa_ie_len=0 rsn_ie_len=0
skip - no WPA/RSN IE
2: 00:0f:66:00:ca:5c ssid='' wpa_ie_len=0 rsn_ie_len=0
skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
freebsd 5.4 -R install error
On install i get this error : Unable to find device node for /dev/ad0s1b in /dev! The creation of filesystems will be aborted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
freebsd 5.4 -R install error
On install i get this error : Unable to find device node for /dev/ad0s1b in /dev! The creation of filesystems will be aborted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
