Re: Booting from firmware RAID
On Wed,16-03-2011 [16:25:54], Ilya Kazakevich wrote: Thank you. I configured boot0 to my ar0 and tried to boot from it. It freezes. I use RAID10 and Intel-ICH7. Looks like I've faced with some other troubles.. Ilya. On Wed, Mar 16, 2011 at 4:05 PM, mcoyles mcoy...@horbury.wakefield.sch.ukwrote: This is probably more PC-specific than freebsd-specific question. I have intel firmware raid. OS needs drivers to work with it. FreeBSD sees it as ar0, so it has drivers. But I want my OS to be installed on this drive and boot from it. It is not good idea, but I really want to do it:) Is it possible? boot0 and boot1 both work with HDD via BIOS interrupts and CHS, right? So, how do they know how to access RAID? They has no drivers. Or BIOS supports interrupts to access RAID with out of drivers? If so -- what for drivers are needed? To access drive via ATA interface? Bios support interrupts and can thus boot from firmware raid. Under windows drivers typically just give you full speed / management features - Marci Hi, here what man atacontrol says: Although the ATA driver allows for creating an ATA RAID on disks with any controller, there are restrictions. It is only possible to boot on an array if it is either located on a real RAID controller like the Promise or Highpoint controllers, or if the RAID declared is of RAID1 or SPAN type; in case of a SPAN, the partition to boot must reside on the first disk in the SPAN. Not sure if it's your case though. -- A complex system that works is invariably found to have evolved from a simple system that works. ___ 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] How to tell whether CPU supports x64?
The original system... I said (on 2011/03/17): CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2387.76-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x4400CNTX-ID,b14 Logical CPUs per core: 2 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 Adam Vande More amvandemore_gmail.com replied (on 2011/03/17): On Thu, Mar 17, 2011 at 5:14 PM, Ilya Kazakevich kazakevichilya_gmail.comwrote: Afaik there should be LM in AMD features output. Even for Intel. Grep your dmesg.boot for LM. yes that is correct, LM stands for Long Mode which indicates amd64 support. If your CPU doesn't list it, it's either a 32 bit only CPU, or it's a bug. Thanks everyone for the assistance. There is no LM feature in dmesg.boot for the system in question, although a different system reports: CPU: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz (2261.03-MHz 686-class CPU) Origin = GenuineIntel Id = 0x106a5 Stepping = 5 Features=0x1781fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,MMX,FXSR,SSE,SSE2,HTT Features2=0x80182201SSE3,SSSE3,CX16,SSE4.1,SSE4.2,b31 AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 16 Logical CPUs per core: 2 The Intel site does say the E5520 supports x64. It seems the lack of LM in the original system does in fact mean it's a 32-bit only processor. John Levine johnl_iecc.com replied (on 2011/03/17): Looking at the Intel web site, the only Xeon I see that runs at 2.4GHz and has two cores with two threads is the Xeon 3060, which does indeed provide the 64 bit instruction set. I looked at the ark.intel.com site hoping to find what processor would report Id = 0xf29 Stepping = 9. I had no luck. I think the dual processors is because of HyperThreading, as indicated by the HTT feature, and that it's actually only a single core. Devin Teske dteske_vicor.com replied (on 2011/03/17): I wrote this for the job (please, suggestions/comments very welcome): #include stdio.h/* printf(3) */ #include stdlib.h /* EXIT_SUCCESS exit(3) */ ... I tried the program, and it reports x86_64 support: NO on both the original system, and the one above that appears to be x64-capable (although it is running the i386 install, which may be why?). Again, thanks all 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
User authentication on Linux with FreeBSD OpenLDAP backend fails: pam_ldap: error trying to bind as user/Failed password for
Hello. I try to use a FreeBSD OpenLDAP (FreeBSD 8.2-STABLE/amd64, most recent OpenLDAP/openldap-sasl-server-2.4.24) as an authentication backend for an UBUNTU 10.10 server (using openldap 2.4.23). Most of the installation on the Ubuntu server has been successfully done (I'm not familiar with Linux, but it seems that things like pam and ldap are quite similar to FreeBSD's installation). From the Linux/Ubuntu server, I'm able to get all users and groups via 'getent passwd' and 'getent group', even 'id' on an OpenLDAP backed up user is successfully. But when it comes to a login via sshd, login fails with this error (loged on Linux Ubuntu in /var/log/auth.log): Mar 18 12:01:00 freyja sshd[26824]: Failed password for testuser from 192.168.0.128 port 40734 ssh2 Mar 18 12:01:23 freyja sshd[26854]: pam_ldap: error trying to bind as user uid=testuser,ou=users,dc=geoinf,dc=freyja,dc=com (Confidentiality required) Mar 18 12:01:25 freyja sshd[26854]: Failed password for testuser from 192.168.0.128 port 54156 ssh2 I'm able to login from other systems (FreeBSD 9 and 8) via this specific OpenLDAP server. Does anyone has a glue? Please set me CC, I'm not subscribing this list. Thanks in advance and regards, Oliver ___ 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] How to tell whether CPU supports x64?
AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 16 Logical CPUs per core: 2 The Intel site does say the E5520 supports x64. It seems the lack of LM in the original system does in fact mean it's a 32-bit only processor. Look again: AMD Features=0x2010NX,LM NX,*LM* :) John Levine johnl_iecc.com replied (on 2011/03/17): Looking at the Intel web site, the only Xeon I see that runs at 2.4GHz and has two cores with two threads is the Xeon 3060, which does indeed provide the 64 bit instruction set. I looked at the ark.intel.com site hoping to find what processor would report Id = 0xf29 Stepping = 9. I had no luck. I think the dual processors is because of HyperThreading, as indicated by the HTT feature, and that it's actually only a single core. Devin Teske dteske_vicor.com replied (on 2011/03/17): I wrote this for the job (please, suggestions/comments very welcome): #include stdio.h/* printf(3) */ #include stdlib.h /* EXIT_SUCCESS exit(3) */ ... I tried the program, and it reports x86_64 support: NO on both the original system, and the one above that appears to be x64-capable (although it is running the i386 install, which may be why?). Again, thanks all 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 ___ 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] How to tell whether CPU supports x64?
On Fri, Mar 18, 2011 at 02:18:22PM +0300, Ilya Kazakevich wrote: AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 16 Logical CPUs per core: 2 The Intel site does say the E5520 supports x64. It seems the lack of LM in the original system does in fact mean it's a 32-bit only processor. Look again: AMD Features=0x2010NX,LM NX,*LM* I believe the reference to the original system means the *other* system whose output was included in the email -- which does not show AMD Features data. The original system does not show a reference to LM, but the second system (whose output you quoted) *does*. . . . which to me suggests that the processor is 64 bit, but the original system for some reason does not recognize that fact. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgprUW6rcxFHP.pgp Description: PGP signature
Re: HAL must die!
On Thu, 17 Mar 2011 18:26:57 -0600 Chad Perrin per...@apotheon.com articulated: On Thu, Mar 17, 2011 at 07:48:58PM -0400, Jerry wrote: On Thu, 17 Mar 2011 16:36:37 -0600 Chad Perrin per...@apotheon.com articulated: No, not really. It's more the fault of the hardware manufacturer. Chad, up until this point I had taken your response seriously. In fact, I thought it was well presented. Then, you went and blew it. You're joking -- right? You haven't taken anything seriously so far other than your own attempts to misrepresent everything I've said. If you want to continue misrepresenting what I said back at me, I recommend you do so off-list rather than clutter up this list any further with it. Maybe, if you contact me off-list, you can explain your clear anti-Chad bias a bit, too. I know you are now going say that the hardware manufacturer should be responsible for the driver. Once again, you demonstrate only that you do not know anything about me. This seems to happen every time you use words like I know when referring to me, my motivations, my actions, and my opinions. Maybe you should stop. The manufacturer does not need to take responsibility for any driver development it does not want to undertake. That does not change the fact that many manufacturers bend over backwards to support one OS and fail to provide sufficient documentation for their hardware interfaces to make it easy for the developers of other OSes to develop drivers independently, so that though the hardware manufacturers are in no way obligated to write drivers (or even provide the documentation needed to support independent driver writers), they *are* to some extent susceptible to blame for the lack of drivers. Even as simple a step as opening up the source to the drivers they provide, preferally under maximally reusable (i.e. copyfree or public domain) licensing terms, for some OSes would be a big help to independent driver writers -- but many hardware manufacturers and vendors fail to do so for no good reason they have ever articulated. That is part of what is to blame for the lack of drivers for some hardware in some OSes. You act as though all it takes for a driver to get added to an OS is for some developer with commit access to snap his fingers, and it must be the fault of the OS developers that a driver is missing. The truth of the matter is that developers must prioritize their work, and tend to do so based not only on what they think is important but also on what they are most qualified to address and what will take more time than they have to devote to the project. Requiring developers to reverse-engineer drivers for other OSes creates some really awful speedbumps on the path to driver development. Look how much trouble nVidia had getting 64 bit drivers into FreeBSD. If nVidia opened the source to just one of its drivers under a license that effectively guaranteed everyone could use the code, it would give everybody in the open source community a tremendous leg up on doing the work that nVidia did, saving nVidia a lot of time. I have read that there are some patent issues that make it difficult for nVidia and AMD/ATI to do so, involving patents that Intel holds in fact, but I also see that while nVidia goes to the trouble of producing closed source drivers for FreeBSD, AMD/ATI has been working with an open source development group to provide documentation for everything not protected by patent to aid in the development of open source drivers. While the latter takes a little longer up front, it also offers much greater returns on investment in the form of someone other than internal development teams doing the work to create drivers for many OSes. Somewhere in the chain, there's someone involved in those network adapters' manufacture that is standing in the way of easier development of drivers. As a result, somebody -- a patent holder, a vendor executive, whatever -- is preventing the documentation and release of clear specs or source code that could be used to jump-start driver development. If nobody does that, then yes, someone out there in the hardware manufacturing chain is at least in part to blame for the lack of drivers, given that it is obvious no developer has unlimited resources to write all the source code the universe needs in the next thirty seconds. You can blame the open-source community in general and *BSD in particular for that problem. Even if they did come to some consensus, they would end up in a pissing contest over the license. There wouldn't need to be any arguments over licensing if the most basic functionality were provided under licenses that are broadly compatible. I really don't see why anyone would think that using a license that precludes license compatibility with other software is a good idea. It just forces people to duplicate effort endlessly:
Re: Updating OpenSSH
On 17 March 2011 11:52, Robert Huff roberth...@rcn.com wrote: Carmel writes: It is part of the base system. I don't know if it has a true maintainer. In any case, I would need commit privileges which I don't and never expect to have and have no desire to acquire.. I do not believe that is correct; a fair number of people contribute productively to the base system with out being committers. Respectfully, 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 yep you just submit a patch, which if it passes muster will get commited ___ 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: HAL must die!
Jerry, allow me to add something to your statements. On Fri, 18 Mar 2011 09:03:54 -0400, Jerry freebsd.u...@seibercom.net wrote: Chad, you are an intelligent individual. I have no doubt of that. However, I think you have failed to think your entire hardware manufacturers are evil for not supporting brand X operating systems concept. The problem is not not supporting brand X, the problem is not supporting established and common standards. A device (whatever it may be) that conforms to the standards existing for that kind of device will work in ANY operating system that implements those standards. There is no predefined way HOW it does it, and it also doesn't matter AS LONG AS it does it. Of course it is the full right of manufactureres to use standards or to avoid them. History teaches that propretary stuff dies. Do you remember the Mini-CD? A great invention, doesn't exist anymore - just an example. According to what documentation I could locate, there are at least 23 different operating systems, in one form or another, presently available. Microsoft controls +/- 90%, with Mac at approximately 5%. The rest divide up what is left. FreeBSD is listed at a minuscule 0.01%. I found these at: http://www.netmarketshare.com/operating-system-market-share.aspx?qprid=8. I obviously cannot vouch for their authenticity although they do seem consistent with other published reports I have seen in the past year. The big problem with those numbers - although they should be valid at large scale - is that they really concentrate on market share. As you correctly pointed out, FreeBSD is a minority in there. This is because there simply is no significant market. Market is derived from either volume sales (you buy it, ++, you throw it away without using it, still ++), licensing (you register something online, ++) or other means to obtain data (e. g. browser identification of visitors who view a certain web site). Now, it is a given that the conglomeration of non-Microsoft/non-Apple operating systems fail to offer a consistent/uniform API for the detection of and installation or procurement of drivers for devices on their respective systems. Fully agree. Although there are standards for many things, manufacturers don't intend to use them - and maybe this is even required due to the nature of their products. While development for free platforms doesn't involve specific licensing costs, it's hard work as well as for the propretary ones to implement a driver. Now, I have a proposal. If the fragmented open-source community really wants to advance, and maybe FreeBSD actually reach a full percentage point, it has to agree on a common interface/API for the detection of, installation and configuration of devices on their respective systems. A uniform driver base is a must. This is relatively easy on systems like FreeBSD with a stable system level API, but can be considered more complicated on the many Linusi. I am not talking about a semi-uniform system; but rather a fully uniform system take works exactly the same on each system. This won't be easy for reasons previously mentioned; but it is doable. Sadly, I don't think so, but I'm just being realistic. An additional benefit is that the time wasted now by each vendor attempting to create and maintain their own API would be eliminated. One common interface could be maintained by a far smaller group of developers thereby freeing up time to work on other system improvements. Obviously, licensing problems would have to be over come. They are one of the main problems in desktop area, as they do also affect fully functional multimedia capabilities. But it's not up to programmers to deal with that - it's the field of the lawyers. Now, back to my ROI reference. If the above were to actually happen, hardware vendors would now only have to code and maintain one single driver database. But manufacturers do traditionally access two markets: They get money (1st) by selling masses of cheap products that rely on proprietary systems, break after one year and include planned obsolescense as they are not compatible, and (2nd) by selling lower amounts of more expensive products to users who are aware of the fact explained first; those products are compatible to standards and have a longer life, and they can be re-used under changed circumstances. This way manufacturers profit from both markets. The tendency seems to be that the 1st market is still growing (what a surprise: when the printer breaks after one year, you _have_ to buy a new one, and as it should be cheap... you know). The majority of users is not interested in good for a long time. They require to buy the best at the moment, and due to technical evolution, there's something new very month that needs to be bought, that _they_ need to have. They don't care for standardized operating system, they don't care for operating systems at all - they'll use whatever comes preinstalled. The
Re: HAL must die!
On 03/18/11 23:03, Jerry wrote: On Thu, 17 Mar 2011 18:26:57 -0600 Chad Perrinper...@apotheon.com articulated: On Thu, Mar 17, 2011 at 07:48:58PM -0400, Jerry wrote: On Thu, 17 Mar 2011 16:36:37 -0600 Chad Perrinper...@apotheon.com articulated: No, not really. It's more the fault of the hardware manufacturer. Chad, up until this point I had taken your response seriously. In fact, I thought it was well presented. Then, you went and blew it. You're joking -- right? You haven't taken anything seriously so far other than your own attempts to misrepresent everything I've said. If you want to continue misrepresenting what I said back at me, I recommend you do so off-list rather than clutter up this list any further with it. Maybe, if you contact me off-list, you can explain your clear anti-Chad bias a bit, too. I know you are now going say that the hardware manufacturer should be responsible for the driver. Once again, you demonstrate only that you do not know anything about me. This seems to happen every time you use words like I know when referring to me, my motivations, my actions, and my opinions. Maybe you should stop. The manufacturer does not need to take responsibility for any driver development it does not want to undertake. That does not change the fact that many manufacturers bend over backwards to support one OS and fail to provide sufficient documentation for their hardware interfaces to make it easy for the developers of other OSes to develop drivers independently, so that though the hardware manufacturers are in no way obligated to write drivers (or even provide the documentation needed to support independent driver writers), they *are* to some extent susceptible to blame for the lack of drivers. Even as simple a step as opening up the source to the drivers they provide, preferally under maximally reusable (i.e. copyfree or public domain) licensing terms, for some OSes would be a big help to independent driver writers -- but many hardware manufacturers and vendors fail to do so for no good reason they have ever articulated. That is part of what is to blame for the lack of drivers for some hardware in some OSes. You act as though all it takes for a driver to get added to an OS is for some developer with commit access to snap his fingers, and it must be the fault of the OS developers that a driver is missing. The truth of the matter is that developers must prioritize their work, and tend to do so based not only on what they think is important but also on what they are most qualified to address and what will take more time than they have to devote to the project. Requiring developers to reverse-engineer drivers for other OSes creates some really awful speedbumps on the path to driver development. Look how much trouble nVidia had getting 64 bit drivers into FreeBSD. If nVidia opened the source to just one of its drivers under a license that effectively guaranteed everyone could use the code, it would give everybody in the open source community a tremendous leg up on doing the work that nVidia did, saving nVidia a lot of time. I have read that there are some patent issues that make it difficult for nVidia and AMD/ATI to do so, involving patents that Intel holds in fact, but I also see that while nVidia goes to the trouble of producing closed source drivers for FreeBSD, AMD/ATI has been working with an open source development group to provide documentation for everything not protected by patent to aid in the development of open source drivers. While the latter takes a little longer up front, it also offers much greater returns on investment in the form of someone other than internal development teams doing the work to create drivers for many OSes. Somewhere in the chain, there's someone involved in those network adapters' manufacture that is standing in the way of easier development of drivers. As a result, somebody -- a patent holder, a vendor executive, whatever -- is preventing the documentation and release of clear specs or source code that could be used to jump-start driver development. If nobody does that, then yes, someone out there in the hardware manufacturing chain is at least in part to blame for the lack of drivers, given that it is obvious no developer has unlimited resources to write all the source code the universe needs in the next thirty seconds. You can blame the open-source community in general and *BSD in particular for that problem. Even if they did come to some consensus, they would end up in a pissing contest over the license. There wouldn't need to be any arguments over licensing if the most basic functionality were provided under licenses that are broadly compatible. I really don't see why anyone would think that using a license that precludes license compatibility with other software is a good idea. It just forces people to duplicate effort endlessly: Code
Re: User authentication on Linux with FreeBSD OpenLDAP backend fails: pam_ldap: error trying to bind as user/Failed password for
In the last episode (Mar 18), O. Hartmann said: I try to use a FreeBSD OpenLDAP (FreeBSD 8.2-STABLE/amd64, most recent OpenLDAP/openldap-sasl-server-2.4.24) as an authentication backend for an UBUNTU 10.10 server (using openldap 2.4.23). Most of the installation on the Ubuntu server has been successfully done (I'm not familiar with Linux, but it seems that things like pam and ldap are quite similar to FreeBSD's installation). From the Linux/Ubuntu server, I'm able to get all users and groups via 'getent passwd' and 'getent group', even 'id' on an OpenLDAP backed up user is successfully. But when it comes to a login via sshd, login fails with this error (loged on Linux Ubuntu in /var/log/auth.log): Mar 18 12:01:00 freyja sshd[26824]: Failed password for testuser from 192.168.0.128 port 40734 ssh2 Mar 18 12:01:23 freyja sshd[26854]: pam_ldap: error trying to bind as user uid=testuser,ou=users,dc=geoinf,dc=freyja,dc=com (Confidentiality required) Confidentiality required means that the server is refusing to authenticate over a non-encrypted connection. Try switching pam_ldap to ldaps (in your pam ldap.conf, either change your uri lines to ldaps:// or add the line ssl on) and see if that works. -- 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
Kind of OFF Topic. Advise pls.
Hello All. These could sound off topic, I am sorry in advance. I am upgrading an old machine from 7.3 to the latest 8.x release branch. I want to use that machine for 1) catalago/shopping cart solution only, nothing complicated not many users , something simple, personal project to learn and try to sell products. Nothing big. 2) I also want to have a couple of sites running a CMS software. The same, not big one, not millions of users expected, some close to a few clients and my relation with them. 3) To have a customer relationship, tickets, help center etc. Nothing big. My company is small now... just me Based onyour experiecne, what ar the best options to chosse that will run the best on Freebsd (yea I now lot of external factors, security etc). Maybe if you tell me what are you using it is enough . I have read aboiut the difrrence and I like all. From the following: Content Management Drupal Geeklog Joomla 1.5 Joomla Mambo PHP-Nuke phpWCMS phpWebSite Siteframe TYPO3 Xoops Zikula E-Commerce CubeCart OS Commerce Zen Cart Customer Relationship Crafty Syntax Live Help Help Center Live osTicket PerlDesk PHP Support Tickets Support Logic Helpdesk Support Services Manage Thanks in advance Jorge Biquez ___ 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 is KIX (super)
Thank you all FreeBSD people I use to keep the servers up to date and have a custom kernel, but some don't need this! FreeBSD 6.0-RELEASE (GENERIC) #0: Thu Nov 3 09:36:13 UTC 2005 $ uptime 6:14PM up 1812 days, 1:51, 1 user, load averages: 0.13, 0.03, 0.01 $ uname -a FreeBSD mail.xxx.nl 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 r...@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC i386 $ It has a nice ipfw and provides some http sites, ssl smtp, mysql and imapproxy for about 100 users roaming throughout the world :) cheers DISCLAIMER: This e-mail is for the intended recipient(s) only. Access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you have received it by mistake please let us know by reply and then delete it from your system. ___ 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: Kind of OFF Topic. Advise pls.
Content Management Joomla 1.5 Joomla 1.6 and/or Wordpress depending on your needs E-Commerce PrestaShop Not sure about CRM as I do not use it but I am sure others will have a clue. Warm regards, Zbigniew Szalbot ___ 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
Hung install (7.4 stable)
I am trying to install 7.4 on an older machine, MSI K7N2 mobo, AMD athlon This board supports 2 SATA Drives and 4 EIDE devices, one of which is the DVDR. It will only boot from a CD and so I am trying to install from 7.4 Disc 1. The EIDE controller supports RAID on its disks. The situation so far is that after disabling the FDD in BIOS, I am only able to boot the install in Safe-mode. The boot program recognizes the DVDR as acd0: ata0-slave UDMA33 I was able to creat file systems on the new SATA drive and proceed with the install but then an error message stating that install media cannot be mounted aborts the install. When the boot is run in normal mode it stalls after recognizing the sata drives, install drive is ad4: 750gb ata2-master SATA150 The last message is: ad6: PROMISE subdisks has no flags. I do not see any discussion of safe-mode in the handbook and would like to know exactly what this means. BTW the machine is currently running Ubuntu and has no problem with booting up from the Ubuntu install CD. Any help greatly appreciated. -- Barry Friedman Emax Computer Systems Inc., 480 Tweedsmuir Ave., Ottawa, Ont. Canada K1Z 5N9 bfried...@emax.ca 613-725-3198 ___ 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: Hung install (7.4 stable)
On Fri, Mar 18, 2011 at 12:24 PM, Friedman fried...@emax.ca wrote: I am trying to install 7.4 on an older machine, MSI K7N2 mobo, AMD athlon snip Any help greatly appreciated. First thing I would do is update the BIOS -- 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: Kind of OFF Topic. Advise pls.
On Fri, 18 Mar 2011 11:03:01 -0600 Jorge Biquez jbiq...@intranet.com.mx wrote: 1) catalago/shopping cart solution only, nothing complicated not many users , something simple, personal project to learn and try to sell products. Nothing big. 2) I also want to have a couple of sites running a CMS software. The same, not big one, not millions of users expected, some close to a few clients and my relation with them. 3) To have a customer relationship, tickets, help center etc. Nothing big. My company is small now... just me I'm in the same boat. :-) At the moment I use Concrete5 (http://www.concrete5.org/) and you have ecommerce which nicely integrates with it (http://www.concrete5.org/marketplace/addons/ecommerce/) but it costs $125. Concrete is very nice to use CMS. However, I also strongly consider to switch to SilverStripe (http://www.silverstripe.org/) which is released under BSD license. ;) There is also ecommerce module available (http://www.silverstripe.org/ecommerce-module/) but it is free as well as all other extension modules. Since I have similar needs and sell only 'services', I prefer to have simple easy to use CMS and integrated ecommerce module. Hope it helps. Sincerely, Gour -- “In the material world, conceptions of good and bad are all mental speculations…” (Sri Caitanya Mahaprabhu) http://atmarama.net | Hlapicina (Croatia) | GPG: CDBF17CA signature.asc Description: PGP signature
Re: Kind of OFF Topic. Advise pls.
On Fri, Mar 18, 2011 at 11:03:01AM -0600, Jorge Biquez wrote: Hello All. These could sound off topic, I am sorry in advance. I am upgrading an old machine from 7.3 to the latest 8.x release branch. Have you looked at what is available in the /usr/ports tree? I want to use that machine for snip Content Management * Drupal * Geeklog * Joomla 1.5 * Joomla * Mambo PHP-Nuke phpWCMS phpWebSite * Siteframe * TYPO3 * Xoops Zikula The ones above that I marked with a * are available in the FreeBSD ports system and should work. I've also tried Plone and Mediawiki. E-Commerce CubeCart * OS Commerce Zen Cart Only OS Commerce is in ports, but there is alse drupal5-ubercart [http://drupal.org/project/ubercart] and Opencart (PHP based) [http://www.opencart.com/]. Maybe one of those will work for you? Customer Relationship Crafty Syntax Live Help Help Center Live osTicket PerlDesk PHP Support Tickets Support Logic Helpdesk Support Services Manage A quick look doesn't show any of these applications in the ports tree. But looking for ticket gives; locate '*ports/*ticket*/Makefile' /usr/ports/www/mod_ticket/Makefile /usr/ports/www/trac-advancedticketworkflow/Makefile /usr/ports/www/trac-mastertickets/Makefile /usr/ports/www/trac-pendingticket/Makefile /usr/ports/www/trac-privatetickets/Makefile /usr/ports/www/trac-simpleticket/Makefile /usr/ports/www/trac-ticketdelete/Makefile /usr/ports/www/trac-ticketimport/Makefile 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) pgpgZy5JG4Dav.pgp Description: PGP signature
Re: User authentication on Linux with FreeBSD OpenLDAP backend fails: pam_ldap: error trying to bind as user/Failed password for
On 03/18/11 17:02, Dan Nelson wrote: In the last episode (Mar 18), O. Hartmann said: I try to use a FreeBSD OpenLDAP (FreeBSD 8.2-STABLE/amd64, most recent OpenLDAP/openldap-sasl-server-2.4.24) as an authentication backend for an UBUNTU 10.10 server (using openldap 2.4.23). Most of the installation on the Ubuntu server has been successfully done (I'm not familiar with Linux, but it seems that things like pam and ldap are quite similar to FreeBSD's installation). From the Linux/Ubuntu server, I'm able to get all users and groups via 'getent passwd' and 'getent group', even 'id' on an OpenLDAP backed up user is successfully. But when it comes to a login via sshd, login fails with this error (loged on Linux Ubuntu in /var/log/auth.log): Mar 18 12:01:00 freyja sshd[26824]: Failed password for testuser from 192.168.0.128 port 40734 ssh2 Mar 18 12:01:23 freyja sshd[26854]: pam_ldap: error trying to bind as user uid=testuser,ou=users,dc=geoinf,dc=freyja,dc=com (Confidentiality required) Confidentiality required means that the server is refusing to authenticate over a non-encrypted connection. Try switching pam_ldap to ldaps (in your pam ldap.conf, either change your uri lines to ldaps:// or add the line ssl on) and see if that works. Well, in /etc/ldap.conf there is ssl start_tls and this should do the thing. I use nearly exact the same configuration as I do on all the FreeBSD boxes connecting to the same OpenLDAP server. I tried issuing 'ldapsaerach -xZZ -h hostIP' and I get ldap_start_tls: Connect error (-11) additional info: (unknown error code) looking deeper into the debug stuff with 'ldapsaerach -xZZ -h hostIP' I receive at the end TLS: peer cert untrusted or revoked (0x42) TLS: can't connect: (unknown error code). ldap_err2string ldap_start_tls: Connect error (-11) additional info: (unknown error code) Obviously, my certificate (self signed, openssl verify cacert.pem gives: OK) isn't found or there is something wrong with it. The certificate is located in /usr/local/etc/cacerts/cacert.pem and in Ubuntu's /etc/ldap.conf there is this line: tls_cacertfile usr/local/etc/cacerts/cacert.pem is referring to the certificate. ___ 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
installing freebsd on a thinkpad x300
Hi, I have successfully installed FreeBSD on my x300 but I have some driver problems. Does someone know how to figure out which driver I need for the sound and the wlan card? And the second point is: does someone know a GUI network manager I can use for xfce4? Regards, alokat ___ 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: sguil-client startup problem
--On March 17, 2011 4:30:31 PM +0100 d.sch...@rn.rabobank.nl wrote: I have a question regarding the installation and startup of sguil-client on a 8.2 Generic OS. It seems that my installation requires an iwidget extension when run with tclsh8.4 and receives an error when running wish8.4: Error in startup script: can't read 0: no such variable while executing Exec /usr/local/bin/wish8.4 $0 $@ line 5. I have all the required packages , I suppose (tclX-8.4,tcl-8.4,tcllib,tcltls,tk8.4,ictl-3), also the iwidget extension is installed... Strangely enough also version 8.5 is present on the system, could that be a problem. Hopefully , there is someone who has experienced the same or better yet, has an answer to my problem... Apparently the default tcl install is now 8.5. Looks like I'm going to have to update the ports. You *may* be able to fix your problem by editing the sguil.tk file, although I'm not sure what other impacts that might have. The script calls wish8.4 explicitly, but that probably doesn't exist on your system. Change it to 8.5 and see if that fixes the problem. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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
Surge 2011 Conference CFP
We are excited to announce Surge 2011, the Scalability and Performance Conference, to be held in Baltimore on Sept 28-30, 2011. The event focuses on case studies that demonstrate successes (and failures) in Web applications and Internet architectures. This year, we're adding Hack Day on September 28th. The inaugural, 2010 conference (http://omniti.com/surge/2010) was a smashing success and we are currently accepting submissions for papers through April 3rd. You can find more information about topics online: http://omniti.com/surge/2011 2010 attendees compared Surge to the early days of Velocity, and our speakers received 3.5-4 out of 4 stars for quality of presentation and quality of content! Nearly 90% of first-year attendees are planning to come again in 2011. For more information about the CFP or sponsorship of the event, please contact us at surge (AT) omniti (DOT) com. -- Katherine Jeschke Marketing Director OmniTI Computer Consulting, Inc. 7070 Samuel Morse Drive, Ste.150 Columbia, MD 21046 O: 410/872-4910, 222 C: 443/643-6140 omniti.com circonus.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: installing freebsd on a thinkpad x300
Alokat,
On Fri, Mar 18, 2011 at 2:04 PM, Alokat mail...@alokat.org wrote:
Hi,
I have successfully installed FreeBSD on my x300 but I have some driver
problems.
Does someone know how to figure out which driver I need for the sound and
the wlan card?
For the sound^{1}, try loading the
$ su -
passwd:
# kldload snd_driver
then do a
# cat /dev/sndstat
and that should guide you as to which driver you need.
For the wlan, you can do a
# ifconfig wlan0 list scan
and see if you can get some information and if you encounter
difficulties, you may refer to ^{2}
{1} http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html
{2}
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html
And the second point is: does someone know a GUI network manager I can use
for xfce4?
This one is a bit more harder to answer, I am not sure if there is
networkmanager in the ports?
Regards,
alokat
Regards,
Antonio
___
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: Hung install (7.4 stable)
You wrote: On Fri, Mar 18, 2011 at 12:24 PM, Friedman fried...@emax.ca wrote: I am trying to install 7.4 on an older machine, MSI K7N2 mobo, AMD athlon First thing I would do is update the BIOS It appears that the BIOS for this board (MSI K7N2 Delta2 LSR) is up to date. (W6570NMS V7.8) -- Barry Friedman Emax Computer Systems Inc., 480 Tweedsmuir Ave., Ottawa, Ont. Canada K1Z 5N9 bfried...@emax.ca 613-725-3198 ___ 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: Hung install (7.4 stable)
On Fri, Mar 18, 2011 at 3:31 PM, Friedman fried...@emax.ca wrote: You wrote: On Fri, Mar 18, 2011 at 12:24 PM, Friedman fried...@emax.ca wrote: I am trying to install 7.4 on an older machine, MSI K7N2 mobo, AMD athlon First thing I would do is update the BIOS It appears that the BIOS for this board (MSI K7N2 Delta2 LSR) is up to date. (W6570NMS V7.8) Seems that you aren't the only one with probs on that board. http://www.tomshardware.com/forum/197306-30-installation-mystery-k7n2-delta2 Make sure your IDE settings are not in RAID mode, it should be straight standard IDE. If you do have it in raid mode, you may have to resort to something like http://www.freebsd.org/cgi/man.cgi?query=ataraidapropos=0sektion=0manpath=FreeBSD+8.1-RELEASE+and+Portsformat=html -- 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: installing freebsd on a thinkpad x300
On Fri, Mar 18, 2011 at 2:04 PM, Alokat mail...@alokat.org wrote: Hi, I have successfully installed FreeBSD on my x300 but I have some driver problems. Does someone know how to figure out which driver I need for the sound and the wlan card? The sound card should be snd_hda(4): http://www.freebsd.org/cgi/man.cgi?query=snd_hdaapropos=0sektion=0manpath=FreeBSD+8.2-RELEASEformat=html Here's a document detailing sound configuration: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html The wireless device driver should be iwn(4): http://www.freebsd.org/cgi/man.cgi?query=iwnapropos=0sektion=0manpath=FreeBSD+8.2-RELEASEformat=html Please refer to the handbook for configuration instructions: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html And the second point is: does someone know a GUI network manager I can use for xfce4? There are (at least) a couple from ports you can try: http://www.freshports.org/net/pcbsd-netmanager http://www.freshports.org/net/wpa_gui/ I remember at one time testing a GTK-based utility, but I can't seem to dredge up the name of it from memory ATM... Regards, alokat Good luck, -Brandon ___ 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: HAL must die!
Chad wrote: Everybody who thinks it's a good idea (by way of analogy) to write command line utilities that default to not letting you specify any options at all, and if you use one option to do something non-default you have to specify *all* options even when the specification is exactly the same as the default -- raise your hands. In fact i am just now writing something which does that: either mostly automatic, or with full expert options if you know what you are doing. There is no real middle ground, in my opinion, and i just don't like the Unix style commands, with tons of options and unscrutable man pages. I think this Unix approach has not led to considerable adoption, generally. To come back to HAL, i have been usually happy with HAL. You just have to know that if you want to modify some simple X configuration (typically change the keyboard language) you have to do it in a HAL config file, not in xorg.conf. The only problem is that the HAL config files are in xml crap, not in usual form. In fact the main HAL problem is a documentation problem, like for many other softs. How many new features of FreeBSD are correctly documented presently? -- Michel TALON ___ 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: HAL must die!
The other two people whose responses to you I have read so far make some good points. Nonetheless, I intend to give my take on the matter as well. On Fri, Mar 18, 2011 at 09:03:54AM -0400, Jerry wrote: Chad, you are an intelligent individual. I have no doubt of that. However, I think you have failed to think your entire hardware manufacturers are evil for not supporting brand X operating systems concept. You are not responding to anything I said when you say that. I never said any manufacturers were evil for not supporting brand X. What I said was that, where FreeBSD lacks drivers for a given piece of hardware (especially stuff like recent graphics, bleeding edge wireless protocols, and so on), hardware manufacturers and vendors are part of the reason. I don't know why you insist on trying to attribute simple statements of fact like this to a bizarre moral judgment I didn't make. I think that most hardware manufacturers are at worst, for purposes of this discussion, short-sighted. In many cases, they may even be taking a longer, broader view -- but the fact they're acting rationally and ethically in no way changes the fact that their choices make it (sometimes prohibitively) difficult for open source developers to produce drivers. Did you ever attend a real business school? If so, you might be familiar with the term ROI which stands for return of investment. It doesn't take attending a real business school to be familiar with ROI. According to what documentation I could locate, there are at least 23 different operating systems, in one form or another, presently available. Microsoft controls +/- 90%, with Mac at approximately 5%. The rest divide up what is left. FreeBSD is listed at a minuscule 0.01%. I found these at: http://www.netmarketshare.com/operating-system-market-share.aspx?qprid=8. I obviously cannot vouch for their authenticity although they do seem consistent with other published reports I have seen in the past year. Most such statistics are wildly inaccurate -- and the fact that most of them are inaccurate in very similar ways is a sign they are collecting their data in the same selection bias influenced manner, and not a sign that they're correct. That having been said, though, I'll stipulate that it is likely MS Windows holds the lion's share of the desktop market by a substantial margin. Now, it is a given that the conglomeration of non-Microsoft/non-Apple operating systems fail to offer a consistent/uniform API for the detection of and installation or procurement of drivers for devices on their respective systems. [snipped the rest of the paragraph for irrelevancy and demonstration of your biases] It is a given that Microsoft OSes fail to offer a consistent/uniform API from one release version to the next, or at times even from one service pack to the next, too. Now, I have a proposal. I'm no expert in OS design. I am not sufficiently conversant in the subject to comment meaningfully on the advisability or technical effectiveness of such an effort. I strongly suspect that the differing needs of various design philsophies substantially prohibit a *comprehensively* standardized hardware drive development interface (DPI?), though. Now, back to my ROI reference. If the above were to actually happen, hardware vendors would now only have to code and maintain one single driver database. Actually three is you include Microsoft and Apple. Interestingly enough, Microsoft and to a lesser degree Apple write drivers for some hardware on their respective systems. Meanwhile, OS projects like FreeBSD and allied development teams *also* write drivers for some hardware on their respective systems. In fact, I strongly suspect that the percentage of FreeBSD driver support that is produced by open source developers rather than hardware manufacturers and vendors is *much* greater than the percentage of MS Windows driver support that is produced by Microsoft employees rather than hardware manufacturers and vendors. In any case, I believe hardware vendors would be willing to invest the time and money in such a venture since they would be able to shown a return on their investment without the need to divulge patented information regarding their devices. Even better, if such a plan were put into effect, any OS that refused to join the alliance would lose their right to blame the hardware manufactures since the blame would then unequivocally be theirs. A win-win solution for all involved. Are you aware that patents are *published*? It's not the information about the patents that is the problem. Anyone can get any registered patent information. In any case, if the vendors just released anything and everything that was not a trade secret or limited in distributability by others' copyrights and patents, that alone would be a huge step toward ensuring the manufacturers and vendors never have to write a single driver for open source operating
Re: [solved] How to tell whether CPU supports x64?
On Fri, Mar 18, 2011 at 1:15 PM, Chad Perrin per...@apotheon.com wrote: On Fri, Mar 18, 2011 at 02:18:22PM +0300, Ilya Kazakevich wrote: AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 16 Logical CPUs per core: 2 The Intel site does say the E5520 supports x64. It seems the lack of LM in the original system does in fact mean it's a 32-bit only processor. Look again: AMD Features=0x2010NX,LM NX,*LM* I believe the reference to the original system means the *other* system whose output was included in the email -- which does not show AMD Features data. The original system does not show a reference to LM, but the second system (whose output you quoted) *does*. . . . which to me suggests that the processor is 64 bit, but the original system for some reason does not recognize that fact. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] It is 32bit Xeon P4 known as Dell PowerEdge 1750 http://www.dell.com/downloads/global/products/pedge/en/1750_specs.pdf http://seattle.craigslist.org/see/sys/2272693617.html The 2nd one is *Dell POWEREDGE* R610 which is 64bit system - completely different model and processor. http://www.dell.com/downloads/global/products/pedge/en/server-poweredge-r610-specs-en.pdf Best regards! ___ 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: HAL must die!
On Fri, Mar 18, 2011 at 10:36:41PM +0100, Michel Talon wrote: Chad wrote: Everybody who thinks it's a good idea (by way of analogy) to write command line utilities that default to not letting you specify any options at all, and if you use one option to do something non-default you have to specify *all* options even when the specification is exactly the same as the default -- raise your hands. In fact i am just now writing something which does that: either mostly automatic, or with full expert options if you know what you are doing. There is no real middle ground, in my opinion, and i just don't like the Unix style commands, with tons of options and unscrutable man pages. I think this Unix approach has not led to considerable adoption, generally. To come back to HAL, i have been usually happy with HAL. You just have to know that if you want to modify some simple X configuration (typically change the keyboard language) you have to do it in a HAL config file, not in xorg.conf. The only problem is that the HAL config files are in xml crap, not in usual form. In fact the main HAL problem is a documentation problem, like for many other softs. How many new features of FreeBSD are correctly documented presently? Wait -- what? Really? Let's say your application has the following options with defaults: foo: one bar: two baz: three qux: four Let's say someone wants qux to be five instead of four. Are you saying you're writing your application to *force* them to specify *all four* configuration settings, even when three of them are default? Are you further saying you're doing this because you think it's a good idea from a UI standpoint, and not just out of laziness? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgp75w5tKjFiw.pgp Description: PGP signature
Re: HAL must die!
Although all very interesting and entertaining, how much will it cost me to kill this thread and any concepts mentioned herein for at least 30 days? At minimum, haven't we strayed quit a bit from the OP and as such this worthwhile discussion should be a new thread? Just sayin' - Original Message - From: Chad Perrin [mailto:per...@apotheon.com] Sent: Friday, March 18, 2011 06:13 PM To: freebsd-questions@freebsd.org freebsd-questions@freebsd.org Subject: Re: HAL must die! On Fri, Mar 18, 2011 at 10:36:41PM +0100, Michel Talon wrote: Chad wrote: Everybody who thinks it's a good idea (by way of analogy) to write command line utilities that default to not letting you specify any options at all, and if you use one option to do something non-default you have to specify *all* options even when the specification is exactly the same as the default -- raise your hands. In fact i am just now writing something which does that: either mostly automatic, or with full expert options if you know what you are doing. There is no real middle ground, in my opinion, and i just don't like the Unix style commands, with tons of options and unscrutable man pages. I think this Unix approach has not led to considerable adoption, generally. To come back to HAL, i have been usually happy with HAL. You just have to know that if you want to modify some simple X configuration (typically change the keyboard language) you have to do it in a HAL config file, not in xorg.conf. The only problem is that the HAL config files are in xml crap, not in usual form. In fact the main HAL problem is a documentation problem, like for many other softs. How many new features of FreeBSD are correctly documented presently? Wait -- what? Really? Let's say your application has the following options with defaults: foo: one bar: two baz: three qux: four Let's say someone wants qux to be five instead of four. Are you saying you're writing your application to *force* them to specify *all four* configuration settings, even when three of them are default? Are you further saying you're doing this because you think it's a good idea from a UI standpoint, and not just out of laziness? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font ___ 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
