After the last major update of www/firefox to version 23 firefox
rejects of moving/swapping the tabs. They are static now. I do not
know whether this has to do with the great pixman update, because
coincidentally I made bot the pixman update and the update of firefox
towards revision 23 slipped
El día Monday, October 14, 2013 a las 08:54:56AM +0200, O. Hartmann escribió:
After the last major update of www/firefox to version 23 firefox
rejects of moving/swapping the tabs. They are static now. I do not
know whether this has to do with the great pixman update, because
coincidentally
On Mon, 14 Oct 2013 09:50:48 +0200
Matthias Apitz g...@unixarea.de wrote:
El día Monday, October 14, 2013 a las 08:54:56AM +0200, O. Hartmann
escribió:
After the last major update of www/firefox to version 23 firefox
rejects of moving/swapping the tabs. They are static now. I do
El día Monday, October 14, 2013 a las 10:23:49AM +0200, O. Hartmann escribió:
I have a 10-CURRENT r255948 from October 1st, with all ports from head
too, rev. r328930.
FF is version 24.0 in the r328930 ports and the tabs can be moved fine
with drag and drop.
HIH
matthias
9-stable and 10-stable.
The pixman update missed some files for me, resolved by using pkg_libchk
(from sysutils/bsdadminscripts) to find the ports that needed rebuilding
and then rebuilding them.
___
freebsd-questions@freebsd.org mailing list
http
. This can happen when the system
is kept up-to-date using freebsd-update and the last SA did not touch
the kernel, or when a new kernel has been installed but the system has
not yet rebooted.
http://svnweb.freebsd.org/base/head/bin/freebsd-version/
By the way, it will be /bin/freebsd-version
and it's
confusing for other sysadmins who aren't intimately familiar with
FreeBSD. Some were updated by freebsd-update, some were updated by src.
But they don't report the same OS version so I get asked why we haven't
updated those servers yet
___
freebsd
that uname -a info is not updated.
If you update the system from p5 to current (p12), and it shows p9 instead p12
the first thing you think is that something on the system update went wrong,
not that everything was fine except the update of the file that uname -a reads.
If release info patch is p12
Mike Brown:
$ grep ^BRANCH /usr/src/sys/conf/newvers.sh
BRANCH=RELEASE-p12
$
then again, I used freebsd-update and not /usr/src, but it makes sense what
you said with kernel, so I guess I _AM_ on the latest -p12 and kernel is on
-p9 as there was no changes after that to kernel.
thank you
Eduardo Morras wrote:
[...] uname -a should give the correct answer. Has uname other utility than
show information about the operating system implementation? No, and it must
be accurate.
That's what I thought, but when I asked about it here last year, I was told
that this is the way things
alexus wrote:
ok, I just did fetch install and got bumped from p5 to p9
# uname -a
FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11
19:47:58 UTC 2012
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
amd64
#
can I take it all the way to -p12?
bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 7.4-RELEASE from update4.freebsd.org...
done.
Fetching metadata index... done.
Inspecting system... done.
The following components of FreeBSD seem
On Mon, 7 Oct 2013 15:22:17 -0400
alexus ale...@gmail.com wrote:
bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12
Is there a way to upgrade 7.4-RELEASE-p5 to 7.4-RELEASE-p12 using
freebsd-update now?
What about:
# freebsd-update fetch
# freebsd-update install
http://www.freebsd.org
On Mon, Oct 7, 2013, at 14:22, alexus wrote:
bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12
Just freebsd-update fetch freebsd-update install is all you should
have to run. The -r flag is for jumping major releases (from 7.x to 8.x,
for example).
I can't comment on whether
, hoping it will
do that)
On Mon, Oct 7, 2013 at 4:16 PM, Mark Felder f...@freebsd.org wrote:
On Mon, Oct 7, 2013, at 14:22, alexus wrote:
bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12
Just freebsd-update fetch freebsd-update install is all you should
have to run. The -r flag
it didn't help..
# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 7.4-RELEASE from update6.freebsd.org...
done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
The following files
On 30/09/2013 06:09, Gary Aitken wrote:
On 09/28/13 10:52, Gary Aitken wrote:
After switching to pkgng, I noticed that my daily run output constantly
complains about the installed packages being corrupt, e.g.:
pkg_info: the package info for package 'asciidoc-8.6.8_1' is corrupt
The problem
On Sun, Sep 29, 2013, at 23:09, Gary Aitken wrote:
Some of the packages reported as corrupt were installed *after* the
conversion to pkgng, so why is pkg_info even noticing them?
The only way this is possible is if they are in the old package format.
Did you happen to convert your packages to
On 09/30/13 07:15, Mathew Seaman wrote:
On 09/28/13 10:52, Gary Aitken wrote:
After switching to pkgng, I
noticed that my daily run output constantly complains about the
installed packages being corrupt, e.g.: pkg_info: the package
info for package 'asciidoc-8.6.8_1' is corrupt
The
On 09/28/13 10:52, Gary Aitken wrote:
After switching to pkgng, I noticed that my daily run output constantly
complains about the installed packages being corrupt, e.g.:
pkg_info: the package info for package 'asciidoc-8.6.8_1' is corrupt
The problem is with
On 09/28/13 10:52, Gary Aitken wrote:
After switching to pkgng, I noticed that my daily run output constantly
complains about the installed packages being corrupt, e.g.:
pkg_info: the package info for package 'asciidoc-8.6.8_1' is corrupt
The problem is with
After switching to pkgng, I noticed that my daily run output constantly
complains about the installed packages being corrupt, e.g.:
pkg_info: the package info for package 'asciidoc-8.6.8_1' is corrupt
The problem is with
etc/periodic/daily/490.status-pkg-changes
which is still using pkg_info
Run pkg_info. If there is anything listed you have not fully converted
to pkgng and have some old broken/corrupt packages. You'll want to clean
this up.
___
freebsd-questions@freebsd.org mailing list
I ran portupgrade last night to upgrade my ports. It upgraded both
openldap24-server and openldap24-client. Now, the server refuses to
start. Upon reboot, I get this message: slapd failed to start. I went
to the rc.d directory and tried to start it manually, but that failed
also.
I do not know
On Sat, 24 Aug 2013 06:05:02 -0400
Carmel articulated:
I ran portupgrade last night to upgrade my ports. It upgraded both
openldap24-server and openldap24-client. Now, the server refuses to
start. Upon reboot, I get this message: slapd failed to start. I
went to the rc.d directory and tried
Update Contact Details
Hello!
You can update your profile by clicking the below link.
[1]Update your profile.
If the above link is not working, copy and paste the below link in your
browser.
[2]http://traders.maillist-manage.com/up.zc?od
Does anyone know how a workaround for having to rm -rf /usr/src every
time the source URL changes? I'm updating from 8.3 to 8.4 with
subversion and got a message along the lines of Error: /usr/src/
contains files from a different URL. -David
___
On 05/08/2013 09:00, David Noel wrote:
Does anyone know how a workaround for having to rm -rf /usr/src every
time the source URL changes? I'm updating from 8.3 to 8.4 with
subversion and got a message along the lines of Error: /usr/src/
contains files from a different URL. -David
You need
Ok great, thanks Matthew. I tried a different search query and
actually found a similar question on the forums:
http://forums.freebsd.org/showthread.php?t=35014
Your solution looks a bit cleaner than the one proposed there: rm -r
/usr/src/.svn, and then check out the new branch.
I'll check out
On Mon, 5 Aug 2013, David Noel wrote:
Ok great, thanks Matthew. I tried a different search query and
actually found a similar question on the forums:
http://forums.freebsd.org/showthread.php?t=35014
That is an outdated thread. Ignore it.
Your solution looks a bit cleaner than the one
On 05/08/2013 14:22, Warren Block wrote:
Your solution looks a bit cleaner than the one proposed there: rm -r
/usr/src/.svn, and then check out the new branch.
I'll check out the man for svn switch.
The new form is just 'svn relocate':
Thanks, guys!
On 8/5/13, Matthew Seaman matt...@freebsd.org wrote:
On 05/08/2013 14:22, Warren Block wrote:
Your solution looks a bit cleaner than the one proposed there: rm -r
/usr/src/.svn, and then check out the new branch.
I'll check out the man for svn switch.
The new form is just
On 8/5/13, David Noel david.i.n...@gmail.com wrote:
Thanks, guys!
On 8/5/13, Matthew Seaman matt...@freebsd.org wrote:
On 05/08/2013 14:22, Warren Block wrote:
Your solution looks a bit cleaner than the one proposed there: rm -r
/usr/src/.svn, and then check out the new branch.
I'll check
On Mon, Aug 5, 2013, at 10:16, David Noel wrote:
Ooops. Top-posted. I always forget. Does anyone know how to change the
default reply behavior of gmail? Last I searched the only way to do
it was with a greasemonkey script...
Google still hasn't figure out how to bottom post. Can you imagine
On Mon, Aug 05, 2013 at 10:16:43AM -0500, David Noel wrote:
Ooops. Top-posted. I always forget. Does anyone know how to change the
default reply behavior of gmail? Last I searched the only way to do
it was with a greasemonkey script...
You can try using Gmail with a MUA, like mutt or
Update Contact Details
Hello!
You can update your profile by clicking the below link.
[1]Update your profile.
If the above link is not working, copy and paste the below link in your
browser.
[2]http://traders.maillist-manage.com/up.zc?od
Help! I just used freebsd-update to upgrade a system to FreeBSD
9.1-RELEASE-p5 to close the latest security holes. I then rebuilt
my custom kernel and tried to reboot. I'm now getting the message
Can't work out which disk we are booting from.
Guessed BIOS device 0x not found by probes
Hi all,
The vBSDcon website has been updated with a full speaker line-up and
schedule for the BSD-related conference October 25 - 27, 2013. Check
it out at http://www.vbsdcon.com/. Registrations will begin in the
coming weeks.
--
Take care
Rick Miller
Hi all,
For those interested in vBSDcon, a BSD-related conference scheduled
for October 2013 in the Washington DC area, the web site has been
updated to include a detailed schedule and speaker line-up including
descriptions of their presentations. Registrations will begin in the
coming month.
Update Contact Details
Hello!
You can update your profile by clicking the below link.
[1]Update your profile.
If the above link is not working, copy and paste the below link in your
browser.
[2]http://traders.maillist-manage.com/up.zc?od
The site seems down from here (AS58054).
2013/7/22 Rick Miller vmil...@hostileadmin.com
Hi all,
For those interested in vBSDcon, a BSD-related conference scheduled
for October 2013 in the Washington DC area, the web site has been
updated to include a detailed schedule and speaker line-up
I just checked it out. Seems to be up for me...
On Monday, July 22, 2013, Виталий Туровец wrote:
The site seems down from here (AS58054).
2013/7/22 Rick Miller vmil...@hostileadmin.com javascript:_e({},
'cvml', 'vmil...@hostileadmin.com');
Hi all,
For those interested in vBSDcon, a
It's down for me too.
Also down according to: http://isup.me/vbsdcon.com
...Fish
Понедельник, 22 июля 2013, 18:37 -04:00 от Rick Miller
vmil...@hostileadmin.com:
I just checked it out. Seems to be up for me...
On Monday, July 22, 2013, Виталий Туровец wrote:
The site seems down from
Weird, now it's up.
...Fish
Вторник, 23 июля 2013, 2:52 +04:00 от Fish Kungfu fish.kun...@mail.ru:
It's down for me too.
Also down according to: http://isup.me/vbsdcon.com
...Fish
Понедельник, 22 июля 2013, 18:37 -04:00 от Rick Miller
vmil...@hostileadmin.com :
I just checked it out.
Fish Kungfu wrote:
Weird, now it's up.
...Fish
DNS takes time to propagate
-Mike
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
Hi all,
A small followup:
Looks like freebsd-update does try to rebuild the password database but does
not quite succeed, leaving binary files in somewhat corrupted state, this
leading to some problems when trying to add new users later. This is
discussed here:
http://www.freebsd.org/cgi
Hi all,
In case anybody was following this discussion, I have successfully upgraded
the system from 8.2 to 8.4 using freebsd-update. The process did have some
glitches (in retrospect, minor ones) but mostly they were not related to
freebsd-update (like some issues with gmirror and firewall
Is it possible to skip point releases using freebsd-update so that I
can go from 8.0 to 8.4, or do I need to go 8.0 - 8.1 - 8.2 - 8.3 -
8.4?
Patrick
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
On Thu, Jun 27, 2013 at 8:05 PM, Patrick gibblert...@gmail.com wrote:
Is it possible to skip point releases using freebsd-update so that I
can go from 8.0 to 8.4
Yes. http://www.freebsd.org/releases/8.4R/relnotes-detailed.html#upgrade
--
Adam Vande More
I wrote:
The main problem this time is that I'm not so lucky with the password files,
because for 8.4, freebsd-update has fetched new, stock .db files to put in
/etc.
Whoa, sorry, I misspoke here.
freebsd-update asked me, after the merges, to approve unspecified differences
in pwd.db
Hello, Tim.
You wrote 26 июня 2013 г., 3:26:24:
TD It seems that svn 1.8 does not like symlinks. I have this:
TD /usr/src - /usr1/src-9-STABLE
TD I can do this fine:
TDsvn update /usr1/src-9-STABLE
TD But this causes svn to dump core:
TDsvn update /usr/src
TD At which point I have
On Wed, Jun 26, 2013, at 2:07, Mike Brown wrote:
Next step, I think, is reboot, before another 'freebsd-update install'
run.
I'm worried something is still amiss, though, so I'm holding off for now.
:(
When in doubt: fetch source, build, install, and use mergemaster. Then
reboot. Better
Fetching 1 metadata files... 70.5%
done.
70.5%
70.5%
74.2%
74.2%
81.7%
81.7%
70.5%
I think this is a result of having -v in my GZIP environment variable.
I always forget about my GZIP and BZIP2 variables. I should've known.
So, never mind about that.
I'm using freebsd-update to upgrade my system to the latest minor version
(from 8.3-RELEASE to 8.4-RELEASE).
I'm surprised that the merge handling system isn't more robust. When
upgrading
the old way, from source, I was used to using mergemaster to handle any
merges that couldn't
On Tue, Jun 25, 2013, at 3:14, Mike Brown wrote:
Well, thanks for reading this far. I'm scared to death to reboot now,
since my
server is in another city, but we'll see how it goes.
I always avoid freebsd-update when moving between releases simply
because of this atrocity.
If it requires
Hi all,
I do not quite understand. Is the freebsd-update upgrade process completely
broken? Or is it some special mode? Or was it broken recently?
Because some time ago I have upgraded from 8.1 to 8.2 quite nicely, with
editor-based merging of config files, and was planning to upgrade to 8.4
On Tue, Jun 25, 2013, at 15:29, Eugene wrote:
Hi all,
I do not quite understand. Is the freebsd-update upgrade process
completely
broken? Or is it some special mode? Or was it broken recently?
Because some time ago I have upgraded from 8.1 to 8.2 quite nicely, with
editor-based merging
On 06/24/2013 04:58 PM, Tim Daneliuk wrote:
On 06/24/2013 03:20 PM, Matthew Seaman wrote:
On 24/06/2013 20:28, Tim Daneliuk wrote:
After the update to svn 1.8, I did a new svn co of the FBSD 9-STABLE
source branch. When I try to do an update to it, I see this now:
svn: E155005: Working
On Tue, Jun 25, 2013, at 15:29, Eugene wrote:
I do not quite understand. Is the freebsd-update upgrade process
completely broken?
IMHO it is partially broken; I'm not doing anything special. How broken it is
depends on what's getting changed. Most of what the system is designed to do
After the update to svn 1.8, I did a new svn co of the FBSD 9-STABLE
source branch. When I try to do an update to it, I see this now:
svn: E155005: Working copy not locked at /usr/scr
svn co svn://svn.freebsd.org/base/stable/9 /usr/src
/usr/src is a symlink to another directory
On 24/06/2013 20:28, Tim Daneliuk wrote:
After the update to svn 1.8, I did a new svn co of the FBSD 9-STABLE
source branch. When I try to do an update to it, I see this now:
svn: E155005: Working copy not locked at /usr/scr
svn co svn://svn.freebsd.org/base/stable/9 /usr/src
/usr
On 06/24/2013 03:20 PM, Matthew Seaman wrote:
On 24/06/2013 20:28, Tim Daneliuk wrote:
After the update to svn 1.8, I did a new svn co of the FBSD 9-STABLE
source branch. When I try to do an update to it, I see this now:
svn: E155005: Working copy not locked at /usr/scr
svn co svn
I'm using freebsd-update to upgrade my system to the latest minor release.
At a couple points in the process, I get weird status indicators (percentages)
showing me that something is happening:
Fetching 1 metadata files... 70.5%
done.
70.5%
70.5%
74.2%
74.2%
81.7%
81.7%
70.5
I'm using freebsd-update to upgrade my system to the latest minor version
(from 8.3-RELEASE to 8.4-RELEASE).
I'm surprised that the merge handling system isn't more robust. When upgrading
the old way, from source, I was used to using mergemaster to handle any
merges that couldn't be done
Hi! Is it possible to upgrade git without installing an entire Docbook
toolchain? The computer in question is a server, which nobody uses as their
primary computer, so if there's a way to just disable all documentation, that
would also be fine.
Thanks,
Ricky
The information in this e-mail is
Installed pkg-devel 1.1.0.b3 and get the following message about incremental
update whenever update is called.
sudo pkg update
Updating repository catalogue
pkg: incremental update is not possible as repo format is inappropriate, trying
full upgrade
packagesite repository catalogue is up-to-date
I am working on a FBSD 9.1-STABLE mail machine that's been working
fine. After upgrading to MailScanner 4.84.5_3, we are now
suddenly seeing like this:
Clamd::ERROR:: UNKNOWN CLAMD RETURN ./lstat() failed: Permission denied.
ERROR :: /var/spool/MailScanner/incoming/68340
Any ideas what
Hi Tim,
Double check what user clamd is run as, and what permissions your mail
spool have. Somewhere along the line your mail spool locked out clamd
The lstat system call's man page says
`execute (search) permission is required on all of the
directories in path that lead to the file.`
Also,
Hi,
I am trying to figure out how to change / update the dependencies on a package.
I have a postfix package which comes from a server where mysql-client is in
version 5.1
And I would like to install the same package on a server where mysql-client is
in version 5.6
I am not sure
On 31/05/2013 16:26, b...@todoo.biz wrote:
Hi,
I am trying to figure out how to change / update the dependencies on a
package.
I have a postfix package which comes from a server where mysql-client is in
version 5.1
And I would like to install the same package on a server where mysql
On May 23, 2013, at 11:09 AM, Michael Sierchio ku...@tenebras.com wrote:
On Thu, May 23, 2013 at 5:33 AM, Warren Block wbl...@wonkity.com wrote:
..
One thing mentioned earlier is that ZFS wants lots of memory. 4G-8G
minimum, some might say as much as the server will hold.
Not
soft update or migrate
from UFS to ZFS?
i heard so much about soft update -that is added in freebsd9.1- which can
fix file corruption in acceptable way with low cost but i don't know how
much is reliable and efficient.
in the other hand, i think migration from UFS to ZFS can be another
solution
is:
is it better to upgrade my freebsd to 9.1 and use soft update or migrate
from UFS to ZFS?
That's a judgement call, which means it depends.
i heard so much about soft update -that is added in freebsd9.1- which can
fix file corruption in acceptable way with low cost but i don't know how
much
is more suitable for my server. using
soft-update or ZFS. please help me to select the best one.
thank you so much
On Thu, May 23, 2013 at 4:28 PM, Warren Block wbl...@wonkity.com wrote:
On Thu, 23 May 2013, saeedeh motlagh wrote:
hello every body
i have a question about fixing file corruption
also invest in a decent UPS.
i do not have any problem in RAM and hardware.
i don't know which approach is more suitable for my server. using
soft-update or ZFS. please help me to select the best one.
thank you so much
On Thu, May 23, 2013 at 4:28 PM, Warren Block wbl...@wonkity.com wrote
.
The lack of a UPS can be considered a hardware problem.
i don't know which approach is more suitable for my server. using soft-update
or ZFS. please help me to select the best one.
Please don't top-post, as it makes responding to your message more
difficult. One thing mentioned earlier is that ZFS
On Thu, May 23, 2013 at 5:33 AM, Warren Block wbl...@wonkity.com wrote:
..
One thing mentioned earlier is that ZFS wants lots of memory. 4G-8G
minimum, some might say as much as the server will hold.
Not necessarily so - deduplication places great demands on memory, but that
can be
into it.
i do not have any problem in RAM and hardware.
i don't know which approach is more suitable for my server. using
soft-update or ZFS. please help me to select the best one.
If power failure is an issue, you have no guarantee of data loss
protection unless you use networked storage
Hi,
since last freebsd-update fetch install I always get this message after
freebsd-update fetch:
The following files will be updated as part of updating to 9.1-RELEASE-p3:
/boot/kernel/linker.hints
but freebsd-update install doesn't install anything.
Is there something wrong with my system
On Mon, May 13, 2013 at 11:22:41AM +0200, Wolfgang Riegler wrote:
Hi,
since last freebsd-update fetch install I always get this message after
freebsd-update fetch:
The following files will be updated as part of updating to 9.1-RELEASE-p3:
/boot/kernel/linker.hints
but freebsd-update
I had an 8.2 system that I wanted to take to 8.4. First I tried upgrade to 8.4,
getting (in essence) can't do that. So I upgraded 8.2 which worked giving the
end-of-life warning. But seemed work. I then did an upgrade to 8.3 with:
freebsd-update -r 8.3-RELEASE upgrade
The first part
I was just wondering if anyone had updated from apache22 to apache24.
Specifically, are there any problems to be overcome? Does the existing
httpd.conf file work with the apache24 branch.
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the
On 03/05/2013 15:47, Jerry wrote:
I was just wondering if anyone had updated from apache22 to apache24.
Specifically, are there any problems to be overcome? Does the existing
httpd.conf file work with the apache24 branch.
httpd.conf might or might not work -- there are some incompatible
On May 3, 2013, at 10:47 AM, Jerry je...@seibercom.net wrote:
I was just wondering if anyone had updated from apache22 to apache24.
Specifically, are there any problems to be overcome? Does the existing
httpd.conf file work with the apache24 branch.
There are some changes.
I was not
The Apache site has documentation on upgrading from 2.2 to 2.4 --
http://httpd.apache.org/docs/2.4/upgrading.html
The main change for me was the new allow/deny syntax.
I've updated almost all of my Apache installs from 2.2 to 2.4 with no
issues. The only installs I haven't updated yet are
Ryan Frederick writes:
The Apache site has documentation on upgrading from 2.2 to 2.4 --
http://httpd.apache.org/docs/2.4/upgrading.html
The main change for me was the new allow/deny syntax.
I've updated almost all of my Apache installs from 2.2 to 2.4 with no
issues.
On Tue, Apr 30, 2013 at 04:37:52PM -0500, Ryan Frederick wrote:
I have a number of boxes running 9.1-RELEASE (amd64) that I updated to
p3 yesterday via freebsd-update. However freebsd-update still indicates
that linker.hints needs to be updated. Running `freebsd-update install`
appears
On 01/05/2013 11:06, Stephan Schindel wrote:
On Tue, Apr 30, 2013 at 04:37:52PM -0500, Ryan Frederick wrote:
I have a number of boxes running 9.1-RELEASE (amd64) that I updated to
p3 yesterday via freebsd-update. However freebsd-update still indicates
that linker.hints needs to be updated
On Wed, May 1, 2013 at 1:01 PM, Paul Macdonald p...@ifdnrg.com wrote:
On 01/05/2013 11:06, Stephan Schindel wrote:
On Tue, Apr 30, 2013 at 04:37:52PM -0500, Ryan Frederick wrote:
I have a number of boxes running 9.1-RELEASE (amd64) that I updated to
p3 yesterday via freebsd-update. However
I have a number of boxes running 9.1-RELEASE (amd64) that I updated to
p3 yesterday via freebsd-update. However freebsd-update still indicates
that linker.hints needs to be updated. Running `freebsd-update install`
appears to install a new linker.hints file but still doesn't appear to
satisfy
On Thu, 25 Apr 2013, Steve O'Hara-Smith wrote:
The problem under discussion is that the kernel version does not
change when a freebsd-update update does not include a kernel change.
Perhaps we could adopt the Linux practice of placing the release
information in /etc/issue
On Thu, 25 Apr 2013 07:37:01 -0400 (EDT), Daniel Feenberg wrote:
On Thu, 25 Apr 2013, Steve O'Hara-Smith wrote:
The problem under discussion is that the kernel version does not
change when a freebsd-update update does not include a kernel change.
Perhaps we could adopt
On Thu, 25 Apr 2013, Polytropon wrote:
On Thu, 25 Apr 2013 07:37:01 -0400 (EDT), Daniel Feenberg wrote:
On Thu, 25 Apr 2013, Steve O'Hara-Smith wrote:
The problem under discussion is that the kernel version does not
change when a freebsd-update update does not include a kernel
On Thu, 25 Apr 2013 11:14:06 -0400 (EDT), Daniel Feenberg wrote:
This is written as though it applies to FreeBSD, but I was
under the impression that FreeBSD didn't do anything with
/etc/issue.
It actually works quite well, I'm using it for decades. :-)
You just need to add the item
When I issue 'freebsd-update fetch install I see this:
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RELEASE from update5.freebsd.org...
done.
Fetching metadata index... done.
Inspecting system... done
On Wed, 24 Apr 2013 16:00:47 + (UTC), Walter Hurry wrote:
When I issue 'freebsd-update fetch install I see this:
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RELEASE from update5.freebsd.org...
done
On Wed, 24 Apr 2013 18:05:04 +0200, Polytropon wrote:
The kernel's version message will only change if the _kernel_ has been
receiving changes. So, for example, if you update from 9.1 to 9.1-p2,
and _no_ change has been written to the kernel, it will still report
9.1, even though the updates
On Wednesday, April 24, 2013, Walter Hurry wrote:
On Wed, 24 Apr 2013 18:05:04 +0200, Polytropon wrote:
The kernel's version message will only change if the _kernel_ has been
receiving changes. So, for example, if you update from 9.1 to 9.1-p2,
and _no_ change has been written
On Wed, 24 Apr 2013 16:00:47 + (UTC)
Walter Hurry walterhu...@gmail.com wrote:
When I issue 'freebsd-update fetch install I see this:
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RELEASE from update5
On Wed, 24 Apr 2013 14:34:30 -0500, Steve O'Hara-Smith st...@sohara.org
wrote:
You have updated to 9.1-RELEASE-p2 - but since there have been no
kernel changes since 9.1-RELEASE the kernel version message hasn't
changed.
This could very reasonably be regarded as bug in the update/version
1 - 100 of 2364 matches
Mail list logo
