netstat manpage update
Hi, I've just added -R to netstat. It's like -x but instead of spitting out the socket buffer details, it spits out the flowid details. I'd like some help to get the manpage updated. Thanks! -a ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
request: help updating TASKQUEUE(9)
Hi, I've just added a new call to taskqueue - taskqueue_start_threads_pinned(). It's like taskqueue_start_threads(), but it takes a cpuid to pin the threads to. Would someone please help me with the manpage markup and wording? Thanks! -a ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: request: help updating TASKQUEUE(9)
Yup! Thanks! -a On 24 May 2014 15:02, Benjamin Kaduk wrote: > On Sat, 24 May 2014, Adrian Chadd wrote: > >> Hi, >> >> I've just added a new call to taskqueue - >> taskqueue_start_threads_pinned(). It's like taskqueue_start_threads(), >> but it takes a cpuid to pin the threads to. >> >> Would someone please help me with the manpage markup and wording? > > > Something like this? > > -Ben ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
looking for help to document the new RSS stuff
Hi! I'm looking for some help to document the new RSS stuff. I'm happy writing up some text documentation - shall I just email out the bits here so I can get some help with markup and such? Thanks! -a ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: looking for help to document the new RSS stuff
On 6 July 2014 12:46, Warren Block wrote: > On Sun, 6 Jul 2014, Adrian Chadd wrote: > >> I'm looking for some help to document the new RSS stuff. >> >> I'm happy writing up some text documentation - shall I just email out >> the bits here so I can get some help with markup and such? > > > Is this for a man page or book or article? Just manpages to start with. I'll worry about updating the handbook once I finish the rest of it off (IPv6, UDP, multi-socket, etc.) But I'd at least like a manpage describing what I'm about to throw into -HEAD so people can give it a whirl. -a ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-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 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-curr...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 17 July 2014 12:57, Andreas Nilsson wrote: > > > > On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd 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-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 17 July 2014 13:03, Alberto Mijares wrote: > On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd 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-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 17 July 2014 13:15, Navdeep Parhar wrote: > On 07/17/14 13:12, Adrian Chadd wrote: >> On 17 July 2014 13:03, Alberto Mijares wrote: >>> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd 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-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 17 July 2014 13:54, Baptiste Daroussin 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 wrote:
>>
>> > On 07/17/14 13:12, Adrian Chadd wrote:
>> > > On 17 July 2014 13:03, Alberto Mijares wrote:
>> > >> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd
>> > 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__enable, right?
-a
___
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
Hi!
On 18 July 2014 07:28, Lars Engels 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 wrote:
>>
>> > On 07/17/14 13:12, Adrian Chadd wrote:
>> > > On 17 July 2014 13:03, Alberto Mijares wrote:
>> > >> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd
>> > 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 hacked up a solution for service(8):
>
> http://bsd-geek.de/FreeBSD/service.sh.enable-disable.patch
>
> The patch adds the following directives to service(8):
>
> enable: Grabs an rc script's rcvar value and runs "sysrc foo_enable=YES"
> disable: The opposite of enable
> rcdelete: Deletes an rc script's rcvar value from /etc/rc.conf using
> "sysrc -x foo_enable"
>
> The nice thing about is that you can use one of the new directives on
> one line with the old ones, as long as the new are the first argument:
>
> # service syslogd enable
> # service apache24 disable stop
> # service apache24 rcdelete stop
> # service nginx enable start
>
>
> So after installing a package, to start and enable a daemon permanently
> all you have to run is
> # service foo enable start
>
> Lars
>
> P.S.: Thansk to Devin for his hard work on sysrc!
Having a way for sysrc and service to know what particular options and
services are exposed by a given package or installed "thing" would be
nice. Right now the namespace is very flat and it's not obvious in all
instances what needs to happen to make it useful and what the options
are.
"Oh, hm, I'd like to know what options there are for controlling the
installed apache24 package, let's see"...
I remember IRIX having that command to list services, stop them and
start them, configure them enabled and disabled. Solaris grew
something like that with Solaris 10 and after the initial learning
curve it was great. Hving something like that would be 100% awesome.
-a
___
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 18 July 2014 14:21, Baptiste Daroussin wrote:
> On Fri, Jul 18, 2014 at 12:10:34PM -0700, Adrian Chadd wrote:
>> Hi!
>>
>>
>> On 18 July 2014 07:28, Lars Engels 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
>> >> wrote:
>> >>
>> >> > On 07/17/14 13:12, Adrian Chadd wrote:
>> >> > > On 17 July 2014 13:03, Alberto Mijares wrote:
>> >> > >> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd
>> >> > 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 hacked up a solution for service(8):
>> >
>> > http://bsd-geek.de/FreeBSD/service.sh.enable-disable.patch
>> >
>> > The patch adds the following directives to service(8):
>> >
>> > enable: Grabs an rc script's rcvar value and runs "sysrc foo_enable=YES"
>> > disable: The opposite of enable
>> > rcdelete: Deletes an rc script's rcvar value from /etc/rc.conf using
>> > "sysrc -x foo_enable"
>> >
>> > The nice thing about is that you can use one of the new directives on
>> > one line with the old ones, as long as the new are the first argument:
>> >
>> > # service syslogd enable
>> > # service apache24 disable stop
>> > # service apache24 rcdelete stop
>> > # service nginx enable start
>> >
>> >
>> > So after installing a package, to start and enable a daemon permanently
>> > all you have to run is
>> > # service foo enable start
>> >
>> > Lars
>> >
>> > P.S.: Thansk to Devin for his hard work on sysrc!
>>
>> Having a way for sysrc and service to know what particular options and
>> services are exposed by a given package or installed "thing" would be
>> nice. Right now the namespace is very flat and it's not obvious in all
>> instances what needs to happen to make it useful and what the options
>> are.
>>
>> "Oh, hm, I'd like to know what options there are for controlling the
>> installed apache24 package, let's see"...
>>
>> I remember IRIX having that command to list services, stop them and
>> start them, configure them enabled and disabled. Solaris grew
>> something like that with Solaris 10 and after the initial learning
>> curve it was great. Hving something like that would be 100% awesome.
>>
> you are asking for rcng2 with a declarative init config rather the a script
It can be a series of scripts. The problem is that the namespace for
options has nothing else attached, like "Hi I'm an option that
starts/stops a service", "Hi I'm an option that's for this package",
"Hi I'm an option that's for this class of things." Right now there's
just a series of shell variables with educated guesses about what
package they're related to and what they do, rather than anything that
specifically says what they do.
-a
___
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: [PATCHES] Extend service(8) and rc(8) was: Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
Hi!
I like it! It's a useful command line API.
Eventually people will realise there needs to be a more formal method
for describing/controlling the underlying framework, but I leave that
up to bapt to figure out and .. well, push people to do. :)
Thanks!
-a
On 19 July 2014 09:08, Lars Engels wrote:
> On Fri, Jul 18, 2014 at 12:10:34PM -0700, Adrian Chadd wrote:
>> Hi!
>>
>>
>> On 18 July 2014 07:28, Lars Engels 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
>> >> wrote:
>> >>
>> >> > On 07/17/14 13:12, Adrian Chadd wrote:
>> >> > > On 17 July 2014 13:03, Alberto Mijares wrote:
>> >> > >> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd
>> >> > 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 hacked up a solution for service(8):
>> >
>> > http://bsd-geek.de/FreeBSD/service.sh.enable-disable.patch
>> >
>> > The patch adds the following directives to service(8):
>> >
>> > enable: Grabs an rc script's rcvar value and runs "sysrc foo_enable=YES"
>> > disable: The opposite of enable
>> > rcdelete: Deletes an rc script's rcvar value from /etc/rc.conf using
>> > "sysrc -x foo_enable"
>> >
>> > The nice thing about is that you can use one of the new directives on
>> > one line with the old ones, as long as the new are the first argument:
>> >
>> > # service syslogd enable
>> > # service apache24 disable stop
>> > # service apache24 rcdelete stop
>> > # service nginx enable start
>> >
>> >
>> > So after installing a package, to start and enable a daemon permanently
>> > all you have to run is
>> > # service foo enable start
>> >
>> > Lars
>> >
>> > P.S.: Thansk to Devin for his hard work on sysrc!
>>
>> Having a way for sysrc and service to know what particular options and
>> services are exposed by a given package or installed "thing" would be
>> nice. Right now the namespace is very flat and it's not obvious in all
>> instances what needs to happen to make it useful and what the options
>> are.
>>
>> "Oh, hm, I'd like to know what options there are for controlling the
>> installed apache24 package, let's see"...
>>
>> I remember IRIX having that command to list services, stop them and
>> start them, configure them enabled and disabled. Solaris grew
>> something like that with Solaris 10 and after the initial learning
>> curve it was great. Hving something like that would be 100% awesome.
>
> I've updated the patch and extended it a little:
>
> https://phabric.freebsd.org/D451
>
> It can now print the rc options for a service.
> It needs however to have the options listed as comments between the
> KEYWORDS section and the sourcing of /etc/rc.subr.
>
>
> And I've made some changes to rc.subr itself:
>
> https://phabric.freebsd.org/D452
>
> So now you can use
>
> # service sshd describe
> Secure Shell Daemon
>
> and
>
> # service sshd extracommands
> configtest keygen reload
>
>
> Sorry for the mess in phabricator's SUMMARY. I will learn the markup
> syntax later...
>
>
> Lars
___
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
review request: BUS_GET_DOMAIN.9
Hi, I have written (well, crimed from another page) BUS_GET_DOMAIN.9 . http://pastebin.com/iNDj4pYc Would someone please give me a hand in reviewing it so I can land it in FreeBSD? THanks! -a ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
