Re: Virtual Box on FreeBSD Server
As others have said, you can run VirtualBox without X. The command line tools provided by VirtualBox are pretty comprehensive and straight-forward. To add to that, there's also phpVirtualBox: https://code.google.com/p/phpvirtualbox/ that provides a nice web interface to managing your VMs, though it appears the project is on pause right now. I actually have a few semi-production servers running under VirtualBox on a Linux host, as I found far better disk performance there for FreeBSD guests than under KVM. Hopefully that changes soon, if it hasn't already. On Fri, Apr 19, 2013 at 6:37 AM, Bill Tillman btillma...@yahoo.com wrote: I've been looking into setting up some Linux servers but instead I'm thinking that I could use Virtual Box on my FreeBSD servers to do this. I would like some seasoned advice from others on the following before proceeding: 1. As I understand it you can install Virtual Box from the ports collection. But then I see the instructions in the Handbook: To launch VirtualBox, type from a Xorg session: % VirtualBox So am I to assume the only way to run Virtual Box is to have Xorg installed and running on the FreeBSD server? Which is a drag because my current FreeBSD servers are exactly that, servers, and do not have the fancy video cards, monitors, etc.. to run Xorg. Is there an alternative to running the interface from Xorg. I'm a command line fanatic when it comes to servers. Or would I be able to install Xvnc or something like that and run it from one of my Windows 7 machines which has all the fancy video capabilities? 2. Once installed, I will be able to install something like Fedora or openSUSE? These will only be installed as server so I can run databases like MySQL in the Linux environment. The client I'm working for insists on using SUSE...no FreeBSD allowed. They think it's poison and are very biased on this so there's no talking them out of it. I need to gain experience using these databases on Linux, not FreeBSD. 3. I'm going to buy a 1 TB SATA drive for this setup. It will be running on an AMD64 server with FreeBSD 9.x or whatever is the latest release as of this weekend. 4. There is also a Plan 'B' to go the other way. Since I already have two i7 machines running Windows 7, perhaps it might be better to install the Windows version of Virtual Box or even VMWare and create my instances of Linux on one or even both of these machines. Any advice would be appreciated. ___ 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
Managing conflicts between ports (same package with multiple maintained versions)
Hello, I am the maintainer of most of the Tryton ports. Tryton is a python based application framework where you can easily build your own business modules on top. It also provides some default modules for common uses. Currently Tryton 2.4 series is in the ports. From upstream the successor Tryton 2.6 is available. At Tryton, also previous releases are supported for an extended time. This is required, because users who spent time to build their own modules on top of e.g. 2.4 should not be forced to migrate immediately to 2.6 (and likely use a different API) just for a security patch or a bug fix. Thats why I want to bring in 2.6 to the ports while continuing maintaining 2.4. During the planning, I ran into the following issue: Tryton 2.4 and 2.6 install files to the same Python site-packages directory /usr/local/lib/python2.7/site-packages/trytond-2.4.5-py2.7.egg /usr/local/lib/python2.7/site-packages/trytond-2.6.3-py2.7.egg Even there egg names are different, the contained package names are equal: /usr/local/lib/python2.7/site-packages/trytond-2.4.5-py2.7.egg/trytond /usr/local/lib/python2.7/site-packages/trytond-2.6.3-py2.7.egg/trytond So for the python interpreter it would not be clear which one to import if you just import trytond. Renaming the package names doesn't look reasonable because it would require patching all Tryton modules (and will make it incompatible with custom built modules). So I think it is required to define it as a conflict if two versions of Tryton will be installed at the same time. My first approach was to define CONFLICTS= trytond-* in the Makefiles of trytond 2.4 and 2.6. This works and prevents installing two different versions. But portlint doesn't seem happy with it: root@compaq:/usr/ports/finance/trytond # portlint -AC [...] FATAL: Package conflicts with itself. You should remove trytond-* from CONFLICTS. 1 fatal error and 4 warnings found. root@compaq:/usr/ports/finance/trytond # So it looks like I need to explicitly specify the conflicting versions, e.g. in Tryton 2.4 Makefile put: CONFLICTS= trytond-2.6.* But this will force me to update the 2.4 Ports everytime a new series of Tryton gets introduced. Is there a better way to achieve this? Thanks in advance kind regards, Matthias ___ 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: Problems with ekiga3 build
El día Sunday, March 31, 2013 a las 01:35:43PM +0200, Koop Mast escribió: I'm looking into updating the ptlib/opal/ekiga ports. So ekiga 4 will happen. Btw if you can't wait for that, gtk30 was updated to 3.6, and you can get a more recent gnome-icon-theme port from our devel repo. I was able to compile ptlib/opal/ekiga out of SVN and Git on my 10-CURRENT with a ports tree from SVN head r315646 as of April 1st, 2013 and the above mentioned gnome-icon-theme-3.4.0; the instructions of the build are here: http://wiki.ekiga.org/index.php/Compile_your_own_SVN_version_of_Ekiga_on_FreeBSD HIH someone matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ 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: Home WiFi Router with pfSense or m0n0wall?
Hi, I'm looking to replace the piece of crap 2wire WiFi router that gets crakced every other day for something with pfSense or m0n0wall I would like something that is plug and play and easy to use in the $300 rage tops that has the WiFi router integrated. It seems only Hacom offers this. Can anyone recommend something different or has anyone here tried Hacom WiFi routers? Any additional comments or recommendations? Thanks, -- Alejandro Imass Get a HostAP capable miniPCI card and stick it in a netbook. I did that to an Acer I picked up cheap and added external antenna (not sure how much that mattered), works great all for under 300USD. I'm running OpenBSD on mine but should do any of the firewall/routers specific variants just fine. -- | _ ASCII Ribbon Eric S Pulley | ( ) Campaign Against pul...@dabus.com | X HTML Mail | / \ www.asciiribbon.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
http://localhost/phpmyadmin
Can you show http://localhost/phpmyadmin/ in my Mozilla fire fox? ___ 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
http://localhost/phpmyadmin
___ 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: Home WiFi Router with pfSense or m0n0wall?
Alejandro Imass wrote: Hi, I'm looking to replace the piece of crap 2wire WiFi router that gets crakced every other day for something with pfSense or m0n0wall Not sure what you mean by 'cracked' here. If you are meaning that someone is using aircrack-ng to break your Wifi authentication key a firewall won't do much to stop this. -Mike [snip] ___ 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: Keeping FreeBSD with custom kernel up to date: freebsd-update no option?
Thank you, Polytropon. I have (as far as I can tell) successfully upgraded to 9.1-RELEASE-p2 now. For this I moved /usr/src (SVN) out of the way and followed the upgrade process described in 25.2.3.2 Performing the Upgrade in the Handbook [1]. on 17.4.13 22:55 Polytropon said the following: On Wed, 17 Apr 2013 22:37:06 +0200, andreas scherrer wrote: For some reason I was under the impression that /usr/src/sys is not being updated by freebsd-update if I remove kernel from the Components directive in freebsd-update.conf. But I might be wrong (I will check). According to the documentation, /usr/src (and therefor the /usr/src/sys subtree) is part of the src component, not of kernel, so it should be updated properly. OK. I will check if my /usr/src(/sys) ever changes now. I too think it should. Maybe related to this: how does freebsd-update know what sources/binaries to get when I don't use the -r switch? Does it rely on /usr/src/sys/conf/newvers.sh? That would still interest me (also see below). By following -RELEASE, freebsd-update will apply _that_ snapshot of the source tree and the prebuild world and kernel at the revision when X.Y-RELEASE-pZ has been verified, sloppily said. So it basically doesn't matter what sources you have on your machine (or even if you have any sources) as long as you're not going to compile anything. But because this is a requirement in your specific setting, freebsd-update will take care of that by having the src component on its list. So how would I follow -RELEASE. Or how does freebsd-update what I want to follow (see above)? I don't want to, so this is an academic question... And something else is bugging me: Is there a way I can contact someone (Tom Rhodes?) about the outdated freebsd-update documentation (concerning the custom kernel handling) in the Handbook (FreeBSD Update [2])? Colin Percival's email is in the man page, would that be the way to go? The Handbook states that Tom Rhodes wrote the freebsd-update section but does not reveal an email address... Kind regards andreas [1] http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html [2] http://www.freebsd.org/doc/en/books/handbook/updating-upgrading-freebsdupdate.html ___ 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: Managing conflicts between ports (same package with multiple maintained versions)
On 21/04/2013 10:24, Matthias Petermann wrote: root@compaq:/usr/ports/finance/trytond # portlint -AC [...] FATAL: Package conflicts with itself. You should remove trytond-* from CONFLICTS. 1 fatal error and 4 warnings found. root@compaq:/usr/ports/finance/trytond # So it looks like I need to explicitly specify the conflicting versions, e.g. in Tryton 2.4 Makefile put: CONFLICTS= trytond-2.6.* But this will force me to update the 2.4 Ports everytime a new series of Tryton gets introduced. The usual idiom would be to use a more complex globbing expression, perhaps like so: CONFLICTS= trytond-2.[012356789].* However clearly this won't account for all possible future versions. The thing you have to ask yourself is 'will the upstream be releasing new version series so frequently that I need to add code to all the tryton ports to account for it?' It may well be the case that updating the CONFLICTS setting in all the ports for the different streams whenerver a new stream is released really is the most effective solution. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Managing conflicts between ports (same package with multiple maintained versions)
Thanks Matthew, your recommendation works for me. As I expect from time to time also an older version getting EOL'd, the amount of versions to look ahead can be estimated quite well. Kind regards, Matthias On 04/21/13 17:57, Matthew Seaman wrote: On 21/04/2013 10:24, Matthias Petermann wrote: root@compaq:/usr/ports/finance/trytond # portlint -AC [...] FATAL: Package conflicts with itself. You should remove trytond-* from CONFLICTS. 1 fatal error and 4 warnings found. root@compaq:/usr/ports/finance/trytond # So it looks like I need to explicitly specify the conflicting versions, e.g. in Tryton 2.4 Makefile put: CONFLICTS= trytond-2.6.* But this will force me to update the 2.4 Ports everytime a new series of Tryton gets introduced. The usual idiom would be to use a more complex globbing expression, perhaps like so: CONFLICTS= trytond-2.[012356789].* However clearly this won't account for all possible future versions. The thing you have to ask yourself is 'will the upstream be releasing new version series so frequently that I need to add code to all the tryton ports to account for it?' It may well be the case that updating the CONFLICTS setting in all the ports for the different streams whenerver a new stream is released really is the most effective solution. Cheers, 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
