On 11/22/12 17:32, Karl Pielorz wrote:
>
> Hi,
>
> I have a number of 9.0-R boxes, some of which I've updated in the past
> to 9.0-STABLE (as of the date they were done).
>
> I'm looking at switching to 'freebsd-update' - is there an equivalent
> way t
On Thu, 22 Nov 2012 16:32:21 +, Karl Pielorz wrote:
> I'm looking at switching to 'freebsd-update' - is there an equivalent way
> to get it to update me to '-STABLE'?
No. The freebsd-update program can only be used to follow
the RELEASE branch, plus t
Hi,
I have a number of 9.0-R boxes, some of which I've updated in the past to
9.0-STABLE (as of the date they were done).
I'm looking at switching to 'freebsd-update' - is there an equivalent way
to get it to update me to '-STABLE'?
i.e. If I run this on a
On Wed, 21 Nov 2012, Arthur Chance wrote:
On 11/21/12 05:11, Warren Block wrote:
gptboot looks for the first UFS partition. Maybe /boot/boot can be
modified to do that also.
It's a little more complicated than that Warren.
AIUI gptboot first looks (in partition order) for partitions with bo
On 11/21/12 05:11, Warren Block wrote:
gptboot looks for the first UFS partition. Maybe /boot/boot can be
modified to do that also.
It's a little more complicated than that Warren.
AIUI gptboot first looks (in partition order) for partitions with both
the bootme and bootonce attributes set.
On Tue, 20 Nov 2012, free...@johnea.net wrote:
On 2012-11-20 14:28, Gary Aitken wrote:
On 11/20/12 13:34, free...@johnea.net wrote:
freebsd-update upgrade -r 9.1-RC3
...
"Not UFS" "No ada0" "No boot"
Seems like it isn't supposed to work for 9.1-RC2
On 2012-11-20 14:28, Gary Aitken wrote:
> On 11/20/12 13:34, free...@johnea.net wrote:
>> freebsd-update upgrade -r 9.1-RC3
...
>> "Not UFS" "No ada0" "No boot"
>
> Seems like it isn't supposed to work for 9.1-RC2
>
I previously u
orsbackup# gpart bootcode -b /boot/boot mirror/gm0s1
>
>
> The system rebooted several times without issue. This system is a testbed for
> 9.1 and is not yet deployed as a production server.
>
> I thought I'd update to 9.1-RC3, so I ran:
>
> freebsd-update upgrad
to 9.1-RC3, so I ran:
freebsd-update upgrade -r 9.1-RC3
freebsd-update install
reboot
The system won't boot and complains about:
"Not UFS" "No ada0" "No boot"
Before I charge ahead with reissuing the gpart bootcode commands I thought I'd:
a) make others awa
Hi,
>> My questions is: how to rebuild all third-party applications? I have
>> kept the ports tree up to date using
>> # portsnap fetch update
>> and
>> # portmaster -Ga
>> every day.
>> ...
>
> I would advise you to drop -G option and use these entries:
> # portsnap fetch update
> # portmaster -
Jinsong Zhao yeah.net> writes:
> ...
> My questions is: how to rebuild all third-party applications? I have
> kept the ports tree up to date using
> # portsnap fetch update
> and
> # portmaster -Ga
> every day.
> ...
I would advise you to drop -G option and use these entries:
# portsnap fetch
Hi there,
I am going to upgrade my FreeBSD 8.2-RELEASE to 9.1-RELEASE according to
http://www.freebsd.org/releases/9.0R/installation.html
However, I don't know how to follow the step below:
##start here##
# freebsd-update install
At this point, users of systems being upgraded
I've installed 9.1-RC2 after using svn to download /usr/src. Shortly after
rebooting into the new system, and just out of curiosity, I
ran "freebsd-update IDS" and was surprised to see that it reported 735 hash
mismatches. Some of these were for files modified locally like /etc
On Tue, 09 Oct 2012 11:47:02 +0200
Istvan Gabor wrote:
> FreeBSD Handbook (at the end of section 25.2.2) says:
>
> "However, freebsd-update will always update the /usr/src/sys/conf/newvers.sh
> file.
> The current patch level (as indicated by the -p number reported by unam
the computer uname gives p3 on the updated system:
> >
> > Why does uname reports p3 while freebsd-update indicates p4 state?
>
> Hi,
>
> if freebsd-update does not update the kernel uname will not show the
> 'correct' patch level.
>
> Andreas
Thanks And
On Mon, 08 Oct 2012 16:52:24 +0200
Istvan Gabor wrote:
> As I remember correctly during the fetch I saw a message that the current
> patch level is p4.
> After rebooting the computer uname gives p3 on the updated system:
>
> Why does uname reports p3 while freebsd-update indicate
Hello:
I updated FreeBSD 9.0 RELEASE
(FreeBSD 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC 2012
r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386)
using freebsd-update fetch and freebsd-update install commands.
As I remember correctly during the fetch I saw a message
I am using freebsd-update to update a system running a generic kernel. I ran
into an interesting situation where after it has downloaded the updates it
enters a configuration phase where it shows "updated" config files with the old
and new. You can hit return to enter vi and clean u
On Sun, 26 Aug 2012, Walter Hurry wrote:
On Sun, 26 Aug 2012 14:24:34 -0400, doug wrote:
In doing an update from 8.3 --> 9.0 I messed up the merge on /etc/ttys.
This has interesting consequences BTW. Are there any docs on how to do
this?
Here's mine. Note: I changed ttyv8 from off to on as I
On Sun, 26 Aug 2012 14:24:34 -0400, doug wrote:
> In doing an update from 8.3 --> 9.0 I messed up the merge on /etc/ttys.
> This has interesting consequences BTW. Are there any docs on how to do
> this?
Here's mine. Note: I changed ttyv8 from off to on as I am using xdm.
console none
In doing an update from 8.3 --> 9.0 I messed up the merge on /etc/ttys. This has
interesting consequences BTW. Are there any docs on how to do this?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questio
On Thu, 23 Aug 2012 13:49:18 -0400 (EDT), d...@safeport.com wrote:
> After seeing if xorg and twm would just work, I did remove all packages with
> pkg_delete. That did not clear out all of /usr/local.
You can do a manual cleanup of /usr/local, entirely removing it
and then reconstructing its str
On Thu, 23 Aug 2012, Polytropon wrote:
On Thu, 23 Aug 2012 11:36:51 -0400 (EDT), d...@safeport.com wrote:
I wanted to see if I could get an 8.1 system updated to 9.0 (mostly) with
freebsd-update. I did this with a source update to RELENG_8_3 and then did the
standard stuff to get to 9.0
perl
On Thu, 23 Aug 2012 11:36:51 -0400 (EDT), d...@safeport.com wrote:
> I wanted to see if I could get an 8.1 system updated to 9.0 (mostly) with
> freebsd-update. I did this with a source update to RELENG_8_3 and then did
> the
> standard stuff to get to 9.0
>
> perl and xd
I wanted to see if I could get an 8.1 system updated to 9.0 (mostly) with
freebsd-update. I did this with a source update to RELENG_8_3 and then did the
standard stuff to get to 9.0
perl and xdm both gave errors that libutil.so.9 was missing. scanning google and
questions suggested this
> If you're building your own customised kernel, why don't you just build the
> entire system from source? I've not used freebsd-update yet and probably
> won't. Is it just a matter of time, i.e. waiting for the compilation to
> finish?
Actually I built this
== Denis wrote on Mon 20.Aug'12 at 16:41:56 +0400 ==
> > Then why not follow my suggestion of _letting_ freebsd-update
> > update the kernel, but _use_ a different one instead which it
> > won't touch? In /boot/loader.conf:
> >
> > kernel="m
> Then why not follow my suggestion of _letting_ freebsd-update
> update the kernel, but _use_ a different one instead which it
> won't touch? In /boot/loader.conf:
>
> kernel="mykernel"
> bootfile="/boot/mykernel/kernel"
>
> Now fr
l
>
> Yes, I rebuilt my custom kernel after. But this doesn't help - every
> time I run "freebsd-update fetch" it suugest me to update kernel and
> kernel.symbols.
Then why not follow my suggestion of _letting_ freebsd-update
update the kernel, but _use_ a different one
ery
time I run "freebsd-update fetch" it suugest me to update kernel and
kernel.symbols.
Best regards,
Denis
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any ma
On Mon, Aug 20, 2012 at 11:47 AM, Denis wrote:
> Hi,
>
> I have FreeBSD 9.0 (p4) with custom kernel.
>
> "uname -i" says it:
> HOMEWIFI90
>
> However, when I run "freebsd-update fetch" command it would like to
> update my kernel as well:
>
>
Hi,
I have FreeBSD 9.0 (p4) with custom kernel.
"uname -i" says it:
HOMEWIFI90
However, when I run "freebsd-update fetch" command it would like to
update my kernel as well:
freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metada
On Fri, 17 Aug 2012 01:48:18 +0200, Polytropon wrote:
< snip problem and comprehensive answer >
That's really helpful. Very many thanks, Polytropon.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-quest
On Thu, 16 Aug 2012 21:24:37 + (UTC), Walter Hurry wrote:
> Every time I run "freebsd-update fetch" it says it wants to update the
> following 5 source files "as part of updating to 9.0-RELEASE-p4":
>
> /usr/src/sys/amd64/amd64/trap.c
> /usr/src/sys/con
Please forgive me if this is a daft question; I am quite new to FreeBSD.
I have read the handbook assiduously and am attempting to follow it. This
is 9.0-RELEASE-p3, by the way.
Every time I run "freebsd-update fetch" it says it wants to update the
following 5 source files "as p
On Mon, Aug 13, 2012 at 1:07 PM, Brett Glass wrote:
> At 11:33 AM 8/13/2012, Michael Sierchio wrote:
>
>> And it does, in my experience. If the hash of the kernel doesn't
>> match that of the distribution (or recent update), freebsd-update
>> leaves it alone.
&g
At 12:59 PM 8/13/2012, Polytropon wrote:
I've never seen a system having a /boot/GENERIC directory
containing the GENERIC kernel.
It does not come that way. The Handbook recommends that one
manuall copy the original kernel from the distribution into
/boot/GENERIC before building a custom kerne
At 11:33 AM 8/13/2012, Michael Sierchio wrote:
And it does, in my experience. If the hash of the kernel doesn't
match that of the distribution (or recent update), freebsd-update
leaves it alone.
That is what I thought it would do, based on the docs. However,
when I recently ran fr
On Mon, 13 Aug 2012 10:35:12 -0600, Brett Glass wrote:
> At 05:24 AM 8/13/2012, Polytropon wrote:
>
> >That seems to be the default behaviour, as freebsd-update is
> >not supposed to be used with a custom kernel. It works with
> >GENERIC kernels (because it upd
On Mon, Aug 13, 2012 at 9:35 AM, Brett Glass wrote:
> Actually, freebsd-update is claimed to respect custom kernels. ...
And it does, in my experience. If the hash of the kernel doesn't
match that of the distribution (or recent update), freebsd-update
leaves
At 05:24 AM 8/13/2012, Polytropon wrote:
That seems to be the default behaviour, as freebsd-update is
not supposed to be used with a custom kernel. It works with
GENERIC kernels (because it updates them by overwriting).
Actually, freebsd-update is claimed to respect custom kernels. See
the
On Sun, 12 Aug 2012 20:50:43 -0600, Brett Glass wrote:
> Everyone:
>
> Just ran freebsd-update (fetch, then install) on a system on which
> I run a customized kernel, and discovered that it has overwritten
> my custom kernel... even though I'd copied the original to
&g
Everyone:
Just ran freebsd-update (fetch, then install) on a system on which
I run a customized kernel, and discovered that it has overwritten
my custom kernel... even though I'd copied the original to
/boot/GENERIC when I first installed the system. I was under the
impression that cre
here is 384M of swap encrypted using geli_swap_flags="-d -l 256 -s 4096".
The rest of the disk space is encrypted with "geli init -b -v -a
hmac/sha256 -l 256 -s 4096 /dev/ada0p4".
After I've installed a VPS in this way, I run the freebsd-update fetch
command and it freezes a
On Mon, 25 Jun 2012 14:12:36 +0100
RW wrote:
> On Mon, 25 Jun 2012 06:53:45 -0500
> Zane C. B-H. wrote:
>
> > On Mon, 25 Jun 2012 12:26:12 +0100
> > RW wrote:
> >
>
> > > freebsd-update doesn't support development branches, you have
> &g
On Mon, 25 Jun 2012 06:53:45 -0500
Zane C. B-H. wrote:
> On Mon, 25 Jun 2012 12:26:12 +0100
> RW wrote:
>
> > freebsd-update doesn't support development branches, you have to go
> > from security branch to security branch.
>
> I know it can't be u
8.3-PRERELEASE FreeBSD
> > 8.3-PRERELEASE #0: Sat Feb 25 04:55:35 CST 2012
> > kits...@shiela.vulpes.vvelox.net:/usr/obj/usr/src/sys/sheila
> > amd64 [root@shiela]/root# freebsd-update -r 9.0-RELEASE upgrade
> > Looking up update.FreeBSD.org mirrors... 3 mirrors found.
a.vulpes.vvelox.net:/usr/obj/usr/src/sys/sheila amd64
> [root@shiela]/root# freebsd-update -r 9.0-RELEASE upgrade Looking up
> update.FreeBSD.org mirrors... 3 mirrors found. Fetching public key
> from update5.FreeBSD.org... failed. Fetching public key from
> update4.FreeBSD.org... failed
Howdy!
Any one have any idea what is going on below?
[root@shiela]/root# uname -a
FreeBSD shiela.vulpes.vvelox.net 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Sat
Feb 25 04:55:35 CST 2012
kits...@shiela.vulpes.vvelox.net:/usr/obj/usr/src/sys/sheila amd64
[root@shiela]/root# freebsd-update
talled the latest update with freebsd-update and it went well
without any warnings.
Thanks for the advice :-)
/Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send a
I tried to update an amd64 FreeBSD 9.0 p0 system via freebsd-update tonight.
It fetched everything fine. However, the install just hung after about 10
minutes. The 2 sh processes are basically doing nothing. Not consuming any
processor time and not doing any I/O. I killed it and tried
> Should I install the libc souces?
I had this error when upgrading 8.x (8.1 to 8.2?), and solved it by creating
the directory only (actual sources not required). I recall someone had
posted this solution to the list at the time.
Regards,
Dale
___
fr
2012-06-14 12:18, Matthew Seaman skrev:
On 14/06/2012 10:45, Leslie Jensen wrote:
When I do
freebsd-update install
I get this error:
Installing updates...install: ///usr/src/lib/libc/gen/libc_dlopen.c: No
such file or directory
I think it's because I do not have all sources installe
On 14/06/2012 10:45, Leslie Jensen wrote:
> When I do
>
> freebsd-update install
>
> I get this error:
>
> Installing updates...install: ///usr/src/lib/libc/gen/libc_dlopen.c: No
> such file or directory
>
> I think it's because I do not have all sources ins
On 14/06/2012 10:41, Leslie Jensen wrote:
> When one recives the
>
> FreeBSD Errata Notice or
>
> FreeBSD Security Advisory
>
> The instruction is to do:
>
>
> # freebsd-update fetch
>
> # freebsd-update install
>
>
>
> From earlier d
When I do
freebsd-update install
I get this error:
Installing updates...install: ///usr/src/lib/libc/gen/libc_dlopen.c: No
such file or directory
I think it's because I do not have all sources installed. So I just want
to confirm that it's the case.
Also, should I care and i
When one recives the
FreeBSD Errata Notice or
FreeBSD Security Advisory
The instruction is to do:
# freebsd-update fetch
# freebsd-update install
From earlier discussions on this list about the -px number not
changing, I usually rebuild and install the kernel.
My question is:
Do I
Hi,
Hopefully a simple problem with a simple solution. Trying to update a server
using freebsd-update, but when I try I get the following:
# freebsd-update fetch install
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 8.3-RELEASE from update5.FreeBSD.org
, Ryan Frederick wrote:
> I have several FreeBSD 9 systems with custom compiled kernels. After
> using freebsd-update to go from 9.0-RELEASE-p2 to 9.0-RELEASE-p3 this
> morning I rebuilt the kernels. However after recompiling, installing,
> and rebooting with the custom kernels subsequent u
Resend as I lost cc questions@ by mistake
Ryan Frederick wrote:
> I have several FreeBSD 9 systems with custom compiled kernels. After
> using freebsd-update to go from 9.0-RELEASE-p2 to 9.0-RELEASE-p3 this
> morning I rebuilt the kernels. However after recompiling, installin
I have several FreeBSD 9 systems with custom compiled kernels. After
using freebsd-update to go from 9.0-RELEASE-p2 to 9.0-RELEASE-p3 this
morning I rebuilt the kernels. However after recompiling, installing,
and rebooting with the custom kernels subsequent update checks using
freebsd-update
On 03/06/2012 13:00, RW wrote:
On Sun, 03 Jun 2012 12:47:47 +0100
Chris Whitehouse wrote:
c400# uname -a
FreeBSD c400 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25
UTC 2012
r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
Following the handbook:
c400# freebsd-update
On Sun, 03 Jun 2012 12:47:47 +0100
Chris Whitehouse wrote:
>
> c400# uname -a
> FreeBSD c400 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25
> UTC 2012
> r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
>
> Following the handbook:
>
> c400#
c400# uname -a
FreeBSD c400 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC
2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
Following the handbook:
c400# freebsd-update -r 9-STABLE upgrade
Looking up update.FreeBSD.org mirrors... 4 mirrors found.
Fetching
LE RECORD of
> > > 'what was done'. 'add to top' has several disadvantages. First,
> > > a performance issue, you do have to read down the log to find the
> > > first 'END' line rather than being able to seek directly to it.
> > > S
Polytropon wrote:
>
> First of all, thanks for explaining your point of view.
> Allow me to add a few thoughts:
>
> On Fri, 4 May 2012 11:44:49 -0500 (CDT), Robert Bonomi wrote:
> >
> > Polytropon wrote:
> > > On Fri, 4 May 2012 04:14:05 -0500 (CDT), Robert Bonomi wrote:
> > > > What is require
On 4 May 2012, at 16:45, Polytropon wrote:
> On Fri, 4 May 2012 04:14:05 -0500 (CDT), Robert Bonomi wrote:
>> What is required is a differentation between the _kernel_ revision level,
>> and the patchlevel of the entire base system.
>>
>> Store the kernel revision level -in- the kernel. Use th
First of all, thanks for explaining your point of view.
Allow me to add a few thoughts:
On Fri, 4 May 2012 11:44:49 -0500 (CDT), Robert Bonomi wrote:
>
> Polytropon wrote:
> > On Fri, 4 May 2012 04:14:05 -0500 (CDT), Robert Bonomi wrote:
> > > What is required is a differentation between the _ke
On 2012-05-04 10:45, Polytropon wrote:
Allow me to extent the approach: For -STABLE versions (e. g. if
updated per CVS), those files could contain the "build number"
and the date of the currently installed -STABLE "snapshot".
A separation of a "kernel version file" and a "world version
file" is
quot;. (Who was, by the way,
a real person.)
Let me introduce you to, "O'Brien's Law" -- it says, very simply, and pithily,
"Murphy was an OPTIMIST!!!"
For systems work, and expecilly 'logging' it is imperative to prevent any
opportunity for O'Brien
hould
rather go to /var or even /var/log. :-)
> With this kind of setup, and assuming that all distributed patchfiles have
> 'unique' names, the 'patchlog' provides a roadmap for reconstructing the
> state of the kernel and 'world' as of any particular poin
> From owner-freebsd-questi...@freebsd.org Fri May 4 02:54:56 2012
> Date: Fri, 04 May 2012 08:52:24 +0100
> From: Matthew Seaman
> To: freebsd-questions@freebsd.org
> Subject: Re: freebsd-update not updating reported patchlevel
>
> On 03/05/2012 23:43, Robert Bonomi wrote
On 03/05/2012 22:52, Mike Brown wrote:
> For example, with this latest OpenSSL security update, running
> 'freebsd-update
> fetch' says (among other things) "The following files will be updated as part
> of updating to 8.2-RELEASE-p7" and "WARNING: FreeBSD
On 03/05/2012 23:43, Robert Bonomi wrote:
> Amazingly, this very question was covered on this list within the last few
> hours.
It's not that much of a coincidence. We always get a rash of queries
like this every time there's a security advisory and consequently a lot
of people are updating.
Mike Brown wrote;
> I installed 8.2-RELEASE when it was new, and have been just using
> freebsd-update since then. I run freebsd-update whenever there are new
> critical patches. But for some reason, my system's reported patchlevel number
> hasn't updated since p3.
[s
I installed 8.2-RELEASE when it was new, and have been just using
freebsd-update since then. I run freebsd-update whenever there are new
critical patches. But for some reason, my system's reported patchlevel number
hasn't updated since p3.
For example, with this latest OpenSSL secur
Matthew Seaman writes:
> That's a known problem and fixable by first updating your 8.2-RELEASE
> machine to the latest patch level before trying the update to 9.0
It appears to be working now. Thank you.
___
freebsd-questions@freebsd.org mailing
On 31/01/2012 13:55, Martin McCormick wrote:
> I started to run freebsd-update to upgrade a 8.x system
> to 9.0-RELEASE
>
> # freebsd-update -r 9.0-RELEASE upgrade
>
> Looking up update.FreeBSD.org mirrors... 4 mirrors found.
> Fetching metadata signature for 8.2
I started to run freebsd-update to upgrade a 8.x system
to 9.0-RELEASE
# freebsd-update -r 9.0-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 4 mirrors found.
Fetching metadata signature for 8.2-RELEASE from update5.FreeBSD.org... done.
Fetching metadata index... done
On Mon, Jan 23, 2012 at 8:50 PM, Christer Solskogen
wrote:
> On Mon, Jan 23, 2012 at 4:08 PM, Colin Percival wrote:
>
>> Hmm, you've got almost everything being different there. Did you use the
>> same
>> src tree as the release? If you checked out the tree via CVS it won't match.
>>
>
> Hang
On Mon, Jan 23, 2012 at 4:08 PM, Colin Percival wrote:
> Hmm, you've got almost everything being different there. Did you use the same
> src tree as the release? If you checked out the tree via CVS it won't match.
>
Hang on. I cheated a little. I used the base.txz from the release and
compared
On 01/23/12 06:59, Christer Solskogen wrote:
> On Mon, Jan 23, 2012 at 3:03 PM, Colin Percival wrote:
>> On 01/22/12 03:45, Christer Solskogen wrote:
>>> I just did, and the file list is the same. Or do you want me to do a
>>> md5 of every file?
>>
>> Yes, I meant to compare the contents of files
On Mon, Jan 23, 2012 at 3:03 PM, Colin Percival wrote:
> On 01/22/12 03:45, Christer Solskogen wrote:
>> I just did, and the file list is the same. Or do you want me to do a
>> md5 of every file?
>
> Yes, I meant to compare the contents of files (or their hashes of course).
Here you go:
http://an
On 01/22/12 03:45, Christer Solskogen wrote:
> On Sat, Jan 21, 2012 at 1:21 PM, Colin Percival wrote:
>> Try doing a release cross-build and compare it against a non-crossed release
>> build; extract the built tarballs and send me a list of which ones aren't
>> identical. I know which files "norm
Matthew Seaman wrote:
> On 21/01/2012 10:25, Christer Solskogen wrote:
> > I've just finished installing FreeBSD on my "new" Mac mini G4 ...
>
> If that's not an Intel based Mac, then your definition of "new" is,
> well, contrary to all accepted usage.
s/"new"/newly acquired/
(I suspect).
__
On 01/21/12 04:15, Christer Solskogen wrote:
> On Sat, Jan 21, 2012 at 12:42 PM, Colin Percival wrote:
>> We don't have suitable build hardware for other architectures, and there are
>> some problems with release cross-building which aren't fixed yet.
>
> I found out that building ppc with TARGET
On Sat, Jan 21, 2012 at 12:42 PM, Colin Percival wrote:
> We don't have suitable build hardware for other architectures, and there are
> some problems with release cross-building which aren't fixed yet.
>
I found out that building ppc with TARGET= worked nicely on 9.0-RELEASE.
Do you know what pr
On Sat, Jan 21, 2012 at 11:52 AM, Matthew Seaman
wrote:
> On 21/01/2012 10:25, Christer Solskogen wrote:
>> I've just finished installing FreeBSD on my "new" Mac mini G4, and
>> when I ran freebsd-update on it I found out that freebsd-update only
>> supports
On 01/21/12 02:25, Christer Solskogen wrote:
> I've just finished installing FreeBSD on my "new" Mac mini G4, and
> when I ran freebsd-update on it I found out that freebsd-update only
> supports i386 and amd64 architectures.
> How come?
We don't have s
On 21/01/2012 10:25, Christer Solskogen wrote:
> I've just finished installing FreeBSD on my "new" Mac mini G4, and
> when I ran freebsd-update on it I found out that freebsd-update only
> supports i386 and amd64 architectures.
> How come?
If that's not an Intel ba
Hi!
I've just finished installing FreeBSD on my "new" Mac mini G4, and
when I ran freebsd-update on it I found out that freebsd-update only
supports i386 and amd64 architectures.
How come?
--
chs,
___
freebsd-questions@freebsd.org ma
On Fri, 20 Jan 2012 17:24:53 +0100, Dick Hoogendijk wrote:
> Is it true that freebsd-update does not update the souce files from
> 8.2-R to 9.0-RELEASE?
I think also updating src/ is the default behaviour.
See "man freebsd-update.conf", setting "Components":
Is it true that freebsd-update does not update the souce files from
8.2-R to 9.0-RELEASE? And if not what is the best way to get the src.txz
installed on an updated system? I do have the disc1 iso. Is src.txz
installed under /usr/src or /usr/src/sys
Hello,
When upgrading from FreeBSD 8.2-RELEASE to 9.0-RELEASE using freebsd-update,
I'm asked to merge, what seems like, everything in /etc manually.
And all of the merges are trivial version controls lines.
E.g. my /etc/amd.map (which I never modified) begins with:
# $FreeBSD: releng/8.
Hi
Since a while I notice on some 8.1-RELEASE machines that after a buildkernel
and installkernel, besides the old kernel being moved to /boot/kernel.old,
it also seems to get copied /boot/kernel.old1. I update most servers with
freebsd-update which also update the sources from which the new
On Sun 2011-12-04 11:06:29 UTC+0100, Dick Hoogendijk (d...@nagual.nl) wrote:
> Why do I get a warning if I use freebsd-update about a renewal of my
> FreeBSD installation within the next two months because after that time
> it will nog be supported anymore?
Presumably you mean 8.
On Sun, 04 Dec 2011 11:06:29 +0100
Dick Hoogendijk wrote:
> Why do I get a warning if I use freebsd-update about a renewal of my
> FreeBSD installation within the next two months because after that
> time it will nog be supported anymore?
> I run FreeBSD-release-p4. Freebsd-update &
Op 4-12-2011 13:03, andrew clarke schreef:
From what I understand, the focus is on releasing FreeBSD 9.0, and 8.3
will be released after that. But 9.0 is still in testing. Despite the
message, I suspect security updates for 8.2 will still be issued for
several months after 8.3 is released, to g
Why do I get a warning if I use freebsd-update about a renewal of my
FreeBSD installation within the next two months because after that time
it will nog be supported anymore?
I run FreeBSD-release-p4. Freebsd-update 'sees' p3. Is this
ssage
Subject: re: freebsd-update upgrade -r 9.0-RC2: incorrect hash error
Date: Sun, 20 Nov 2011 20:57:50 +0200
From: Alexander Kapshuk
To: freebsd-questions@freebsd.org
when performing a binary upgrade from 9.0-RC1 to 9.0-RC2 by following
the instructions found here:
101 - 200 of 656 matches
Mail list logo
