Re: USB 2.0 webcam in virtualbox on CURRENT not working!
17.07.2014 08:30, Sergey V. Dyatko пишет: On Wed, 16 Jul 2014 23:40:48 +0200 Hans Petter Selasky h...@selasky.org wrote: On 07/16/14 13:40, Maciej Milewski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.07.2014 13:28, O. Hartmann wrote: I desperately need to have a SKYPE based chat with an offshore department. Since Skype is not a native port, I try to use a virtual box running Windows 7. And here the nightmare begins. Skype works in the VBox, but audio only. I have two WebCAMs here, a brand new Logitech C270 and a older Medion MD86511. The latter one can be seen in the device list of Windows 7 within the VBox, but can not be activated. More frustrating, the Logitech C270, doesn't work, it is not even seen by the VBox. I tested the cam on another Windows 7 system of a colleague and it works. FreeBSD does also see this USB Cam, but why is the device hidden for the VBox? What do you mean by saying see? usbconfig on freebsd lists it as ugen device? Is it attached to vbox machine by some filter? Have you tried VBoxManage usbfilter add? I'm currently using some kind of software security jingle device this way: VBoxManage usbfilter add 1 --target VMachineName --name USBKey --vendorid 0x --productid 0x But I haven't used any webcam this way. In the configuration, I have the ability to enable/disable USB 2.0 subsystem. Enabled, VBox rejects to start on all FBSD around (9.3-PRE, 11-CURRENT). What is that? Is VBox not capable of using USB 2.0 devices in conjunction with FreeBSD? How to solve this? Is there a Skype 6 client for FreeBSD? Thanks in advance, please CC me, Oliver Hi, Skype: Mount this union with /usr/ports: https://github.com/cpu82/skype4-ports And then you can install skype and even use the video chat. Note: This GH repository is outdated, please, you should install or update your ports tree from the following repository: https://github.com/xmj/linux-ports/ xmj follow the instructions on https://github.com/xmj/linux-ports/ Does it planned to be merged into main ports tree? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: USB 2.0 webcam in virtualbox on CURRENT not working!
On Thu, 17 Jul 2014 10:25:52 +0300 Alexandr Krivulya shur...@shurik.kiev.ua wrote: 17.07.2014 08:30, Sergey V. Dyatko пишет: On Wed, 16 Jul 2014 23:40:48 +0200 Hans Petter Selasky h...@selasky.org wrote: On 07/16/14 13:40, Maciej Milewski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.07.2014 13:28, O. Hartmann wrote: I desperately need to have a SKYPE based chat with an offshore department. Since Skype is not a native port, I try to use a virtual box running Windows 7. And here the nightmare begins. Skype works in the VBox, but audio only. I have two WebCAMs here, a brand new Logitech C270 and a older Medion MD86511. The latter one can be seen in the device list of Windows 7 within the VBox, but can not be activated. More frustrating, the Logitech C270, doesn't work, it is not even seen by the VBox. I tested the cam on another Windows 7 system of a colleague and it works. FreeBSD does also see this USB Cam, but why is the device hidden for the VBox? What do you mean by saying see? usbconfig on freebsd lists it as ugen device? Is it attached to vbox machine by some filter? Have you tried VBoxManage usbfilter add? I'm currently using some kind of software security jingle device this way: VBoxManage usbfilter add 1 --target VMachineName --name USBKey --vendorid 0x --productid 0x But I haven't used any webcam this way. In the configuration, I have the ability to enable/disable USB 2.0 subsystem. Enabled, VBox rejects to start on all FBSD around (9.3-PRE, 11-CURRENT). What is that? Is VBox not capable of using USB 2.0 devices in conjunction with FreeBSD? How to solve this? Is there a Skype 6 client for FreeBSD? Thanks in advance, please CC me, Oliver Hi, Skype: Mount this union with /usr/ports: https://github.com/cpu82/skype4-ports And then you can install skype and even use the video chat. Note: This GH repository is outdated, please, you should install or update your ports tree from the following repository: https://github.com/xmj/linux-ports/ xmj follow the instructions on https://github.com/xmj/linux-ports/ Does it planned to be merged into main ports tree? better ask author (xmj), CCd :-) -- wbr, tiger ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Future of pf / firewall in FreeBSD ? - does it have one ?
Hi all, I have been encouraged by people on the pf-mailinglist to move this discussion to the current mailinglist since this may be an area in the OS where FreeBSD need to focus on next. First of all I am a happy user of the pf-firewall module and have been for years and think it is really great - the trouble is that lately (since 2008) its getting a bit dusty. The last few years it seem that pf in FreeBSD got a long way away from pf in OpenBSD where it originated - also looking at the ipfilter (ipf) and ipfw - they both to me do not seem to be as complete as pf. So I am curious if any on the mailing could elaborate about what the future of pf in FreeBSD is or should be. a) First of all - are any actively developing pf in FreeBSD? b) We are a major release away from OpenBSD (5.6 coming soon) - is following OpenBSD's pf the past? - should it be? c) We never got the new syntax from OpenBSD 4.7's pf - at the time a long discussion on the pf-mailing list flamed the new syntax saying it would cause FreeBSD administrators too much headache. Today on the list it seems everyone wants it - so would we rather stay on a dead branch than keep up with the main stream? d) Anyone working on bringing FreeBSD up to pf 5.6? - seem dead on the pf-list. e) OpenBSD is retiring ALTQ entirely - any thoughts on that? http://undeadly.org/cgi?action=articlesid=20140419151959 f) IPv6 support?- it seem to be more and more challenged in the current version of pf in FreeBSD and I am (as well as others) introducing more and more IPv6 in networks. E.x. Bugs #179392, #172648, #130381, #127920 and more seriously #124933, which is the bug on not handling IPv6 fragments which have been open since 2008 and where the workaround is necessity to leave an completely open hole in your firewall ruleset to allow all fragments. According to comment in the bug, this have been long gone in OpenBSD. g) Performance, can we live with pf-performance that compared to OpenBSD is slower by a factor of 3 or 4, even after the multi-core support in FreeBSD 10? (Henning Brauer noted that in this talk at http://tech.yandex.ru/events/yagosti/ruBSD/talks/1488/ (at 33:18 and 36:53)) - credit/Jim Thompson h) Bringing back patches from pfSense? And my most important question: * Should this or could this be a project for the foundation to either do a summer project or funded project to bring this part of the OS up to date? Hope to heard from you all, Best regards, Kristian Kræmmer Nielsen, Odense, Denmark ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: PostgreSQL performance on FreeBSD
On 7/16/2014 5:59 PM, Konstantin Belousov wrote: On Fri, Jun 27, 2014 at 03:56:13PM +0300, Konstantin Belousov wrote: Hi, I did some measurements and hacks to see about the performance and scalability of PostgreSQL 9.3 on FreeBSD, sponsored by The FreeBSD Foundation. The results are described in https://kib.kiev.ua/kib/pgsql_perf.pdf. The uncommitted patches, referenced in the article, are available as https://kib.kiev.ua/kib/pig1.patch.txt https://kib.kiev.ua/kib/patch-2 A followup to the original paper. Most importantly, I identified the cause for the drop on the graph after the 30 clients, which appeared to be the debugging version of malloc(3) in libc. Also there are some updates on the patches. New version of the paper is available at https://www.kib.kiev.ua/kib/pgsql_perf_v2.0.pdf The changes are marked as 'update for version 2.0'. Thanks for the great work! Did you tested the effect of hyper-threading (on or off) on the results? -- Best regards. Hooman Fazaeli ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
Hi, I attend a lot of different Meetup groups in the San Francisco Bay Area / Silicon Valley. What I am seeing is the following usage pattern for new developers, especially for web apps and cloud applications. (1) On their desktop/laptop, they will generally be using a Mac running OS X. This is their desktop Unix environment. This seems to be true of almost 90% of the people that I meet. The 10% of people who run a PC laptop, will mostly be running Windows. Very few seem to run Linux on their laptops, but if they do, it will likely be Ubuntu Linux. (2) For their deployed application, generally they will deploy to a Linux environment on a server. These days, the server will very likely be in a cloud environment: Amazon, Rackspace, Heroku. For (1), encouraging people to move away from a Mac to FreeBSD for their desktop environment is a tough sell. Apple is a multi-billion dollar company, and they make beautiful hardware, and software with a fantastic end-user experience. The PC-BSD project is fighting the good fight in terms of making a usable FreeBSD desktop, but its a touch battle to fight. For (2), encouraging people to move away from Linux to FreeBSD on the server, may be something where we can get more wins. I think we can do this by having more HOWTO articles on the FreeBSD web page that explain the following: (1) We need a HOWTO article that explains for each command using apt or yum for installing packages, how can I do the same thing using pkg. Even if we have a web page with a table, contrasting the apt/yum commands, and pkg commands, that would be super useful. A lot of folks have moved away from FreeBSD, purely because they are sick of pkg_add. We need to explain to folks that we have something better, that is quite competitive to apt/yum, and it is easy to use. (2) We need a HOWTO article that explains how to set up a FreeBSD environment with some of the major cloud providers, i.e. Amazon, Rackspace, Microsoft Azure, etc. Do we have such articles today, or is anybody working on something like that? I think if we had these two HOWTO articles today, and we could aggressively point people at them, this would be a huge win for expanding the number of people who try out FreeBSD for modern server applications. -- Craig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; 5) .. and then we need examples of actually deploying useful scenarios, like so here's what you type to get django working right, here's how you get a default memcached that works well, here's how you bring up node.js, etc. 6) Then make VMs of the above so people can just clone and install them. -a On 17 July 2014 11:25, Craig Rodrigues rodr...@freebsd.org wrote: Hi, I attend a lot of different Meetup groups in the San Francisco Bay Area / Silicon Valley. What I am seeing is the following usage pattern for new developers, especially for web apps and cloud applications. (1) On their desktop/laptop, they will generally be using a Mac running OS X. This is their desktop Unix environment. This seems to be true of almost 90% of the people that I meet. The 10% of people who run a PC laptop, will mostly be running Windows. Very few seem to run Linux on their laptops, but if they do, it will likely be Ubuntu Linux. (2) For their deployed application, generally they will deploy to a Linux environment on a server. These days, the server will very likely be in a cloud environment: Amazon, Rackspace, Heroku. For (1), encouraging people to move away from a Mac to FreeBSD for their desktop environment is a tough sell. Apple is a multi-billion dollar company, and they make beautiful hardware, and software with a fantastic end-user experience. The PC-BSD project is fighting the good fight in terms of making a usable FreeBSD desktop, but its a touch battle to fight. For (2), encouraging people to move away from Linux to FreeBSD on the server, may be something where we can get more wins. I think we can do this by having more HOWTO articles on the FreeBSD web page that explain the following: (1) We need a HOWTO article that explains for each command using apt or yum for installing packages, how can I do the same thing using pkg. Even if we have a web page with a table, contrasting the apt/yum commands, and pkg commands, that would be super useful. A lot of folks have moved away from FreeBSD, purely because they are sick of pkg_add. We need to explain to folks that we have something better, that is quite competitive to apt/yum, and it is easy to use. (2) We need a HOWTO article that explains how to set up a FreeBSD environment with some of the major cloud providers, i.e. Amazon, Rackspace, Microsoft Azure, etc. Do we have such articles today, or is anybody working on something like that? I think if we had these two HOWTO articles today, and we could aggressively point people at them, this would be a huge win for expanding the number of people who try out FreeBSD for modern server applications. -- Craig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; I disagree on this. For network services on linux ( apart from ssh ), I want that started very seldom. But I do want the package installed so that when I need it, it is there. Having it autostart as part of being installed is breaking KISS and in some way unix philosophy: I asked for something to be installed, not installed and autostarted. 5) .. and then we need examples of actually deploying useful scenarios, like so here's what you type to get django working right, here's how you get a default memcached that works well, here's how you bring up node.js, etc. Oh yes. I think that quite a few packages have default options that make them unsuitable for out-of-box usage, ie some lack the sane default dbi-stuff and so on. 6) Then make VMs of the above so people can just clone and install them. At least zfs-datasets ready to be run as jails would be really good too. /A -a On 17 July 2014 11:25, Craig Rodrigues rodr...@freebsd.org wrote: Hi, I attend a lot of different Meetup groups in the San Francisco Bay Area / Silicon Valley. What I am seeing is the following usage pattern for new developers, especially for web apps and cloud applications. (1) On their desktop/laptop, they will generally be using a Mac running OS X. This is their desktop Unix environment. This seems to be true of almost 90% of the people that I meet. The 10% of people who run a PC laptop, will mostly be running Windows. Very few seem to run Linux on their laptops, but if they do, it will likely be Ubuntu Linux. (2) For their deployed application, generally they will deploy to a Linux environment on a server. These days, the server will very likely be in a cloud environment: Amazon, Rackspace, Heroku. For (1), encouraging people to move away from a Mac to FreeBSD for their desktop environment is a tough sell. Apple is a multi-billion dollar company, and they make beautiful hardware, and software with a fantastic end-user experience. The PC-BSD project is fighting the good fight in terms of making a usable FreeBSD desktop, but its a touch battle to fight. For (2), encouraging people to move away from Linux to FreeBSD on the server, may be something where we can get more wins. I think we can do this by having more HOWTO articles on the FreeBSD web page that explain the following: (1) We need a HOWTO article that explains for each command using apt or yum for installing packages, how can I do the same thing using pkg. Even if we have a web page with a table, contrasting the apt/yum commands, and pkg commands, that would be super useful. A lot of folks have moved away from FreeBSD, purely because they are sick of pkg_add. We need to explain to folks that we have something better, that is quite competitive to apt/yum, and it is easy to use. (2) We need a HOWTO article that explains how to set up a FreeBSD environment with some of the major cloud providers, i.e. Amazon, Rackspace, Microsoft Azure, etc. Do we have such articles today, or is anybody working on something like that? I think if we had these two HOWTO articles today, and we could aggressively point people at them, this would be a huge win for expanding the number of people who try out FreeBSD for modern server applications. -- Craig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 17 July 2014 12:57, Andreas Nilsson andrn...@gmail.com wrote: On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; I disagree on this. For network services on linux ( apart from ssh ), I want that started very seldom. But I do want the package installed so that when I need it, it is there. Having it autostart as part of being installed is breaking KISS and in some way unix philosophy: I asked for something to be installed, not installed and autostarted. That's cool. We can disagree on that. But the fact that you have to edit a file to enable things and hope you get the right start entry in /etc/rc.conf or /usr/local/etc/rc.conf, or wherever you put it is, is a pain. -a ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? -a ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Regards, Alberto Mijares ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 07/17/14 13:12, Adrian Chadd wrote: On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? Aren't sysrc(8) and service(8) for this kind of stuff? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar npar...@gmail.com wrote:
On 07/17/14 13:12, Adrian Chadd wrote:
On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote:
On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org
wrote:
Hi!
3) The binary packages need to work out of the box
4) .. which means, when you do things like pkg install apache, it
can't just be installed and not be enabled, because that's a bit of a
problem;
No. Please NEVER do that! The user must be able to edit the files and
start the service by himself.
Cool, so what's the single line command needed to type in to start a
given package service?
Aren't sysrc(8) and service(8) for this kind of stuff?
They sure are.
Well, pkg install $service ; sysrc ${service}_enable=YES would do.
Although some services have different names than the packge, which is sort
of annoying.
I wouldn't mind though if pkg via dialog or some such mechanism asked if
wanted it enabled. Or via pkg-message told me howto enable it.
/A
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 17 July 2014 13:15, Navdeep Parhar npar...@gmail.com wrote: On 07/17/14 13:12, Adrian Chadd wrote: On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? Aren't sysrc(8) and service(8) for this kind of stuff? Yup, and if the default is going to be off, then you want the instructions to be type this in, not edit this file. There's odd things too, like oh look I installed xorg, but then I can't run it without enabling hald/dbus, then starting it.. oh wait, no mouse, so I have to reboot for them to come up right kind of crap. That's the kind of thing that turns people away. -a ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 3:42 PM, Adrian Chadd adr...@freebsd.org wrote: On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? # service appname onestart For the rest, read the manual and understand your OS. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 10:21 PM, Adrian Chadd adr...@freebsd.org wrote: On 17 July 2014 13:15, Navdeep Parhar npar...@gmail.com wrote: On 07/17/14 13:12, Adrian Chadd wrote: On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? Aren't sysrc(8) and service(8) for this kind of stuff? Yup, and if the default is going to be off, then you want the instructions to be type this in, not edit this file. There's odd things too, like oh look I installed xorg, but then I can't run it without enabling hald/dbus, then starting it.. oh wait, no mouse, so I have to reboot for them to come up right kind of crap. That's the kind of thing that turns people away. But this is more of a desktop/laptop setup, right? If services had an option ( the ones provided via ports anyway) for autostart, and package sets for different use cases was provided, like server and desktop say, there could for desktop be the default to have the option set for autostart and for server the option would be to not autostart. /A ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar npar...@gmail.com wrote:
On 07/17/14 13:12, Adrian Chadd wrote:
On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote:
On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org
wrote:
Hi!
3) The binary packages need to work out of the box
4) .. which means, when you do things like pkg install apache, it
can't just be installed and not be enabled, because that's a bit of a
problem;
No. Please NEVER do that! The user must be able to edit the files and
start the service by himself.
Cool, so what's the single line command needed to type in to start a
given package service?
Aren't sysrc(8) and service(8) for this kind of stuff?
They sure are.
Well, pkg install $service ; sysrc ${service}_enable=YES would do.
Although some services have different names than the packge, which is sort
of annoying.
Maybe service needs to be extended (seriously sysrc ${service}_enable=YES is
not user friendly) we have service -l that list the services, maybe a service
${service} on that create /etc/rc.conf.d/${service} with ${service}_enable=YES
in it and service ${service} off to remove it
maybe service -l could also be extended to show the current status (maybe with a
-v switch)
but for sure having the service off by default is a good idea :)
regards,
Bapt
pgpPDGYS8Mmyi.pgp
Description: PGP signature
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 01:21:32PM -0700, Adrian Chadd wrote: On 17 July 2014 13:15, Navdeep Parhar npar...@gmail.com wrote: On 07/17/14 13:12, Adrian Chadd wrote: On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? Aren't sysrc(8) and service(8) for this kind of stuff? Yup, and if the default is going to be off, then you want the instructions to be type this in, not edit this file. There's odd things too, like oh look I installed xorg, but then I can't run it without enabling hald/dbus, then starting it.. oh wait, no mouse, so I have to reboot for them to come up right kind of crap. yes that is why xorg needs to have devd instead of hal support by default :) regards, Bapt pgpyIxofSUsXQ.pgp Description: PGP signature
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 17 July 2014 13:54, Baptiste Daroussin b...@freebsd.org wrote:
On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar npar...@gmail.com wrote:
On 07/17/14 13:12, Adrian Chadd wrote:
On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote:
On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org
wrote:
Hi!
3) The binary packages need to work out of the box
4) .. which means, when you do things like pkg install apache, it
can't just be installed and not be enabled, because that's a bit of a
problem;
No. Please NEVER do that! The user must be able to edit the files and
start the service by himself.
Cool, so what's the single line command needed to type in to start a
given package service?
Aren't sysrc(8) and service(8) for this kind of stuff?
They sure are.
Well, pkg install $service ; sysrc ${service}_enable=YES would do.
Although some services have different names than the packge, which is sort
of annoying.
Maybe service needs to be extended (seriously sysrc ${service}_enable=YES is
not user friendly) we have service -l that list the services, maybe a service
${service} on that create /etc/rc.conf.d/${service} with
${service}_enable=YES
in it and service ${service} off to remove it
maybe service -l could also be extended to show the current status (maybe
with a
-v switch)
but for sure having the service off by default is a good idea :)
Yeah, maybe having it populate an entry of service_enable=NO for now .
It's even more unclear-ish - it's not obvious which options control
services and which ones are configuration things. We don't call it
service_xxx_enable, right?
-a
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, 2014-07-17 at 13:21 -0700, Adrian Chadd wrote: On 17 July 2014 13:15, Navdeep Parhar npar...@gmail.com wrote: On 07/17/14 13:12, Adrian Chadd wrote: On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? Aren't sysrc(8) and service(8) for this kind of stuff? Yup, and if the default is going to be off, then you want the instructions to be type this in, not edit this file. There's odd things too, like oh look I installed xorg, but then I can't run it without enabling hald/dbus, then starting it.. oh wait, no mouse, so I have to reboot for them to come up right kind of crap. That's the kind of thing that turns people away. I see your point, and agree that there should be clear instructions after installing a port/package. Most ports I install already do a good job at this. But I would not like anything to autostart just because I install it. Prefer to enable rather than disable something, or worse, having it autostart without knowing. That's the kind of thing that turned me to FreeBSD :-) -a ___ freebsd-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 01:57:52PM -0700, Adrian Chadd wrote:
On 17 July 2014 13:54, Baptiste Daroussin b...@freebsd.org wrote:
On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar npar...@gmail.com wrote:
On 07/17/14 13:12, Adrian Chadd wrote:
On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote:
On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org
wrote:
Hi!
3) The binary packages need to work out of the box
4) .. which means, when you do things like pkg install apache, it
can't just be installed and not be enabled, because that's a bit of a
problem;
No. Please NEVER do that! The user must be able to edit the files and
start the service by himself.
Cool, so what's the single line command needed to type in to start a
given package service?
Aren't sysrc(8) and service(8) for this kind of stuff?
They sure are.
Well, pkg install $service ; sysrc ${service}_enable=YES would do.
Although some services have different names than the packge, which is sort
of annoying.
Maybe service needs to be extended (seriously sysrc ${service}_enable=YES
is
not user friendly) we have service -l that list the services, maybe a
service
${service} on that create /etc/rc.conf.d/${service} with
${service}_enable=YES
in it and service ${service} off to remove it
maybe service -l could also be extended to show the current status (maybe
with a
-v switch)
but for sure having the service off by default is a good idea :)
Yeah, maybe having it populate an entry of service_enable=NO for now .
then you need to extend rcng to support /usr/local/etc/rc.conf.d so the packages
can install them without touching base :) and we will need to wait for all
supported FreeBSD version to have the said modification)
It's even more unclear-ish - it's not obvious which options control
services and which ones are configuration things. We don't call it
service_xxx_enable, right?
imho this is obvious xxx_enable == control service.
regards,
Bapt
pgp7WpAjJ0ste.pgp
Description: PGP signature
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 09:57:44PM +0200, Andreas Nilsson wrote: On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; I disagree on this. For network services on linux ( apart from ssh ), I want that started very seldom. But I do want the package installed so that when I need it, it is there. Having it autostart as part of being installed is breaking KISS and in some way unix philosophy: I asked for something to be installed, not installed and autostarted. 5) .. and then we need examples of actually deploying useful scenarios, like so here's what you type to get django working right, here's how you get a default memcached that works well, here's how you bring up node.js, etc. Oh yes. I think that quite a few packages have default options that make them unsuitable for out-of-box usage, ie some lack the sane default dbi-stuff and so on. Reporting them is very much needed, we try to change this but without report it is hard, as much as I can I use vanilla packages now, and I discovered that they are now pretty much sane, a few example has been found and modified recently like nginx not supporting https by default, so do not hesitate to report any unsuitable options for out-of-box usage. regards, Bapt pgpa473PzXlOE.pgp Description: PGP signature
Re: [CURRENT]: weird memory/linker problem?
Am Tue, 01 Jul 2014 17:23:14 +0200
Willem Jan Withagen w...@digiware.nl schrieb:
On 2014-07-01 16:48, Rang, Anton wrote:
DOT = DOD
444F54 = 444F44
That's a single-bit flip. Bad memory, perhaps?
Very likely, especially if the system does not have ECC
It just happens on rare occasions that a alpha particle, power cycle, or
any things else disruptive damages a memory cell. And it could be that
it requires a special pattern of accesses to actually exhibit the error.
In the past (199x's) 'make buildworld' used to be a rather good memory
tester. But nowadays look at
http://www.memtest.org/
This tool has found all of the bad memory in all the systems I used and
or build for others...
Note that it might take a few runs and some more heat to actually
trigger the faulty cell, but memtest86 will usually find it.
Note that on big systems with lots of memory it can take a loong
time to run just one full testset to completion.
--WjW
Anton
-Original Message-
From: owner-freebsd-curr...@freebsd.org
[mailto:owner-freebsd-curr...@freebsd.org] On
Behalf Of O. Hartmann Sent: Tuesday, July 01, 2014 8:08 AM
To: Dimitry Andric
Cc: Adrian Chadd; FreeBSD CURRENT
Subject: Re: [CURRENT]: weird memory/linker problem?
Am Mon, 23 Jun 2014 17:22:25 +0200
Dimitry Andric d...@freebsd.org schrieb:
On 23 Jun 2014, at 16:31, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
Am Sun, 22 Jun 2014 10:10:04 -0700
Adrian Chadd adr...@freebsd.org schrieb:
When they segfault, where do they segfault?
...
GIMP, LaTeX work, nothing special, but a bit memory consuming
regrading GIMP) I tried updating the ports tree and surprisingly the
tree is left over in a unclean condition while /usr/bin/svn segfault
(on console: pid 18013 (svn), uid 0: exited on signal 11 (core dumped)).
Using /usr/local/bin/svn, which is from the devel/subversion port,
performs well, while FreeBSD 11's svn contribution dies as described. It
did not
hours ago!
I think what Adrian meant was: can you run svn (or another crashing
program) in gdb, and post a backtrace? Or maybe run ktrace, and see
where it dies?
Alternatively, put a core dump and the executable (with debug info) in
a tarball, and upload it somewhere, so somebody else can analyze it.
-Dimitry
It's me again, with the same weird story.
After a couple of days silence, the mysterious entity in my computer is
back. This
time it is again a weird compiler message of failure (trying to buildworld):
[...]
c++ -O2 -pipe -O3 -O3
c++ -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I.
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include
-DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS
-D__STDC_CONSTANT_MACROS
-fno-strict-aliasing
-DLLVM_DEFAULT_TARGET_TRIPLE=\x86_64-unknown-freebsd11.0\
-DLLVM_HOST_TRIPLE=\x86_64-unknown-freebsd11.0\ -DDEFAULT_SYSROOT=\\
-Qunused-arguments -I/usr/obj/usr/src/tmp/legacy/usr/include -std=c++11
-fno-exceptions -fno-rtti -Wno-c++11-extensions
-c
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Host.cpp
-o
Host.o --- GraphWriter.o --- In file included
from
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/GraphWriter.cpp:14:
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/Support/GraphWriter.h:269:10:
error: use of undeclared identifier 'DOD'; did you mean 'DOT'? O
DOD::EscapeString(Label); ^~~
DOT
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/Support/GraphWriter.h:35:11:
note: 'DOT' declared here namespace DOT { // Private functions... ^ 1 error
generated. *** [GraphWriter.o] Error code 1
Well, in the past I saw many of those messages, especially not found labels
of
routines in shared objects/libraries or even those funny misspelled
messages shown
above.
I can not reproduce them after a reboot, but as long as the system is
running with
this error occured, it is sticky. So in order to compile the OS
successfully, I
reboot.
Does anyone have an idea what this could be? Since it affects at the moment
only one
machine (the other CoreDuo has been retired in the meanwhile), it feels a
bit like a
miscompilation on a certain type of CPU.
Thanks for your patience,
Oliver
Hello all.
Well, I'd like to update some informations. It doesn't relief the special
concern, but
might be a kind of replenishment of experience.
The box in question is now with only 4GB - and is oprable as expected. With 8
GB, I see
those reported weird bugs and they revealed themselfes as indeed bit flips. I
can not
reproduce them, the occur spontanously, but I can raise the frequency by
Re: PostgreSQL performance on FreeBSD
Am Thu, 17 Jul 2014 20:15:39 +0430 Hooman Fazaeli hoomanfaza...@gmail.com schrieb: On 7/16/2014 5:59 PM, Konstantin Belousov wrote: On Fri, Jun 27, 2014 at 03:56:13PM +0300, Konstantin Belousov wrote: Hi, I did some measurements and hacks to see about the performance and scalability of PostgreSQL 9.3 on FreeBSD, sponsored by The FreeBSD Foundation. The results are described in https://kib.kiev.ua/kib/pgsql_perf.pdf. The uncommitted patches, referenced in the article, are available as https://kib.kiev.ua/kib/pig1.patch.txt https://kib.kiev.ua/kib/patch-2 A followup to the original paper. Most importantly, I identified the cause for the drop on the graph after the 30 clients, which appeared to be the debugging version of malloc(3) in libc. Also there are some updates on the patches. New version of the paper is available at https://www.kib.kiev.ua/kib/pgsql_perf_v2.0.pdf The changes are marked as 'update for version 2.0'. Thanks for the great work! Did you tested the effect of hyper-threading (on or off) on the results? A naive question besides: Does this labor and effort only affects the work with the PostgreSQL 9.3 database and is recent FreeBSD only optimized for this servicing puprpose or provides this also some benefeits for other high-performance scenarios? Oliver signature.asc Description: PGP signature
