From mtm at wubethiopia.com Fri Aug 1 10:51:00 2008 From: mtm at wubethiopia.com (Mike Makonnen) Date: Fri Aug 1 10:51:06 2008 Subject: conf/126060: [ipfw] [patch] IPFW limit checking in nightly security scripts slightly botched In-Reply-To: <200807311926.m6VJQaRT071559@freefall.freebsd.org> References: <200807311926.m6VJQaRT071559@freefall.freebsd.org> Message-ID: <4892E861.9020508@wubethiopia.com> dougb@FreeBSD.org wrote: > Synopsis: [ipfw] [patch] IPFW limit checking in nightly security scripts slightly botched > > Responsible-Changed-From-To: freebsd-rc->freebsd-bugs > Responsible-Changed-By: dougb > Responsible-Changed-When: Thu Jul 31 19:26:12 UTC 2008 > Responsible-Changed-Why: > > periodic != rc > > Correct, but I think -rc is probably the list it's most relevant to. Cheers. -- Mike Makonnen | GPG-KEY: http://people.freebsd.org/~mtm/mtm.asc mtm @ FreeBSD.Org | AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55 FreeBSD | http://www.freebsd.org From dougb at FreeBSD.org Fri Aug 1 19:33:28 2008 From: dougb at FreeBSD.org (Doug Barton) Date: Fri Aug 1 19:33:34 2008 Subject: conf/126060: [ipfw] [patch] IPFW limit checking in nightly security scripts slightly botched In-Reply-To: <4892E861.9020508@wubethiopia.com> References: <200807311926.m6VJQaRT071559@freefall.freebsd.org> <4892E861.9020508@wubethiopia.com> Message-ID: <489364ED.4050307@FreeBSD.org> Mike Makonnen wrote: > dougb@FreeBSD.org wrote: >> Synopsis: [ipfw] [patch] IPFW limit checking in nightly security >> scripts slightly botched >> >> Responsible-Changed-From-To: freebsd-rc->freebsd-bugs >> Responsible-Changed-By: dougb >> Responsible-Changed-When: Thu Jul 31 19:26:12 UTC 2008 >> Responsible-Changed-Why: >> periodic != rc >> >> > Correct, but I think -rc is probably the list it's most relevant to. I have no objection to switching it back if you think it belongs. Doug -- This .signature sanitized for your protection From bugmaster at FreeBSD.org Mon Aug 4 11:07:01 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 4 11:08:41 2008 Subject: Current problem reports assigned to freebsd-rc@FreeBSD.org Message-ID: <200808041107.m74B714h082181@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/98758 rc [jail] [patch] Templatize 'jail_fstab' in /etc/rc.d/ja o conf/98846 rc [jail] [patch] Templatize 'jail_rootdir' in /etc/rc.d/ o conf/105689 rc [ppp] [request] syslogd starts too late at boot o conf/118255 rc savecore never finding kernel core dumps (rcorder prob o conf/122036 rc [rc.d]: Mounting at boot with ZFS causes a halt in boo 5 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/44170 rc [patch] Add ability to run multiple pppoed(8) on start o conf/45226 rc [patch] Fix for rc.network, ppp-user annoyance o conf/56934 rc [patch] rc.firewall rules for natd expect an interface o conf/58939 rc [patch] dumb little hack for /etc/rc.firewall{,6} s bin/65258 rc [patch] [request] save /etc/rc.firewall from changing o conf/73677 rc [patch] add support for powernow states to power_profi o conf/77663 rc Suggestion: add /etc/rc.d/addnetswap after addcritremo o kern/81006 rc ipnat not working with tunnel interfaces on startup o conf/85819 rc [patch] script allowing multiuser mode in spite of fsc o conf/88913 rc [patch] wrapper support for rc.subr o conf/89061 rc [patch] IPv6 6to4 auto-configuration enhancement o conf/89870 rc [patch] [request] make netif verbose rc.conf toggle o conf/92523 rc [patch] allow rc scripts to kill process after a timeo o conf/93815 rc [patch] Adds in the ability to save ipfw rules to rc.d o conf/96343 rc [patch] rc.d order change to start inet6 before pf o conf/99444 rc [patch] Enhancement: rc.subr could easily support star o conf/99721 rc [patch] /etc/rc.initdiskless problem copy dotfile in s o conf/102700 rc [geli] [patch] Add encrypted /tmp support to GELI/GBDE o conf/103486 rc [rc.d] [jail] [patch] rc.d/jail: mount fstab after dev o conf/103489 rc [rc.d] [jail] [patch] named_chroot_autoupdate doesn't o conf/104549 rc [patch] rc.d/nfsd needs special _find_processes functi o conf/105145 rc [ppp] [patch] [request] add redial function to rc.d/pp o conf/105568 rc [patch] [request] Add more flexibility to rc.conf, to o conf/106009 rc [ppp] [patch] [request] Fix pppoed startup script to p o conf/109562 rc [rc.d] [patch] [request] Make rc.d/devfs usable from c o conf/109980 rc /etc/rc.d/netif restart doesn't destroy cloned_interfa o conf/113915 rc [patch] ndis wireless driver fails to associate when i o conf/114119 rc [jail] [patch] [request] /etc/rc.d/jail improvements f o conf/117935 rc [patch] ppp fails to start at boot because of missing o bin/118325 rc [patch] [request] new periodic script to test statuses o conf/119076 rc [patch] [rc] /etc/rc.d/netif tries to remove alias add o conf/119874 rc [patch] "/etc/rc.d/pf reload" fails if there are macro o conf/120194 rc [patch] UFS volumes on ZVOLs cannot be fsck'd at boot o conf/120228 rc [zfs] [patch] Split ZFS volume startup / ease ZFS swap o conf/120406 rc [devd] [patch] Handle newly attached pcm devices (eg. o conf/120431 rc [patch] devfs.rules are not initialized under certain o kern/121566 rc [nfs] [request] [patch] ethernet iface should be broug o conf/122170 rc [patch] [request] New feature: notify admin via page o o conf/122477 rc [patch] /etc/rc.d/mdconfig and mdconfig2 are ignoring o conf/123222 rc [patch] Add rtprio(1)/idprio(1) support to rc.subr(8). o conf/123734 rc [patch] Chipset VIA CX700 requires extra initializatio o conf/124248 rc [patch] add support for nice value for rc.d/jail + rc. o conf/124747 rc [patch] savecore can't create dump from encrypted swap 43 problems total. From gavin at FreeBSD.org Thu Aug 7 19:42:27 2008 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Thu Aug 7 19:42:39 2008 Subject: bin/126324: [patch] rc.d/tmp: Prevent mounting /tmp in second time Message-ID: <200808071942.m77JgQop030965@freefall.freebsd.org> Synopsis: [patch] rc.d/tmp: Prevent mounting /tmp in second time Responsible-Changed-From-To: freebsd-bugs->freebsd-rc Responsible-Changed-By: gavin Responsible-Changed-When: Thu Aug 7 19:36:37 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). Deliberately don't reclassify as conf for now as discussions are currently ongoing. http://www.freebsd.org/cgi/query-pr.cgi?pr=126324 From spam at rm-rf.kiev.ua Fri Aug 8 00:30:03 2008 From: spam at rm-rf.kiev.ua (Alex Kozlov) Date: Fri Aug 8 00:30:09 2008 Subject: bin/126324: [patch] rc.d/tmp: Prevent mounting /tmp in second time Message-ID: <200808080030.m780U3Yu057813@freefall.freebsd.org> The following reply was made to PR bin/126324; it has been noted by GNATS. From: Alex Kozlov To: Kris Kennaway , bug-followup@freebsd.org, spam@rm-rf.kiev.ua Cc: Subject: Re: bin/126324: [patch] rc.d/tmp: Prevent mounting /tmp in second time Date: Fri, 8 Aug 2008 03:25:19 +0300 On Thu, Aug 07, 2008 at 06:50:06PM +0000, Alex Kozlov wrote: > The following reply was made to PR bin/126324; it has been noted by GNATS. > > From: Alex Kozlov > To: Kris Kennaway , bug-followup@freebsd.org, > spam@rm-rf.kiev.ua > Cc: > Subject: Re: bin/126324: [patch] rc.d/tmp: Prevent mounting /tmp in second > time > Date: Thu, 7 Aug 2008 21:49:03 +0300 > > On Thu, Aug 07, 2008 at 07:25:49PM +0200, Kris Kennaway wrote: > > Alex Kozlov wrote: > > > > > Well, as alternative We can just don't touch /tmp if it already mounted. > > This is much better on general grounds. > I post patch for review soon. Index: src/etc/rc.d/tmp @@ -37,13 +37,20 @@ load_rc_config $name +is_mounted () +{ + /sbin/mount | /usr/bin/grep -ql $1 && return 0 + return 1 +} + # If we do not have a writable /tmp, create a memory # filesystem for /tmp. If /tmp is a symlink (e.g. to /var/tmp, -# then it should already be writable). +# then it should already be writable). If we already have /tmp +# mounted somewhere, doing nothing. # case "${tmpmfs}" in [Yy][Ee][Ss]) - mount_md ${tmpsize} /tmp "${tmpmfs_flags}" + is_mounted /tmp || mount_md ${tmpsize} /tmp "${tmpmfs_flags}" chmod 01777 /tmp ;; [Nn][Oo]) @@ -57,7 +64,7 @@ echo "dropping into shell, ^D to continue anyway." /bin/sh else - mount_md ${tmpsize} /tmp "${tmpmfs_flags}" + is_mounted /tmp || mount_md ${tmpsize} /tmp "${tmpmfs_flags}" chmod 01777 /tmp fi fi From bugmaster at FreeBSD.org Mon Aug 11 11:07:03 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 11 11:08:40 2008 Subject: Current problem reports assigned to freebsd-rc@FreeBSD.org Message-ID: <200808111107.m7BB73js047308@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/98758 rc [jail] [patch] Templatize 'jail_fstab' in /etc/rc.d/ja o conf/98846 rc [jail] [patch] Templatize 'jail_rootdir' in /etc/rc.d/ o conf/105689 rc [ppp] [request] syslogd starts too late at boot o conf/118255 rc savecore never finding kernel core dumps (rcorder prob o conf/122036 rc [rc.d]: Mounting at boot with ZFS causes a halt in boo 5 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/44170 rc [patch] Add ability to run multiple pppoed(8) on start o conf/45226 rc [patch] Fix for rc.network, ppp-user annoyance o conf/56934 rc [patch] rc.firewall rules for natd expect an interface o conf/58939 rc [patch] dumb little hack for /etc/rc.firewall{,6} s bin/65258 rc [patch] [request] save /etc/rc.firewall from changing o conf/73677 rc [patch] add support for powernow states to power_profi o conf/77663 rc Suggestion: add /etc/rc.d/addnetswap after addcritremo o kern/81006 rc ipnat not working with tunnel interfaces on startup o conf/85819 rc [patch] script allowing multiuser mode in spite of fsc o conf/88913 rc [patch] wrapper support for rc.subr o conf/89061 rc [patch] IPv6 6to4 auto-configuration enhancement o conf/89870 rc [patch] [request] make netif verbose rc.conf toggle o conf/92523 rc [patch] allow rc scripts to kill process after a timeo o conf/93815 rc [patch] Adds in the ability to save ipfw rules to rc.d o conf/96343 rc [patch] rc.d order change to start inet6 before pf o conf/99444 rc [patch] Enhancement: rc.subr could easily support star o conf/99721 rc [patch] /etc/rc.initdiskless problem copy dotfile in s o conf/102700 rc [geli] [patch] Add encrypted /tmp support to GELI/GBDE o conf/103486 rc [rc.d] [jail] [patch] rc.d/jail: mount fstab after dev o conf/103489 rc [rc.d] [jail] [patch] named_chroot_autoupdate doesn't o conf/104549 rc [patch] rc.d/nfsd needs special _find_processes functi o conf/105145 rc [ppp] [patch] [request] add redial function to rc.d/pp o conf/105568 rc [patch] [request] Add more flexibility to rc.conf, to o conf/106009 rc [ppp] [patch] [request] Fix pppoed startup script to p o conf/109562 rc [rc.d] [patch] [request] Make rc.d/devfs usable from c o conf/109980 rc /etc/rc.d/netif restart doesn't destroy cloned_interfa o conf/113915 rc [patch] ndis wireless driver fails to associate when i o conf/114119 rc [jail] [patch] [request] /etc/rc.d/jail improvements f o conf/117935 rc [patch] ppp fails to start at boot because of missing o bin/118325 rc [patch] [request] new periodic script to test statuses o conf/119076 rc [patch] [rc] /etc/rc.d/netif tries to remove alias add o conf/119874 rc [patch] "/etc/rc.d/pf reload" fails if there are macro o conf/120194 rc [patch] UFS volumes on ZVOLs cannot be fsck'd at boot o conf/120228 rc [zfs] [patch] Split ZFS volume startup / ease ZFS swap o conf/120406 rc [devd] [patch] Handle newly attached pcm devices (eg. o conf/120431 rc [patch] devfs.rules are not initialized under certain o kern/121566 rc [nfs] [request] [patch] ethernet iface should be broug o conf/122170 rc [patch] [request] New feature: notify admin via page o o conf/122477 rc [patch] /etc/rc.d/mdconfig and mdconfig2 are ignoring o conf/123222 rc [patch] Add rtprio(1)/idprio(1) support to rc.subr(8). o conf/123734 rc [patch] Chipset VIA CX700 requires extra initializatio o conf/124248 rc [patch] add support for nice value for rc.d/jail + rc. o conf/124747 rc [patch] savecore can't create dump from encrypted swap o bin/126324 rc [patch] rc.d/tmp: Prevent mounting /tmp in second tim 44 problems total. From brooks at FreeBSD.org Mon Aug 11 17:43:34 2008 From: brooks at FreeBSD.org (brooks@FreeBSD.org) Date: Mon Aug 11 17:43:45 2008 Subject: conf/126392: rc.conf ifconfig_xx keywords cannot be escaped Message-ID: <200808111743.m7BHhXJg088125@freefall.freebsd.org> Synopsis: rc.conf ifconfig_xx keywords cannot be escaped State-Changed-From-To: open->feedback State-Changed-By: brooks State-Changed-When: Mon Aug 11 17:43:00 UTC 2008 State-Changed-Why: Requested feedback. Responsible-Changed-From-To: freebsd-bugs->freebsd-rc Responsible-Changed-By: brooks Responsible-Changed-When: Mon Aug 11 17:43:00 UTC 2008 Responsible-Changed-Why: This is part of rc.d. http://www.freebsd.org/cgi/query-pr.cgi?pr=126392 From brooks at freebsd.org Mon Aug 11 17:50:05 2008 From: brooks at freebsd.org (Brooks Davis) Date: Mon Aug 11 17:50:12 2008 Subject: conf/126392: rc.conf ifconfig_xx keywords cannot be escaped Message-ID: <200808111750.m7BHo43w088300@freefall.freebsd.org> The following reply was made to PR conf/126392; it has been noted by GNATS. From: Brooks Davis To: Jean-Charles Longuet Cc: freebsd-gnats-submit@freebsd.org Subject: Re: conf/126392: rc.conf ifconfig_xx keywords cannot be escaped Date: Mon, 11 Aug 2008 12:43:34 -0500 Setting "authmode WPA" makes no sense. It's only supported by ifconfig for completeness and is useless without wpa_supplicant. As such I can't see a reason to try to fix this. Do you have a practical example? -- Brooks From vince at unsane.co.uk Tue Aug 12 12:29:23 2008 From: vince at unsane.co.uk (Vincent Hoffman) Date: Tue Aug 12 12:29:35 2008 Subject: Idea for FreeBSD In-Reply-To: <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> References: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> Message-ID: <48A18213.3050307@unsane.co.uk> Adrian Penisoara wrote: > > > I also agree that it would be good for the rc.d scripts to > (re)configure themselves, since they are the ones who really know > what's best for them. > > While we're at it, I wish we could leverage the posibility for the > admin to manually start the service at the CLI, no matter whether the > service has been enabled or not -- that is the "_enable" keyword > should have effect only in the bootup/automatic contexts. > > /etc/rc.d/$service forcestart seems to be what you want. I do like the idea of being able to enable/disable services from the rc scripts as /etc/rc.d/$service rcvar | sed 's/NO/YES/' >> /etc/rc.conf and/or editing rc.conf can feel a little clunky at times. Vince >> I think a drop-in command like "rcadm" (someone mentioned this as an idea, >> but cant remember who) would be a good start for managing the states of >> services. Mike Meyer also brought up many good points that I agree with. >> Please try not to get caught up in the XML stuff, that is not a >> requirement or suggestion, it is just an example of how Sun did it, now >> how FreeBSD has to;) >> >> Someone recommended Puppet, but this is an entire framework that would >> have to be added/implemented and configured to work with FreeBSD as well >> as learning a new markup language for it. launchd has a lot of good ideas, >> but I am not sure how mature it is yet; maybe it is a good place to start. >> > > Let's put another name on the table: Upstart (upstart.ubuntu.com). > It's quite fast. > > >> If we start with the basics and break it down and program this from a >> modular standpoint it is not so bad. Begin with the basic (high-level) >> approach. A shell script (service) that is aware of where rc scripts are >> located and that can keep track of what the current state of the services >> (PID's) are. An enable/disable command is nothing more that throwing a >> start/stop command to these rc files. The rc.conf can assist with knowing >> what should be enabled/disabled and what flags to throw at it. For >> EXAMPLE!!!!, (you got that, example only) Solaris uses one master service >> that is started first, and the whole point of that first service is to >> monitor the other services and know what state they are in and starts >> dependent services upon boot. Consider it the service manager almost. >> > > That would very important to for service crash recovery, to keep > critical services running. > > Side note:what about starting up and monitoring services in jails, > probably we'd need one such master service per jail ? > > My 5cents, > Adrian. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From ady at freebsd.ady.ro Tue Aug 12 12:31:54 2008 From: ady at freebsd.ady.ro (Adrian Penisoara) Date: Tue Aug 12 12:32:00 2008 Subject: Idea for FreeBSD In-Reply-To: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> References: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> Message-ID: <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> Hi, I'm a bit late to jump on board, but since I'm interested in the subject and previously given some thinking, here are my thoughts. And perhaps the freebsd-rc list is better suited. On Fri, Aug 8, 2008 at 1:20 AM, wrote: > I am surprised by the overwhelming response that this thread has acquired. > I have spent the majority of the day reading all the responses that > everyone has put forward. I would like to clear a few things up, comment > on others, and suggest some solutions to a lot of good points that > everyone has made so far. > > First let me reiterate a few things. I started in FreeBSD and it will > always be my first love. Second, keep in mind that Solaris is a commercial > product and must be viewed as such. Good point. Like it happened in the Linux world, we should also have some commercially backed versions of [Free]BSD in order to get better visibility and business support (which, in the end, counts a lot). That's why I've been thinking for some time about starting up the EnterpriseBSD project (see http://launchpad.net/enterprisebsd). I believe PC-BSD is a good start for the desktop. > > Now that that is out of the way. I want to make it clear to everyone that > I was not suggesting the idea of copying or reproducing any part of how > Sun manages or implements its services; only the CONCEPT of how they do > it. It does not have to be XML, or in a database or anything else. > Actually I am thinking more along the lines of a wrapper that can > read/modify/execute from rc.d and the rc.conf. After all, we do not want > to make drastic changes. No one wants to re-write rc's or move them to > another location. Even solaris still relies on rc scripts to exist. And I > am sure I speak for all of us when I say that we all love the concept of > how rc.conf handles everything. > > As some people have already pointed out multiple times so far, the idea of > an enable/disable is a great idea. Maybe we can start with that and see > how it goes and develop further based on > need/requirements/accomplishments. I also agree that it would be good for the rc.d scripts to (re)configure themselves, since they are the ones who really know what's best for them. While we're at it, I wish we could leverage the posibility for the admin to manually start the service at the CLI, no matter whether the service has been enabled or not -- that is the "_enable" keyword should have effect only in the bootup/automatic contexts. > > I think a drop-in command like "rcadm" (someone mentioned this as an idea, > but cant remember who) would be a good start for managing the states of > services. Mike Meyer also brought up many good points that I agree with. > Please try not to get caught up in the XML stuff, that is not a > requirement or suggestion, it is just an example of how Sun did it, now > how FreeBSD has to;) > > Someone recommended Puppet, but this is an entire framework that would > have to be added/implemented and configured to work with FreeBSD as well > as learning a new markup language for it. launchd has a lot of good ideas, > but I am not sure how mature it is yet; maybe it is a good place to start. Let's put another name on the table: Upstart (upstart.ubuntu.com). It's quite fast. > > If we start with the basics and break it down and program this from a > modular standpoint it is not so bad. Begin with the basic (high-level) > approach. A shell script (service) that is aware of where rc scripts are > located and that can keep track of what the current state of the services > (PID's) are. An enable/disable command is nothing more that throwing a > start/stop command to these rc files. The rc.conf can assist with knowing > what should be enabled/disabled and what flags to throw at it. For > EXAMPLE!!!!, (you got that, example only) Solaris uses one master service > that is started first, and the whole point of that first service is to > monitor the other services and know what state they are in and starts > dependent services upon boot. Consider it the service manager almost. That would very important to for service crash recovery, to keep critical services running. Side note:what about starting up and monitoring services in jails, probably we'd need one such master service per jail ? My 5cents, Adrian. From stefan.lambrev at moneybookers.com Tue Aug 12 12:54:04 2008 From: stefan.lambrev at moneybookers.com (Stefan Lambrev) Date: Tue Aug 12 12:54:10 2008 Subject: Idea for FreeBSD In-Reply-To: <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> References: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> Message-ID: <48A183D0.6070901@moneybookers.com> Adrian Penisoara wrote: > Hi, > > I'm a bit late to jump on board, but since I'm interested in the > subject and previously given some thinking, here are my thoughts. > > And perhaps the freebsd-rc list is better suited. > > On Fri, Aug 8, 2008 at 1:20 AM, wrote: > >> I am surprised by the overwhelming response that this thread has acquired. >> I have spent the majority of the day reading all the responses that >> everyone has put forward. I would like to clear a few things up, comment >> on others, and suggest some solutions to a lot of good points that >> everyone has made so far. >> >> First let me reiterate a few things. I started in FreeBSD and it will >> always be my first love. Second, keep in mind that Solaris is a commercial >> product and must be viewed as such. >> > > Good point. Like it happened in the Linux world, we should also have > some commercially backed versions of [Free]BSD in order to get better > visibility and business support (which, in the end, counts a lot). > That's why I've been thinking for some time about starting up the > EnterpriseBSD project (see http://launchpad.net/enterprisebsd). I > believe PC-BSD is a good start for the desktop. > There is commercial support for FreeBSD out there. Actually the problem is that misinformed people are still spreading the lie that there is not... Also the example with Linux is very bad, where you have a "stable" version only in enterprise RH or SuSe and the vanilla kernel is only for development and beta testing .. I do not want to see this happens to FreeBSD > >> Now that that is out of the way. I want to make it clear to everyone that >> I was not suggesting the idea of copying or reproducing any part of how >> Sun manages or implements its services; only the CONCEPT of how they do >> it. It does not have to be XML, or in a database or anything else. >> Actually I am thinking more along the lines of a wrapper that can >> read/modify/execute from rc.d and the rc.conf. After all, we do not want >> to make drastic changes. No one wants to re-write rc's or move them to >> another location. Even solaris still relies on rc scripts to exist. And I >> am sure I speak for all of us when I say that we all love the concept of >> how rc.conf handles everything. >> >> As some people have already pointed out multiple times so far, the idea of >> an enable/disable is a great idea. Maybe we can start with that and see >> how it goes and develop further based on >> need/requirements/accomplishments. >> > > I also agree that it would be good for the rc.d scripts to > (re)configure themselves, since they are the ones who really know > what's best for them. > > While we're at it, I wish we could leverage the posibility for the > admin to manually start the service at the CLI, no matter whether the > service has been enabled or not -- that is the "_enable" keyword > should have effect only in the bootup/automatic contexts. > Like keywords - forcestart forcerestart forcestop ?!?! > >> I think a drop-in command like "rcadm" (someone mentioned this as an idea, >> but cant remember who) would be a good start for managing the states of >> services. Mike Meyer also brought up many good points that I agree with. >> Please try not to get caught up in the XML stuff, that is not a >> requirement or suggestion, it is just an example of how Sun did it, now >> how FreeBSD has to;) >> >> Someone recommended Puppet, but this is an entire framework that would >> have to be added/implemented and configured to work with FreeBSD as well >> as learning a new markup language for it. launchd has a lot of good ideas, >> but I am not sure how mature it is yet; maybe it is a good place to start. >> > > Let's put another name on the table: Upstart (upstart.ubuntu.com). > It's quite fast. > Some of us use FreeBSD because we think this is the proper way things to be done, if we want another linux distro we may switch to *buntu .. > >> If we start with the basics and break it down and program this from a >> modular standpoint it is not so bad. Begin with the basic (high-level) >> approach. A shell script (service) that is aware of where rc scripts are >> located and that can keep track of what the current state of the services >> (PID's) are. An enable/disable command is nothing more that throwing a >> start/stop command to these rc files. The rc.conf can assist with knowing >> what should be enabled/disabled and what flags to throw at it. For >> EXAMPLE!!!!, (you got that, example only) Solaris uses one master service >> that is started first, and the whole point of that first service is to >> monitor the other services and know what state they are in and starts >> dependent services upon boot. Consider it the service manager almost. >> > > That would very important to for service crash recovery, to keep > critical services running. > Looks like we are reinventing inetd ? > Side note:what about starting up and monitoring services in jails, > probably we'd need one such master service per jail ? > Like inetd running in jail ? > My 5cents, > Overpriced ;) and good luck with enterprisebsd > Adrian. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- Best Wishes, Stefan Lambrev ICQ# 24134177 From ady at freebsd.ady.ro Tue Aug 12 14:22:49 2008 From: ady at freebsd.ady.ro (Adrian Penisoara) Date: Tue Aug 12 14:23:02 2008 Subject: Idea for FreeBSD In-Reply-To: <48A183D0.6070901@moneybookers.com> References: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> <48A183D0.6070901@moneybookers.com> Message-ID: <78cb3d3f0808120722t461bfb56x4782899811cf63f0@mail.gmail.com> Hi, On Tue, Aug 12, 2008 at 2:36 PM, Stefan Lambrev wrote: >>> >>> First let me reiterate a few things. I started in FreeBSD and it will >>> always be my first love. Second, keep in mind that Solaris is a >>> commercial >>> product and must be viewed as such. >>> >> >> Good point. Like it happened in the Linux world, we should also have >> some commercially backed versions of [Free]BSD in order to get better >> visibility and business support (which, in the end, counts a lot). >> That's why I've been thinking for some time about starting up the >> EnterpriseBSD project (see http://launchpad.net/enterprisebsd). I >> believe PC-BSD is a good start for the desktop. >> > > There is commercial support for FreeBSD out there. > Actually the problem is that misinformed people are still spreading the lie > that there is not... OK, I will reword that a bit: I believe having also a "business" face for the business market will help a lot in increasing visibility. > > Also the example with Linux is very bad, where you have a "stable" version > only in enterprise RH or SuSe > and the vanilla kernel is only for development and beta testing .. I do not > want to see this happens to FreeBSD I'm not sure where is that remark headed to. And I don't think (re)packaging a business-centric version would harm -- please correct me if I'm wrong. >> While we're at it, I wish we could leverage the posibility for the >> admin to manually start the service at the CLI, no matter whether the >> service has been enabled or not -- that is the "_enable" keyword >> should have effect only in the bootup/automatic contexts. >> > > Like keywords - forcestart forcerestart forcestop ?!?! Yes, I am always reminded of that :). Well, to tell you the truth, I do not know of any other OS which requires prefixing with "force" the start/stop actions in order to act on the service at the command line, and personally I wish it weren't the case. >>> I think a drop-in command like "rcadm" (someone mentioned this as an >>> idea, >>> but cant remember who) would be a good start for managing the states of >>> services. Mike Meyer also brought up many good points that I agree with. >>> Please try not to get caught up in the XML stuff, that is not a >>> requirement or suggestion, it is just an example of how Sun did it, now >>> how FreeBSD has to;) >>> >>> Someone recommended Puppet, but this is an entire framework that would >>> have to be added/implemented and configured to work with FreeBSD as well >>> as learning a new markup language for it. launchd has a lot of good >>> ideas, >>> but I am not sure how mature it is yet; maybe it is a good place to >>> start. >>> >> >> Let's put another name on the table: Upstart (upstart.ubuntu.com). >> It's quite fast. >> > > Some of us use FreeBSD because we think this is the proper way things to be > done, if we want another linux distro we may switch to *buntu .. Oh, we are debating here, not imposing personal preferences :). Good ideas can come up from any direction, it's up to us whether we want to learn from them. >>> If we start with the basics and break it down and program this from a >>> modular standpoint it is not so bad. Begin with the basic (high-level) >>> approach. A shell script (service) that is aware of where rc scripts are >>> located and that can keep track of what the current state of the services >>> (PID's) are. An enable/disable command is nothing more that throwing a >>> start/stop command to these rc files. The rc.conf can assist with knowing >>> what should be enabled/disabled and what flags to throw at it. For >>> EXAMPLE!!!!, (you got that, example only) Solaris uses one master service >>> that is started first, and the whole point of that first service is to >>> monitor the other services and know what state they are in and starts >>> dependent services upon boot. Consider it the service manager almost. >>> >> >> That would very important to for service crash recovery, to keep >> critical services running. >> > > Looks like we are reinventing inetd ? Inetd is only for multiplexing seldomly used network services bound to specific ports -- not too many real-life services fall under this exact specification. >> >> Side note:what about starting up and monitoring services in jails, >> probably we'd need one such master service per jail ? >> > > Like inetd running in jail ? >> >> My 5cents, >> > > Overpriced ;) and good luck with enterprisebsd Well, that was usually conceived as a contribution, not a price. Ideas are free anyway ;). Thanks. Adrian. From stefan.lambrev at moneybookers.com Tue Aug 12 14:52:11 2008 From: stefan.lambrev at moneybookers.com (Stefan Lambrev) Date: Tue Aug 12 14:52:24 2008 Subject: Idea for FreeBSD In-Reply-To: <78cb3d3f0808120722t461bfb56x4782899811cf63f0@mail.gmail.com> References: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> <48A183D0.6070901@moneybookers.com> <78cb3d3f0808120722t461bfb56x4782899811cf63f0@mail.gmail.com> Message-ID: <48A1A391.9090808@moneybookers.com> Adrian Penisoara wrote: > Hi, > > On Tue, Aug 12, 2008 at 2:36 PM, Stefan Lambrev > wrote: > >>>> First let me reiterate a few things. I started in FreeBSD and it will >>>> always be my first love. Second, keep in mind that Solaris is a >>>> commercial >>>> product and must be viewed as such. >>>> >>>> >>> Good point. Like it happened in the Linux world, we should also have >>> some commercially backed versions of [Free]BSD in order to get better >>> visibility and business support (which, in the end, counts a lot). >>> That's why I've been thinking for some time about starting up the >>> EnterpriseBSD project (see http://launchpad.net/enterprisebsd). I >>> believe PC-BSD is a good start for the desktop. >>> >>> >> There is commercial support for FreeBSD out there. >> Actually the problem is that misinformed people are still spreading the lie >> that there is not... >> > > OK, I will reword that a bit: I believe having also a "business" face > for the business market will help a lot in increasing visibility. > > >> Also the example with Linux is very bad, where you have a "stable" version >> only in enterprise RH or SuSe >> and the vanilla kernel is only for development and beta testing .. I do not >> want to see this happens to FreeBSD >> > > I'm not sure where is that remark headed to. And I don't think > (re)packaging a business-centric version would harm -- please correct > me if I'm wrong. > The problem with "enterprise" is that they ship their own kernel which is heavily modified. If you want enterprise go for OSX :) I think it's the best enterprise BSDish system ;) Also there are more packages for FreeBSD available then for RH, and I can assure you that all programs that you actually use (like ssh, apache, perl and etc) you have to manually compile to fit your needs. > >>> While we're at it, I wish we could leverage the posibility for the >>> admin to manually start the service at the CLI, no matter whether the >>> service has been enabled or not -- that is the "_enable" keyword >>> should have effect only in the bootup/automatic contexts. >>> >>> >> Like keywords - forcestart forcerestart forcestop ?!?! >> > > Yes, I am always reminded of that :). > Well, to tell you the truth, I do not know of any other OS which > requires prefixing with "force" the start/stop actions in order to act > on the service at the command line, and personally I wish it weren't > the case. > Well I bet you can find this in most linux distros that copy FreeBSD. What about gentoo? Anyway I think that the beauty of the current rc/ng system in freebsd is that it's very easy to understand and use it. Not like those nasty XML config files that makes you blind. There are small fixes that can be applied to make the system even better, but rewriting it just for the sport looks like wasting too much power :) But after all FreeBSD innovate do not imitate ;) Anyway it's may be just me, but I do not think that the rc system in freebsd is the showstopper, that needs funding or more ppl looking at it. And btw burdening the rc subsystem to monitor your daemons is overkill too. It will never work as good as real monitoring software, and will only bloat things. There are tons of utilities that can do this. -cut- -- Best Wishes, Stefan Lambrev ICQ# 24134177 From kimelto at gmail.com Tue Aug 12 17:43:28 2008 From: kimelto at gmail.com (kimelto) Date: Tue Aug 12 17:43:35 2008 Subject: Idea for FreeBSD In-Reply-To: <48A183D0.6070901@moneybookers.com> References: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> <48A183D0.6070901@moneybookers.com> Message-ID: <20080812171513.GA1512@laptop.kimelto.eu> Stefan Lambrev wrote: > > > > Let's put another name on the table: Upstart (upstart.ubuntu.com). > > It's quite fast. > > > Some of us use FreeBSD because we think this is the proper way things to > be done, if we want another linux distro we may switch to *buntu .. What about OpenRC ? http://roy.marples.name/openrc It's BSD-licensed, compatilbe with FreeBSD & NetBSD rc.d implementation ... ;-) Regards, -- Julien LAFFAYE | GPG: 0x46DE4110 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-rc/attachments/20080812/65c0bbc8/attachment.pgp From jclonguet at laposte.net Tue Aug 12 19:40:06 2008 From: jclonguet at laposte.net (Jean-Charles Longuet) Date: Tue Aug 12 19:40:15 2008 Subject: conf/126392: rc.conf ifconfig_xx keywords cannot be escaped Message-ID: <200808121940.m7CJe5fu059233@freefall.freebsd.org> The following reply was made to PR conf/126392; it has been noted by GNATS. From: Jean-Charles Longuet To: bug-followup@freebsd.org, jclonguet@free.fr Cc: Subject: Re: conf/126392: rc.conf ifconfig_xx keywords cannot be escaped Date: Tue, 12 Aug 2008 21:10:04 +0200 From what I understand, wpa_supplicant is only used by client stations. In my case, I am configuring an access point with hostapd for the wpa handling, and do not require wpa_supplicant in any way, hence the configuration line I added in the intial report. More generaly, keywords can not be used anywhere in the ifconfig command line: you cannot set your ssid to such values, for example. There are workarounds, like running an extra ifconfig command in start_if.ath0, but that's just plain ugly, and I use FreeBSD to avoid this. Having an extra keyword meaning "do not look thereafter" could do the trick (something like "--" on command lines). -- Jc From sam at freebsd.org Tue Aug 12 21:12:46 2008 From: sam at freebsd.org (Sam Leffler) Date: Tue Aug 12 21:13:01 2008 Subject: conf/126392: rc.conf ifconfig_xx keywords cannot be escaped In-Reply-To: <200808121940.m7CJe5fu059233@freefall.freebsd.org> References: <200808121940.m7CJe5fu059233@freefall.freebsd.org> Message-ID: <48A1F414.3000608@freebsd.org> Jean-Charles Longuet wrote: > The following reply was made to PR conf/126392; it has been noted by GNATS. > > From: Jean-Charles Longuet > To: bug-followup@freebsd.org, jclonguet@free.fr > Cc: > Subject: Re: conf/126392: rc.conf ifconfig_xx keywords cannot be escaped > Date: Tue, 12 Aug 2008 21:10:04 +0200 > > > From what I understand, wpa_supplicant is only used by client stations. > In my case, I am configuring an access point with hostapd for the wpa > handling, and do not require wpa_supplicant in any way, hence the > configuration line I added in the intial report. > > More generaly, keywords can not be used anywhere in the ifconfig command > line: you cannot set your ssid to such values, for example. There are > workarounds, like running an extra ifconfig command in start_if.ath0, > but that's just plain ugly, and I use FreeBSD to avoid this. Having an > extra keyword meaning "do not look thereafter" could do the trick > (something like "--" on command lines). > > Using ifconfig to enable WPA authmode will never be useful. I will remove it so it's not possible. Not sure however if the rc scripts will recognize use of "WPA" for setting the ssid as distinct from the metta-keyword. If not that is an issue. Sam From dfilter at FreeBSD.ORG Fri Aug 15 19:00:13 2008 From: dfilter at FreeBSD.ORG (dfilter service) Date: Fri Aug 15 19:00:19 2008 Subject: bin/65258: commit references a PR Message-ID: <200808151900.m7FJ0CYd003819@freefall.freebsd.org> The following reply was made to PR bin/65258; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: bin/65258: commit references a PR Date: Fri, 15 Aug 2008 18:58:33 +0000 (UTC) jhb 2008-08-15 18:58:15 UTC FreeBSD src repository Modified files: etc rc.firewall Log: SVN rev 181760 on 2008-08-15 18:58:15Z by jhb Use 'me' rather than explicit IP addresses for the "simple" and "client" firewall configurations. PR: bin/65258 Silence on: net@ MFC after: 1 week Revision Changes Path 1.58 +9 -12 src/etc/rc.firewall _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From jhb at FreeBSD.org Fri Aug 15 19:24:00 2008 From: jhb at FreeBSD.org (jhb@FreeBSD.org) Date: Fri Aug 15 19:24:07 2008 Subject: bin/65258: [patch] [request] save /etc/rc.firewall from changing for standard firewall types Message-ID: <200808151923.m7FJNxwa008030@freefall.freebsd.org> Synopsis: [patch] [request] save /etc/rc.firewall from changing for standard firewall types State-Changed-From-To: suspended->patched State-Changed-By: jhb State-Changed-When: Fri Aug 15 19:23:20 UTC 2008 State-Changed-Why: Barring any uproar after my commits today, I will merge this to 6.x and 7.x after a couple of weeks. Responsible-Changed-From-To: freebsd-rc->jhb Responsible-Changed-By: jhb Responsible-Changed-When: Fri Aug 15 19:23:20 UTC 2008 Responsible-Changed-Why: Barring any uproar after my commits today, I will merge this to 6.x and 7.x after a couple of weeks. http://www.freebsd.org/cgi/query-pr.cgi?pr=65258 From gavin at FreeBSD.org Sat Aug 16 12:38:44 2008 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Sat Aug 16 12:38:59 2008 Subject: bin/126562: rcorder(8) fails to run unrelated startup scripts when some startup scripts require un-PROVIDEd services Message-ID: <200808161238.m7GCch5i061304@freefall.freebsd.org> Synopsis: rcorder(8) fails to run unrelated startup scripts when some startup scripts require un-PROVIDEd services Responsible-Changed-From-To: freebsd-bugs->freebsd-rc Responsible-Changed-By: gavin Responsible-Changed-When: Sat Aug 16 12:38:14 UTC 2008 Responsible-Changed-Why: Over to maintainers http://www.freebsd.org/cgi/query-pr.cgi?pr=126562 From bugmaster at FreeBSD.org Mon Aug 18 11:06:56 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 18 11:08:34 2008 Subject: Current problem reports assigned to freebsd-rc@FreeBSD.org Message-ID: <200808181106.m7IB6tOR079924@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/98758 rc [jail] [patch] Templatize 'jail_fstab' in /etc/rc.d/ja o conf/98846 rc [jail] [patch] Templatize 'jail_rootdir' in /etc/rc.d/ o conf/105689 rc [ppp] [request] syslogd starts too late at boot o conf/118255 rc savecore never finding kernel core dumps (rcorder prob o conf/122036 rc [rc.d]: Mounting at boot with ZFS causes a halt in boo o bin/126562 rc rcorder(8) fails to run unrelated startup scripts when 6 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/44170 rc [patch] Add ability to run multiple pppoed(8) on start o conf/45226 rc [patch] Fix for rc.network, ppp-user annoyance o conf/56934 rc [patch] rc.firewall rules for natd expect an interface o conf/58939 rc [patch] dumb little hack for /etc/rc.firewall{,6} o conf/73677 rc [patch] add support for powernow states to power_profi o conf/77663 rc Suggestion: add /etc/rc.d/addnetswap after addcritremo o kern/81006 rc ipnat not working with tunnel interfaces on startup o conf/85819 rc [patch] script allowing multiuser mode in spite of fsc o conf/88913 rc [patch] wrapper support for rc.subr o conf/89061 rc [patch] IPv6 6to4 auto-configuration enhancement o conf/89870 rc [patch] [request] make netif verbose rc.conf toggle o conf/92523 rc [patch] allow rc scripts to kill process after a timeo o conf/93815 rc [patch] Adds in the ability to save ipfw rules to rc.d o conf/96343 rc [patch] rc.d order change to start inet6 before pf o conf/99444 rc [patch] Enhancement: rc.subr could easily support star o conf/99721 rc [patch] /etc/rc.initdiskless problem copy dotfile in s o conf/102700 rc [geli] [patch] Add encrypted /tmp support to GELI/GBDE o conf/103486 rc [rc.d] [jail] [patch] rc.d/jail: mount fstab after dev o conf/103489 rc [rc.d] [jail] [patch] named_chroot_autoupdate doesn't o conf/104549 rc [patch] rc.d/nfsd needs special _find_processes functi o conf/105145 rc [ppp] [patch] [request] add redial function to rc.d/pp o conf/105568 rc [patch] [request] Add more flexibility to rc.conf, to o conf/106009 rc [ppp] [patch] [request] Fix pppoed startup script to p o conf/109562 rc [rc.d] [patch] [request] Make rc.d/devfs usable from c o conf/109980 rc /etc/rc.d/netif restart doesn't destroy cloned_interfa o conf/113915 rc [patch] ndis wireless driver fails to associate when i o conf/114119 rc [jail] [patch] [request] /etc/rc.d/jail improvements f o conf/117935 rc [patch] ppp fails to start at boot because of missing o bin/118325 rc [patch] [request] new periodic script to test statuses o conf/119076 rc [patch] [rc] /etc/rc.d/netif tries to remove alias add o conf/119874 rc [patch] "/etc/rc.d/pf reload" fails if there are macro o conf/120194 rc [patch] UFS volumes on ZVOLs cannot be fsck'd at boot o conf/120228 rc [zfs] [patch] Split ZFS volume startup / ease ZFS swap o conf/120406 rc [devd] [patch] Handle newly attached pcm devices (eg. o conf/120431 rc [patch] devfs.rules are not initialized under certain o kern/121566 rc [nfs] [request] [patch] ethernet iface should be broug o conf/122170 rc [patch] [request] New feature: notify admin via page o o conf/122477 rc [patch] /etc/rc.d/mdconfig and mdconfig2 are ignoring o conf/123222 rc [patch] Add rtprio(1)/idprio(1) support to rc.subr(8). o conf/123734 rc [patch] Chipset VIA CX700 requires extra initializatio o conf/124248 rc [patch] add support for nice value for rc.d/jail + rc. o conf/124747 rc [patch] savecore can't create dump from encrypted swap o bin/126324 rc [patch] rc.d/tmp: Prevent mounting /tmp in second tim f conf/126392 rc rc.conf ifconfig_xx keywords cannot be escaped 44 problems total. From jclonguet at laposte.net Sat Aug 23 09:10:04 2008 From: jclonguet at laposte.net (Jean-Charles Longuet) Date: Sat Aug 23 09:10:14 2008 Subject: conf/126392: rc.conf ifconfig_xx keywords cannot be escaped Message-ID: <200808230910.m7N9A4hV084462@freefall.freebsd.org> The following reply was made to PR conf/126392; it has been noted by GNATS. From: Jean-Charles Longuet To: bug-followup@FreeBSD.org, jclonguet@free.fr Cc: Subject: Re: conf/126392: rc.conf ifconfig_xx keywords cannot be escaped Date: Sat, 23 Aug 2008 11:02:31 +0200 This is a multi-part message in MIME format. --------------080700040509060605030705 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Here is a patch for /etc/network.subr that handles a special string "--" so that keywords found thereafter are ignored. -- Jc --------------080700040509060605030705 Content-Type: text/plain; name="network.subr.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="network.subr.patch" --- /etc/network.subr.ORIG 2008-08-12 22:24:50.000000000 +0200 +++ /etc/network.subr 2008-08-12 22:24:59.000000000 +0200 @@ -142,18 +142,26 @@ return 1 fi _args= + eoparsing=0 for _arg in $_tmpargs; do - case $_arg in - [Dd][Hh][Cc][Pp]) ;; - [Nn][Oo][Aa][Uu][Tt][Oo]) ;; - [Nn][Oo][Ss][Yy][Nn][Cc][Dd][Hh][Cc][Pp]) ;; - [Ss][Yy][Nn][Cc][Dd][Hh][Cc][Pp]) ;; - [Ww][Pp][Aa]) ;; - *) + if [ $eoparsing -eq 0 ]; then + case $_arg in + [Dd][Hh][Cc][Pp]) ;; + [Nn][Oo][Aa][Uu][Tt][Oo]) ;; + [Nn][Oo][Ss][Yy][Nn][Cc][Dd][Hh][Cc][Pp]) ;; + [Ss][Yy][Nn][Cc][Dd][Hh][Cc][Pp]) ;; + [Ww][Pp][Aa]) ;; + --) + eoparsing=1 + ;; + *) + _args="$_args $_arg" + ;; + esac + else _args="$_args $_arg" - ;; - esac + fi done echo $_args @@ -170,6 +178,9 @@ [Nn][Oo][Aa][Uu][Tt][Oo]) return 1 ;; + --) + return 0 + ;; esac done return 0 @@ -191,6 +202,9 @@ [Ss][Yy][Nn][Cc][Dd][Hh][Cc][Pp]) return 0 ;; + --) + return 1 + ;; esac done return 1 @@ -210,6 +224,13 @@ [Ss][Yy][Nn][Cc][Dd][Hh][Cc][Pp]) return 0 ;; + --) + if checkyesno synchronous_dhclient; then + return 0 + else + return 1 + fi + ;; esac done if checkyesno synchronous_dhclient; then @@ -229,6 +250,9 @@ [Ww][Pp][Aa]) return 0 ;; + --) + return 1 + ;; esac done return 1 --------------080700040509060605030705-- From bugmaster at FreeBSD.org Mon Aug 25 11:06:57 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 25 11:08:46 2008 Subject: Current problem reports assigned to freebsd-rc@FreeBSD.org Message-ID: <200808251106.m7PB6unc027872@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/98758 rc [jail] [patch] Templatize 'jail_fstab' in /etc/rc.d/ja o conf/98846 rc [jail] [patch] Templatize 'jail_rootdir' in /etc/rc.d/ o conf/105689 rc [ppp] [request] syslogd starts too late at boot o conf/118255 rc savecore never finding kernel core dumps (rcorder prob o conf/122036 rc [rc.d]: Mounting at boot with ZFS causes a halt in boo o bin/126562 rc rcorder(8) fails to run unrelated startup scripts when 6 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/44170 rc [patch] Add ability to run multiple pppoed(8) on start o conf/45226 rc [patch] Fix for rc.network, ppp-user annoyance o conf/56934 rc [patch] rc.firewall rules for natd expect an interface o conf/58939 rc [patch] dumb little hack for /etc/rc.firewall{,6} o conf/73677 rc [patch] add support for powernow states to power_profi o conf/77663 rc Suggestion: add /etc/rc.d/addnetswap after addcritremo o kern/81006 rc ipnat not working with tunnel interfaces on startup o conf/85819 rc [patch] script allowing multiuser mode in spite of fsc o conf/88913 rc [patch] wrapper support for rc.subr o conf/89061 rc [patch] IPv6 6to4 auto-configuration enhancement o conf/89870 rc [patch] [request] make netif verbose rc.conf toggle o conf/92523 rc [patch] allow rc scripts to kill process after a timeo o conf/93815 rc [patch] Adds in the ability to save ipfw rules to rc.d o conf/96343 rc [patch] rc.d order change to start inet6 before pf o conf/99444 rc [patch] Enhancement: rc.subr could easily support star o conf/99721 rc [patch] /etc/rc.initdiskless problem copy dotfile in s o conf/102700 rc [geli] [patch] Add encrypted /tmp support to GELI/GBDE o conf/103486 rc [rc.d] [jail] [patch] rc.d/jail: mount fstab after dev o conf/103489 rc [rc.d] [jail] [patch] named_chroot_autoupdate doesn't o conf/104549 rc [patch] rc.d/nfsd needs special _find_processes functi o conf/105145 rc [ppp] [patch] [request] add redial function to rc.d/pp o conf/105568 rc [patch] [request] Add more flexibility to rc.conf, to o conf/106009 rc [ppp] [patch] [request] Fix pppoed startup script to p o conf/109562 rc [rc.d] [patch] [request] Make rc.d/devfs usable from c o conf/109980 rc /etc/rc.d/netif restart doesn't destroy cloned_interfa o conf/113915 rc [patch] ndis wireless driver fails to associate when i o conf/114119 rc [jail] [patch] [request] /etc/rc.d/jail improvements f o conf/117935 rc [patch] ppp fails to start at boot because of missing o bin/118325 rc [patch] [request] new periodic script to test statuses o conf/119076 rc [patch] [rc] /etc/rc.d/netif tries to remove alias add o conf/119874 rc [patch] "/etc/rc.d/pf reload" fails if there are macro o conf/120194 rc [patch] UFS volumes on ZVOLs cannot be fsck'd at boot o conf/120228 rc [zfs] [patch] Split ZFS volume startup / ease ZFS swap o conf/120406 rc [devd] [patch] Handle newly attached pcm devices (eg. o conf/120431 rc [patch] devfs.rules are not initialized under certain o kern/121566 rc [nfs] [request] [patch] ethernet iface should be broug o conf/122170 rc [patch] [request] New feature: notify admin via page o o conf/122477 rc [patch] /etc/rc.d/mdconfig and mdconfig2 are ignoring o conf/123222 rc [patch] Add rtprio(1)/idprio(1) support to rc.subr(8). o conf/123734 rc [patch] Chipset VIA CX700 requires extra initializatio o conf/124248 rc [patch] add support for nice value for rc.d/jail + rc. o conf/124747 rc [patch] savecore can't create dump from encrypted swap o bin/126324 rc [patch] rc.d/tmp: Prevent mounting /tmp in second tim f conf/126392 rc rc.conf ifconfig_xx keywords cannot be escaped 44 problems total.