When doing a major version upgrade of FreeBSD, the last (mandatory) step is
to rebuild and reinstall all third party software (ports)
(# portupgrade -af )
I have a system with 750+ ports, I guess the portupgrade -af will take
something like 30 hours to compile
(on a test system with 425 ports port
believe you can pull 8.0-RELEASE-p2 using -r as well.
Regards,
Thanks.
Have another question.
When freebsd-update first entered the ports system, it was limited to
updating systems that not been changed from the basic release. IE:
Recompiling the kernel adding devices or removing them. Is that
-RELEASE-p2 using -r as well.
Regards,
Thanks.
Have another question.
When freebsd-update first entered the ports system, it was limited to
updating systems that not been changed from the basic release. IE:
Recompiling the kernel adding devices or removing them. Is that still
true now
On 6/9/10 9:07 PM, Aiza wrote:
The upgrade function requires the -r newrelease flag.
The manpage does not state the formate of the newrelease value.
Is it just the release number like this 8.0 or is it like this 8.0-RELEASE?
8.0-RELEASE. I believe you can pull 8.0-RELEASE-p2 using -r as well.
The upgrade function requires the -r newrelease flag.
The manpage does not state the formate of the newrelease value.
Is it just the release number like this 8.0 or is it like this 8.0-RELEASE?
___
freebsd-questions@freebsd.org mailing list
http://lists
On Thu, 03 Jun 2010 17:46:54 +0800
Fbsd1 wrote:
> After running FreeBSD-update fetch and install is there any way to
> tell it worked without rebooting?
A kernel upgrade requires your system to reboot :(
--
Anh Ky Huynh
___
freebsd-que
After running FreeBSD-update fetch and install is there any way to tell
it worked without rebooting?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "fr
Hello everybody!
Please answer about what can be if ssh session was disconnected during second
run of "freebsd-update install". Can I just connect again and run it again?
What terrible thing can be?.. Because server is faaar-faaar away :((
_
Repost... Any idea, other should I really have a look at the source code
of freebsd-update? :) Thanks & regards, O.
On Thu, 2010-04-22 at 18:43 +0200, Olivier Mueller wrote:
> Two little questions about freebsd-update "best-practices":
>
> 1) These are the output
Hello,
Two little questions about freebsd-update "best-practices":
1) These are the output when I start a "freebsd-update upgrade" on two
different systems. On the first one, everything ok, on the second, the
sources are still there and I would like to get rid of them:
On Fri, Apr 02, 2010 at 06:01:49PM +0100, Graeme Dargie thus spake:
Hello All
I have an issue with freebsd-update, I will back track a few steps to
give you some background as to what I was doing prior to using
freebsd-update.
I have been trying to get half-life dedicated server working on
Hello All
I have an issue with freebsd-update, I will back track a few steps to
give you some background as to what I was doing prior to using
freebsd-update.
I have been trying to get half-life dedicated server working on one of
my machines, seemed to install ok from games/linux-steam but
John Baldwin wrote:
> On Friday 26 March 2010 11:00:28 am Colin Percival wrote:
>> I think the best approach towards having FreeBSD Update support for
>> sparc64 is to get release cross-building working; that way we would
>> be able to use amd64 hardware, which I think we can
On Friday 26 March 2010 11:00:28 am Colin Percival wrote:
> I think the best approach towards having FreeBSD Update support for
> sparc64 is to get release cross-building working; that way we would
> be able to use amd64 hardware, which I think we can safely assume
> will continue to
they would need to wait -- time-sensitive security advisories --
are exactly the times when they shouldn't wait.
(As a side note, for obvious security reasons I don't want to add
hardware outside of the established FreeBSD.org datacenters for
this sort of thing.)
I think the best approach to
re was quite some
> > > interest in getting this running but the showstopper was that
> > > cperciva@ said that a requirement for any platform supported
> > > by freebsd-update(8) would be that the build server is able
> > > to run buildworld in 1 hour at most (
le. Since our userbase is small,
> >> and developer time is limited, we've never set it up.
> >>
> >
> > The last time this topic came up IMO there was quite some
> > interest in getting this running but the showstopper was that
> > cperciva@ said that a re
t it up.
>>
>
> The last time this topic came up IMO there was quite some
> interest in getting this running but the showstopper was that
> cperciva@ said that a requirement for any platform supported
> by freebsd-update(8) would be that the build server is able
> to
On 3/24/10 11:38 PM, Marius Strobl wrote:
> The last time this topic came up IMO there was quite some
> interest in getting this running but the showstopper was that
> cperciva@ said that a requirement for any platform supported
> by freebsd-update(8) would be that the build server
his topic came up IMO there was quite some
> interest in getting this running but the showstopper was that
> cperciva@ said that a requirement for any platform supported
> by freebsd-update(8) would be that the build server is able
> to run buildworld in 1 hour at most (unfortunately I cur
his running but the showstopper was that
cperciva@ said that a requirement for any platform supported
by freebsd-update(8) would be that the build server is able
to run buildworld in 1 hour at most (unfortunately I currently
just can't find that email). My 4x1.5GHz V440 I originally
intended for th
Mark Linimon wrote:
You're the first one to ask in a while. Since our userbase is small,
and developer time is limited, we've never set it up.
Right now I'd just be happy if I can get all the major ports to work :-)
mcl
If I can do something for this project, please tell me what to do :)
I
You're the first one to ask in a while. Since our userbase is small,
and developer time is limited, we've never set it up.
Right now I'd just be happy if I can get all the major ports to work :-)
mcl
___
freebsd-questions@freebsd.org mailing list
http:
I feel that the FreeBSD project doesn't have enough sparc64 build machine.
Is this the reason why binary freebsd-update is not available for
sparc64 arch?
The only methods for upgrading sparc64 are reinstall or build from source?
--
Adam
Hi,
I have experienced this when you use csup to sync your sources. You have to use
one or other but not twice.
There is a difference of the date on the files, because freebsd-update patches
are created before the CVS commits are done.
see this thread on FreeBSD Forums :
http
Hi all,
I've performed system upgrade last night, then I wanted to give a try to
freebsd-update tool. If I understand it correctly, it should fetch only
updates to my currently working system (unless -r option was given). But
now it insists to upgrade my 6.4-p9 system to 6.4-p9 system:
> That handbook section is where I read:
> "The default is to update the source code, the entire base
> system, and the kernel."
First, freebsd-update tool sync the source.
> And in fact much of the /usr/src/ does contain source
> code.
>
> /usr/src/sys/ subdirec
On 2010-03-14 05:39, Alexandre L. wrote:
Please read the handbook section related to the FreeBSD update tool
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html
freebsd-update is a binary update tool, so you haven't got anything to rebuild,
e
Please read the handbook section related to the FreeBSD update tool
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html
freebsd-update is a binary update tool, so you haven't got anything to rebuild,
except your custom kernel (if you are usin
doc/handbook/updating-upgrading-freebsdupdate.html
>
> I've also seem other references indicate that the source downloaded by
> freebsd-update
> could be patched and installed.
If you list src component, evidently freebsd-update claims to update /usr/src.
I suspect that if you'
On 2010-03-13 19:58, Chuck Swiger wrote:
freebsd-update provides a binary update mechanism.
It doesn't do anything to update the source files; if you choose to rebuild
from source, use cvsup/csup/svn; you will normally get a -STABLE system from
the build cycle, and not a -RELEASE system
On Mar 13, 2010, at 7:37 PM, johnea wrote:
> I have been using freebsd-update to update several 7.1 systems.
> [ ... ]
> How can I build the source updated by freebsd-update?
freebsd-update provides a binary update mechanism.
It doesn't do anything to update the source files; if
Hello,
I have been using freebsd-update to update several 7.1 systems.
The default freebsd-update.conf contains:
Components src world kernel
Recently while trying to build sendmail to enable SASL I ran into errors:
host# cd /usr/src/usr.sbin/sendmail
host# make depend
make: don't kno
daniele writes:
> Hi !
>
> I have a question about using freebsd-update && IDS command.
> what is the correct way to specify 'the "known good" index of the
> installed release' ?
> I would like to compare an installed system with the(its) origina
Hi !
I have a question about using freebsd-update && IDS command.
what is the correct way to specify 'the "known good" index of the
installed release' ?
I would like to compare an installed system with the(its) original
released CD.
Thanks
d
Ref:
http://www.f
hat, the system is using stock 8.0 binaries. Since fully rebuilding
> world and kernel on this system is a 5 hour process, I would very much
> like to use freebsd-update and I wanted someone to clarify the
> utility's behaviour. If I run freebsd-update on this system, what will
he system is using stock 8.0 binaries. Since fully rebuilding
> world and kernel on this system is a 5 hour process, I would very much
> like to use freebsd-update and I wanted someone to clarify the
> utility's behaviour. If I run freebsd-update on this system, what will
> it do
kernel on this system is a 5 hour process, I would very much
like to use freebsd-update and I wanted someone to clarify the
utility's behaviour. If I run freebsd-update on this system, what will
it do when it detects that the bootloader binaries do not match those
of stock 8.0-RELEASE? Will i
On 16 February 2010 18:22, Steve Franks wrote:
> On Tue, Feb 16, 2010 at 3:55 AM, Peter Kirk wrote:
>> Updating freebsd 7.2 to 8 and fan the following command
>>
>> freebsd-update upgrade -r 8.0-RELEASE
>>
>> Everything goes through fine but then it gets
hat myself, and I have written an article on it. It is also
> pending a commit to the FreeBSD Documentation Project.
>
>
> http://www.experts-exchange.com/articles/OS/Unix/BSD/FreeBSD/Build-Your-Own-FreeBSD-Update-Server.html
>
> Hope this is helpful,
> Jason
>
> On Tu
Search the list archives for emails pertaining to mergemaster.rc - it
worked wonders for me!
Steve
On Tue, Feb 16, 2010 at 3:55 AM, Peter Kirk wrote:
> Updating freebsd 7.2 to 8 and fan the following command
>
> freebsd-update upgrade -r 8.0-RELEASE
>
> Everything goes through f
/Unix/BSD/FreeBSD/Build-Your-Own-FreeBSD-Update-Server.html
Hope this is helpful,
Jason
On Tue, Feb 16, 2010 at 11:46:38AM +0100, Andreas Nilsson thus spake:
Hello,
I have a need to ship updates to a customized freebsd install, and thought
that freebsd-update could serve me. However
http
Updating freebsd 7.2 to 8 and fan the following command
freebsd-update upgrade -r 8.0-RELEASE
Everything goes through fine but then it gets to a point and its says
The following file could not be merged automatically: /etc/amd.map
Press Enter to edit this file in vi and resolve the conflicts
Hello,
I have a need to ship updates to a customized freebsd install, and thought
that freebsd-update could serve me. However
http://www.freebsd.org/cgi/cvsweb.cgi/projects/freebsd-update-server/ is
rather old and misses amd64 builds. There must be newer code around since
freebsd-update can be
Updating freebsd 7.2 to 8 and fan the following command
freebsd-update upgrade -r 8.0-RELEASE
Everything goes through fine but then it gets to a point and its says
The following file could not be merged automatically: /etc/amd.map
Press Enter to edit this file in vi and resolve the conflicts
On Thu, Dec 24, 2009 at 03:47:51PM +, Marwan Sultan thus spake:
This is a lesson for me and everyone to never run freebsd-update on a custom
kernel
I run FreeBSD on a custom kernel, and do binary updates. However, I can do
this because I run my own update server. So all kernels are
I will today use the ordiary freebsd update (csup) and see if this will fix
what
freebsd-update broke- and will update this list.
This is a lesson for me and everyone to never run freebsd-update on a custom
kernel
system, however It shouldnot produce such problem. (i think)
error? The setting in rc.conf
is defaultrouter="..." - routeR.
> But eventho it shouldnot touch rc.conf right?
Correct. The rc.conf file is one of the few ones that
shouldn't be in the scope of freebsd-update or mergemaster
(if you update by source).
> my rc.local
Hi Poly,
Its very short story,
my system is on FreeBSD 7.2- P4
and everything works great. Yes I have custom kernel, mainly for quotas.
I have run freebsd-update fetch and install, I forgot its only for generic
kernel.
However, after the freebsd-update fetch/install done, i
On Thu, 24 Dec 2009 13:31:13 +, Marwan Sultan wrote:
> i'm on FreeBSD 7.2-R p4
> I just applied :
> # freebsd-update fetch
> # freebsd-update install
> with no problems
Later you mentioned that you run a custom kernel,
especially for inclusion of quota. When using the
Hello FreeBSD people.
i'm on FreeBSD 7.2-R p4
I just applied :
# freebsd-update fetch
# freebsd-update install
with no problems
After i restarted the server
i lost my ssh connection, server went down!
I have contacted the hosting company, and after investigation
of bsdlabel output mean?
How do I manage this?
Thank's in advance for any advice.
2009/11/27 S4mmael :
> Thank you.
>
> 2009/11/26 Alexandre L. :
>> Hi,
>>
>> I paste this link where Colin Percival explain who to use the tool
>> freebsd-update with cust
Hi maillist.
After applying non kernel-level patch set via freebsd-update my system after
rebooting show FreeBSD 8.0 version, not 8.0-p1. New instance of freebsd-update
check system again by checksum and show that system is already patched as -p1.
With updating i see changing of file
Hi,
I paste this link where Colin Percival explain who to use the tool
freebsd-update with custom kernel. But I think that same thing as been written
in the handbook.
http://forums.freebsd.org/showpost.php?p=30920&postcount=9
--- En date de : Jeu 26.11.09, S4mmael a écrit :
> De:
On Thursday 26 November 2009 14:32:01 S4mmael wrote:
> Hi all!
>
> I've got a problem while upgrading FreeBSD 7.2-RELEASE-p3 -> FreeBSD
> 8.0-RELESE with freebsd-update(8).
>
> First of all I made a copy of the most configuration files. Then I made:
> # freebsd-
Hi all!
I've got a problem while upgrading FreeBSD 7.2-RELEASE-p3 -> FreeBSD
8.0-RELESE with freebsd-update(8).
First of all I made a copy of the most configuration files. Then I made:
# freebsd-update -r 8.0-RELEASE upgrade
All went good, except the message, that because of MYKERNE
The installer eventually worked on the sixth attempt (I had to use the CD
to load the kernel and then yank the CD out amongst streams of
READ_TIMED_OUT errors).
May have made things worse, however.
___
freebsd-questions@freebsd.org mailing list
http://li
On Wed, 25 Nov 2009 11:49:44 +, cali clarke
wrote:
> What's the quickest and cleanest way out of this mess?
You can install the base system from the FreeBSD 8.0-RC
CD-ROM. This should give you a working system again.
Keep an eye on NOT formatting anything.
Using a live system CD-ROM, it wou
I just updated to 8.0-RELEASE with freebsd-update.
I ran:
# freebsd-update -r 8.0-RELEASE upgrade
# freebsd-update install
I was told to reboot and run freebsd-update install again to complete the
process.
I rebooted into single user mode, mounted /usr and /var and somehow forgot
to
mount
On Wed 2009-11-11 12:35:55 UTC-0600, Jason Fried (r...@churchofbsd.org) wrote:
> I have a fairly old install and not much room on my ROOT is there a way to
> prevent freebsd-update from installing ".symbols" files.
In /etc/freebsd-update.conf:
IgnorePaths /boot/kernel/*.symbol
I have a fairly old install and not much room on my ROOT is there a way to
prevent freebsd-update from installing ".symbols" files.
Thanks,
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-qu
Whether there is a method of reception of the list of the releases
accessible to updating through freebsd-update(8)? For example, if open
http://update5.freebsd.org catalogs "to-N.M-RELEASE\*" are visible -
where it is possible to be updated. But it well thanking for Indexes
options
Fernando Apesteguía wrote:
> 2009/9/20 Fernando Apesteguía :
>
>> Hi all,
>>
>> I'm having some problems trying to update from FreeBSD 8.0 Beta1 to 8.0
>> Beta4.
>>
>> I upgraded from 7.2 to beta1 some time ago, using freebsd-update
>> wit
2009/9/20 Fernando Apesteguía :
> Hi all,
>
> I'm having some problems trying to update from FreeBSD 8.0 Beta1 to 8.0 Beta4.
>
> I upgraded from 7.2 to beta1 some time ago, using freebsd-update
> without problems. Later
> I did the same thing to reach beta2. Yesterday I
Hi all,
I'm having some problems trying to update from FreeBSD 8.0 Beta1 to 8.0 Beta4.
I upgraded from 7.2 to beta1 some time ago, using freebsd-update
without problems. Later
I did the same thing to reach beta2. Yesterday I tried it to get to
beta3 but I have a bunch
of errors like thi
No worries, all. I've managed to get this to work, and have a working
internal freebsd-update server.
With some help from Colin, I've realized a couple of things that needed to
be changed for my setup to work. In regards to the amd64 build I was doing,
it was missing some kernel so
On Wed, 9 Sep 2009 05:26:13 +
Eitan Adler wrote:
> When I try to update to 8.0-BETA3
Try Beta4 instead.
http://lists.freebsd.org/pipermail/freebsd-stable/2009-September/051801.html
Andreas
--
GnuPG key : 0x2A573565|http://www.gnupg.org/howtos/de/
Fingerprint: 925D 2089 0BF9 8DE5 91
When I try to update to 8.0-BETA3 using freebsd-update I get a gunzip
problem like: metadata iscorrupt
I tried to remove /var/db/freebsd-update/files/* but I get the same
error message
Is this a client side problem or a server problem?
If the former how do I fix it
Hi,
I am wondering if anyone has attempted to mirror the freebsd-update server?
Thanks,
Jason
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "fr
--
From: "Eitan Adler"
Sent: Monday, August 17, 2009 6:48 PM
To:
Subject: freebsd-update to -BETA2 p1
AlphaBeta# freebsd-update fetch install
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for
AlphaBeta# freebsd-update fetch install
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 8.0-BETA2 from update5.FreeBSD.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
No updates needed to
Does anyone have any thoughts, or experience in using the
freebsd-update-server code?
Thanks,
Jason
On Mon, Aug 10, 2009 at 09:24:52AM -0700, Jason thus spake:
Hi.
The freebsd-update-server project software hasn't been updated for 7,2,
but after making a couple of simple modification
Hi.
The freebsd-update-server project software hasn't been updated for 7,2,
but after making a couple of simple modifications, it seems to work rather well.
I am close, but not quiet smoking the cigar of triumph, yet.
When it initially builds, I get this error in the output:
Fri Aug
Richard Mahlerwein wrote:
[snip]
>
> I currently have my little westell DSL router set to be my DNS for all my
> boxes behind it. While a neat little box, it has its issues from time to
> time. Should I at least point my DNS to the DNS it uses to save an extra
> relay?
Depends. I don't know if
--- On Sat, 8/8/09, RW wrote:
> From: RW
> Subject: Re: Freebsd-update question
> To: freebsd-questions@freebsd.org
> Date: Saturday, August 8, 2009, 4:59 PM
> On Sat, 8 Aug 2009 11:14:10 -0700
> (PDT)
> Richard Mahlerwein
> wrote:
>
>
> > mobius# dig +sho
On Sat, 8 Aug 2009 11:14:10 -0700 (PDT)
Richard Mahlerwein wrote:
> mobius# dig +short _http._tcp.update.freebsd.org srv
> (returns nothing)
This is typically either due either to broken SRV support in DNS, or
the absence of full dns on a private network behind proxies. Perhaps
you need to set
Thanks for the help, I figured out the [likely] answer and included it at the
bottom.
--- On Sat, 8/8/09, Richard Mahlerwein wrote:
> From: Richard Mahlerwein
> Subject: Re: Freebsd-update question
> To: freebsd-questions@freebsd.org
> Date: Saturday, August 8, 2009, 2:06
> From: RW
> Subject: Re: Freebsd-update question
> To: freebsd-questions@freebsd.org
> Date: Saturday, August 8, 2009, 11:46 AM
> On Sat, 8 Aug 2009 07:16:15 -0700
> (PDT)
> Richard Mahlerwein
> wrote:
>
> > I thought I'd give freebsd-updat
[random snippage all over]
> > From: Glen Barber
> > Subject: Re: Freebsd-update question
> > On Sat, Aug 8, 2009 at 10:25 AM,
> > Richard Mahlerwein
> > wrote:
> > mobius# freebsd-update -s update.freebsd.org fetch
> > Looking up update.freebsd.org mirr
On Sat, 8 Aug 2009 07:16:15 -0700 (PDT)
Richard Mahlerwein wrote:
> I thought I'd give freebsd-update a try since I run a GENERIC kernel.
>
> mobius# freebsd-update -s update.freebsd.org fetch
> Looking up update.freebsd.org mirrors... none found.
> Fetching public key fro
On Sat, Aug 8, 2009 at 10:25 AM, Richard Mahlerwein wrote:
>> > I thought I'd give freebsd-update a try since I run a
>> GENERIC kernel.
>> >
>> > mobius# freebsd-update -s update.freebsd.org fetch
>> > Looking up update.freebsd.org mirro
--- On Sat, 8/8/09, Glen Barber wrote:
> From: Glen Barber
> Subject: Re: Freebsd-update question
> To: mahle...@yahoo.com
> Cc: freebsd-questions@freebsd.org
> Date: Saturday, August 8, 2009, 10:20 AM
> Hi Richard,
>
> On Sat, Aug 8, 2009 at 10:16 AM, Richard Mahlerwei
Hi Richard,
On Sat, Aug 8, 2009 at 10:16 AM, Richard Mahlerwein wrote:
> I thought I'd give freebsd-update a try since I run a GENERIC kernel.
>
> mobius# freebsd-update -s update.freebsd.org fetch
> Looking up update.freebsd.org mirrors... none found.
> Fetc
I thought I'd give freebsd-update a try since I run a GENERIC kernel.
mobius# freebsd-update -s update.freebsd.org fetch
Looking up update.freebsd.org mirrors... none found.
Fetching public key from update.freebsd.org... failed.
No mirrors remaining, giving up.
Thinking perhaps a netwo
Evening folks... have just built up a new 7.0-RELEASE box, and have gone to
update it to 7.0-RELEASEp11, however, whenever I run freebsd-update fetch I get
the following:
bigsis2# freebsd-update fetch
Looking up update1.FreeBSD.org mirrors... none found.
Fetching metadata signature for 7.0
On Sunday 02 August 2009 16:10:37 Tom Mende wrote:
Is there a way to get freebsd-update to keep userland sources up to
date?
Yes. If you have source code installed (for the right version of FreeBSD)
in /usr/src, then freebsd-update will keep it updated.
(Slight complication: Because freebsd
On Sunday 02 August 2009 16:10:37 Tom Mende wrote:
> Is there a way to get freebsd-update to keep userland sources up to
> date?
Since it is for binary upgrades, it doesn't make much sense, but ...
> By way of background, I am trying not to use csup / cvsup and like
> proces
2009/8/2 Tom Mende :
> Is there a way to get freebsd-update to keep userland sources up to date?
>
> I had thought that having src, world and kernel as components in the
> freebsd-update.conf file would do this but it doesn't seem to. Do I just add
> usr.bin and usr.sbin to th
Is there a way to get freebsd-update to keep userland sources up to
date?
I had thought that having src, world and kernel as components in the
freebsd-update.conf file would do this but it doesn't seem to. Do I
just add usr.bin and usr.sbin to the components list in the conf file
an
Embarrassingly simple actually. I configured a new server from a 7.0 CD I made a
while back, brought the system to 7.1 the regular way and ran freebsd-update.
The embarrassing part is I took little note of the fetch output other than 24
files were updated. Can I find out which 24?
As always
On Wednesday 29 July 2009 11:31:51 Glen Barber wrote:
> On Wed, Jul 29, 2009 at 10:58 AM, Predrag Aleksic wrote:
> > freebsd-update fetch
> > Looking up update.FreeBSD.org mirrors... 3 mirrors found.
> > Fetching metadata signature for 7.2-RELEASE from update5.FreeBSD.org...
&
On Wed, 2009-07-29 at 11:36 -0400, John Nielsen wrote:
> On Wednesday 29 July 2009 11:31:51 Glen Barber wrote:
> > On Wed, Jul 29, 2009 at 10:58 AM, Predrag Aleksic wrote:
> > > freebsd-update fetch
> > > Looking up update.FreeBSD.org mirrors... 3 mirrors found.
> &
On Wed, Jul 29, 2009 at 10:58 AM, Predrag Aleksic wrote:
> freebsd-update fetch
> Looking up update.FreeBSD.org mirrors... 3 mirrors found.
> Fetching metadata signature for 7.2-RELEASE from update5.FreeBSD.org...
> done.
> Fetching metadata index... done.
> Inspecting system...
freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 7.2-RELEASE from update5.FreeBSD.org...
done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
No updates needed to update system to 7.2
Axel wrote:
> Hello,
>
> I have previously kept my machine updated by fetching the STABLE
> branch using csup and rebuilding the kernel. (As described in Handbook
> chapter 24.7)
>
> From now on, I want to use freebsd-update to simplify the process and
> follow the
Axel wrote:
Hello,
I have previously kept my machine updated by fetching the STABLE branch
using csup and rebuilding the kernel. (As described in Handbook chapter
24.7)
From now on, I want to use freebsd-update to simplify the process and
follow the RELEASE branch (+patches) instead
Axel wrote:
From now on, I want to use freebsd-update to simplify the process and
follow the RELEASE branch (+patches) instead.
But it seems that freebsd-update cannot help me upgrade from 7.1-STABLE
to 7.2-RELEASE.
Any tips on how to make the transition to RELEASE?
You must use CVSup
Hello,
I have previously kept my machine updated by fetching the STABLE branch
using csup and rebuilding the kernel. (As described in Handbook chapter
24.7)
From now on, I want to use freebsd-update to simplify the process and
follow the RELEASE branch (+patches) instead.
But it seems
I noticed that on my amd64 systems almost all of /bin, /sbin, /lib, /
usr/bin, etc had changed from 7.2-RELEASE-p1 to 7.2-RELEASE-p2. On my
i386 only some network drivers, libc and rescue files were updated.
Is this normal? Before installing the update I made a copy of the
files, and it looks
Maybe you shouldn't run those while typing an email?
Seriously, ENOTENOUGHINFO | EQUESTIONMISSING.
--
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebs
301 - 400 of 656 matches
Mail list logo
