Re: radiusd-cistron
On 11/19/2011 10:38 PM, Jim Pazarena wrote: I recently switched from FBSD 7.0 i386 to FBSD 8.2 amd64 my radius only sees garbage in place of the password, so no one can authenticate. Since I changed both OS (7.0-8.2) AND platform (i386-amd64), I am unsure where to start looking for an encryption problem. Any suggestions would be appreciated. Yes, I could switch to freeradius, but would that change/help an encryption issue? I am not sure if cistron works correctly on 64bit architectures. Is plain text authentication working? Cistron is unmaintained, but there is a very low traffic mailing list, you could ask there. http://lists.cistron.nl/mailman/listinfo/cistron-radius HTH, Nikos ___ 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: where to ask about problems with bsdinstall in 9.0RC2?
from William Bulley w...@umich.edu: Possible, but unlikely. Plus I doubt that 'tar -tvf base.txz' without a pipe having an xzcat(1) in front of the tar(1) command. Maybe there is an xz option for tar(1) during extraction mode, but my tar(1) man page doesn't list any, sigh... It does list -y and -z options for other compression/decompression modes, hmmm :-( It looks like tar in extraction mode automatically recognizes xz compression in the file to be extracted from. Section from the man page for tar in FreeBSD 9.0-RC1: -J, --xz (c mode only) Compress the resulting archive with xz(1). In extract or list modes, this option is ignored. Note that, unlike other tar implementations, this implementation recognizes XZ com- pression automatically when reading archives. 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: epson printers on amd64
On Saturday 19 November 2011 21:27:42 Warren Block wrote: On Sun, 20 Nov 2011, per...@pluto.rain.com wrote: Warren Block wbl...@wonkity.com wrote: On Sat, 19 Nov 2011, David Southwell wrote: Anyone up to date on how to do high quality printing with epson inkjet printers (in my case r2400 and r2880) on amd64 systems. print/pips* reports they require 386 and do not compile on amd64. print/gimp-gutenprint works pretty well from Gimp, although I have not figured out how to get consistent color and brightness. It supports both of those printers. I'm sure I'm not alone in doubting that _any_ ink-spitter is likely to produce high quality printing or consistent color and brightness, regardless of the host support used. Those printers are designed to be manufactured as inexpensively as possible so as to be sold at very low prices, the profit being in the recurring ink sales. Cheap and high quality tend to be incompatible design goals. (Sorry, I hadn't realized I was replying on -emulation, which is meant for computer emulation. CCed to -questions on this reply.) Quality color photos are the one area where inkjets really can do a good job. Experimenting with cheap Epson R200 and R280 has shown that they can print better quality photos than local photo printing places. Color and brightness are consistent until I print a different photo. Gutenprint saves the settings, it's just that they don't work the same with different photos. Possibly this is due to my changing the wrong adjustments. Oh, and I've only used Gutenprint on 32-bit systems so far. To get high quality printing with good inkjet printeres like r2400 and r2880 here are the main steps I follow: 1. Define the colour space (e.g adobe rgb 1998) to be used when the image is being captured. 2. Shoot using the correct white space setting for the scene. 3. Load onto the computer having first profiled your monitor. 4. Use your preferred editing software (e.g. photoshop) using a defined working space colour profile e.g. adobe 1998 (I prefer prophoto which is 32bit floating decimal point). 5. Convert the colour profile of the image to the working colour space. 6. Process the image. 7. When processing complete choose the paper for printing. 8. Make sure you have a suitable colour profile for that paper for your chosen printer. 9. Print using the appropriate paper profile. . ___ 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: epson printers on amd64
On Sunday 20 November 2011 01:33:53 David Southwell wrote: On Saturday 19 November 2011 21:27:42 Warren Block wrote: On Sun, 20 Nov 2011, per...@pluto.rain.com wrote: Warren Block wbl...@wonkity.com wrote: On Sat, 19 Nov 2011, David Southwell wrote: Anyone up to date on how to do high quality printing with epson inkjet printers (in my case r2400 and r2880) on amd64 systems. print/pips* reports they require 386 and do not compile on amd64. print/gimp-gutenprint works pretty well from Gimp, although I have not figured out how to get consistent color and brightness. It supports both of those printers. I'm sure I'm not alone in doubting that _any_ ink-spitter is likely to produce high quality printing or consistent color and brightness, regardless of the host support used. Those printers are designed to be manufactured as inexpensively as possible so as to be sold at very low prices, the profit being in the recurring ink sales. Cheap and high quality tend to be incompatible design goals. (Sorry, I hadn't realized I was replying on -emulation, which is meant for computer emulation. CCed to -questions on this reply.) Quality color photos are the one area where inkjets really can do a good job. Experimenting with cheap Epson R200 and R280 has shown that they can print better quality photos than local photo printing places. Color and brightness are consistent until I print a different photo. Gutenprint saves the settings, it's just that they don't work the same with different photos. Possibly this is due to my changing the wrong adjustments. Oh, and I've only used Gutenprint on 32-bit systems so far. To get high quality printing with good inkjet printeres like r2400 and r2880 here are the main steps I follow: 1. Define the colour space (e.g adobe rgb 1998) to be used when the image is being captured. 2. Shoot using the correct white space setting for the scene. 3. Load onto the computer having first profiled your monitor. 4. Use your preferred editing software (e.g. photoshop) using a defined working space colour profile e.g. adobe 1998 (I prefer prophoto which is 32bit floating decimal point). 5. Convert the colour profile of the image to the working colour space. 6. Process the image. 7. When processing complete choose the paper for printing. 8. Make sure you have a suitable colour profile for that paper for your chosen printer. 9. Print using the appropriate paper profile. Sorry I should have mentioned that ghostscript are integrating colour profiling using icc profiles although the last time I checked there was no support for the kind of monitor profile creation devices such as those manufactured by datacolor which I use on I hate to say it MS$ systems. There is an interesting paper on Ghostscript Color Management to be found on www.artifex.com/Ghostscript_Color_Architecture.pdf david ___ 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: file system on 9.0
from darc...@gmail.com (Denise H. G.): I strongly advise that /usr and /usr/local reside on different partitions. Furthermore, If you plan to run a desktop environment, your /usr/local should be big enough, say 8G - 10G, to hold all stuff you built from the ports. And putting /var on a separate partitiion is a good idea, I think. You can find detailed information on how to lay out and size your partitions in tuning(7) either locally or online. The one directory I really want to put on a separate partition is /home . That way, you can fully rebuild/redo your system and keep user data. I don't like to put /var on a separate partition because of the danger of running short of space. I had nervous moments when running freebsd-update on the older computer and seeing the used part of /var grow. I don't really see a need to put /usr/local on a separate partition, though conceivably you could build applications with both FreeBSD ports and NetBSD pkgsrc, but keep these separate. NetBSD pkgsrc has been ported to other (quasi-)Unixes including FreeBSD. Default directory corresponding to FreeBSD's /usr/local is /usr/pkg . I think I like FreeBSD ports better than NetBSD pkgsrc, the latter which I used only with NetBSD. I originally installed FreeBSD 9.0-BETA1 using bsdinstall on the USB stick, including the ports. There was a conflict when I ran portsnap fetch update, that didn't work. I had to run portsnap fetch and portsnap extract, scrapping the ports tree from bsdinstall in favor of the fresh ports tree. So now I know best to not install ports tree from bsdinstall; this would presumably apply for sysinstall too. 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: The results of your email commands
I saw that the usb device is like a scsi da so now I am trying this: # mount -t msdosfs /dev/da0 /mnt/usb mount_msdosfs: /dev/da0: Invalid argument now what? how I have to refered on my usb device? I do not understand a word here! thanx! 2011/11/19 owner-freebsd-questi...@freebsd.org The results of your email command are provided below. Attached is your original message. - Results: Ignoring non-text/plain MIME parts - Unprocessed: doing the follow: First I am giving: mkdir mnt/usb and then I am giving: mount -t msdos /dev/usb /mnt/usb but I am seeing this on my screen: mount: Using -t msdosfs, since -t msdos is deprecated. mount_msdosfs: /dev/usb: Block device required I also trying: mount -t msdosfs /dev/usb /mnt/usb But I am getting the same message: mount_msdosfs: /dev/usb: Block device required Any suggestions please? Because I am lost here, I have NO idea... Thanx! - Done. -- Messaggio inoltrato -- From: thanos trompoukis atr0...@gmail.com To: freebsd-questions-requ...@freebsd.org Date: Sat, 19 Nov 2011 17:33:09 +0200 Subject: Can't mount usb disk Hi, I have freebsd 8.2 and I am trying to mount an external usb disk doing the follow: First I am giving: mkdir mnt/usb and then I am giving: mount -t msdos /dev/usb /mnt/usb but I am seeing this on my screen: mount: Using -t msdosfs, since -t msdos is deprecated. mount_msdosfs: /dev/usb: Block device required I also trying: mount -t msdosfs /dev/usb /mnt/usb But I am getting the same message: mount_msdosfs: /dev/usb: Block device required Any suggestions please? Because I am lost here, I have NO idea... Thanx! ___ 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
What happens with lang/gnustep-base in FreeBSD 9?
Hi all, I'm currently running the 9.0 RC1 version of FreeBSD and the lang/gnustep-base cannot be installed: it says I need an Objective C compiler but I actually do: clang version 3.0 is an Objective-C compiler too. So what's wrong here? Are there any license issues or something? Thanks, Antonio P.S.: Technical details antonio:/usr/ports/lang/gnustep-base# make === gnustep-base-1.19.3_5 needs an objective C compiler. *** Error code 1 Stop in /usr/ports/lang/gnustep-base. antonio:/usr/ports/lang/gnustep-base# clang --version FreeBSD clang version 3.0 (trunk 135360) 20110717 Target: i386-unknown-freebsd9.0 Thread model: posix ___ 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
Interrupts statistic differ
Hi Why statistic for total interrupts are differ? 38178 total in case of 'systat -v' 33309 Total in case of 'vmstat -i' # systat -v 1 usersLoad 1.78 1.76 1.86 Nov 20 13:48 Mem:KBREALVIRTUAL VN PAGER SWAP PAGER Tot Share TotShareFree in out in out Act 703196 14508 228552819332 1041760 count 19 All 878044 23120 449418864368 pages 20 Proc:Interrupts r p d s w Csw Trp Sys Int Sof Flt463 cow 38178 total 2 149 201k 9402 37k 21k 30k 3187 1778 zfod 22 ata0 14 93 ozfod 1 ehci0 16 11.9%Sys 27.8%Intr 7.3%User 0.0%Nice 53.0%Idle 5%ozfod 2 ehci1 23 ||||||||||| daefr 4128 cpu0:timer ==++ 1129 prcfr 21641 re0 256 115 dtbuf 2374 totfr 4128 cpu1:timer Namei Name-cache Dir-cache142271 desvn react 4128 cpu3:timer Callshits %hits % 92587 numvn pdwak 4128 cpu2:timer 45539 45539 100 35556 frevn pdpgs intrn Disks ad0 da0 pass0287660 wire KB/t 19.37 0.00 0.00275972 act tps 22 0 0 2386196 inact MB/s 0.42 0.00 0.00 244 cache %busy 2 0 0 1041516 free # vmstat -i interrupt total rate irq14: ata0 1393012 7 irq16: ehci0 299862 1 irq23: ehci1 442436 2 cpu0:timer 775750767 4122 irq256: re0 3196247374 16986 cpu1:timer 769445708 4089 cpu3:timer 752495866 3999 cpu2:timer 771600218 4100 Total 6267675243 33309 -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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: epson printers on amd64
On Sunday 20 November 2011 01:58:07 David Southwell wrote: On Sunday 20 November 2011 01:33:53 David Southwell wrote: On Saturday 19 November 2011 21:27:42 Warren Block wrote: On Sun, 20 Nov 2011, per...@pluto.rain.com wrote: Warren Block wbl...@wonkity.com wrote: On Sat, 19 Nov 2011, David Southwell wrote: Anyone up to date on how to do high quality printing with epson inkjet printers (in my case r2400 and r2880) on amd64 systems. print/pips* reports they require 386 and do not compile on amd64. print/gimp-gutenprint works pretty well from Gimp, although I have not figured out how to get consistent color and brightness. It supports both of those printers. I'm sure I'm not alone in doubting that _any_ ink-spitter is likely to produce high quality printing or consistent color and brightness, regardless of the host support used. Those printers are designed to be manufactured as inexpensively as possible so as to be sold at very low prices, the profit being in the recurring ink sales. Cheap and high quality tend to be incompatible design goals. (Sorry, I hadn't realized I was replying on -emulation, which is meant for computer emulation. CCed to -questions on this reply.) Quality color photos are the one area where inkjets really can do a good job. Experimenting with cheap Epson R200 and R280 has shown that they can print better quality photos than local photo printing places. Color and brightness are consistent until I print a different photo. Gutenprint saves the settings, it's just that they don't work the same with different photos. Possibly this is due to my changing the wrong adjustments. Oh, and I've only used Gutenprint on 32-bit systems so far. To get high quality printing with good inkjet printeres like r2400 and r2880 here are the main steps I follow: 1. Define the colour space (e.g adobe rgb 1998) to be used when the image is being captured. 2. Shoot using the correct white space setting for the scene. 3. Load onto the computer having first profiled your monitor. 4. Use your preferred editing software (e.g. photoshop) using a defined working space colour profile e.g. adobe 1998 (I prefer prophoto which is 32bit floating decimal point). 5. Convert the colour profile of the image to the working colour space. 6. Process the image. 7. When processing complete choose the paper for printing. 8. Make sure you have a suitable colour profile for that paper for your chosen printer. 9. Print using the appropriate paper profile. Sorry I should have mentioned that ghostscript are integrating colour profiling using icc profiles although the last time I checked there was no support for the kind of monitor profile creation devices such as those manufactured by datacolor which I use on I hate to say it MS$ systems. There is an interesting paper on Ghostscript Color Management to be found on www.artifex.com/Ghostscript_Color_Architecture.pdf OK thanks to you guys asking some questions I have found that graphics/lprof-devel can support the creation of monitor and print profiles using Spyder 2 Spyder 3 from datacolor. I have been a bit lazy in following up my earlier interest in profiling monitors on freebsd 7.2 8.2 as I would like to reduce my reliance on MS$ and apple systems. It looks like I missed this one which is being compiled as I speak. I will try forcing a compile of the 32bit code for the epson r2400 r2880 which I am told may compile on 64bit given some work. I will report back if I finish up with a viable system. David ___ 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
Wine-fbsd64 updated to 1.3.33 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.33 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessable). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.33,1.tbz) = a3eb5e2b32b8c7fa91e67aecee1cc197 MD5 (freebsd9/wine-fbsd64-1.3.33,1.txz) = 0a1b483fc8ee107653586aa56d464814 [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Re: file system on 9.0
On 2011/11/20 at 19:25, Thomas Mueller mueller6...@bellsouth.net wrote: from darc...@gmail.com (Denise H. G.): I strongly advise that /usr and /usr/local reside on different partitions. Furthermore, If you plan to run a desktop environment, your /usr/local should be big enough, say 8G - 10G, to hold all stuff you built from the ports. And putting /var on a separate partitiion is a good idea, I think. You can find detailed information on how to lay out and size your partitions in tuning(7) either locally or online. The one directory I really want to put on a separate partition is /home . That way, you can fully rebuild/redo your system and keep user data. Yes. I always put /home on a separate partition. Actually, my /home is on a ZFS partition which is of more scalability and easier snapshots. I don't like to put /var on a separate partition because of the danger of running short of space. I had nervous moments when running freebsd-update on the older computer and seeing the used part of /var grow. I always size /var to 2G or 3G, which is typical for me. I seldom run freebsd-update, but upgrade from sources instead. I only encountered problems with Xorg that crashed filling up /var with core dumps... I don't really see a need to put /usr/local on a separate partition, though conceivably you could build applications with both FreeBSD ports and NetBSD pkgsrc, but keep these separate. NetBSD pkgsrc has been ported to other (quasi-)Unixes including FreeBSD. Default directory corresponding to FreeBSD's /usr/local is /usr/pkg . It is long before I started thinking of joining /usr and /usr/local into one partition. However, my current installation dates back to FreeBSD 6 or 7. Many things changed exept the filesystem layout. I think I like FreeBSD ports better than NetBSD pkgsrc, the latter which I used only with NetBSD. I originally installed FreeBSD 9.0-BETA1 using bsdinstall on the USB stick, including the ports. There was a conflict when I ran portsnap fetch update, that didn't work. I had to run portsnap fetch and portsnap extract, scrapping the ports tree from bsdinstall in favor of the fresh ports tree. So now I know best to not install ports tree from bsdinstall; this would presumably apply for sysinstall too. I guess 'portsnap fetch update' is run only after the ports tree is there. For a fresh install of the ports tree, 'portsnap fetch extract' is the correct way. For me, I only pull the ports tree with 'portsnap'. That way, I can complete a fresh install of FreeBSD in less than 20 minutes. Tom -- If you've got them by the balls, their hearts and minds will follow. ___ 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
journal timestamp fsck error amd64
Hello, An amd64 running fbsd9-RC1 was shutdown overnight from the 'shutdown -p' command. It reported an unclean shutdown and I ran 'fsck -y'. Still it will not boot and the message is Journal timestamp does not match fs mount time. This is occurring for both /var and /usr. How can I fix this? Thanks, Darrel ___ 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
journal timestamp fsck error amd64
Hello, An amd64 running fbsd9-RC1 was shutdown overnight from the 'shutdown -p now' command. It reported an unclean shutdown and I ran 'fsck -y'. Still it will not boot and the message is Journal timestamp does not match fs mount time. This is occurring for both /var and /usr. How can I fix this? Thanks, Darrel ___ 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: The results of your email commands
On Sun, 20 Nov 2011 13:17:23 +0200, thanos trompoukis wrote: I saw that the usb device is like a scsi da so now I am trying this: # mount -t msdosfs /dev/da0 /mnt/usb mount_msdosfs: /dev/da0: Invalid argument now what? how I have to refered on my usb device? I do not understand a word here! Depending on he partitioning of the USB media, it's possible to access /dev/da0s1 instead of /dev/da0. The command # fdisk da0 lists the partitioning information. According to the example above, you can # mount -t msdosfs /dev/da0s1 /mnt/usb There is a section in the FreeBSD Handbook discussing the topic of how to access MS-DOS formatted media per USB. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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.2-RELEASE-p4
If I'm the OP (original poster ?) I'm running GENERIC, and 'uname -a' output has remained '8.2-RELEASE-p4' despite running 'freebsd-update fetch', 'freebsd-update install', and then rebooting the system, over the past couple of weeks. I did download the source, ran 'freebsd-update fetch' and 'freebsd-update install' to update the source, then compiled a new kernel using the GENERIC config file, rebooted, and now 'uname -a' output shows the '-p4' version number, but I was trying to avoid compiling kernels. -Tom Carpenter On 11/20/2011 02:37 AM, Matthew Seaman wrote: On 19/11/2011 23:26, Robert Simmons wrote: On Fri, Nov 18, 2011 at 3:50 PM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: If you compile your own kernel, then freebsd-update will patch the kernel sources, but leave you to rebuild and reinstall your customized kernel. I don't know about the -p4 update. By rights it should have involved updating the kernel by one or other of the two methods shown. So far however, we've seen two reports questioning that[*] and none saying that the -p4 update did in fact update the kernel. Which is suspicious, but hardly conclusive. Do you compile your own kernel, or do you have a machine that uses GENERIC? If you do, what is the output of uname -a on it? Me personally? No, in general I track -STABLE on my systems. Try asking the OP. Matthew ___ 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: The results of your email commands
From owner-freebsd-questi...@freebsd.org Sun Nov 20 05:44:42 2011 Date: Sun, 20 Nov 2011 13:17:23 +0200 From: thanos trompoukis atr0...@gmail.com To: freebsd-questions@freebsd.org Subject: Re: The results of your email commands I saw that the usb device is like a scsi da so now I am trying this: # mount -t msdosfs /dev/da0 /mnt/usb mount_msdosfs: /dev/da0: Invalid argument now what? how I have to refered on my usb device? I do not understand a word here! The following is a 'catch *everything*' approch. There are less-drastic ways, bud you don't provide enough information to determine what short-cuts are possible. *FIRST* _shut_down_ the machine. Next, remove the USB device. Now, turn on the machine and boot into FreeBSD. Do an 'ls -l' of the /dev directory. save the output to a file in your home directory. Plug in the USB device. Did you get system log and/or console messages about a new USB device? (if not, you may be missing USB device suport from the kernel0 Again, do an 'ls -l' of the /dev directoy. Save the output to a *differnt* file in your home directory. Look for device entries that are mentioned in _this_ list, that are *not* in the list you got when the USB device was not connected. *THOSE* are the possible devices for the 'mount' command you are trying. ___ 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: file system on 9.0
On Sun, Nov 20, 2011 at 11:25:35AM +, Thomas Mueller wrote: from darc...@gmail.com (Denise H. G.): I strongly advise that /usr and /usr/local reside on different partitions. Furthermore, If you plan to run a desktop environment, your /usr/local should be big enough, say 8G - 10G, to hold all stuff you built from the ports. And putting /var on a separate partitiion is a good idea, I think. I don't like to put /var on a separate partition because of the danger of running short of space. I had nervous moments when running freebsd-update on the older computer and seeing the used part of /var grow. For that very reason, I put /var on a separate partition. Stuff being written to /var is most likely to over run stuff and trash a / partition. jerry I don't really see a need to put /usr/local on a separate partition, though conceivably you could build applications with both FreeBSD ports and NetBSD pkgsrc, but keep these separate. NetBSD pkgsrc has been ported to other (quasi-)Unixes including FreeBSD. Default directory corresponding to FreeBSD's /usr/local is /usr/pkg . I think I like FreeBSD ports better than NetBSD pkgsrc, the latter which I used only with NetBSD. I originally installed FreeBSD 9.0-BETA1 using bsdinstall on the USB stick, including the ports. There was a conflict when I ran portsnap fetch update, that didn't work. I had to run portsnap fetch and portsnap extract, scrapping the ports tree from bsdinstall in favor of the fresh ports tree. So now I know best to not install ports tree from bsdinstall; this would presumably apply for sysinstall too. 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
Compiler
Hi How could I compile some cgi files for FreeBSD Is there any online tool ? ___ 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: where to ask about problems with bsdinstall in 9.0RC2?
According to Thomas Mueller mueller6...@bellsouth.net on Sun, 11/20/11 at 05:46: It looks like tar in extraction mode automatically recognizes xz compression in the file to be extracted from. Section from the man page for tar in FreeBSD 9.0-RC1: -J, --xz (c mode only) Compress the resulting archive with xz(1). In extract or list modes, this option is ignored. Note that, unlike other tar implementations, this implementation recognizes XZ com- pression automatically when reading archives. You see? That just goes to show you... ;^) The above section is missing from my 8.2-STABLE platform tar(1) man page. The whole problem is my trying to get there from here - which was what started this thread... :-) Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ 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 help with wep authentication
On 11/20/11, Rob Clark rpcl...@tds.net wrote: Running fbsd 8.2R on a Dell C640 laptop. Using a pcmcia card with atheros. My 2wire wireless router comes setup default with wep open with wireless security enabled, i.e., needs the default passkey from the router. I cannot get the ifconfig line correct so as to authenticate this way, and have tried many different strings of text here. However, following the handbook, I turned off enable security (on the 2wire router) to test things, hence, using wep (not as authmode shared or authmode open) and it works using the following in /etc/rc.conf: wlans_ath0=wlan0 ifconfig_wlan0=ssid Mynetname DHCP Mynetname is different -- of course. I can browse the web and ping with 0% packet loss. I have not delved into using a /etc/wpa_supplicant.conf yet, I was hoping i could get it done in rc.conf with ifconfig. I have tried many many things, for days on end for authenticating with the passkey from the router. Any help appreciated, I can provide further info and things I've tried -- most things in the handbook wireless section, minus wpa_supplicant.conf. Should adding nwkey key to ifconfig_wlan0 line above be enough? Key may be in ascii or in hex (in which case it must start with 0x). As you should probably already know wep provides 0% security so having wep or open network gives you almost exactly same amount of security. ___ 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
linphone-base conflicts with ortp and fails to install, it also fails to build: error: expected specifier-qualifier-list before 'UInt96'
Hi, When I do portupgrade, I get this message (kdenetwork fails to update due to this): === linphone-base-3.2.1_1,1 conflicts with installed package(s): ^M ortp-0.13.0_1^M ^M They install files into the same place.^M You may want to stop build with Ctrl + C.^M === Vulnerability check disabled, database not found^M === License check disabled, port has not defined LICENSE^M ^M === linphone-base-3.2.1_1,1 conflicts with installed package(s): ^M ortp-0.13.0_1^M ^M They will not build together.^M Please remove them first with pkg_delete(1).^M When I follow instruction in UPDATING and run this command 'portmaster -o net/linphone-base ortp', I get this messages: In file included from ../include/mediastreamer2/msrtp.h:25, from msrtp.c:20: ../include/mediastreamer2/ice.h:60: error: expected specifier-qualifier-list before 'UInt96' msrtp.c: In function 'receiver_process': msrtp.c:333: warning: implicit declaration of function 'rtp_get_payload' gmake[5]: *** [msrtp.lo] Error 1 gmake[5]: Leaving directory `/usr/ports/net/linphone-base/work/linphone-3.2.1/mediastreamer2/src' gmake[4]: *** [all] Error 2 gmake[4]: Leaving directory `/usr/ports/net/linphone-base/work/linphone-3.2.1/mediastreamer2/src' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/net/linphone-base/work/linphone-3.2.1/mediastreamer2' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/net/linphone-base/work/linphone-3.2.1/mediastreamer2' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/net/linphone-base/work/linphone-3.2.1' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/net/linphone-base. === make failed for net/linphone-base === Aborting update I am not sure why linphone-base build fails. But it looks like linphone-base contains some version of ortp. And this creates a problem of the conflict: They install files into the same place. Sylvio, should you consider renaming conflicting files stemming from ortp copy into some other name to remove such conflict? Yuri ___ 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
9.0 and bsdinstall - avoiding updating the MBR
I'm planning to install FreeBSD alongside a whole range of Windows builds for testing. In 8.x it's possible to tell the installer not to bother updating the MBR so you can use something like EasyBCD to boot it via the Windows bootloader instead. Is it still possible on 9.0-RC2 using bsdinstall? I don't seem to remember seeing any option to avoid writing out the new boot code. -- Bruce Cran ___ 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 up ZFS - Filesystem Properties and Installing on Root
Hello, I'll be setting up a server with ZFS on 9.0-RELEASE (when it's released...). I've never used ZFS before, and although I've been reading quite a bit about it, I have some questions. My plan is to use RAID-Z1 across 4 disks. I'll be using GPT, and I would like the root to be ZFS as well. I found a guide: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 In step #4, it has you create boot, swap, and zfs partitions on all 3 (which would be 4 in my case) disks. Then, in step #5, you install the bootloader into all 3 (4) drives. Why do you need boot and swap partitions on EACH disk? It seems to me that you would only need disk 1 to have boot, swap, and zfs, and the other 3 disks only have one partition (using the entire drive) for zfs's pool. Does it have to do with the RAIDZ1 setup? Even then, I don't understand it because it's not disk mirroring, it's RAID. The BIOS is set to look on one specific disk for the loader, not all of them. It seems I'm not understanding something entirely here. Also, with ZFS, you can have an unlimited number of filesystems, correct? I've been trying to figure out the best way to create these filesystems with the appropriate flags (specifically: atime, compression, devices, exec, quota, readonly, and setuid). If, for example, I set devices=off and suid=off on the tank/var filesystem, it is applied to the children filesystem, such as, /var/log, /var/db, and so on? The flags/properties can be changed on-the-fly, correct? If, for example, I set a filesystem noexec, but later realize I need exec, I can change it without issue? Does anyone with zfs experience have any tips on creating a filesystem layout, in terms of which filesystems to create and what flags/properties? Would it be bad to set noatime, nosuid, nodev, and noexec all on the tank, then allow each property appropriately for each directory as necessary? As in, set the whole tank noexec, but allow exec for /bin, /usr/home, /usr/local/bin, etc.? Thank you all very much! ___ 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: Setting up ZFS - Filesystem Properties and Installing on Root
On Sun, Nov 20, 2011 at 10:34 PM, APseudoUtopia apseudouto...@gmail.comwrote: Hello, I'll be setting up a server with ZFS on 9.0-RELEASE (when it's released...). I've never used ZFS before, and although I've been reading quite a bit about it, I have some questions. My plan is to use RAID-Z1 across 4 disks. I'll be using GPT, and I would like the root to be ZFS as well. I found a guide: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 In step #4, it has you create boot, swap, and zfs partitions on all 3 (which would be 4 in my case) disks. Then, in step #5, you install the bootloader into all 3 (4) drives. Why do you need boot and swap partitions on EACH disk? It seems to me that you would only need disk 1 to have boot, swap, and zfs, and the other 3 disks only have one partition (using the entire drive) for zfs's pool. Does it have to do with the RAIDZ1 setup? Even then, I don't understand it because it's not disk mirroring, it's RAID. The BIOS is set to look on one specific disk for the loader, not all of them. It seems I'm not understanding something entirely here. http://en.wikipedia.org/wiki/RAID http://en.wikipedia.org/wiki/Category:RAID If disk 1 fails , the computer ( BIOS ) will look disk 2 . If disk 2 fails , the computer ( BIOS ) will look disk 3 . If disk ( n - 1 ) fails , the computer ( BIOS ) will look disk ( n ) . Also, with ZFS, you can have an unlimited number of filesystems, correct? I've been trying to figure out the best way to create these filesystems with the appropriate flags (specifically: atime, compression, devices, exec, quota, readonly, and setuid). If, for example, I set devices=off and suid=off on the tank/var filesystem, it is applied to the children filesystem, such as, /var/log, /var/db, and so on? The flags/properties can be changed on-the-fly, correct? If, for example, I set a filesystem noexec, but later realize I need exec, I can change it without issue? Does anyone with zfs experience have any tips on creating a filesystem layout, in terms of which filesystems to create and what flags/properties? Would it be bad to set noatime, nosuid, nodev, and noexec all on the tank, then allow each property appropriately for each directory as necessary? As in, set the whole tank noexec, but allow exec for /bin, /usr/home, /usr/local/bin, etc.? Thank you all very much! ___ Thank you very much . Mehmet Erol Sanliturk ___ 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
Base compiler and amdfam10 - anybody/anything? (fwd)
Sorry for crossposting but since no one on hackers@ seems to be interested... -- Forwarded message -- Date: Wed, 16 Nov 2011 12:30:35 +0200 (EET) From: Vladimir Kushnir vkush...@bigmir.net To: hack...@freebsd.org Subject: Base compiler and amdfam10 - anybody/anything? Hi, Are there any attempts to bring to -CURRENT newer AMD chips support? Personally, I've just tried to apply the patches from openSUSE's gcc-4.2.1 SRPM. With slight adaptation they've applied and gave rather significant boost in resulting code speed. At least, testfcpy by Alexander Konovalenko (http://daemon.safety.sci.kth.se/~kono/testfcpu) gave me ~20% (!) speedup with -march=amdfam10 compared to our -march=athlon64-sse3 on Phenom II 970. Unfortunately, the patched compiler with -march=amdfam10 fails in buildworld (internal compiler error's while compiling clang). The buildworld was successful with patched compiler and -march=athlon64-sse3 but since this is my main working system... Well, I had to come back to our unpatched compiler :-( If anyone is interested, the patches were taken from gcc42-4.2.1_20070724-17.src.rpm (actually, I applied all the patches marked as AMD stuff), the resulting patches towards our src/contrib/gcc and share/mk/bsd.cpu.mk are attached (or I can send them by email), and I am quite ready to test what comes out of it. WBR, Vladimir gcc-amdfam10.diff.gz Description: Binary data bsd.cpu.mk.amdfam10.gz Description: Binary data ___ 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
