Re: Does / Is anyone maintaining CVS for FreeBSD?
Hi, all, Am 03.01.2013 um 19:21 schrieb Matthew Seaman : > On 03/01/2013 17:48, Patrick M. Hausen wrote: >> I'm a bit reluctant to installing svn on every system that needs source >> updates. Are there more lightweight ways? > > freebsd-update(8) > > which is what 'make update' will run by default and in the absence of > any configuration to use other mechanisms. Sorry for being too terse in my first post. Seems like I should have a closer look at freebsd-update. "Of course" I have lines like this in my /etc/make.conf on each machine that I update from sources: SUP_UPDATE= yes SUP=/usr/bin/csup SUPFLAGS= -g -L 2 SUPHOST=cvsup2.de.freebsd.org SUPFILE=/usr/share/examples/cvsup/standard-supfile PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile And yes, guilty of never ever re-evaluating that mechanism since FreeBSD 2.x. The only change I ever made was replacing cvsup with csup, once the latter became available. And I did not know "make update" had a default without any configuration. That's why I ask stupid questions about whatever it is people use nowadays. Thanks, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 i...@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Does / Is anyone maintaining CVS for FreeBSD?
"Dewayne Geraghty" wrote: > > > I'm a bit reluctant to installing svn on every system that > > > needs source updates. Are there more lightweight ways? http://lists.freebsd.org/pipermail/freebsd-stable/2012-November/070794.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Does / Is anyone maintaining CVS for FreeBSD?
Hi, On Fri, 4 Jan 2013 15:45:10 +1100 "Dewayne Geraghty" wrote: > > -Original Message- > > From: owner-freebsd-sta...@freebsd.org > > [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Erich > > Dollansky Sent: Friday, 4 January 2013 12:26 PM > > To: Patrick M. Hausen > > Cc: Eitan Adler; freebsd-stable@freebsd.org > > Subject: Re: Does / Is anyone maintaining CVS for FreeBSD? > > > > Hi, > > > > On Thu, 3 Jan 2013 18:48:01 +0100 > > "Patrick M. Hausen" wrote: > > > > > Hello, > > > > > > Am 03.01.2013 um 16:36 schrieb Eitan Adler : > > > > CVS/SVN should be considered a development tool. Users > > should not > > > > see the impact of the switch. In theory. > > > > > > > > > What is the recommended csup replacement for users that did > > > > > > cd /usr/src && make update buildworld buildkernel > > > > > > as their method of keeping the system current? > > > > the above's line keeps the originally installed sources > > intact and just recompiles them again and again and again ... > > > > > > I'm a bit reluctant to installing svn on every system that needs > > > source updates. Are there more lightweight ways? > > > > > The line above will stay the same. Only the process of > > downloading the changes will change. > > > > Erich > > ___ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to > > "freebsd-stable-unsubscr...@freebsd.org" > > Erich, If there's a more lightweight way than : you have thrown the bait: > 1. cd /usr/ports/devel/subversion > 2. turning off all options > 3. turn on these options: ENHANCED_KEYWORD P4_STYLE_MARKERS STATIC > 4. make install > 5. Copy the svn as needed. The image should be 4.2MB csup is currently installed by default. Not a single one of the steps shown above are needed at the moment. Can it be more lightweight than zero weight? > Then I'd be happy to adopt. You can do. I am very sorry to tell you that the people decided to stop supporting this. erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Does / Is anyone maintaining CVS for FreeBSD?
Hi, On Fri, 4 Jan 2013 09:38:05 +0100 "Patrick M. Hausen" wrote: > Am 03.01.2013 um 19:21 schrieb Matthew Seaman > : > > On 03/01/2013 17:48, Patrick M. Hausen wrote: > >> I'm a bit reluctant to installing svn on every system that needs > >> source updates. Are there more lightweight ways? > > > > freebsd-update(8) > > > > which is what 'make update' will run by default and in the absence > > of any configuration to use other mechanisms. > > > Sorry for being too terse in my first post. Seems like I should have > a closer look at freebsd-update. "Of course" I have lines like this > in my /etc/make.conf on each machine that I update from sources: no matter, you showed how deeply this integration was up to the point that you did not notice it anymore. You also showed that there was a reliable infrastructure available which served you for years without any problems. What will happen after the jump into the cold water? Erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Does / Is anyone maintaining CVS for FreeBSD?
On 4 Jan 2013 09:25, "Erich Dollansky" wrote: > > Hi, > > On Fri, 4 Jan 2013 09:38:05 +0100 > "Patrick M. Hausen" wrote: > > > Am 03.01.2013 um 19:21 schrieb Matthew Seaman > > : > > > On 03/01/2013 17:48, Patrick M. Hausen wrote: > > >> I'm a bit reluctant to installing svn on every system that needs > > >> source updates. Are there more lightweight ways? > > > > > > freebsd-update(8) > > > > > > which is what 'make update' will run by default and in the absence > > > of any configuration to use other mechanisms. > > > > > > Sorry for being too terse in my first post. Seems like I should have > > a closer look at freebsd-update. "Of course" I have lines like this > > in my /etc/make.conf on each machine that I update from sources: > > no matter, you showed how deeply this integration was up to the point > that you did not notice it anymore. > > You also showed that there was a reliable infrastructure available > which served you for years without any problems. > > What will happen after the jump into the cold water? Is there a problem with using freebsd-update for your sources too? Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Does / Is anyone maintaining CVS for FreeBSD?
Hi, all, Am 04.01.2013 um 10:42 schrieb Chris Rees : > Is there a problem with using freebsd-update for your sources too? I don't know - yet. First question that comes up, after reading the manpages and freebsd-update.conf(5): datatomb2# uname -r 8.3-RELEASE-p4 datatomb2# grep Components /etc/freebsd-update.conf ... Components src ... First naive try: datatomb2# cd /usr/src/ datatomb2# make update # nothing happens Next try: datatomb2# freebsd-update fetch Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching public key from update4.FreeBSD.org... done. Fetching metadata signature for 8.3-RELEASE from update4.FreeBSD.org... done. Fetching metadata index... done. Fetching 2 metadata files... done. Inspecting system... done. Preparing to download files... done. Fetching 6 patches done. Applying patches... done. Fetching 6 files... done. The following files will be updated as part of updating to 8.3-RELEASE-p5: /usr/src/contrib/bind9/bin/named/query.c /usr/src/contrib/bind9/lib/dns/include/dns/rdata.h /usr/src/contrib/bind9/lib/dns/master.c /usr/src/contrib/bind9/lib/dns/rdata.c /usr/src/contrib/wpa/src/eap_server/eap_tls_common.c /usr/src/secure/lib/libcrypt/crypt-des.c /usr/src/sys/amd64/amd64/trap.c /usr/src/sys/compat/linux/linux_ioctl.c /usr/src/sys/conf/newvers.sh /usr/src/sys/netinet/tcp_input.c /usr/src/sys/netinet6/in6.c /usr/src/sys/netinet6/ip6_input.c datatomb2# freebsd-update install Installing updates... done. Great, but /usr/src/UPDATING is still at p4 instead of p5??? So - this is definitely no simple plug-in replacement for csup. And is there a "Components ports"? Doesn't look like it. Thanks, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 i...@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Does / Is anyone maintaining CVS for FreeBSD?
On 04/01/2013 09:52, Patrick M. Hausen wrote: > So - this is definitely no simple plug-in replacement for csup. > And is there a "Components ports"? Doesn't look like it. No. You'ld use portsnap(8) for ports. It's very similar to freebsd-update(8) from a user perspective but apparently quite different in the back-end. Cheers, Matthew ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Solved?: Re: Upgrade of RELENG_8 ZFS boot pool leads to unbootable system
On 03/01/2013 21:18, Paul Mather wrote:
>
>
> It turns out it was my /boot.config that was preventing booting. The system
> is usually always headless, so I have "-S115200 -Dh" as the sole line in
> /boot.config to enable a 115200 baud serial console. This has been working
> fine for me up until I did a {build,install} {kernel,world} on 1st January
> 2013. I was pretty sure my woes began after I did the "zpool upgrade -a" and
> subsequently rebooted again, but now I can't be sure whether I successfully
> rebooted at all after the "make installworld" and mergemaster step.
>
> Does anyone know a sure-fire way of getting a dual console setup (high-speed
> serial + VGA). The recipe I had been using had worked well for a long time.
> I had "-S115200 -Dh" in /boot.config and the following entries in
> /boot/loader.conf:
>
> boot_multicons="YES"
> comconsole_speed="115200"
> console="comconsole,vidconsole"
>
> Now, though, if I have "-S115200 -Dh" then the system locks up at boot.
> Removing /boot.config gets me dual console, but only at 9600 baud. :-(
I have
root@copia:/root # more /boot.config
-Dh
and
root@copia:/root # grep 'cons' /boot/loader.conf
console="comconsole,vidconsole"
comconsole_speed="19200"
boot_multicons="yes"
Which works fine for ipmi based serial over lan console in a generic
9.1-RELEASE.
Not sure thats that helpful but 19200 is better than 9600 ;)
Vince
>
> Cheers,
>
> Paul.
>
> PS: Is the BOOT_COMCONSOLE_SPEED entry in /etc/make.conf needed? I was under
> the impression it has been obsolete for a while and took it out of my
> /etc/make.conf file.
>
>
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Solved?: Re: Upgrade of RELENG_8 ZFS boot pool leads to unbootable system
On Jan 4, 2013, at 5:39 AM, Vincent Hoffman wrote:
> On 03/01/2013 21:18, Paul Mather wrote:
>>
>>
>> It turns out it was my /boot.config that was preventing booting. The system
>> is usually always headless, so I have "-S115200 -Dh" as the sole line in
>> /boot.config to enable a 115200 baud serial console. This has been working
>> fine for me up until I did a {build,install} {kernel,world} on 1st January
>> 2013. I was pretty sure my woes began after I did the "zpool upgrade -a"
>> and subsequently rebooted again, but now I can't be sure whether I
>> successfully rebooted at all after the "make installworld" and mergemaster
>> step.
>>
>> Does anyone know a sure-fire way of getting a dual console setup (high-speed
>> serial + VGA). The recipe I had been using had worked well for a long time.
>> I had "-S115200 -Dh" in /boot.config and the following entries in
>> /boot/loader.conf:
>>
>> boot_multicons="YES"
>> comconsole_speed="115200"
>> console="comconsole,vidconsole"
>>
>> Now, though, if I have "-S115200 -Dh" then the system locks up at boot.
>> Removing /boot.config gets me dual console, but only at 9600 baud. :-(
> I have
> root@copia:/root # more /boot.config
> -Dh
>
> and
> root@copia:/root # grep 'cons' /boot/loader.conf
> console="comconsole,vidconsole"
> comconsole_speed="19200"
> boot_multicons="yes"
>
> Which works fine for ipmi based serial over lan console in a generic
> 9.1-RELEASE.
> Not sure thats that helpful but 19200 is better than 9600 ;)
That's weird. I have the same basic /boot/loader.conf entries (except for a
speed of 115200) and even just putting "-Dh" into /boot.config leads to the
same unbootable system behaviour. :-(
Maybe something broke recently in the RELENG_8 boot loader? Like I said
originally, that /boot.config entry had been working for me without problems
for a long time.
Cheers,
Paul.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Solved?: Re: Upgrade of RELENG_8 ZFS boot pool leads to unbootable system
If memory serves me right, Paul Mather wrote: > That's weird. I have the same basic /boot/loader.conf entries > (except for a speed of 115200) and even just putting "-Dh" into > /boot.config leads to the same unbootable system behaviour. :-( > > Maybe something broke recently in the RELENG_8 boot loader? Like I > said originally, that /boot.config entry had been working for me > without problems for a long time. Hi Paul-- I recently ran into this as well. I didn't do any setting of the console bitrate, just "-Dh" in /boot.config, and it caused a server I was upgrading to lock up just as you described. I had to learn about mounting ZFS filesystems from the Fixit environment in a hurry. My workaround was to get rid of /boot.config, which obviously doesn't restore the original functionality. The system in question was (is) running 8.3-RELEASE. Bruce. signature.asc Description: OpenPGP digital signature
FreeBSD wiki offline for a bit
Hey, Due to a security issue in the moinmoin wiki software, the FreeBSD wiki will be offline for a bit. I do not yet know if the issue actually has been exploited in the FreeBSD wiki (haven't had the time yet to examine it), but I took the wiki down just in case. Note that even if the software was compromised, it was considered untrusted from the start and as such heavily sandboxed (including jailed) to keep it away from any sensitive FreeBSD.org parts, so there is absolutely no reason to believe a compromise would go any further than the wiki itself. I hope to have the wiki back within 24 hours, assuming not too much gets in the way. For further reference see: http://moinmo.in/SecurityFixes and http://permalink.gmane.org/gmane.linux.debian.devel.announce/1754 . PS. this is entirely unrelated to the 2012 November FreeBSD.org compromise. -- Simon L. B. Nielsen Hat: FreeBSD clusteradm / FreeBSD Security Officer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: Does / Is anyone maintaining CVS for FreeBSD?
> -Original Message- > From: owner-freebsd-sta...@freebsd.org > [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Perry Hutchison > Sent: Friday, 4 January 2013 7:30 PM > To: dewayne.gerag...@heuristicsystems.com.au > Cc: erichsfreebsdl...@alogt.com; freebsd-stable@freebsd.org > Subject: Re: Does / Is anyone maintaining CVS for FreeBSD? > > "Dewayne Geraghty" wrote: > > > > > I'm a bit reluctant to installing svn on every system > that needs > > > > source updates. Are there more lightweight ways? > > http://lists.freebsd.org/pipermail/freebsd-stable/2012-Novembe > r/070794.html > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscr...@freebsd.org" Perry, Thanks for the pointer I did not consider freebsd-update as the first paragraph of the description only mentions binary updates. I'll need to take a closer look. Kimmo, I agree and usually prefer to distribute binaries as a package. However it includes other binaries and doc etc that aren't required to maintain source. The emphasise was on lightweight. To accomplish the task of source maintenance (get and update) then a static svn image is all that's required. Erich, You're right, csup is an elegant and proven solution which I've used for years. We could continue using it for the life of RELENG_9 but the change to svn becomes mandatory for 10. There has been a lot of discussion in this and other threads, that there is more effort involved in maintaining sources than developers and contributors wish to spend when an alternative presents itself. I'd rather their generous contribution of time be spent of fixing or enhancing our OS. The only "down-side" that I've noticed is that csup would replace all files under /usr/src which I modified (a good thing). Svn does not. Where I've patched a source and there's, it needs to be told to "svn --accept tf update /usr/src" to replace a change; so my tools can repatch. If there's no conflict svn doesn't look at the local files, and the patched files are unchanged. I'm sure that there are better ways, but I care about svn only to the extent that I can maintain FreeBSD sources. ref: http://www.freebsd.org/cgi/man.cgi?query=freebsd-update&apropos=0&sektion=0&manpath=FreeBSD+9.1-RELEASE&arch=default&format=html Regards, Dewayne PS I'm offsite for next 5 days so apologies in advance for delay responding. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
