malformed man pages
Hi FreeBSD community We have an issue on Tomahawk Desktop (an upcoming FreeBSD-based distro) that all man pages malformed. Eg. man tar shows as follows: 1mNAME0m 1mtar 22m-- format of tape archive files 1mDESCRIPTION0m The 1mtar 22marchive format collects any number of files, directories, and What have we missed? Kind regards Sagara ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
lxde
hello, I installed the lxde-meta in a new FreeBSD 8.0 i386 machine, but when I start it (via exec startlxde in ~.xinitrc) only a black desktop appears with no panel or menu bars. Right-clicking on the desktop a *very* minimal menu appears (basically containing xterm, firefox and the file manager). I was wondering whether this is the intended behavior or I am missing something... Does anyone know how to get the panel up? Also, I don't think lxterminal is present in the ports... is there any plan to include it? thanks in advance for any comments or suggestions regards giuseppe -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41125 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5336 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: malformed man pages
Hi, On Fri, 04 Dec 2009 16:50:31 +0800 Sagara Wijetunga wrote: We have an issue on Tomahawk Desktop (an upcoming FreeBSD-based distro) that all man pages malformed. What is the base FreeBSD version? Eg. man tar shows as follows: 1mNAME0m 1mtar 22m-- format of tape archive files 1mDESCRIPTION0m The 1mtar 22marchive format collects any number of files, directories, and What are your terminal, locale, fonts? What have we missed? Well, there were good old days ;-) when the grass was green and manual pages were written in plain ASCII. Those days passed, welcome to the shiny future. Manual pages have colors, belts and whistles and can be viewed only at xterm and with some fonts. *sign* bsam, who used a copy-n-paste from DISKLESS(8) and lost nfs connectivity. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
strange samba issue
Hi List I have encountered a problem with samba and I cant seem to find a solution to it. I re-installed my 3 BSD servers over the last week and am now running 8.0 amd 64. I`ll use the machine names as it will make it less confusing to explain, Proteus AMD64 3500+ 4GB 3 x 500GB ZFS raidz samba-3.3.9 Amalthea AMD64 x2 4200+ 2GB 4x 500GB ZFS raidz samba-3.3.9 Eris AMD64 x2 5200+ 4GB 6 x 1.5TB ZFS raidz samba-3.3.9 Mercury win2k3 server Saturn win2k3 server Hyperion windows XP pro Samba is setup to just function as part of the workgroup. Accessing all the network shares from Hyperion is what I would call normal in speed, except for Proteus clicking on a folder can take 15 seconds or so for the folder to open. Now if I connect to either Saturn or Mercury via remote desktop, and I then access Proteus the speed is normal pretty much the instant you double click the folder it opens. I have tried adding socket options = TCP_NODELAY to the smb.conf on Proteus but that made no difference, anyone got any ideas ? Regards Graeme ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Hardware migration and upgrade from 6.3 to 8.0 advice
Hello, i am facing this situation, where i need to upgrade from my 6.3 i386 system, used as my main workstation, to a new hardware based on amd64 (phenom II x4). My current system is alive since 2005, so is full of code, scripts, configurations,lookfeel,ssh keys etc.. that i would like to keep handy in my new system. Also, currently i run gmirror, i am mentioning it, in case it affects something. Since 2005, dealing with programming/support/etc.. i haven't done any upgrade task in FreeBSD, so i dont feel that confident in this regard. I could: a) install a brand new 8.0-RELEASE in the new hardware and then a1) just mount the old disks to the new system or a2) migrate /home user data directly to the new home dirs b) migrate all current data to the new hardware, kernel/system included, and then try to upgrade to 8.0 (by sysinstall or makeworld/makekernel) So, its a trade-off between pain, correctness, effectiveness, and ease of use. What would you guys recommend? Which way to go? Any other options? Thanx in advance! Please include me in your CC, as i am not subscribed to the list. Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Hardware migration and upgrade from 6.3 to 8.0 advice
Achilleas Mantzios schrieb: Hi! Hello, i am facing this situation, where i need to upgrade from my 6.3 i386 system, used as my main workstation, to a new hardware based on amd64 (phenom II x4). Well, you know that i386 is Intel, do you? It might work just moving the old kernel to a 64-bit system but I have no experience with it. My current system is alive since 2005, so is full of code, scripts, configurations,lookfeel,ssh keys etc.. that i would like to keep handy in my new system. Also, currently i run gmirror, i am mentioning it, in case it affects something. Since 2005, dealing with programming/support/etc.. i haven't done any upgrade task in FreeBSD, so i dont feel that confident in this regard. I could: a) install a brand new 8.0-RELEASE in the new hardware and then a1) just mount the old disks to the new system or a2) migrate /home user data directly to the new home dirs b) migrate all current data to the new hardware, kernel/system included, and then try to upgrade to 8.0 (by sysinstall or makeworld/makekernel) Item b) is not recommended. There are so many changes AFAIK that it is no clear update. You might do so but then you should update the following way from 6.3 - 7.0 - 7.1 - 7.2 - 8.0 as was recommended on this list earlier (search the archives, please, for further details if you choose this way). For me, a clean install of 8.0 and a move from the old data to the fresh install is better. Use a2) ! Greetings Frank ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Hardware migration and upgrade from 6.3 to 8.0 advice
On Fri, Dec 4, 2009 at 2:57 AM, Achilleas Mantzios mantzios.ach...@yahoo.com wrote: Hello, i am facing this situation, where i need to upgrade from my 6.3 i386 system, used as my main workstation, to a new hardware based on amd64 (phenom II x4). My current system is alive since 2005, so is full of code, scripts, configurations,lookfeel,ssh keys etc.. that i would like to keep handy in my new system. Also, currently i run gmirror, i am mentioning it, in case it affects something. Since 2005, dealing with programming/support/etc.. i haven't done any upgrade task in FreeBSD, so i dont feel that confident in this regard. I could: a) install a brand new 8.0-RELEASE in the new hardware and then a1) just mount the old disks to the new system or a2) migrate /home user data directly to the new home dirs b) migrate all current data to the new hardware, kernel/system included, and then try to upgrade to 8.0 (by sysinstall or makeworld/makekernel) So, its a trade-off between pain, correctness, effectiveness, and ease of use. What would you guys recommend? Which way to go? Any other options? Thanx in advance! Please include me in your CC, as i am not subscribed to the list. Achilleas Mantzios You may want to consider installing from scratch and migrating over. This would allow you setup zfs and make the move easier. Also may want to explore run ahci(4) as that can seriously increase disk speed although I believe many more improvements live in STABLE, not RELEASE. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Hardware migration and upgrade from 6.3 to 8.0 advice
Frank Wissmann writes: i am facing this situation, where i need to upgrade from my 6.3 i386 system, used as my main workstation, to a new hardware based on amd64 (phenom II x4). b) migrate all current data to the new hardware, kernel/system included, and then try to upgrade to 8.0 (by sysinstall or makeworld/makekernel) Item b) is not recommended. Confirmed. _Highly_ not recommended. .0 releases usually contain ABI/API changes (among other things) and you don't want anything getting confused. For me, a clean install of 8.0 and a move from the old data to the fresh install is better. To the OP: the machine I'm typing on is also AMD Phenom II x4 (940, if it matters) originally installed with 8.0-RC3/amd64. Once I got past the dangerously dedicated disk issue (and close relatives) everything went smoothly. Of the choices presented, I recommend (a1) with the old disk set to read-only in hardware. New disks are cheap, and this gives you a perfect backup for as long as you want it. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: malformed man pages
Boris Samorodov wrote: Hi, On Fri, 04 Dec 2009 16:50:31 +0800 Sagara Wijetunga wrote: We have an issue on Tomahawk Desktop (an upcoming FreeBSD-based distro) that all man pages malformed. What is the base FreeBSD version? FreeBSD 7.2 Eg. man tar shows as follows: 1mNAME0m 1mtar 22m-- format of tape archive files 1mDESCRIPTION0m The 1mtar 22marchive format collects any number of files, directories, and What are your terminal, locale, fonts? echo $TERM xterm-color How do I know what locale and fonts are effective? Our default in /etc/login.conf is same as FreeBSD's. What have we missed? Well, there were good old days ;-) when the grass was green and manual pages were written in plain ASCII. Those days passed, welcome to the shiny future. Manual pages have colors, belts and whistles and can be viewed only at xterm and with some fonts. *sign* bsam, who used a copy-n-paste from DISKLESS(8) and lost nfs connectivity. Regards Sagara ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
recovering data from this disk
any suggestions how to recover data from either of the mirrored disks that i can't get to boot? the situation is described below. (i'm assuming, given the silence on this, that making the system work after the freebsd-update is a lost cause.) On 12/3/09 11:14 AM, Tom Worster f...@thefsb.org wrote: after running freebsd-update -r 8.0-RELEASE upgrade my system won't boot. it gets stuck on mountroot and i can't find the magic word it wants. the system used to have two sata drives /dev/ad4 and ad6. they were partitioned and sliced using the deafaults that sysinstall suggested. at the boot prompt, lsdev says: disk devices disk0: BIOS drive C: disk0s1a: FFS disk0s1b: swap disk0s1d: FFS disk0s1e: FFS disk0s1f: FFS disk1: BIOS drive D: disk1s1a: FFS disk1s1b: swap disk1s1d: FFS disk1s1e: FFS disk1s1f: FFS which looks right, although i'm not familiar with the disk nomenclature. entering ? at mountroot mentions ad4 and ad6. geom_mirror was being used. i've tried saying load geom_mirror and/or enable-module geom_mirror at the boot prompt. neither made any difference. nothing i've said to mountroot works: ufs:/dev/ad4s1a ufs:/dev/ad6s1a ufs:/dev/mirror/gm0s1a ufs:/dev/disk0s1a ufs:/dev/disk1s1a does anyone know the magic word? i'd be very grateful. tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Newbie questions (updating, ports, etc.)
Thanks to all for your detailed and informative replies to my questions. I have many new things to try out. I can't speak for anyone else, but long posts don't bother me. I hope we've clarified things for you. Welcome to FreeBSD! Thanks. Its good to be here! -Richard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8.0 not detecting hot swap drive insertion
I'm running a 10 hot-swap SATA disk ZFS pool and recently upgraded from 7.2 to 8. Since I upgraded, freebsd isn't spinning up or recognizing a new drive that is inserted. In freebsd 7.[0,2], I could remove a drive and insert a new one and freebsd would recognize it, spin it up, and create the device nodes. None of that is happening in 8.0, and the only way I've found to get it to recognize the disk is to reboot the system. I tried using atacontrol to force freebsd to reinit an ata channel, but that didn't have any effect. Did something change in 8.0 that prevents this auto-detection? Is there a way to re-enable it? Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.0 not detecting hot swap drive insertion
Rob wrote: I'm running a 10 hot-swap SATA disk ZFS pool and recently upgraded from 7.2 to 8. Since I upgraded, freebsd isn't spinning up or recognizing a new drive that is inserted. In freebsd 7.[0,2], I could remove a drive and insert a new one and freebsd would recognize it, spin it up, and create the device nodes. None of that is happening in 8.0, and the only way I've found to get it to recognize the disk is to reboot the system. I tried using atacontrol to force freebsd to reinit an ata channel, but that didn't have any effect. Did something change in 8.0 that prevents this auto-detection? Is there a way to re-enable it? Are you using the original (7.x) ata(4) driver or the newer enhanced SATA drivers like ahci(4) or siis(4)? If you're using the latter your devices will be labeled /dev/ada* instead of /dev/ad*. If you are indeed using the newer enhanced SATA drivers, you will need to use camcontrol to reset and rescan the associated SATA channels. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.0 not detecting hot swap drive insertion
I don't have any /dev/ada* devices, so I assume I'm using the original ata driver. I haven't done any kernel customization, and am running the distribution's kernel (upgraded with the freebsd-update tool). Does the older driver no longer detect drive insertion? Rob Steve Polyack wrote: Rob wrote: I'm running a 10 hot-swap SATA disk ZFS pool and recently upgraded from 7.2 to 8. Since I upgraded, freebsd isn't spinning up or recognizing a new drive that is inserted. In freebsd 7.[0,2], I could remove a drive and insert a new one and freebsd would recognize it, spin it up, and create the device nodes. None of that is happening in 8.0, and the only way I've found to get it to recognize the disk is to reboot the system. I tried using atacontrol to force freebsd to reinit an ata channel, but that didn't have any effect. Did something change in 8.0 that prevents this auto-detection? Is there a way to re-enable it? Are you using the original (7.x) ata(4) driver or the newer enhanced SATA drivers like ahci(4) or siis(4)? If you're using the latter your devices will be labeled /dev/ada* instead of /dev/ad*. If you are indeed using the newer enhanced SATA drivers, you will need to use camcontrol to reset and rescan the associated SATA channels. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: malformed man pages
On Fri, 04 Dec 2009 22:02:41 +0800 Sagara Wijetunga wrote: Boris Samorodov wrote: On Fri, 04 Dec 2009 16:50:31 +0800 Sagara Wijetunga wrote: We have an issue on Tomahawk Desktop (an upcoming FreeBSD-based distro) that all man pages malformed. What is the base FreeBSD version? FreeBSD 7.2 OK. Eg. man tar shows as follows: 1mNAME0m 1mtar 22m-- format of tape archive files 1mDESCRIPTION0m The 1mtar 22marchive format collects any number of files, directories, and What are your terminal, locale, fonts? echo $TERM xterm-color OK. How do I know what locale and fonts are effective? % locale I don't remember how to detect current font, but I know how to set it up. ;-) I use x11-fonts/dejavu and set it at ~/XTerm: - XTerm*faceName: DejaVu Sans Mono XTerm*faceSize: 12 - -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
GEOM: ad0s1: geometry does not match label (255h,63s != 16h,63s).
Hi, I have installed my laptop with FreeBSD 8.0-RC1 first (now I'm on 8.0-Release-p1) and in dmesg I got this error message : GEOM: ad0s1: geometry does not match label (255h,63s != 16h,63s). I have search on the Web about the method to resolv this, but I haven't found anything that helps me. Here the result of #bsdlabel ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 104857604.2BSD0 0 0 b: 2028960 1048576 swap c: 1172101770unused0 0 # raw part, don't edit d: 3110912 30775364.2BSD0 0 0 e: 1048576 61884484.2BSD0 0 0 f: 109973153 72370244.2BSD0 0 0 And the result of # gpart show = 63 117210177 ad0 MBR (56G) 63 1172101771 freebsd [active] (56G) =0 117210177 ad0s1 BSD (56G) 01048576 1 freebsd-ufs (512M) 10485762028960 2 freebsd-swap (991M) 30775363110912 4 freebsd-ufs (1.5G) 61884481048576 5 freebsd-ufs (512M) 7237024 109973153 6 freebsd-ufs (52G) Thanks for your help, Alexandre L. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Wireless network control
I am just trying to find out if theres an easier way to do this. currently to get wireless to work on my system, i have to clone the wireless interface to a wlan0 interface to actually do any real connections. My home network uses WPA2 encryption so i use the wpa-supplicant to set that up, but if i go out and about and hit free wifi spots, I have to add the info for them into the wpa-supplicant.conf file to get it to access it. keep in mind that ideally I use the latest gnome as my desktop. is there an easier tool to do this all with? I remember there was an issue with the gnome-network tool that it could not actually make any changes in freebsd, but i cannot find if that is still true or if it has been fixed. End goal, I am trying to get this set up to be equally as idiot-proof as most linux distros in case i have to hand this off to someone a bit less technically inclined. sorry if this is a bit hard to read, i have ADHD so it someti..OHLOOKASQUIRREL -Sean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Hardware migration and upgrade from 6.3 to 8.0 advice
Thanx to all. I will keep the old machine for development/maintenance/support, while bulding/testing/migrating the newest versions of software in the new hardware. Up to now, i got the base system/kernel working ok on the new beast, and currently installing additional distributions. All seem fine. Achilleas Mantzios --- On Fri, 12/4/09, Adam Vande More amvandem...@gmail.com wrote: From: Adam Vande More amvandem...@gmail.com Subject: Re: Hardware migration and upgrade from 6.3 to 8.0 advice To: Achilleas Mantzios mantzios.ach...@yahoo.com Cc: freebsd-questions@freebsd.org Date: Friday, December 4, 2009, 1:36 PM On Fri, Dec 4, 2009 at 2:57 AM, Achilleas Mantzios mantzios.ach...@yahoo.com wrote: Hello, i am facing this situation, where i need to upgrade from my 6.3 i386 system, used as my main workstation, to a new hardware based on amd64 (phenom II x4). My current system is alive since 2005, so is full of code, scripts, configurations,lookfeel,ssh keys etc.. that i would like to keep handy in my new system. Also, currently i run gmirror, i am mentioning it, in case it affects something. Since 2005, dealing with programming/support/etc.. i haven't done any upgrade task in FreeBSD, so i dont feel that confident in this regard. I could: a) install a brand new 8.0-RELEASE in the new hardware and then a1) just mount the old disks to the new system or a2) migrate /home user data directly to the new home dirs b) migrate all current data to the new hardware, kernel/system included, and then try to upgrade to 8.0 (by sysinstall or makeworld/makekernel) So, its a trade-off between pain, correctness, effectiveness, and ease of use. What would you guys recommend? Which way to go? Any other options? Thanx in advance! Please include me in your CC, as i am not subscribed to the list. Achilleas Mantzios You may want to consider installing from scratch and migrating over. This would allow you setup zfs and make the move easier. Also may want to explore run ahci(4) as that can seriously increase disk speed although I believe many more improvements live in STABLE, not RELEASE. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
PF binat rule issue - feature or bug?
Using 7.2-RELEASE-p4 i386 with GENERIC kernel, I've found (the hard way)
that if I have a pf.conf rule like
nat on $ext_if proto { tcp udp icmp } from $my_subnet \
to any - some.public.ip.num
then pfctl will perform the expected expansion of the listed protocols
into three separate NAT rules.
However, if I have a rule like
binat on $ext_if proto { tcp udp icmp } from $server_dmz_ip \
to any - $server_public_ip
then I will /only/ get one NAT rule, for TCP.
Then things like NTP, DNS and ping will fail, but the filtering rules
that permit such traffic will increment their byte, packet and state
counters like PF is working just fine (and I suppose in some sense that
the filtering part is). But only if I explicitly declare in pf.conf a
separate binat rule for each desired protocol, instead of listing them,
will things work as needed.
Feature or bug? If the former, it is not well documented that I could
see. I expected that a list of protocols for a binat rule would just
work, and pfctl certainly didn't mark it as bad syntax. If a bug, is
this a FreeBSD bug or OpenBSD?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Wireless network control
Sean Cavanaugh wrote: I am just trying to find out if theres an easier way to do this. currently to get wireless to work on my system, i have to clone the wireless interface to a wlan0 interface to actually do any real connections. My home network uses WPA2 encryption so i use the wpa-supplicant to set that up, but if i go out and about and hit free wifi spots, I have to add the info for them into the wpa-supplicant.conf file to get it to access it. keep in mind that ideally I use the latest gnome as my desktop. is there an easier tool to do this all with? I remember there was an issue with the gnome-network tool that it could not actually make any changes in freebsd, but i cannot find if that is still true or if it has been fixed. End goal, I am trying to get this set up to be equally as idiot-proof as most linux distros in case i have to hand this off to someone a bit less technically inclined. sorry if this is a bit hard to read, i have ADHD so it someti..OHLOOKASQUIRREL -Sean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org There was a person asking for a similar thing on this same list. I think the subject was something like ifconfig - GUI interface. Have a search on the list's archive. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
SMP and ALTQ_NOPCC
Hello, With the improvements in SMP in FreeBSD 8.0, is the ALTQ_NOPCC option still required? In the handbook and other older documentation, it says ALTQ_NOPCC is in fact required on SMP systems because the TSC is unstable. I was wondering if this is still the case after the improvements done with SMP. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Setting devfs rules inside jail
Hi, I'm trying to setup CUPS (in a jail) using an old parallel port printer on my server machine. I used ezjail to create a jail and the installed CUPS within it. I've got everything up and running, but i've had to work around some issues. Initially, the CUPS administration website didn't list the printer on the Add Printer screen. I discovered that this because the /dev/lpt0 and /dev/lpt0.ctl devices weren't showing up in the jail. I therefore (on the host system), created a /etc/devfs.rules file... [devfsrules_jail_pearl=5] add include $devfsrules_hide_all add include $devfsrules_unhide_basic add include $devfsrules_unhide_login add path 'lpt*' unhide add path 'lpt*' mode 0660 group cups I updated the devfs ruleset entry in /usr/local/etc/ezjail/pearl_domain.tld, and rebooted. This successfully made the /dev/lpt0 and /dev/lpt0.ctl devices visible in the jail and assigned them the correct permissions. Unfortunately, I was seeing an error message on-screen when the system was booted (when the jails were being started)... devfs rule: error converting to integer: cups After a moment, I realised what had happened - I installed CUPS in a jail, not on the host system. Naturally the CUPS group does not exist on the host so when the system tried to translate the group name to a UID, it couldn't do so. I modified the last line of the hosts /dev/devfs.rules line to as follows (basically removing the 'group cups')... add path 'lpt*' mode 0660 At this point, I thought what I needed to do is setup a /etc/devfs.rules file in the jail - setting the group ownership in the jail where the CUPS group exists. I created a /etc/devfs.rules file *in* the jail... [localrules=5] add path 'lpt*' group cups I also added the following entry in my jail's /etc/rc.conf file... devfs_system_ruleset=localrules Unfortunately, the group assignment statement never seems to get executed. I've gotten around this by just creating a quick script which explicitly sets the group ownership, and having the script be executed on boot via /etc/crontab. I'm not understanding why the devfs rules aren't being applied in the jail however. Can anyone help? If its relevant, i'm using FreeBSD 7.2 (FreeBSD xxx.xxx.xxx 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Tue Dec 1 19:05:36 GMT 2009 u...@xxx.xxx.xxx:/usr/obj/usr/src/sys/xxx i386). Regards, Jazz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Wireless network control
On Fri, Dec 04, 2009 at 05:05:47PM +, Ricardo Jesus wrote: Sean Cavanaugh wrote: I am just trying to find out if theres an easier way to do this. currently to get wireless to work on my system, i have to clone the wireless interface to a wlan0 interface to actually do any real connections. My home network uses WPA2 encryption so i use the wpa-supplicant to set that up, but if i go out and about and hit free wifi spots, I have to add the info for them into the wpa-supplicant.conf file to get it to access it. keep in mind that ideally I use the latest gnome as my desktop. is there an easier tool to do this all with? Have a look at http://opal.com/freebsd/ports/net-mgmt/wifimgr It is in ports; see /usr/ports/net-mgmt/wifimgr Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpOatuJkysEs.pgp Description: PGP signature
Re: Last login message
On 04.12.2009 00:16, Nerius Landys wrote: I was wondering what controls this, meaning if I get an IP or a hostname, and why it's being truncated. don't know about the truncating, but this behavior of displaying the last login time and host is handled by pam_lastlog(8). i guess the FQHN is just displayed if a reverse dns entry exists for the corresponding ip. regards - michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8.0 zfs install
Does the installer in 8.0 support zfs? If not whats the easiest way to get a full zfs install done? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: recovering data from this disk
On Fri, 04 Dec 2009, Tom Worster wrote: any suggestions how to recover data from either of the mirrored disks that i can't get to boot? the situation is described below. If they were indeed mirrored then try a FreeBSD live distro boot CD and boot into that then just mount one of the disk partitions that you need. Henrik (i'm assuming, given the silence on this, that making the system work after the freebsd-update is a lost cause.) On 12/3/09 11:14 AM, Tom Worster f...@thefsb.org wrote: after running freebsd-update -r 8.0-RELEASE upgrade my system won't boot. it gets stuck on mountroot and i can't find the magic word it wants. the system used to have two sata drives /dev/ad4 and ad6. they were partitioned and sliced using the deafaults that sysinstall suggested. at the boot prompt, lsdev says: disk devices disk0: BIOS drive C: disk0s1a: FFS disk0s1b: swap disk0s1d: FFS disk0s1e: FFS disk0s1f: FFS disk1: BIOS drive D: disk1s1a: FFS disk1s1b: swap disk1s1d: FFS disk1s1e: FFS disk1s1f: FFS which looks right, although i'm not familiar with the disk nomenclature. entering ? at mountroot mentions ad4 and ad6. geom_mirror was being used. i've tried saying load geom_mirror and/or enable-module geom_mirror at the boot prompt. neither made any difference. nothing i've said to mountroot works: ufs:/dev/ad4s1a ufs:/dev/ad6s1a ufs:/dev/mirror/gm0s1a ufs:/dev/disk0s1a ufs:/dev/disk1s1a does anyone know the magic word? i'd be very grateful. tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Henrik Hudson li...@rhavenn.net - God, root, what is difference? Pitr; UF ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0 zfs install
William Taylor wrote: Does the installer in 8.0 support zfs? No. If not whats the easiest way to get a full zfs install done? http://wiki.freebsd.org/RootOnZFS and links referenced from that page. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: 8.0 zfs install
On Fri, Dec 4, 2009 at 10:28 AM, William Taylor willi...@corp.sonic.net wrote: Does the installer in 8.0 support zfs? If not whats the easiest way to get a full zfs install done? This is probably the best place to start, in general the FreeBSD handbook is the best place to start looking for any information you may have regarding the OS: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/filesystems-zfs.html You can also get more information via the FreeBSD wiki here: http://wiki.freebsd.org/ZFS -- pete wright www.nycbug.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: recovering data from this disk
On 12/4/09 1:51 PM, Henrik Hudson li...@rhavenn.net wrote: On Fri, 04 Dec 2009, Tom Worster wrote: any suggestions how to recover data from either of the mirrored disks that i can't get to boot? the situation is described below. If they were indeed mirrored then try a FreeBSD live distro boot CD and boot into that then just mount one of the disk partitions that you need. thanks, henrik, but i wasn't able to make the live fs fixit shell work. i get an error message when i try to start the live fs shell: ldconfig could not create the ld.so hints file and all commands fail to work. tom (i'm assuming, given the silence on this, that making the system work after the freebsd-update is a lost cause.) On 12/3/09 11:14 AM, Tom Worster f...@thefsb.org wrote: after running freebsd-update -r 8.0-RELEASE upgrade my system won't boot. it gets stuck on mountroot and i can't find the magic word it wants. the system used to have two sata drives /dev/ad4 and ad6. they were partitioned and sliced using the deafaults that sysinstall suggested. at the boot prompt, lsdev says: disk devices disk0: BIOS drive C: disk0s1a: FFS disk0s1b: swap disk0s1d: FFS disk0s1e: FFS disk0s1f: FFS disk1: BIOS drive D: disk1s1a: FFS disk1s1b: swap disk1s1d: FFS disk1s1e: FFS disk1s1f: FFS which looks right, although i'm not familiar with the disk nomenclature. entering ? at mountroot mentions ad4 and ad6. geom_mirror was being used. i've tried saying load geom_mirror and/or enable-module geom_mirror at the boot prompt. neither made any difference. nothing i've said to mountroot works: ufs:/dev/ad4s1a ufs:/dev/ad6s1a ufs:/dev/mirror/gm0s1a ufs:/dev/disk0s1a ufs:/dev/disk1s1a does anyone know the magic word? i'd be very grateful. tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Is there the equivalent of a Windows fast format for UFS?
I suspect I know the answer to this question but I'll ask it anyway. We're dealing with some very large disks (11TB raid array) and a newfs operation takes a significant time. Is there any way to get a volume formatted faster than the typical newfs does? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [Solved] Having problems burning a DVD
James Phillips wrote: Hello, After making two coasters with a graphical CD burning program using Ubuntu, I decided to try using FreeBSD: I want to start backing up to DVD anyway. After some searching I learned I missed some details in the handbook on the first and second reads such as: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-dvds.html The program growisofs(1) will be used to perform DVD recording. This command is part of the dvd+rw-tools utilities (sysutils/dvd+rw-tools). The dvd+rw-tools support all DVD media types. I had hard time finding the non-existent growisofs package! These tools use the SCSI subsystem to access to the devices, therefore the ATAPI/CAM support must be added to your kernel. If your burner uses the USB interface this addition is useless, and you should read the Section 18.5 for more details on USB devices configuration. Using the atapicd driver generated the following error message: :-( unable to CAMGETPASSTHRU for /dev/acd0: Inappropriate ioctl for device After the command: $ growisofs -dvd-compat -Z /dev/acd0=8.0-RELEASE-i386-dvd1.iso before you ask: MD5 (8.0-RELEASE-i386-dvd1.iso) = 5336cd827991e4d4cff6d73c4a5ca105 Release announcement: 5336cd827991e4d4cff6d73c4a5ca105 I tried playing with /etc/devfs.conf as suggested by Predrag Punosevac $ id uid=1002(backup) gid=1002(backup) groups=1002(backup),5(operator),1003(Share) $ cat /etc/devfs.conf |sed 's/#.*//g' linkcd0 cdrom linkcd0 dvd linkcd0 rdvd own cdrom root:operator own dvd root:operator own rdvdroot:operator permcd0 0660 permcdrom 0660 permdvd 0660 permrdvd0660 permxpt00660 permpass0 0660 - that sed command was stolen from a script expecting CRlf -originally used device acd0 (until enabling atapicam) $ cat /boot/loader.conf acpi_load=no apm_load=yes atapicam_load=yes #ata_load=yes# enabled by default scbus_load=yes cd_load=yes pass_load=yes atapicd_load=no #hw.ata.atapi_dma=1 # enabled by default With the atapicam driver I was able to somehow get growisofs to go through the motions of burning the DVD, even have a kernel message from GEOM reading the BSD label: $ tail /var/log/messages Dec 3 20:00:00 dusty newsyslog[833]: logfile turned over due to size100K Dec 3 20:00:28 dusty kernel: GEOM_LABEL: Label for provider acd0t01 is iso9660/FreeBSD_Install. but can't read the disk to verify it: $ dd if=/dev/cd0 bs=2048 | md5 996592+0 records in 996592+0 records out 2041020416 bytes transferred in 1292.388284 secs (1579263 bytes/sec) 19b087536234b316b64232ba6b1c1799 Umm. Nevermind. I added the block size so nobody would try suggesting it has an effect :P previous error: $ dd if=/dev/cd0 | md5 dd: /dev/cd0: Invalid argument 0+0 records in 0+0 records out 0 bytes transferred in 0.000721 secs (0 bytes/sec) d41d8cd98f00b204e9800998ecf8427e I noticed that the hash does not match the ISO file. Is that normal for DVDs? For CD images I often get the md5 hash to match. The man page for atapicam(4) warns: atapicam and ATAPI-specific target drivers (acd(4), ast(4), and afd(4)) can be configured in the same kernel. Simultaneous access to the same device through the SCSI generic drivers and the ATAPI-specific drivers may cause problems and is strongly discouraged. Is there anything special I should do to try to disable the atapicd driver? I don't think my 'atapicd_load=no' line in /boot/loader.conf has much of an effect. Regards, James Phillips __ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Aloha JP, This is what I use on FreeBSD from the command line to burn DVD's. I have used it on FreeBSD 8* for a while. (Simple and it works.)- ## dvdburner.doc DVD+R burner Setup and operation From sysutils/dvd+rw-tools Intall the DVD port # growisofs ( used the following from all the suggestions and it worked with Manolis DVD p1 7.2) 1st Put hw.ata.atapi_dma=1 in the /boot/loader.conf 2nd Put apticam_load=YES in the /boot/loader.conf (That 2nd 18.7.2 instruction is not clear in the Handbook section and should be added.) Then Run # growisofs -dvd-compat -Z dev/cd0=/usr/home/alp/FreeBSD_7/7.2-RELEASE-p1-i386-disc1.iso (all on one line) Then Use cd0 as a DVD burner and make the DVD-R I tested the DVD on a spare box and it installed just fine. ## ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol
Re: malformed man pages
In the last episode (Dec 04), Sagara Wijetunga said: Hi FreeBSD community We have an issue on Tomahawk Desktop (an upcoming FreeBSD-based distro) that all man pages malformed. Eg. man tar shows as follows: 1mNAME0m 1mtar 22m-- format of tape archive files 1mDESCRIPTION0m The 1mtar 22marchive format collects any number of files, directories, and That looks sort of like malformed ANSI escape codes (bold would be ESC [ 1 m, but the man utilities shouldn't be generating those. If you run man 5 tar | hd | head, what do you get? I get this: 54 41 52 28 35 29 09 09 09 20 20 46 72 65 65 42 |TAR(5)... FreeB| 0010 53 44 20 46 69 6c 65 20 46 6f 72 6d 61 74 73 20 |SD File Formats | 0020 4d 61 6e 75 61 6c 09 09 09 54 41 52 28 35 29 0a |Manual...TAR(5).| 0030 0a 4e 08 4e 41 08 41 4d 08 4d 45 08 45 0a 20 20 |.N.NA.AM.ME.E. | 0040 20 20 20 74 08 74 61 08 61 72 08 72 20 2d 2d 20 | t.ta.ar.r -- | 0050 66 6f 72 6d 61 74 20 6f 66 20 74 61 70 65 20 61 |format of tape a| 0060 72 63 68 69 76 65 20 66 69 6c 65 73 0a 0a 44 08 |rchive files..D.| 0070 44 45 08 45 53 08 53 43 08 43 52 08 52 49 08 49 |DE.ES.SC.CR.RI.I| 0080 50 08 50 54 08 54 49 08 49 4f 08 4f 4e 08 4e 0a |P.PT.TI.IO.ON.N.| 0090 20 20 20 20 20 54 68 65 20 74 08 74 61 08 61 72 | The t.ta.ar| The doubled letters are handled by /usr/bin/less and converted to bold before displaying. If you get the same hd output as I have above, then we know that the manpage is fine, and your problem is in /usr/bin/less or your terminal type is incorrect. If you see ANSI escape codes in the hd output, then we know the problem is with the manpage tools. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Xorg - no mouse and no keyboard
I had a working Xorg config, and everything was fine. Then my monitors crapped out. I got new ones and installed them. No I have no mouse and no keyboard in Xorg. I've tried disabling hald and dbus and manually configuring them. That doesn't work either. What sort of troubleshooting steps do I need to take to figure out why they're not working and get them working again? Mouse and keyboard work find at the console. It's only in X that they don't work. I'm running 7.2-STABLE FreeBSD 7.2-STABLE #13. I've uninstalled and reinstalled xf86-input-keyboard, xf86-input-mouse and the radeonhd driver to no avail. I've searched the web for answers but haven't found any. Here's some stuff from the Xorg.0.log: # grep -i mouse /var/log/Xorg.0.log (==) RADEONHD(0): Silken mouse enabled (II) config/hal: Adding input device Optical USB Mouse (II) LoadModule: mouse (II) Loading /usr/local/lib/xorg/modules/input//mouse_drv.so (II) Module mouse: vendor=X.Org Foundation (**) Optical USB Mouse: Device: /dev/ums1 (==) Optical USB Mouse: Protocol: Auto (**) Optical USB Mouse: always reports core events (==) Optical USB Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) Optical USB Mouse: ZAxisMapping: buttons 4 and 5 (**) Optical USB Mouse: Buttons: 9 (**) Optical USB Mouse: Sensitivity: 1 (II) XINPUT: Adding extended input device Optical USB Mouse (type: MOUSE) (**) Optical USB Mouse: (accel) keeping acceleration scheme 1 (**) Optical USB Mouse: (accel) filter chain progression: 2.00 (**) Optical USB Mouse: (accel) filter stage 0: 20.00 ms (**) Optical USB Mouse: (accel) set acceleration profile 0 (II) Optical USB Mouse: SetupAuto: hw.iftype is 5, hw.model is 0 (II) Optical USB Mouse: SetupAuto: protocol is SysMouse (II) config/hal: removing device Optical USB Mouse (II) UnloadModule: mouse (II) config/hal: Adding input device PS/2 Mouse (**) PS/2 Mouse: Device: /dev/psm0 (==) PS/2 Mouse: Protocol: Auto (**) PS/2 Mouse: always reports core events (==) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5 (**) PS/2 Mouse: Buttons: 9 (**) PS/2 Mouse: Sensitivity: 1 (II) XINPUT: Adding extended input device PS/2 Mouse (type: MOUSE) (**) PS/2 Mouse: (accel) keeping acceleration scheme 1 (**) PS/2 Mouse: (accel) filter chain progression: 2.00 (**) PS/2 Mouse: (accel) filter stage 0: 20.00 ms (**) PS/2 Mouse: (accel) set acceleration profile 0 (II) PS/2 Mouse: SetupAuto: hw.iftype is 3, hw.model is 0 (II) PS/2 Mouse: SetupAuto: protocol is PS/2 (II) PS/2 Mouse: ps2EnableDataReporting: succeeded No, I don't have a PS/2 Mouse. I have no idea why hald is removing my USB mouse and replacing it with a non-existent one. ]# grep -i keyboard /var/log/Xorg.0.log (II) Cannot locate a core keyboard device. (II) Initializing built-in extension XKEYBOARD (II) config/hal: Adding input device Microsoft Natural Keyboard Elite (**) Microsoft Natural Keyboard Elite: always reports core events (**) Microsoft Natural Keyboard Elite: Protocol: standard (**) Microsoft Natural Keyboard Elite: XkbRules: xorg (**) Microsoft Natural Keyboard Elite: XkbModel: microsoft (**) Microsoft Natural Keyboard Elite: XkbLayout: fr (**) Microsoft Natural Keyboard Elite: XkbOptions: terminate:ctrl_alt_bksp (**) Microsoft Natural Keyboard Elite: CustomKeycodes disabled (II) XINPUT: Adding extended input device Microsoft Natural Keyboard Elite (type: KEYBOARD) (II) config/hal: Adding input device AT Keyboard (**) AT Keyboard: always reports core events (**) AT Keyboard: Protocol: standard (**) AT Keyboard: XkbRules: xorg (**) AT Keyboard: XkbModel: microsoft (**) AT Keyboard: XkbLayout: fr (**) AT Keyboard: XkbOptions: terminate:ctrl_alt_bksp (**) AT Keyboard: CustomKeycodes disabled (II) XINPUT: Adding extended input device AT Keyboard (type: KEYBOARD) No, I have no idea why hal is adding an AT keyboard after installing my real keyboard. But disabling hal and dbus and adding input devices to the xorg.conf file doesn't change a thing. Paul Schmehl (pschmehl_li...@tx.rr.com) In case it isn't already obvious, my opinions are my own and not those of my employer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: recovering data from this disk
You might try freesbie. It's not a fixit shell, it's a full FreeBSD on a live CD. I've had better luck with it in the past than the fixit shell. Worth a shot. -Modulok- On 12/4/09, Tom Worster f...@thefsb.org wrote: On 12/4/09 1:51 PM, Henrik Hudson li...@rhavenn.net wrote: On Fri, 04 Dec 2009, Tom Worster wrote: any suggestions how to recover data from either of the mirrored disks that i can't get to boot? the situation is described below. If they were indeed mirrored then try a FreeBSD live distro boot CD and boot into that then just mount one of the disk partitions that you need. thanks, henrik, but i wasn't able to make the live fs fixit shell work. i get an error message when i try to start the live fs shell: ldconfig could not create the ld.so hints file and all commands fail to work. tom (i'm assuming, given the silence on this, that making the system work after the freebsd-update is a lost cause.) On 12/3/09 11:14 AM, Tom Worster f...@thefsb.org wrote: after running freebsd-update -r 8.0-RELEASE upgrade my system won't boot. it gets stuck on mountroot and i can't find the magic word it wants. the system used to have two sata drives /dev/ad4 and ad6. they were partitioned and sliced using the deafaults that sysinstall suggested. at the boot prompt, lsdev says: disk devices disk0: BIOS drive C: disk0s1a: FFS disk0s1b: swap disk0s1d: FFS disk0s1e: FFS disk0s1f: FFS disk1: BIOS drive D: disk1s1a: FFS disk1s1b: swap disk1s1d: FFS disk1s1e: FFS disk1s1f: FFS which looks right, although i'm not familiar with the disk nomenclature. entering ? at mountroot mentions ad4 and ad6. geom_mirror was being used. i've tried saying load geom_mirror and/or enable-module geom_mirror at the boot prompt. neither made any difference. nothing i've said to mountroot works: ufs:/dev/ad4s1a ufs:/dev/ad6s1a ufs:/dev/mirror/gm0s1a ufs:/dev/disk0s1a ufs:/dev/disk1s1a does anyone know the magic word? i'd be very grateful. tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Is there the equivalent of a Windows fast format for UFS?
On Fri, Dec 4, 2009 at 2:23 PM, Peter Steele pste...@maxiscale.com wrote: I suspect I know the answer to this question but I'll ask it anyway. We're dealing with some very large disks (11TB raid array) and a newfs operation takes a significant time. Is there any way to get a volume formatted faster than the typical newfs does? It's actually the other way around - there is only fast format for UFS. As far as I know, full format for FAT or NTFS also checks for bad sectors on the drive, so that's why Windows has that distinction. What you need to do is properly configure block/frag sizes and inode density. Figure out the average file size that will be stored on the volume and divide the total volume size by that number. That is the minimum number of inodes you should create, since one inode is required per file. Of course, you should aim higher since you will not be able to add more inodes without reformatting the system. Increasing block and fragment sizes may also help, depending on what type of files you are storing. Read tuning(7) and then newfs(8) for options -b, -f, and -i. - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8 portinstall gnome2 failure
Hello, BSD friends, After installing FreeBSD 8 (successful), I was unable to install gnome2. (from ports) Error was : I0 Error: [Errno 28] No space left on device. gmake [2] : *** [Gtk-2.0.gir] Error 1 I did found out, I had to empty .cache in root dir about 5/6 times though. When the install was complete, my log onscreen was unable to enter Username/Password, so all the work did not bring me complete happiness. Did anybody have these problems too ? Help appreciated ;) Regards, -- Dhondub Tsering. _ _ooOoo_ o888o 88 . 88 (| -_- |) O\ = /O /`---'\ .' \\| |// `. / \\||| : |||// \ / _| -:- |_ \ | | \\\ - /'| | | | \_| `\`---'// |_/ | \ .-\__ `-. -'__/-. / ___`. .' /--.--\ `. .'___ . ' `.___\_|_/___.' _ \. | | : `- \`. ;`. _/; .'/ / .' ; | \ \ `-. \_\_`. _.'_/_/ -' _.' / ===`-.`___`-.__\ \___ /__.-'_.'_.-' ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ep(4) after upgrade to 8.0
I updated one of my old servers to freebsd 8.0. After the upgrade my Etherlink III card will not allow connections into or out of the server. If I run tcpdump for a few seconds then everything works. I ran CVSUP twice to update to RELENG_8_0 and followed the source update procedure 3 times. I'm using a GENERIC kernel. What am I missing? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg - no mouse and no keyboard
Paul Schmehl wrote: I had a working Xorg config, and everything was fine. Then my monitors crapped out. I got new ones and installed them. No I have no mouse and no keyboard in Xorg. I've tried disabling hald and dbus and manually configuring them. That doesn't work either. What sort of troubleshooting steps do I need to take to figure out why they're not working and get them working again? Mouse and keyboard work find at the console. It's only in X that they don't work. I'm running 7.2-STABLE FreeBSD 7.2-STABLE #13. I've uninstalled and reinstalled xf86-input-keyboard, xf86-input-mouse and the radeonhd driver to no avail. I've searched the web for answers but haven't found any. Here's some stuff from the Xorg.0.log: # grep -i mouse /var/log/Xorg.0.log (==) RADEONHD(0): Silken mouse enabled (II) config/hal: Adding input device Optical USB Mouse (II) LoadModule: mouse (II) Loading /usr/local/lib/xorg/modules/input//mouse_drv.so (II) Module mouse: vendor=X.Org Foundation (**) Optical USB Mouse: Device: /dev/ums1 (==) Optical USB Mouse: Protocol: Auto (**) Optical USB Mouse: always reports core events (==) Optical USB Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) Optical USB Mouse: ZAxisMapping: buttons 4 and 5 (**) Optical USB Mouse: Buttons: 9 (**) Optical USB Mouse: Sensitivity: 1 (II) XINPUT: Adding extended input device Optical USB Mouse (type: MOUSE) (**) Optical USB Mouse: (accel) keeping acceleration scheme 1 (**) Optical USB Mouse: (accel) filter chain progression: 2.00 (**) Optical USB Mouse: (accel) filter stage 0: 20.00 ms (**) Optical USB Mouse: (accel) set acceleration profile 0 (II) Optical USB Mouse: SetupAuto: hw.iftype is 5, hw.model is 0 (II) Optical USB Mouse: SetupAuto: protocol is SysMouse (II) config/hal: removing device Optical USB Mouse (II) UnloadModule: mouse (II) config/hal: Adding input device PS/2 Mouse (**) PS/2 Mouse: Device: /dev/psm0 (==) PS/2 Mouse: Protocol: Auto (**) PS/2 Mouse: always reports core events (==) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5 (**) PS/2 Mouse: Buttons: 9 (**) PS/2 Mouse: Sensitivity: 1 (II) XINPUT: Adding extended input device PS/2 Mouse (type: MOUSE) (**) PS/2 Mouse: (accel) keeping acceleration scheme 1 (**) PS/2 Mouse: (accel) filter chain progression: 2.00 (**) PS/2 Mouse: (accel) filter stage 0: 20.00 ms (**) PS/2 Mouse: (accel) set acceleration profile 0 (II) PS/2 Mouse: SetupAuto: hw.iftype is 3, hw.model is 0 (II) PS/2 Mouse: SetupAuto: protocol is PS/2 (II) PS/2 Mouse: ps2EnableDataReporting: succeeded No, I don't have a PS/2 Mouse. I have no idea why hald is removing my USB mouse and replacing it with a non-existent one. ]# grep -i keyboard /var/log/Xorg.0.log (II) Cannot locate a core keyboard device. (II) Initializing built-in extension XKEYBOARD (II) config/hal: Adding input device Microsoft Natural Keyboard Elite (**) Microsoft Natural Keyboard Elite: always reports core events (**) Microsoft Natural Keyboard Elite: Protocol: standard (**) Microsoft Natural Keyboard Elite: XkbRules: xorg (**) Microsoft Natural Keyboard Elite: XkbModel: microsoft (**) Microsoft Natural Keyboard Elite: XkbLayout: fr (**) Microsoft Natural Keyboard Elite: XkbOptions: terminate:ctrl_alt_bksp (**) Microsoft Natural Keyboard Elite: CustomKeycodes disabled (II) XINPUT: Adding extended input device Microsoft Natural Keyboard Elite (type: KEYBOARD) (II) config/hal: Adding input device AT Keyboard (**) AT Keyboard: always reports core events (**) AT Keyboard: Protocol: standard (**) AT Keyboard: XkbRules: xorg (**) AT Keyboard: XkbModel: microsoft (**) AT Keyboard: XkbLayout: fr (**) AT Keyboard: XkbOptions: terminate:ctrl_alt_bksp (**) AT Keyboard: CustomKeycodes disabled (II) XINPUT: Adding extended input device AT Keyboard (type: KEYBOARD) No, I have no idea why hal is adding an AT keyboard after installing my real keyboard. But disabling hal and dbus and adding input devices to the xorg.conf file doesn't change a thing. Paul Schmehl (pschmehl_li...@tx.rr.com) In case it isn't already obvious, my opinions are my own and not those of my employer Have you tried adding AutoAddDevices false to your xorg.conf? Section ServerFlags Option AutoAddDevices false EndSection I had to do that until the latest hal update in order to get my wireless usb mouse and keyboard to work under X. Otherwise your settings for mouse and keyboard have no effect after X org 7.4. Colin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Samba3 - error during compile
Hi, Upon compiling samba3 (/usr/ports/net/samba3) from source I ran into the following error: -- Cut here -- . . . Compiling passdb/machine_sid.c Compiling locking/locking.c locking/locking.c: In function 'unparse_share_modes': locking/locking.c:701: error: invalid operands to binary - The following command failed: cc -I. -I/usr/ports/net/samba3/work/samba-3.0.37/source -O -pipe -DLDAP_DEPRECATED -D_SAMBA_BUILD_=3 -I/usr/local/include -I/usr/ports/net/samba3/work/samba-3.0.37/source/iniparser/src -Iinclude -I./include -I. -I. -I./lib/replace -I./lib/talloc -I./tdb/include -I./libaddns -I./librpc -DHAVE_CONFIG_H -I/usr/local/include -I/usr/local/include -DLDAP_DEPRECATED -I/usr/ports/net/samba3/work/samba-3.0.37/source/lib -D_SAMBA_BUILD_=3 -fPIC -DPIC -c locking/locking.c -o locking/locking.o *** Error code 1 Stop in /usr/ports/net/samba3/work/samba-3.0.37/source. *** Error code 1 Stop in /usr/ports/net/samba3. *** Error code 1 Stop in /usr/ports/net/samba3. # -- Cut here -- System: FreeBSD 7.2-STABLE #7 - amd64; kernel GENERIC Any ideas what could be wrong here? Any cure against this? Thanks much in advance for your help, -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Use of COMPAT Kernel Options
Hello, I'm working on editing the kernel configuration file for a custom kernel. The system will be running FreeBSD 8.0-RELEASE-p1. I'm wondering about the use of the COMPAT options in the kernel config. COMPAT_43 COMPAT_43TTY COMPAT_FREEBSD[4-7] I'm not aware of any software I use which requires certain compatibility with old system calls. The system will be running PHP, Nginx, PostgreSQL, InspIRCd, and other small applications (The latest stable releases of each). Is it recommended that I keep certain compatibility flags? If I recall correctly, previous documentation claimed that it was required to keep COMPAT_43TTY, but I no longer see this in the handbook. Thanks for the help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Use of COMPAT Kernel Options
On Fri, Dec 04, 2009 at 04:39:59PM -0500, APseudoUtopia wrote: Hello, I'm working on editing the kernel configuration file for a custom kernel. The system will be running FreeBSD 8.0-RELEASE-p1. I'm wondering about the use of the COMPAT options in the kernel config. COMPAT_43 Well, COMPAT_43 one isn't even in GENERIC anymore, so I guess it is not that important anymore. COMPAT_43TTY This is still in the GENERIC kernel. I'd keep it in initially. Then build a kernel without it. If that fails to start the system properly, you'll always have a good kernel to fall back on. Have a look at what is written under COMPATIBILITY OPTIONS in /sys/conf/NOTES. COMPAT_FREEBSD[4-7] If you do not have binaries from ealier FreeBSD versions around, you can skip these. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp3aoPXzrDzp.pgp Description: PGP signature
RE: Is there the equivalent of a Windows fast format for UFS?
Okay, thanks for the reply. I know where I need to go from here... -Original Message- From: Maxim Khitrov [mailto:mkhit...@gmail.com] Sent: Friday, December 04, 2009 12:23 PM To: Peter Steele Cc: freebsd-questions@freebsd.org Subject: Re: Is there the equivalent of a Windows fast format for UFS? On Fri, Dec 4, 2009 at 2:23 PM, Peter Steele pste...@maxiscale.com wrote: I suspect I know the answer to this question but I'll ask it anyway. We're dealing with some very large disks (11TB raid array) and a newfs operation takes a significant time. Is there any way to get a volume formatted faster than the typical newfs does? It's actually the other way around - there is only fast format for UFS. As far as I know, full format for FAT or NTFS also checks for bad sectors on the drive, so that's why Windows has that distinction. What you need to do is properly configure block/frag sizes and inode density. Figure out the average file size that will be stored on the volume and divide the total volume size by that number. That is the minimum number of inodes you should create, since one inode is required per file. Of course, you should aim higher since you will not be able to add more inodes without reformatting the system. Increasing block and fragment sizes may also help, depending on what type of files you are storing. Read tuning(7) and then newfs(8) for options -b, -f, and -i. - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Use of COMPAT Kernel Options
--- On Fri, 12/4/09, Roland Smith rsm...@xs4all.nl wrote: From: Roland Smith rsm...@xs4all.nl Subject: Re: Use of COMPAT Kernel Options To: APseudoUtopia apseudouto...@gmail.com Cc: FreeBSD Questions freebsd-questions@freebsd.org Date: Friday, December 4, 2009, 9:52 PM On Fri, Dec 04, 2009 at 04:39:59PM -0500, APseudoUtopia wrote: Hello, I'm working on editing the kernel configuration file for a custom kernel. The system will be running FreeBSD 8.0-RELEASE-p1. I'm wondering about the use of the COMPAT options in the kernel config. COMPAT_43 Well, COMPAT_43 one isn't even in GENERIC anymore, so I guess it is not that important anymore. COMPAT_43TTY This is still in the GENERIC kernel. I'd keep it in initially. Then build a kernel without it. If that fails to start the system properly, you'll always have a good kernel to fall back on. Have a look at what is written under COMPATIBILITY OPTIONS in /sys/conf/NOTES. COMPAT_FREEBSD[4-7] If you do not have binaries from ealier FreeBSD versions around, you can skip these. FWIW, a FreeBSD 8.0 kernel fails to build without COMPAT_FREEBSD7 so I'd keep that. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Use of COMPAT Kernel Options
On Fri, Dec 4, 2009 at 5:04 PM, Gardner Bell gbel...@rogers.com wrote: --- On Fri, 12/4/09, Roland Smith rsm...@xs4all.nl wrote: From: Roland Smith rsm...@xs4all.nl Subject: Re: Use of COMPAT Kernel Options To: APseudoUtopia apseudouto...@gmail.com Cc: FreeBSD Questions freebsd-questions@freebsd.org Date: Friday, December 4, 2009, 9:52 PM On Fri, Dec 04, 2009 at 04:39:59PM -0500, APseudoUtopia wrote: Hello, I'm working on editing the kernel configuration file for a custom kernel. The system will be running FreeBSD 8.0-RELEASE-p1. I'm wondering about the use of the COMPAT options in the kernel config. COMPAT_43 Well, COMPAT_43 one isn't even in GENERIC anymore, so I guess it is not that important anymore. COMPAT_43TTY This is still in the GENERIC kernel. I'd keep it in initially. Then build a kernel without it. If that fails to start the system properly, you'll always have a good kernel to fall back on. Have a look at what is written under COMPATIBILITY OPTIONS in /sys/conf/NOTES. COMPAT_FREEBSD[4-7] If you do not have binaries from ealier FreeBSD versions around, you can skip these. FWIW, a FreeBSD 8.0 kernel fails to build without COMPAT_FREEBSD7 so I'd keep that. It didn't for meI initially compiled with not a single COMPAT option before I sent the mail to this list. I wanted to inquire about it before I installed the kernel. But it did build with no COMPAT options at all ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Hardware migration and upgrade from 6.3 to 8.0 advice
On Fri, 04 Dec 2009 14:07:41 +0100 Frank Wissmann frank.wissman...@web.de wrote: Achilleas Mantzios schrieb: Hi! Hello, i am facing this situation, where i need to upgrade from my 6.3 i386 system, used as my main workstation, to a new hardware based on amd64 (phenom II x4). Well, you know that i386 is Intel, do you? No i386 is 32-bit, amd64 is 64-bit, Intel and AMD make both. All amd64 compatible processors are i386 compatible too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Where's Snapshots and pub.allbsd.org
Aloha, Anybody on the FreeBSD list know what has happened to the snapshots that have not been available on FreeBSD.org since last Sept.? Also what happened to pub.allbsd.org snapshots? Are there new URL's for current and daily snapshots to test? ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PF binat rule issue - feature or bug?
On Fri, Dec 04, 2009 at 10:41:20AM -0600, Greg Barniskis wrote:
Using 7.2-RELEASE-p4 i386 with GENERIC kernel, I've found (the hard way)
that if I have a pf.conf rule like
nat on $ext_if proto { tcp udp icmp } from $my_subnet \
to any - some.public.ip.num
then pfctl will perform the expected expansion of the listed protocols
into three separate NAT rules.
However, if I have a rule like
binat on $ext_if proto { tcp udp icmp } from $server_dmz_ip \
to any - $server_public_ip
then I will /only/ get one NAT rule, for TCP.
Then things like NTP, DNS and ping will fail, but the filtering rules
that permit such traffic will increment their byte, packet and state
counters like PF is working just fine (and I suppose in some sense that
the filtering part is). But only if I explicitly declare in pf.conf a
separate binat rule for each desired protocol, instead of listing them,
will things work as needed.
Feature or bug? If the former, it is not well documented that I could
see. I expected that a list of protocols for a binat rule would just
work, and pfctl certainly didn't mark it as bad syntax. If a bug, is
this a FreeBSD bug or OpenBSD?
The BNF grammar in pfconf(5) suggests that binat rules don't take a
list. Summarised:
nat-rule = ... proto ( proto-name | proto-number | { proto-list } )
binat-rule = ... proto ( proto-name | proto-number )
--
George
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Use of COMPAT Kernel Options
--- On Fri, 12/4/09, APseudoUtopia apseudouto...@gmail.com wrote: From: APseudoUtopia apseudouto...@gmail.com Subject: Re: Use of COMPAT Kernel Options To: Gardner Bell gbel...@rogers.com Cc: Roland Smith rsm...@xs4all.nl, FreeBSD Questions freebsd-questions@freebsd.org Date: Friday, December 4, 2009, 10:17 PM On Fri, Dec 4, 2009 at 5:04 PM, Gardner Bell gbel...@rogers.com wrote: --- On Fri, 12/4/09, Roland Smith rsm...@xs4all.nl wrote: From: Roland Smith rsm...@xs4all.nl Subject: Re: Use of COMPAT Kernel Options To: APseudoUtopia apseudouto...@gmail.com Cc: FreeBSD Questions freebsd-questions@freebsd.org Date: Friday, December 4, 2009, 9:52 PM On Fri, Dec 04, 2009 at 04:39:59PM -0500, APseudoUtopia wrote: Hello, I'm working on editing the kernel configuration file for a custom kernel. The system will be running FreeBSD 8.0-RELEASE-p1. I'm wondering about the use of the COMPAT options in the kernel config. COMPAT_43 Well, COMPAT_43 one isn't even in GENERIC anymore, so I guess it is not that important anymore. COMPAT_43TTY This is still in the GENERIC kernel. I'd keep it in initially. Then build a kernel without it. If that fails to start the system properly, you'll always have a good kernel to fall back on. Have a look at what is written under COMPATIBILITY OPTIONS in /sys/conf/NOTES. COMPAT_FREEBSD[4-7] If you do not have binaries from ealier FreeBSD versions around, you can skip these. FWIW, a FreeBSD 8.0 kernel fails to build without COMPAT_FREEBSD7 so I'd keep that. It didn't for meI initially compiled with not a single COMPAT option before I sent the mail to this list. I wanted to inquire about it before I installed the kernel. But it did build with no COMPAT options at all Error on my part, sorry for the noise. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Xorg - no mouse and no keyboard
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Colin Albert Sent: Friday, December 04, 2009 3:29 PM Cc: 'Free BSD Questions list' Subject: Re: Xorg - no mouse and no keyboard Have you tried adding AutoAddDevices false to your xorg.conf? Section ServerFlags Option AutoAddDevices false EndSection I had to do that until the latest hal update in order to get my wireless usb mouse and keyboard to work under X. Otherwise your settings for mouse and keyboard have no effect after X org 7.4. I should have posted my xorg.conf file. Yes, I have that in ServerFlags. Here's my current xorg.conf: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section ServerFlags Option DontZap No Option AllowEmptyInput No Option AutoAddDevices No EndSection Section Files ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ FontPath /usr/local/lib/X11/fonts/bitstream-vera/ FontPath /usr/local/lib/X11/fonts/TrueType/ EndSection # Make flash work correctly Section Extensions Option Composite Off EndSection Section Module Load GLcore EndSection Section DRI Group 0 Mode 0660 EndSection Section Monitor Identifier Monitor0 VendorName Dell Computer ModelNameDELL 2009W HorizSync30.0 - 83.0 VertRefresh 56.0 - 75.0 Option DPMS EndSection Section Monitor Identifier left EndSection Section Monitor Identifier right Option RightOf left EndSection Section Device Identifier Card0 Driver radeonhd VendorName ATI Technologies Inc BoardName RV610 Option Monitor-DVI-I_1/digital left Option Monitor-DVI-I_2/digital right BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Virtual 3360 1050 EndSubSection EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection And here's the one I had that was working: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 EndSection Section ServerFlags Option DontZap No EndSection Section Files ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ FontPath /usr/local/lib/X11/fonts/bitstream-vera/ FontPath /usr/local/lib/X11/fonts/TrueType/ EndSection # Make flash work correctly Section Extensions Option Composite Off EndSection Section Module Load GLcore EndSection Section DRI Group 0 Mode 0660 EndSection Section Monitor Identifier Monitor0 VendorName Dell Computer ModelNameDELL 2009W HorizSync30.0 - 83.0 VertRefresh 56.0 - 75.0 Option DPMS EndSection Section Monitor Identifier left EndSection Section Monitor Identifier right Option RightOf left EndSection Section Device Identifier Card0 Driver radeonhd VendorName ATI Technologies Inc BoardName RV610 Option Monitor-DVI-I_1/digital left Option Monitor-DVI-I_2/digital right BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Virtual 3360 1050 EndSubSection EndSection Paul Schmehl (pschmehl_li...@tx.rr.com) In case it isn't already obvious, my opinions are my own and not those of my employer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mount dump0 as ISO9660 filesystem?
On Thu, Dec 03, 2009 at 03:27:48PM -0800, Nerius Landys wrote: I heard somewhere that you can mount a dump as an ISO9660 filesystem, but I cannot find any Google answers on this subject. I took my dump in the following fashion: dump -0Lan -C 16 -f - /usr | gzip -2 | ssh-to-some-remote-location So, I have a file named dump0-var.gz. Your dump is just a regular file sitting on a hard drive with a file system that's already mounted. If you created an on-disk ISO image of that file, you'd have to mount the file system of that ISO image to read the file. If you burned the ISO image to a CD, you'd mount the CD's file system to read it. Either way, the file remains just a file, and is read using restore(8). I'll offer a guess that you're confusing things with tar(1) (which is often used for backups) and the recent changes. From the manpage: This implementation can extract from tar, pax, cpio, zip, jar, ar, and ISO 9660 cdrom images and can create tar, pax, cpio, ar, and shar archives. The above means you can now do nifty things like 'tar xvf mybackup.iso', and if you've configured a pre-processor for less(1), even niftier things like: less backup.tar.gz less backup.zip less backup.iso It's also possible you might be thinking of file system snapshots (which can be mounted). Check the Handbook for details. -- George ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Last login message
On Thu, Dec 03, 2009 at 03:16:54PM -0800, Nerius Landys wrote: When I ssh to my FreeBSD machine, I get something like this: Last login: Thu Dec 3 15:12:40 2009 from 11.22.33.44 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 7.1-RELEASE-p9 (DAFFY) #0: Thu Dec 3 11:33:28 PST 2009 ..where 11.22.33.44 is an IP address. However, sometimes, in place of an IP address I get a truncated hostname, for example daffy.nerius.co (note the last 'm' missing). I was wondering what controls this, meaning if I get an IP or a hostname, and why it's being truncated. If 'touch ~/.hushlogin' isn't what you're after, consider modifying sshd_flags in /etc/rc.conf. From sshd(8): -u len This option is used to specify the size of the field in the utmp structure that holds the remote host name. If the resolved host name is longer than len, the dotted decimal value will be used instead. This allows hosts with very long host names that over- flow this field to still be uniquely identified. Specifying -u0 indicates that only dotted decimal addresses should be put into the utmp file. -u0 may also be used to prevent sshd from making DNS requests unless the authentication mechanism or configuration requires it. Authentication mechanisms that may require DNS include RhostsRSAAuthentication, HostbasedAuthentication, and using a from=pattern-list option in a key file. Configuration options that require DNS include using a u...@host pattern in AllowUsers or DenyUsers. I count 'daffy.nerius.co' as 15. -- George ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mount dump0 as ISO9660 filesystem?
Your dump is just a regular file sitting on a hard drive with a file system that's already mounted. If you created an on-disk ISO image of that file, you'd have to mount the file system of that ISO image to read the file. If you burned the ISO image to a CD, you'd mount the CD's file system to read it. Either way, the file remains just a file, and is read using restore(8). I'll offer a guess that you're confusing things with tar(1) (which is often used for backups) and the recent changes. From the manpage: This implementation can extract from tar, pax, cpio, zip, jar, ar, and ISO 9660 cdrom images and can create tar, pax, cpio, ar, and shar archives. The above means you can now do nifty things like 'tar xvf mybackup.iso', and if you've configured a pre-processor for less(1), even niftier things like: less backup.tar.gz less backup.zip less backup.iso It's also possible you might be thinking of file system snapshots (which can be mounted). Check the Handbook for details. All I really want to do is take my dump file and see the files inside it, and do things with those files such as copy or md5sum (not edit). And I don't even know which tool do use to accomplish that. For example, if I took a dump 0 of /usr (which I did), I would like to see the file /usr/home/nlandys/.zshrc inside the dump, and then actually see (read) this file and/or copy it over scp or to another filesystem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mount dump0 as ISO9660 filesystem?
On Fri, Dec 04, 2009 at 04:50:43PM -0800, Nerius Landys wrote: Either way, the file remains just a file, and is read using restore(8). [snip] All I really want to do is take my dump file and see the files inside it, and do things with those files such as copy or md5sum (not edit). And I don't even know which tool do use to accomplish that. You still don't know which tool? -- George ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
x86info port complains cpuid driver not present
WARNING: Detected SMP, but unable to access cpuid driver. Used Uniprocessor CPU routines. Results inaccurate. I then installed port cpuid-3.3_5, but it still complains. I saw that x86info needs devcpu and devcpu-data. When I tried to install devcpu, it said it was already in the base system. devcpu-data wasn't so I installed that port. But the result is the same. Do I need to add something to rc.conf or somewhere else? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE and dangerously dedicated disks
Polytropon wrote: On Wed, 2 Dec 2009 13:09:22 -0500, Jerry McAllister jerr...@msu.edu wrote: Good. Except that in FreeBSD land you are talking about a slice table. To carry things forward consistently, the partition table is within a slice and describes FreeBSD partitions a..h (and more now I guess). Only in MS or Lunix land should primary divisions be called partitions and then they are _primary_ partitions. To be most precise, they are called DOS primary partitions. As far as I know, the need for them has been massively by MICROS~1 operating systems (DOS, Windows). That what FreeBSD calls partitions are subdivions of slices. A partition holds a file system (each), while a slice holds partitions. Those partitions could be compared to what MICROS~1 calls logical volumes inside a DOS extended partition, allthoug that's just a *comparison* and not an exact equivalent. But, even some of the fdisk and other documentation still mucks this up and occasionally refers to slices as partitions. Maybe we can come up with some new terminology like 'blobs' and 'dollops' to get away from the problem. Borrow some artificially created fantasy words from modern KDE or Gnome application development? :-) An idea that follows your inspiration could be: (old) slice = (new) primary partition eq. DOS primary partition (old) partition = (new) secondary partition, alt. (new) subpartition comp. logical volumes inside a DOS extended partition But it would help to get at least FreeBSD's documentation consistent, even if it uses the non-MICROS~1 names for things (which is very fine for me). Note that the limitation to 4 slices per disk - we remember that we are talking about DOS primary partitions here - is grounded in the fact that MICROS~1 stuff doesn't seem to be able to handle more than 4, a legacy restriction from the past. I've not yet tested if it's possible to create e. g. ad0s1, ad0s2, ad0s3, ad0s4 and ad0s5 with FreeBSD, but it should be possible. (Because multi-booting PCs respectively their operating systems eat up primary partitions like coockies, often people complain that they can't install FreeBSD because it requires a primary partition as well. Mostly, people don't have 4 OSes on their disks, but the one or two they often have (e. g. a Linux and a Windows) have already occupied adX0..adX3.) Hi all, Out of curiousity, I just tested to bsdlabel a disk I had lying around. In dangerously dedicated mode. No problem at all. I newfs'd it and mounted it. Also no problem. I haven't tried to boot from it though, but I may do that later, when I have nothing running that can't be halted. I did config -x /boot/kernel/kernel and I noticed that GEOM_PART_BSD was there, though I'm absolutely certain I haven't included it, and if I understand correctly, it shouldn't be there unless explicitly included? I'm running 8.0-RELEASE-p1 amd64 with a custom kernel config. However the kernel config file was more or less copied from 7.2, with just a little tweaking. I guess I should create a new one, using sys/conf/NOTES and sys/amd64/conf/NOTES as guidelines and sys/amd64/conf/GENERIC as template, but I haven't gotten around to that yet. Anyway, is GEOM_PART_BSD supposed to be there (I just checked, and noticed it's in sys/amd64/conf/DEFAULTS) or can I safely remove it? And will it, considering I migrated to gpt and zfs, be meaningful to remove it (e.g. will it make the kernel smaller or have any positive impact on zfs performance)? And should DD disks work except to boot from, or shouldn't they work at all? Sincerely, Rolf Nielsen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: binary upgrade 6.1 - 7.2/8.0
On Tue, Oct 27, 2009 at 02:01:04PM +, Robin Becker wrote: Is it feasible to upgrade a system from 6.1 to 7.2 or 8.0-RC1 and if yes what sequence of upgrades should I actually carry out ie is it feasible to do 6.1-6.2 and then 6.2 - 7.2 or should it be done in small steps? I didn't see anyone else responed so I give it a go. I thougth it was posible for the base but not the ports. And I thought binairy upgrade only works from releses not patches or RCs. I haven't done this my self, but got this info from the handbook / the list. -- Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Xorg - no mouse and no keyboard
I had to add the following when moving from Xorg 6 to 7 since moused no longer manages the mouse - hald and dbus do: In /etc/rc.conf # X11 7.4 #moused_enable=YES moused_enable=NO hald_enable=YES dbus_enable=YES which turns on hald and dbus. Mike Squires ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-questions Digest, Vol 287, Issue 13
Sorry about that (accidentally quoted most the Digest (issue 12) in a reply). Need to start using a real email client :( -james. __ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd 6.4 can't load kernel after upgrade
On Sat, Oct 31, 2009 at 07:04:55AM +0200, Manolis Kiagias wrote: oscar Seo wrote: I'm a beginner in freebsd. my machine consists of freebsd-6.4 + i386 bootstrap loader,+ windowmaker after upgrade freebsd-6.4 using sysinstall then reboot the system, I got an error message as follows +++ Loading /boot/defaults/loader.conf Unable to load a kernel! / can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. OK _ +++ You could try loading your old kernel. When you build a new kernel, your old kernel is preserved under /boot/kernel.old Type these commands in the loader prompt unload (probably not needed here) load kernel.old boot Because kernel.old is overwritten with each attemt you might mv /boot/kernel.old to /boot/kernel.good. This prevents you from being stuck with a system you can't boot. -- Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
tty problem after upgrade to 8.0
Ladies and Gentlemen, I completed the upgrade to FreeBSD 8.0 this afternoon and have an error plaguing me that I cannot solve. When the system is booted, I am receiving the following error. Dec 5 20:43:30 getty[902]: open /dev/ttyd0: No such file or directory However, when I run ps -ax | grep ttyd0, I see the following entry. 902 ?? I 0:00.00 /usr/libexec/getty std.9600 ttyd0 I have a modem connected to cuau0 for dial-in purposes. The /etc/ttys file contains the following entry to allow for dial-in access. # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyd0 /usr/libexec/getty std.9600 dialup on Any suggestions would be greatly appreciated. Thanks, Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Xorg - no mouse and no keyboard
--On December 4, 2009 8:10:08 PM -0600 Michael L. Squires mi...@siralan.org wrote: I had to add the following when moving from Xorg 6 to 7 since moused no longer manages the mouse - hald and dbus do: In /etc/rc.conf # X11 7.4 # moused_enable=YES moused_enable=NO hald_enable=YES dbus_enable=YES which turns on hald and dbus. As I mentioned in a previous post, I have tried it both with and without hald and dbus. Nothing works. moused_enable=NO is already set in /etc/defaults/rc.conf, so setting it in /etc/rc.conf won't change anything. Here's my current rc.conf: dbus_enable=YES hald_enable=YES Here's my current xorg.conf. This was working fine before I changed monitors. The only change I made was the Model of the monitor, which shouldn't affect mouse or keyboard behavior: ]# cat /etc/X11/xorg.conf Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 EndSection Section ServerFlags Option DontZap No EndSection Section Files ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ FontPath /usr/local/lib/X11/fonts/bitstream-vera/ FontPath /usr/local/lib/X11/fonts/TrueType/ EndSection # Make flash work correctly Section Extensions Option Composite Off EndSection Section Module Load GLcore EndSection Section DRI Group 0 Mode 0660 EndSection Section Monitor Identifier Monitor0 VendorName Dell Computer ModelNameDELL 2009W HorizSync30.0 - 83.0 VertRefresh 56.0 - 75.0 Option DPMS EndSection Section Monitor Identifier left EndSection Section Monitor Identifier right Option RightOf left EndSection Section Device Identifier Card0 Driver radeonhd VendorName ATI Technologies Inc BoardName RV610 Option Monitor-DVI-I_1/digital left Option Monitor-DVI-I_2/digital right BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Virtual 3360 1050 EndSubSection EndSection Here's my current Xorg.0.log (the relevant parts): # grep -i mouse /var/log/Xorg.0.log (==) RADEONHD(0): Silken mouse enabled (II) config/hal: Adding input device Optical USB Mouse (II) LoadModule: mouse (II) Loading /usr/local/lib/xorg/modules/input//mouse_drv.so (II) Module mouse: vendor=X.Org Foundation (**) Optical USB Mouse: Device: /dev/sysmouse (==) Optical USB Mouse: Protocol: Auto (**) Optical USB Mouse: always reports core events (**) Option Device /dev/sysmouse (==) Optical USB Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) Optical USB Mouse: ZAxisMapping: buttons 4 and 5 (**) Optical USB Mouse: Buttons: 9 (**) Optical USB Mouse: Sensitivity: 1 (II) XINPUT: Adding extended input device Optical USB Mouse (type: MOUSE) (**) Optical USB Mouse: (accel) keeping acceleration scheme 1 (**) Optical USB Mouse: (accel) filter chain progression: 2.00 (**) Optical USB Mouse: (accel) filter stage 0: 20.00 ms (**) Optical USB Mouse: (accel) set acceleration profile 0 (II) Optical USB Mouse: SetupAuto: hw.iftype is 4, hw.model is 0 (II) Optical USB Mouse: SetupAuto: protocol is SysMouse (II) config/hal: Adding input device PS/2 Mouse (**) PS/2 Mouse: Device: /dev/psm0 (==) PS/2 Mouse: Protocol: Auto (**) PS/2 Mouse: always reports core events (==) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5 (**) PS/2 Mouse: Buttons: 9 (**) PS/2 Mouse: Sensitivity: 1 (II) XINPUT: Adding extended input device PS/2 Mouse (type: MOUSE) (**) PS/2 Mouse: (accel) keeping acceleration scheme 1 (**) PS/2 Mouse: (accel) filter chain progression: 2.00 (**) PS/2 Mouse: (accel) filter stage 0: 20.00 ms (**) PS/2 Mouse: (accel) set acceleration profile 0 (II) PS/2 Mouse: SetupAuto: hw.iftype is 3, hw.model is 0 (II) PS/2 Mouse: SetupAuto: protocol is PS/2 (II) PS/2 Mouse: ps2EnableDataReporting: succeeded # grep -i keyboard /var/log/Xorg.0.log (II) Cannot locate a core keyboard device. (II) Initializing built-in extension XKEYBOARD (II) config/hal: Adding input device Microsoft Natural Keyboard Elite (**) Microsoft Natural Keyboard Elite: always reports core events (**) Microsoft Natural Keyboard Elite: Protocol: standard (**) Microsoft Natural Keyboard Elite: XkbRules: xorg (**) Microsoft Natural Keyboard Elite: XkbModel: pc105 (**) Microsoft Natural Keyboard Elite: XkbLayout: us (**) Microsoft Natural Keyboard Elite: CustomKeycodes disabled (II) XINPUT: Adding extended input device Microsoft Natural Keyboard Elite (type: KEYBOARD) (II)
Re: Xorg - no mouse and no keyboard
On Fri, Dec 4, 2009 at 10:20 PM, Paul Schmehl pschmehl_li...@tx.rr.comwrote: As I mentioned in a previous post, I have tried it both with and without hald and dbus. Nothing works. moused_enable=NO is already set in /etc/defaults/rc.conf, so setting it in /etc/rc.conf won't change anything. Here's my current rc.conf: dbus_enable=YES hald_enable=YES Leave hal and dbus on, make sure xorg-server is compiled with hal support. Make sure x input mouse and kb are installed. This is a working xorg.conf and log. Also you have to reboot after enabling dbus and hal. There is is a handbook entry on this. Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ EndSection Section Module Load extmod Load record Load dbe Load glx Load dri Load dri2 EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse OptionProtocol auto OptionDevice /dev/sysmouse OptionZAxisMapping 4 5 6 7 EndSection Section Monitor #DisplaySize 470 300# mm Identifier Monitor0 VendorName ACR ModelNameAcer AL2216W HorizSync30.0 - 82.0 VertRefresh 56.0 - 76.0 OptionDPMS EndSection Section Monitor #DisplaySize 470 300 # mm Identifier Monitor1 VendorName ACR ModelNameAcer AL2016W HorizSync30.0 - 82.0 VertRefresh 56.0 - 76.0 Option DPMS Option LeftOf Monitor0 EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option SWcursor # [bool] #Option HWcursor # [bool] #Option NoAccel# [bool] #Option ShadowFB # [bool] #Option VideoKey # i #Option FPDither # [bool] #Option FPScale# [bool] #Option CBLocation # str #Option CBSize # i #Option ScalingMode# str #Option EXAPixmaps # [bool] Identifier Card0 Driver nouveau VendorName nVidia Corporation BoardName G84 [GeForce 8600 GTS] BusID PCI:2:0:0 Option monitor-DVI-I-0 Monitor0 Option monitor-DVI-I-1 Monitor1 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 Virtual 3360 2100 EndSubSection EndSection X.Org X Server 1.6.1 Release Date: 2009-4-14 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.0-STABLE amd64 Current Operating System: FreeBSD galacticdominator.com 8.0-STABLE FreeBSD 8.0-STABLE #3: Tue Dec 1 20:04:51 CST 2009 a...@galacticdominator.com:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 03 December 2009 05:55:33PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Dec 3 22:13:55 2009 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout X.org Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/local/lib/X11/fonts/misc/ does not exist. Entry deleted from font path. (WW) The directory /usr/local/lib/X11/fonts/Type1/ does not exist. Entry deleted from font path. (WW) The directory /usr/local/lib/X11/fonts/100dpi/ does not exist. Entry deleted from font path. (WW) The
Re: Mount dump0 as ISO9660 filesystem?
On Fri, Dec 04, 2009 at 04:50:43PM -0800, Nerius Landys wrote: Either way, the file remains just a file, and is read using restore(8). [snip] All I really want to do is take my dump file and see the files inside it, and do things with those files such as copy or md5sum (not edit). And I don't even know which tool do use to accomplish that. You still don't know which tool? I see. For some reason I thought restore had to actually restore all the files, as in expand the dump into a collection of files and directories. I'll have a look at the man page. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Upgrade problem 6.1 - 6.4
I wanted to upgrade to 8.0 to take advantage of the USB code. I've run in to a compile problem going grom 6.1 to 6.2.0. I've copied sys/dev/twa from 7.0 in to the source of 6.2. Without this source it will not boot. # uname -a FreeBSD Server1.lan 6.1-RELEASE-p20 FreeBSD 6.1-RELEASE-p20 #0: Wed Nov 14 02:07:49 CET 2007 akrui...@server1.lan:/temp/obj/temp/src/sys/SERVER-SMP i386 # 'make buildworld' gives me: -- stage 1.2: bootstrap tools -- (...) c++ -O2 -fno-strict-aliasing -pipe -I/usr/obj/temp/src/tmp/legacy/usr/include -I/temp/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/temp/src/gnu/usr.bin/gperf -static -L/usr/obj/temp/src/tmp/legacy/usr/lib -o gperf bool-array.o gen-perf.o hash-table.o iterator.o key-list.o list-node.o main.o new.o options.o read-line.o trace.o vectors.o version.o hash.o -legacy gen-perf.o(.text+0x12f): In function `Gen_Perf::Gen_Perf()': : undefined reference to `_Unwind_Resume' : undefined reference to `_Unwind_Resume' gen-perf.o(.text+0xb8b): In function `Gen_Perf::~Gen_Perf()': : undefined reference to `_Unwind_Resume' gen-perf.o(.text+0xc53): In function `Gen_Perf::~Gen_Perf()': : undefined reference to `_Unwind_Resume' key-list.o(.text+0x583): In function `parse_line(char const*, char const*)': : undefined reference to `_Unwind_Resume' key-list.o(.text+0xb8e): more undefined references to `_Unwind_Resume' follow /usr/lib/libstdc++.a(eh_personality.o)(.text._Z21base_of_encoded_valuehP15_Unwind_Context+0x4a): In function `base_of_encoded_value(unsigned char, _Unwind_Context*)': : undefined reference to `_Unwind_GetRegionStart' /usr/lib/libstdc++.a(eh_personality.o)(.text._Z21base_of_encoded_valuehP15_Unwind_Context+0x55): In function `base_of_encoded_value(unsigned char, _Unwind_Context*)': : undefined reference to `_Unwind_GetTextRelBase' /usr/lib/libstdc++.a(eh_personality.o)(.text._Z21base_of_encoded_valuehP15_Unwind_Context+0x5f): In function `base_of_encoded_value(unsigned char, _Unwind_Context*)': : undefined reference to `_Unwind_GetDataRelBase' /usr/lib/libstdc++.a(eh_personality.o)(.text._Z17parse_lsda_headerP15_Unwind_ContextPKhP16lsda_header_info+0x19): In function `parse_lsda_header(_Unwind_Context*, unsigned char const*, lsda_header_info*)': : undefined reference to `_Unwind_GetRegionStart' /usr/lib/libstdc++.a(eh_personality.o)(.text.__cxa_call_unexpected+0xc5): In function `__cxa_call_unexpected': : undefined reference to `_Unwind_Resume' /usr/lib/libstdc++.a(eh_personality.o)(.text.__gxx_personality_v0+0x60): In function `__gxx_personality_v0': : undefined reference to `_Unwind_GetLanguageSpecificData' /usr/lib/libstdc++.a(eh_personality.o)(.text.__gxx_personality_v0+0x97): In function `__gxx_personality_v0': : undefined reference to `_Unwind_GetIP' /usr/lib/libstdc++.a(eh_personality.o)(.text.__gxx_personality_v0+0x205): In function `__gxx_personality_v0': : undefined reference to `_Unwind_SetGR' /usr/lib/libstdc++.a(eh_personality.o)(.text.__gxx_personality_v0+0x21c): In function `__gxx_personality_v0': : undefined reference to `_Unwind_SetGR' /usr/lib/libstdc++.a(eh_personality.o)(.text.__gxx_personality_v0+0x22e): In function `__gxx_personality_v0': : undefined reference to `_Unwind_SetIP' /usr/lib/libstdc++.a(eh_personality.o)(.text.__gxx_personality_v0+0x3b4): In function `__gxx_personality_v0': : undefined reference to `_Unwind_Resume' /usr/lib/libstdc++.a(new_opv.o)(.text._Znaj+0x21): In function `operator new[](unsigned int)': : undefined reference to `_Unwind_Resume' /usr/lib/libstdc++.a(eh_catch.o)(.text.__cxa_end_catch+0x50): In function `__cxa_end_catch': : undefined reference to `_Unwind_DeleteException' /usr/lib/libstdc++.a(eh_catch.o)(.text.__cxa_end_catch+0x7c): In function `__cxa_end_catch': : undefined reference to `_Unwind_DeleteException' /usr/lib/libstdc++.a(eh_catch.o)(.text.__cxa_begin_catch+0x96): In function `__cxa_begin_catch': : undefined reference to `_Unwind_Resume' /usr/lib/libstdc++.a(eh_alloc.o)(.text.__cxa_free_exception+0x278): In function `__cxa_free_exception': : undefined reference to `_Unwind_Resume' /usr/lib/libstdc++.a(eh_alloc.o)(.text.__cxa_allocate_exception+0x2b4): In function `__cxa_allocate_exception': : undefined reference to `_Unwind_Resume' /usr/lib/libstdc++.a(eh_throw.o)(.text.__cxa_rethrow+0x37): In function `__cxa_rethrow': : undefined reference to `_Unwind_Resume_or_Rethrow' /usr/lib/libstdc++.a(eh_throw.o)(.text.__cxa_throw+0x45): In function `__cxa_throw': : undefined reference to `_Unwind_RaiseException' /usr/lib/libstdc++.a(eh_terminate.o)(.text._ZN10__cxxabiv111__terminateEPFvvE+0x27): In function `__cxxabiv1::__terminate(void (*)())': : undefined reference to `_Unwind_Resume' /usr/lib/libstdc++.a(vterminate.o)(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x1b7): In function `__gnu_cxx::__verbose_terminate_handler()': : undefined reference
Re: Upgrade problem 6.1 - 6.4
On Fri, Dec 4, 2009 at 10:44 PM, Alex de Kruijff free...@akruijff.dds.nlwrote: I wanted to upgrade to 8.0 to take advantage of the USB code. I've run in to a compile problem going grom 6.1 to 6.2.0. I've copied sys/dev/twa from 7.0 in to the source of 6.2. Without this source it will not boot. I am unclear as to your goal. Seems like you want 8.0 but reference building 6.2 source. Why is that? -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: malformed man pages
Dan Nelson wrote: In the last episode (Dec 04), Sagara Wijetunga said: Hi FreeBSD community We have an issue on Tomahawk Desktop (an upcoming FreeBSD-based distro) that all man pages malformed. Eg. man tar shows as follows: 1mNAME0m 1mtar 22m-- format of tape archive files 1mDESCRIPTION0m The 1mtar 22marchive format collects any number of files, directories, and That looks sort of like malformed ANSI escape codes (bold would be ESC [ 1 m, but the man utilities shouldn't be generating those. If you run man 5 tar | hd | head, what do you get? I get this: 54 41 52 28 35 29 09 09 09 20 20 46 72 65 65 42 |TAR(5)... FreeB| 0010 53 44 20 46 69 6c 65 20 46 6f 72 6d 61 74 73 20 |SD File Formats | 0020 4d 61 6e 75 61 6c 09 09 09 54 41 52 28 35 29 0a |Manual...TAR(5).| 0030 0a 4e 08 4e 41 08 41 4d 08 4d 45 08 45 0a 20 20 |.N.NA.AM.ME.E. | 0040 20 20 20 74 08 74 61 08 61 72 08 72 20 2d 2d 20 | t.ta.ar.r -- | 0050 66 6f 72 6d 61 74 20 6f 66 20 74 61 70 65 20 61 |format of tape a| 0060 72 63 68 69 76 65 20 66 69 6c 65 73 0a 0a 44 08 |rchive files..D.| 0070 44 45 08 45 53 08 53 43 08 43 52 08 52 49 08 49 |DE.ES.SC.CR.RI.I| 0080 50 08 50 54 08 54 49 08 49 4f 08 4f 4e 08 4e 0a |P.PT.TI.IO.ON.N.| 0090 20 20 20 20 20 54 68 65 20 74 08 74 61 08 61 72 | The t.ta.ar| The doubled letters are handled by /usr/bin/less and converted to bold before displaying. If you get the same hd output as I have above, then we know that the manpage is fine, and your problem is in /usr/bin/less or your terminal type is incorrect. If you see ANSI escape codes in the hd output, then we know the problem is with the manpage tools. Here is what I get: man 5 tar | hd | head /usr/share/groff/1.20.1/tmac/doc.tmac:3375: bad character definition 54 41 52 28 35 29 09 09 09 20 20 20 20 42 53 44 |TAR(5)...BSD| 0010 20 46 69 6c 65 20 46 6f 72 6d 61 74 73 20 4d 61 | File Formats Ma| 0020 6e 75 61 6c 09 09 09 54 41 52 28 35 29 0a 0a 31 |nual...TAR(5)..1| 0030 6d 4e 41 4d 45 30 6d 0a 20 20 20 20 20 31 6d 74 |mNAME0m. 1mt| 0040 61 72 20 32 32 6d 2d 2d 20 66 6f 72 6d 61 74 20 |ar 22m-- format | 0050 6f 66 20 74 61 70 65 20 61 72 63 68 69 76 65 20 |of tape archive | 0060 66 69 6c 65 73 0a 0a 31 6d 44 45 53 43 52 49 50 |files..1mDESCRIP| 0070 54 49 4f 4e 30 6d 0a 20 20 20 20 20 54 68 65 20 |TION0m. The | 0080 31 6d 74 61 72 20 32 32 6d 61 72 63 68 69 76 65 |1mtar 22marchive| 0090 20 66 6f 72 6d 61 74 20 63 6f 6c 6c 65 63 74 73 | format collects| Error executing formatting or display command. system command exited with status 36096 No entry for tar in section 5 of the manual We use /usr/bin/less from ftp://ftp.gnu.org/gnu/less, the less-382.tar.gz, unpatched. Does the less need to be patched in FreeBSD? If so, is there such a patch exist? Regards Sagara ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Last login message
OK, I did some digging. Setting sshd_flags=-u 32 actually didn't change anything (and of course restarting sshd). I did have a look at this file though: /var/log/lastlog And I noticed that the truncated hostname is stored in that file. You can do a man lastlog or man utmp and it will indeed tell you that pam_lastlog does the writing to this file. No hint as to the truncation however. I did do an experiment by logging in from 2 different hosts which both have valid reverse IP lookups. r...@speedy# dig 249.164.240.216.in-addr.arpa PTR ; DiG 9.4.2-P2 249.164.240.216.in-addr.arpa PTR ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 49800 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;249.164.240.216.in-addr.arpa. IN PTR ;; ANSWER SECTION: 249.164.240.216.in-addr.arpa. 2500 IN PTR roadrunner.metaflex.com. ;; AUTHORITY SECTION: 164.240.216.in-addr.arpa. 2500 IN NS ns2.tiora.net. 164.240.216.in-addr.arpa. 2500 IN NS ns.tiora.net. ;; ADDITIONAL SECTION: ns2.tiora.net. 142262 IN A 216.240.164.132 ns.tiora.net. 142262 IN A 216.240.164.131 ;; Query time: 1 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Fri Dec 4 21:17:17 2009 ;; MSG SIZE rcvd: 159 and this one: r...@speedy# dig 169.192.156.64.in-addr.arpa PTR ; DiG 9.4.2-P2 169.192.156.64.in-addr.arpa PTR ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 12860 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;169.192.156.64.in-addr.arpa. IN PTR ;; ANSWER SECTION: 169.192.156.64.in-addr.arpa. 50462 IN PTR daffy.nerius.com. ;; AUTHORITY SECTION: 192.156.64.in-addr.arpa. 50462 IN NS ns2.m5hosting.com. 192.156.64.in-addr.arpa. 50462 IN NS ns3.m5hosting.com. ;; ADDITIONAL SECTION: ns3.m5hosting.com. 136862 IN A 209.216.230.5 ns2.m5hosting.com. 136862 IN A 209.216.206.167 ;; Query time: 1 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Fri Dec 4 21:18:09 2009 ;; MSG SIZE rcvd: 153 Strange thing is, when I log in to speedy from daffy.nerius.com, it logs the truncated hostname in /var/log/lastlog. When I log in to speedy from roadrunner.metaflex.com, it logs only the IP address in /var/log/lastlog. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [Solved] Having problems burning a DVD
--- On Fri, 12/4/09, Al Plant n...@hdk5.net wrote: From: Al Plant n...@hdk5.net Subject: Re: [Solved] Having problems burning a DVD To: James Phillips anti_spam...@yahoo.ca Cc: freebsd-questions@freebsd.org Received: Friday, December 4, 2009, 12:26 PM James Phillips wrote: SNIP! I noticed that the hash does not match the ISO file. Is that normal for DVDs? For CD images I often get the md5 hash to match. SNIP! Aloha JP, This is what I use on FreeBSD from the command line to burn DVD's. I have used it on FreeBSD 8* for a while. (Simple and it works.)- Yes, I got that far, hence the [Solved] tag. I was mainly concerned that I made a mess of my /boot/loader.conf I am also a little concerned that the DVD only reads a ~1.5MB/s (a little faster than 1x), but it appears to work. Burning happened at ~7x according to growisofs. Then Run # growisofs -dvd-compat -Z dev/cd0=/usr/home/alp/FreeBSD_7/7.2-RELEASE-p1-i386-disc1.iso (all on one line) Then Use cd0 as a DVD burner and make the DVD-R I tested the DVD on a spare box and it installed just fine. I found out why the checksum didn't match: the -dvd-compat option adds 6 2048 byte sectors of zeros to the end of the disk. So, I was able to verify the md5 sum by reading only the number of sectors present in the iso file. $ dd if=/dev/dvd bs=2048 count=996586 | md5 I noticed the size discrepancy while doing a binary search using the iseek (dd)(and count) argument(s) to narrow down the location of the corruption. Regards, James Phillips __ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
port math/mpfr update failure www.mpfr.org site seems to be down
Hi List; portupgrade mpfr --- Upgrading 'mpfr-2.4.1_1' to 'mpfr-2.4.2' (math/mpfr) --- Building '/usr/ports/math/mpfr' === Cleaning for mpfr-2.4.2 === Vulnerability check disabled, database not found = mpfr-2.4.2.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/mpfr. = Attempting to fetch from http://www.mpfr.org/mpfr-current/. fetch: http://www.mpfr.org/mpfr-current/mpfr-2.4.2.tar.bz2: Operation timed out = Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mpfr/. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20091205-2588-1gmko89-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=mpfr-2.4.1_1 UPGRADE_PORT_VER=2.4.1_1 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! math/mpfr (mpfr-2.4.1_1) (unknown build error) www.mpfr.org site seems to be down. I can't seem to find mpfr-2.4.2.tar.bz2 on any of the half dozen or so mirrors I manually checked nor is it mentioned in UPDATING or MOVED to try anything out of the ordinary. Shouldn't it be in the ports/distfiles on the mirror sites by now? Cheers, Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade problem 6.1 - 6.4
On Fri, Dec 04, 2009 at 10:56:19PM -0600, Adam Vande More wrote: On Fri, Dec 4, 2009 at 10:44 PM, Alex de Kruijff free...@akruijff.dds.nlwrote: I wanted to upgrade to 8.0 to take advantage of the USB code. I've run in to a compile problem going grom 6.1 to 6.2.0. I've copied sys/dev/twa from 7.0 in to the source of 6.2. Without this source it will not boot. I am unclear as to your goal. Seems like you want 8.0 but reference building 6.2 source. Why is that? /usr/src/UPDATING says: When upgrading from one major version to another it is generally best to upgrade to the latest code in the currently installed branch first, then do an upgrade to the new branch. This is the best-tested upgrade path, and has the highest probability of being successful. Please try this approach before reporting problems with a major version upgrade. Since 6.4 didn't work I tried 6.2 -- Alex Please copy the original recipients, otherwise I may not read your reply. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: malformed man pages
Sagara Wijetunga wrote: [snip] We use /usr/bin/less from ftp://ftp.gnu.org/gnu/less, the less-382.tar.gz, unpatched. Why? Does the less need to be patched in FreeBSD? If so, is there such a patch exist? Uhmm, this may sound a little strange, but why not use the one included as part of the system? In other words, there was no need to 'install' less. Remove whatever you installed and use the right one. It even has a man page, e.g., man less and you will see a man page for the included one unless you've made a total mess of your man pages. I suspect there may be a possibility of bringing Linuxisms to your approach to FreeBSD. While there may be some amount of crossover, FreeBSD is not Linux. Learn FreeBSD as if it were new to you and leave the Linuxisms aside. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: malformed man pages
Michael Powell wrote: Sagara Wijetunga wrote: [snip] We use /usr/bin/less from ftp://ftp.gnu.org/gnu/less, the less-382.tar.gz, unpatched. Why? Does the less need to be patched in FreeBSD? If so, is there such a patch exist? Uhmm, this may sound a little strange, but why not use the one included as part of the system? In other words, there was no need to 'install' less. Remove whatever you installed and use the right one. It even has a man page, e.g., man less and you will see a man page for the included one unless you've made a total mess of your man pages. I suspect there may be a possibility of bringing Linuxisms to your approach to FreeBSD. While there may be some amount of crossover, FreeBSD is not Linux. Learn FreeBSD as if it were new to you and leave the Linuxisms aside. -Mike In Tomahawk Desktop, we try to make as much as possible all components of the OS are separately installable by the user, therefore, all components are separately upgradeable. We have a really running well OS based on FreeBSD sources though there are some hopefully minor issues to be resolved. We are about to release the OS for developer preview. As the less we installed was too old, we have upgraded our less to less-436.tar.gz from http://www.greenwoodsoftware.com/less/. Again unpatched. The result is the same. Are we sure less is the culprit? Regards Sagara ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
which filrs/directories must be chowned bind?
I've just finished getting % nslookup 10.47.0.230 to respond, so at least my test configuration is finally right ... or on the right track. I am not certain that I ever had things chowned bind:bind; even before my '07 meltdown. Now it's time to make certain that every file that should be owned by bind really *is*. Anybody? tia, -g -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: tty problem after upgrade to 8.0
Jay Hall wrote: Ladies and Gentlemen, I completed the upgrade to FreeBSD 8.0 this afternoon and have an error plaguing me that I cannot solve. When the system is booted, I am receiving the following error. Dec 5 20:43:30 getty[902]: open /dev/ttyd0: No such file or directory However, when I run ps -ax | grep ttyd0, I see the following entry. 902 ?? I 0:00.00 /usr/libexec/getty std.9600 ttyd0 I have a modem connected to cuau0 for dial-in purposes. The /etc/ttys file contains the following entry to allow for dial-in access. # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyd0 /usr/libexec/getty std.9600 dialup on Any suggestions would be greatly appreciated. Thanks, Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org this will point you in the correct direction http://www.freebsd.org/cgi/query-pr.cgi?pr=140918 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: malformed man pages
In the last episode (Dec 05), Sagara Wijetunga said:
Dan Nelson wrote:
In the last episode (Dec 04), Sagara Wijetunga said:
We have an issue on Tomahawk Desktop (an upcoming FreeBSD-based distro)
that all man pages malformed.
Eg. man tar shows as follows:
1mNAME0m
1mtar 22m-- format of tape archive files
1mDESCRIPTION0m
The 1mtar 22marchive format collects any number of files,
directories, and
That looks sort of like malformed ANSI escape codes (bold would be ESC
[ 1 m, but the man utilities shouldn't be generating those. If you run
man 5 tar | hd | head, what do you get? I get this:
54 41 52 28 35 29 09 09 09 20 20 46 72 65 65 42 |TAR(5)...
FreeB|
0010 53 44 20 46 69 6c 65 20 46 6f 72 6d 61 74 73 20 |SD File
Formats |
0020 4d 61 6e 75 61 6c 09 09 09 54 41 52 28 35 29 0a
|Manual...TAR(5).|
0030 0a 4e 08 4e 41 08 41 4d 08 4d 45 08 45 0a 20 20 |.N.NA.AM.ME.E.
|
0040 20 20 20 74 08 74 61 08 61 72 08 72 20 2d 2d 20 | t.ta.ar.r
-- |
0050 66 6f 72 6d 61 74 20 6f 66 20 74 61 70 65 20 61 |format of tape
a|
0060 72 63 68 69 76 65 20 66 69 6c 65 73 0a 0a 44 08 |rchive
files..D.|
0070 44 45 08 45 53 08 53 43 08 43 52 08 52 49 08 49
|DE.ES.SC.CR.RI.I|
0080 50 08 50 54 08 54 49 08 49 4f 08 4f 4e 08 4e 0a
|P.PT.TI.IO.ON.N.|
0090 20 20 20 20 20 54 68 65 20 74 08 74 61 08 61 72 | The
t.ta.ar|
The doubled letters are handled by /usr/bin/less and converted to bold
before displaying. If you get the same hd output as I have above, then
we know that the manpage is fine, and your problem is in /usr/bin/less
or your terminal type is incorrect. If you see ANSI escape codes in the
hd output, then we know the problem is with the manpage tools.
Here is what I get:
man 5 tar | hd | head
/usr/share/groff/1.20.1/tmac/doc.tmac:3375: bad character definition
^ this looks suspicious. doc.tmac should live at /usr/share/tmac/doc.tmac
54 41 52 28 35 29 09 09 09 20 20 20 20 42 53 44 |TAR(5)...BSD|
0010 20 46 69 6c 65 20 46 6f 72 6d 61 74 73 20 4d 61 |File Formats Ma|
0020 6e 75 61 6c 09 09 09 54 41 52 28 35 29 0a 0a 31 |nual...TAR(5)..1|
0030 6d 4e 41 4d 45 30 6d 0a 20 20 20 20 20 31 6d 74 |mNAME0m. 1mt|
0040 61 72 20 32 32 6d 2d 2d 20 66 6f 72 6d 61 74 20 |ar 22m-- format |
0050 6f 66 20 74 61 70 65 20 61 72 63 68 69 76 65 20 |of tape archive |
0060 66 69 6c 65 73 0a 0a 31 6d 44 45 53 43 52 49 50 |files..1mDESCRIP|
0070 54 49 4f 4e 30 6d 0a 20 20 20 20 20 54 68 65 20 |TION0m. The |
0080 31 6d 74 61 72 20 32 32 6d 61 72 63 68 69 76 65 |1mtar 22marchive|
0090 20 66 6f 72 6d 61 74 20 63 6f 6c 6c 65 63 74 73 | format collects|
Error executing formatting or display command.
system command exited with status 36096
No entry for tar in section 5 of the manual
^ the above 3 lines you can ignore; man is just complaining because we
^ stopped reading its output after a few lines.
We use /usr/bin/less from ftp://ftp.gnu.org/gnu/less, the
less-382.tar.gz, unpatched.
Does the less need to be patched in FreeBSD? If so, is there such a
patch exist?
Since your output differs from mine, the manpages are getting damaged before
they reach /usr/bin/less.
Have you maybe installed your own copy of GNU groff? The original source
enables ANSI escapes in manpages, but the version in FreeBSD disables them.
Make sure your /usr/share/tmac/troffrc matches the content at
http://svn.freebsd.org/viewvc/base/stable/8/contrib/groff/tmac/troffrc?view=markup
, especially the last 10 lines or so, and check for other installations of
groff.
--
Dan Nelson
dnel...@allantgroup.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: malformed man pages
On Fri 04 Dec 2009 at 22:38:22 PST Sagara Wijetunga wrote: Michael Powell wrote: Sagara Wijetunga wrote: [snip] We use /usr/bin/less from ftp://ftp.gnu.org/gnu/less, the less-382.tar.gz, unpatched. Why? Does the less need to be patched in FreeBSD? If so, is there such a patch exist? Uhmm, this may sound a little strange, but why not use the one included as part of the system? In other words, there was no need to 'install' less. Remove whatever you installed and use the right one. It even has a man page, e.g., man less and you will see a man page for the included one unless you've made a total mess of your man pages. I suspect there may be a possibility of bringing Linuxisms to your approach to FreeBSD. While there may be some amount of crossover, FreeBSD is not Linux. Learn FreeBSD as if it were new to you and leave the Linuxisms aside. -Mike In Tomahawk Desktop, we try to make as much as possible all components of the OS are separately installable by the user, therefore, all components are separately upgradeable. We have a really running well OS based on FreeBSD sources though there are some hopefully minor issues to be resolved. We are about to release the OS for developer preview. In other words, you're only using the kernel from FreeBSD, but replacing all or most of the userland stuff with your own versions? Not only the stuff in /usr/local/bin but also stuff in /usr/bin? As Michael said, that's a Linuxism. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
