On 05/20/2011 03:58 AM, Chris Brennan wrote:
On Thu, May 19, 2011 at 5:04 PM, Polytropon free...@edvax.de wrote:
Yes, the recommended order. :-)
One last question ... hopefully lol. am I going to run into any issues w/
the default fbsd6 layout?
[root@Ziggy [~]# df -h
Filesystem Size
On Thu, 19 May 2011 21:58:13 -0400, Chris Brennan xa...@xaerolimit.net wrote:
One last question ... hopefully lol. am I going to run into any issues w/
the default fbsd6 layout?
[root@Ziggy [~]# df -h
Filesystem SizeUsed Avail Capacity Mounted on
/dev/ad0s1a496M328M
On Fri, May 20, 2011 at 10:18 AM, Polytropon free...@edvax.de wrote:
On Thu, 19 May 2011 21:58:13 -0400, Chris Brennan xa...@xaerolimit.net
wrote:
One last question ... hopefully lol. am I going to run into any issues w/
the default fbsd6 layout?
[root@Ziggy [~]# df -h
Filesystem
On Fri, 20 May 2011 12:09:43 +0200, Bas Smeelen b.smee...@ose.nl wrote:
It can fit, however don't build the kernel with debug symbols and move or
remove the current debug symbol files of your kernel.
See below, our development box. It has GENERIC with debug symbol files, a
kernel.old and a
On Fri, 20 May 2011 10:26:01 -0400, Chris Brennan xa...@xaerolimit.net wrote:
OK, I am off now to research how to build the kernel w/o debugging symbols
... then I shall embark on this.
It should be makeoptions DEBUG=-g _NOT_ being present
in the config file. Another idea would be to omit the
On Fri, May 20, 2011 at 11:23 AM, Polytropon free...@edvax.de wrote:
On Fri, 20 May 2011 10:26:01 -0400, Chris Brennan xa...@xaerolimit.net
wrote:
OK, I am off now to research how to build the kernel w/o debugging
symbols
... then I shall embark on this.
It should be makeoptions DEBUG=-g
On Fri, 20 May 2011 11:36:37 -0400, Chris Brennan xa...@xaerolimit.net wrote:
I will modify my kernel config to reflect that change and I was going to
make a backup ... I'm using the same config from 7.x, only slightly modified
to reflect this machine, that said, how do I clobber the current
On Fri, 20 May 2011, Polytropon wrote:
However, I think increasing the default size to 1GB for /
would be a nice addition for the next release
That was recently implemented, maybe even for 8.2. It was in there the
last time I ran sysinstall, anyway. 8-)
On Wed, May 4, 2011 at 6:11 PM, Jerry je...@seibercom.net wrote:
Yes, from the man pages it states it will rebuild all packages and their
dependencies. I simply include the l so he would have a log file
available if something did go wrong.
In any case, I thought it might save him some trouble
On Thu, 19 May 2011 16:29:41 -0400, Chris Brennan xa...@xaerolimit.net wrote:
If I go the way of pkg_delete -fravd, will it save configs in
/usr/local/etc/ ? I just need to know if I need to take the extra step to
archive that directory beforehand or not
I would advice to do so, no matter
On Thu, May 19, 2011 at 4:40 PM, Polytropon free...@edvax.de wrote:
I would advice to do so, no matter what the pkg_delete
command will cause. If I remember correctly, MODYFIED
files will not be touched (checksum test), and a directory
won't be removed if it contains something that won't
be
On Thu, 19 May 2011 16:47:26 -0400, Chris Brennan xa...@xaerolimit.net wrote:
After much thought, I think my process would be this:
chsh back to bin/sh (I currently use bash as my primary shell)
logout back in for shell change
pkg_delete -fravd
get new base srcs
portsnap
(re)install
On Thu, May 19, 2011 at 5:04 PM, Polytropon free...@edvax.de wrote:
Yes, the recommended order. :-)
First, update your ports/ and src/ trees (e. g. using portsnap
and csup), then compile and install. You don't need any tools
provided by ports for this task. After you've started your
new
On Wed 2011-05-04 12:50:05 UTC-0400, Chris Brennan (xa...@xaerolimit.net) wrote:
I have an old PIII running FreeBSD7.3 currently, ports is all kinds of
screwed up, when I did my first cross-version upgrade from 6.x to 7.x, I
didn't know I had to rebuild ports, I subsequently upgrades though
On Wed, 4 May 2011 12:50:05 -0400
Chris Brennan xa...@xaerolimit.net articulated:
I have an old PIII running FreeBSD7.3 currently, ports is all kinds of
screwed up, when I did my first cross-version upgrade from 6.x to
7.x, I didn't know I had to rebuild ports, I subsequently upgrades
though
On 4 May 2011 12:50, Chris Brennan xa...@xaerolimit.net wrote:
is it safe to nuke /usr/local (excluding /usr/local/home), rebuild
world/kernel for 8.2 and start with a fresh ports tree?
Yes, though pkg_delete -af will probably suffice for removing
the ports ( /var/db/pkg/ as well).
--
--
On Wed, May 4, 2011 at 2:26 PM, Jerry je...@seibercom.net wrote:
Chris, when I have had to do major rebuilds, I have found
portmanager to be the best tool. It just seems to work. In any case,
if it were me, I would clean out the /usr/ports/distfiles directory,
update your ports tree, and then
On Wed, May 4, 2011 at 2:40 PM, ill...@gmail.com ill...@gmail.com wrote:
On 4 May 2011 12:50, Chris Brennan xa...@xaerolimit.net wrote:
is it safe to nuke /usr/local (excluding /usr/local/home), rebuild
world/kernel for 8.2 and start with a fresh ports tree?
Yes, though pkg_delete -af
On 4 May 2011 15:54, Chris Brennan xa...@xaerolimit.net wrote:
On Wed, May 4, 2011 at 2:40 PM, ill...@gmail.com ill...@gmail.com wrote:
On 4 May 2011 12:50, Chris Brennan xa...@xaerolimit.net wrote:
is it safe to nuke /usr/local (excluding /usr/local/home), rebuild
world/kernel for 8.2
On 04/05/2011 20:53, Chris Brennan wrote:
On Wed, May 4, 2011 at 2:26 PM, Jerryje...@seibercom.net wrote:
Chris, when I have had to do major rebuilds, I have found
portmanager to be the best tool. It just seems to work. In any case,
if it were me, I would clean out the /usr/ports/distfiles
On Wed, 04 May 2011 22:51:05 +0100
Chris Whitehouse cwhi...@onetel.com articulated:
I second Jerry, portmanager is indeed a very effective tool, it's
simple and thorough and probably has as good a chance of fixing ports
issues as anything. Or used to, I've been trying out tinderbox so
haven't
* Matthew Seaman schrieb:
Alex Huth wrote:
Yes. If you want to track one of the development branches (HEAD, RELENG_N)
then you have to update sources by csup(1) or various other mechanisms and
then compile your kernel+world yourself.
Alternatively you can track release branches
2009/12/8 Alex Huth a.h...@tmr.net:
* Matthew Seaman schrieb:
Alex Huth wrote:
Yes. If you want to track one of the development branches (HEAD, RELENG_N)
then you have to update sources by csup(1) or various other mechanisms and
then compile your kernel+world yourself.
Alternatively you
Hello!
Maybe i haven't understand the process of updating not really. I thought when
i use Releng_6 in the stable_supfile i get the latest version of 6.x = 6.4.
But after the process of make buildworld and so on, it is still 6.3. Do i have
to use Releng_6_4 even when i do not get the patches
Alex Huth wrote:
Hello!
Maybe i haven't understand the process of updating not really. I thought when
i use Releng_6 in the stable_supfile i get the latest version of 6.x = 6.4.
But after the process of make buildworld and so on, it is still 6.3. Do i have
to use Releng_6_4 even when i do
* Matthew Seaman schrieb:
Next question is if i don't get updates with freebsd-update when i have
a stable version? I have the problem with two machines (6.3 and 6.4). On
both
i do not get the public key because it is not available on the remote
server.
I have test it with debug.
Alex Huth wrote:
* Matthew Seaman schrieb:
Next question is if i don't get updates with freebsd-update when i have
a stable version? I have the problem with two machines (6.3 and 6.4). On
both
i do not get the public key because it is not available on the remote
server.
I have test it
Hi,
I think this Q is pretty basic, but I just want to make sure. I was
considering if upgrading from 6.3 to 7.0 and something goes wrong, and
I need to do a fresh install. Can I only change/overwrite the /etc
/usr, etc but leave /home intact?? thank you!!
yeah, I understand. backup is crucial. But I have 90% full in a 200G
drive, so it's a pain in the rear end. But I wonder if I can choose
what contents (or directories) to be installed so I can keep the rest
intact. just a thought
On Wed, Mar 5, 2008 at 9:09 AM, Chris [EMAIL PROTECTED]
On Wed, 5 Mar 2008 09:14:14 -0500
Tsu-Fan Cheng [EMAIL PROTECTED] wrote:
yeah, I understand. backup is crucial. But I have 90% full in a 200G
drive, so it's a pain in the rear end. But I wonder if I can choose
what contents (or directories) to be installed so I can keep the rest
intact. just
On Wed, 5 Mar 2008 08:59:45 -0500
Tsu-Fan Cheng [EMAIL PROTECTED] wrote:
Hi,
I think this Q is pretty basic, but I just want to make sure. I was
considering if upgrading from 6.3 to 7.0 and something goes wrong, and
I need to do a fresh install. Can I only change/overwrite the /etc
/usr,
On Wednesday 05 March 2008 14:59:45 Tsu-Fan Cheng wrote:
I think this Q is pretty basic, but I just want to make sure. I was
considering if upgrading from 6.3 to 7.0 and something goes wrong, and
I need to do a fresh install. Can I only change/overwrite the /etc
/usr, etc but leave /home
um... dont remember exactly.. but it mounts 2 other HD drives, and the
usual, such as / (root), procs (perhaps?), /home swap, .. why??
On Wed, Mar 5, 2008 at 9:36 AM, Mel [EMAIL PROTECTED] wrote:
On Wednesday 05 March 2008 14:59:45 Tsu-Fan Cheng wrote:
I think this Q is pretty basic,
On Wednesday 05 March 2008 17:13:50 Tsu-Fan Cheng wrote:
On Wed, Mar 5, 2008 at 9:36 AM, Mel [EMAIL PROTECTED]
wrote:
On Wednesday 05 March 2008 14:59:45 Tsu-Fan Cheng wrote:
I think this Q is pretty basic, but I just want to make sure. I was
considering if upgrading from 6.3 to 7.0
Tsu-Fan Cheng wrote:
Can I only change/overwrite the /etc
/usr, etc but leave /home intact??
Depends. If your /home is a seperate partition AND you don't need to
repartition (relabel) the disk, you should be ok. In disklabel, you'll find
a newfs toggle. If you set this to N for a certain
I am currently running:
FreeBSD 6.1-RELEASE-p20 #2
After reading the docs, it appears the procedure to upgrade from 6.1 to
6.2 is the following:
1) Change: default release=cvs tag=RELENG_6_1 to tag=RELENG_6_2
in /usr/local/etc/cvsup/cvsupfile
2) run cvsup /usr/local/etc/cvsup/cvsupfile to
On Mon, Nov 26, 2007 at 11:20:39AM +, Bob Richards wrote:
I am currently running:
FreeBSD 6.1-RELEASE-p20 #2
After reading the docs, it appears the procedure to upgrade from 6.1 to
6.2 is the following:
1) Change: default release=cvs tag=RELENG_6_1 to tag=RELENG_6_2
in
On Mon, 26 Nov 2007 11:28:44 +
Daniel Bye [EMAIL PROTECTED] wrote:
Yes. You might prefer to wait a little while longer, and go straight
to 6.3, which is on its way soon.
Indeed. Thanks for the heads up. Guess I better subscribe to
freebsd-announce!
What sort of kick-started this was the
On November 26, 2007 at 06:20AM Bob Richards wrote:
[ snip ]
I do NOT need to portupgrade -a since this is a minor version upgrade
right?
I think you are confusing '-a' with '-f'. The former updates all out of date
files. The latter forces the rebuilding of a port. I have never tried it;
Graham Bentley wrote:
You've confused STABLE with RELEASE. 6.2 has not reached RELEASE.
6-STABLE is the latest these changes worked fine in CURRENT (right
now, aka 7) and have been MFCed (merged from current) so that more
people can try them out, which right now corresponds to the version
On Tuesday November 21, 2006 at 09:08:42 (PM) [EMAIL PROTECTED] wrote:
RELENG_6 for whatever 6-STABLE is (6.2 right now but will soon
enough be moving on towards 6.3.).
I wasn't aware that 6.2 had been released as 'STABLE' yet.
--
Gerard
Mail from '@gmail' is rejected and/or discarded
Gerard Seibert wrote:
On Tuesday November 21, 2006 at 09:08:42 (PM) [EMAIL PROTECTED] wrote:
RELENG_6 for whatever 6-STABLE is (6.2 right now but will soon
enough be moving on towards 6.3.).
I wasn't aware that 6.2 had been released as 'STABLE' yet.
Short version: No, the OP
On Wed, Nov 22, 2006 at 01:34:23AM +, Robert Davison wrote:
If my cvs-upfile reads, and specfically im looking at the default release
line
*default release=cvs delete use-rel-suffix compress
*default delete use-rel-suffix
src-all
ports-all tag=.
doc-all tag=.
You've confused STABLE with RELEASE. 6.2 has not reached RELEASE.
6-STABLE is the latest these changes worked fine in CURRENT (right now,
aka 7) and have been MFCed (merged from current) so that more people can
try them out, which right now corresponds to the version of FreeBSDthat
is just
On Wed, Nov 22, 2006 at 09:05:13PM -, Graham Bentley wrote:
You've confused STABLE with RELEASE. 6.2 has not reached RELEASE.
6-STABLE is the latest these changes worked fine in CURRENT (right now,
aka 7) and have been MFCed (merged from current) so that more people can
try them out,
If my cvs-upfile reads, and specfically im looking at the default release
line
*default release=cvs delete use-rel-suffix compress
*default delete use-rel-suffix
src-all
ports-all tag=.
doc-all tag=.
Can anyone tell me what release and branch of FreeBSD im tracking. its a 6.1
On 11/21/06, Robert Davison [EMAIL PROTECTED] wrote:
If my cvs-upfile reads, and specfically im looking at the default release
line
*default release=cvs delete use-rel-suffix compress
*default delete use-rel-suffix
src-all
ports-all tag=.
doc-all tag=.
Can anyone tell me what
Boris Samorodov wrote:
Can anyon tell me why this port is marked ignore? Has it been superseeded?
You may consider reading /usr/ports/UPDATING.
BTW, it's the right file to read from time to time and especially if
you have questions about the port system. ;-)
The info you are searching
On Tue, 05 Sep 2006 05:56:03 -0400 Gerard Seibert wrote:
Boris Samorodov wrote:
Can anyon tell me why this port is marked ignore? Has it been superseeded?
You may consider reading /usr/ports/UPDATING.
BTW, it's the right file to read from time to time and especially if
you have
Boris Samorodov wrote:
Personally, why a new source was not created so that anyone downloading
Which type of source are you speaking of?
When a new, or not, user downloads an image file for FBSD, he/she is
getting an image file with this obsoleted version. They must then use
'portupgrade'
I'm trying to upgrade a machine, which was built only about 2 weeks agao.
portmanager reprts the following:
portmanager 0.4.1_6
FreeBSD brown.fas.com 6.1-STABLE FreeBSD 6.1-STABLE #11: Sun Sep 3
13:33:28 EDT 2006
[EMAIL
On 04/09/06, stan [EMAIL PROTECTED] wrote:
I'm trying to upgrade a machine, which was built only about 2 weeks agao.
portmanager reprts the following:
portmanager 0.4.1_6
FreeBSD brown.fas.com 6.1-STABLE FreeBSD 6.1-STABLE
On Mon, 4 Sep 2006 17:44:43 -0400 stan wrote:
I'm trying to upgrade a machine, which was built only about 2 weeks agao.
Seems that either you didn't upgrade the portstree or installed a
deprecated linux_base port by hands.
linux_base-8-8.0_16 /emulators/linux_base-8
On 6/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I'm a newbie running 6.1 stable and I have what may be several
simple questions: What exactly is happening when I run make index
make readmes after I upgrade my ports tree? Why aren't the
indexes and readmes made when we run cvsup ports
I'm a newbie running 6.1 stable and I have what may be several simple
questions: What exactly is happening when I run make index make readmes
after I upgrade my ports tree? Why aren't the indexes and readmes made when we
run cvsup ports-supfile? Finally, why does it take so long to make what
On 6/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I'm a newbie running 6.1 stable and I have what may be several simple questions: What exactly is
happening when I run make index make readmes after I upgrade my ports
tree? Why aren't the indexes and readmes made when we run cvsup
On 6/10/06, Nikolas Britton [EMAIL PROTECTED] wrote:
On 6/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I'm a newbie running 6.1 stable and I have what may be several simple questions: What exactly
is happening when I run make index make readmes after I upgrade my ports
tree? Why aren't
Is there a way to force a rebuild with new dependencies when you get
errors like:
**
OLD ethereal-0.10.11_1 built with old dependency net-snmp-5.2.1_2,
current dependency is net-snmp-5.2.1.2
OLD gtk-2.6.8 built with old dependency libxml2-2.6.19, current
dependency is libxml2-2.6.20
OLD
On 14/07/05, Bart Silverstrim [EMAIL PROTECTED] wrote:
Is there a way to force a rebuild with new dependencies when you get
errors like:
**
OLD ethereal-0.10.11_1 built with old dependency net-snmp-5.2.1_2,
current dependency is net-snmp-5.2.1.2
OLD gtk-2.6.8 built with old dependency
On Tue, Nov 02, 2004 at 07:38:34AM +1300, Jonathan Chen wrote:
On Mon, Nov 01, 2004 at 06:25:54AM -0900, Andy Firman wrote:
[...]
The new IP address has been registered with the registar
and all is well on the new box.
The old box still has a bunch of sites on it that I am in
the
Hi,
I have an old FreeBSD 4.10 stable box that is running the
default Bind 8 and was the primary DNS server.
I have a new FreeBSD 4.10 stable box that is running
Bind 9 and is now the primary DNS server.
The new IP address has been registered with the registar
and all is well on the new box.
On Mon, Nov 01, 2004 at 06:25:54AM -0900, Andy Firman wrote:
[...]
The new IP address has been registered with the registar
and all is well on the new box.
The old box still has a bunch of sites on it that I am in
the process of moving to the new box over the next few months.
The zone
I am a new FreeBSD user coming from Debian Linux.
I think I have finally got the upgrading process done right. I just
need to know if I am missing anything or have something configured
wrong. I have gotten bits and pieces from this forum, FreeBSD handbook
and the examples that came with this
In the immortal words of Brent Wiese [EMAIL PROTECTED]...
Am I missing some environment variable somewhere or what?
Did you run
use.perl port
after you upgraded the port?
--
Tim Aslat [EMAIL PROTECTED]
Spyderweb Consulting
http://www.spyderweb.com.au
Phone: +61 0401088479
-Original Message-
In the immortal words of Brent Wiese [EMAIL PROTECTED]...
Am I missing some environment variable somewhere or what?
Did you run
use.perl port
after you upgraded the port?
D'oh!
See, I knew it was dumb. For some reason, I didn't think that needed to be
done
This is the sort of thing I know I should know, but I don't right now... Too
many other stresses...
Upgraded perl from 5.8.2 to 5.8.4 (both were ports).
I need to recompile a bunch of modules (for example, mod_perl).
But, most of them error out because they can't find perl 5.8.2 libraries.
Am
Hi to everyone !
I'm sure that this is a trivial question to ask . I'm considering source and
ports tree upgarde from 5.2_REL to 5.2.1_REL . I've never did cvs before
(usually i back up , format + binary install and restore ) . I've read the
article from the handbook and everything is pretty
On Mon, May 03, 2004 at 02:25:18PM +0300, alexander botov wrote:
I'm sure that this is a trivial question to ask . I'm considering source and
ports tree upgarde from 5.2_REL to 5.2.1_REL . I've never did cvs before
(usually i back up , format + binary install and restore ) . I've read the
I just upgraded from 5.2.1.Release via cvsup to RELENG_5_2. This is the
p3 security update for openssl issues. The upgrade completed successfully
up to the last step, when I tried to run mergemaster. I got the following
response:
*** The directory specified for the temporary root environment,
At 2004-03-22T15:13:17Z, [EMAIL PROTECTED] writes:
*** The directory specified for the temporary root environment,
/var/tmp/temproot, exists. This can be a security risk if untrusted
users have access to the system.
Use 'd' to delete the old /var/tmp/temproot and continue
Use
70 matches
Mail list logo
