Hi,
Because of severe problems wrt. a third party app (TSM Backup - see my
previous post) I'm looking for a way to compile a kernel/system to a
state as it was several weeks ago.
To be specific I'd like to build my system/kernel using the
source-files of FreeBSD 6.2 as they were back on
Ewald Jenisch writes:
To be specific I'd like to build my system/kernel using the
source-files of FreeBSD 6.2 as they were back on September 14,
2007.
In cvsup there seems to be a feature date=... that should be
able to accomplish this. Has anybody out there used it
sucessfully? Is
Ewald Jenisch wrote:
Hi,
Because of severe problems wrt. a third party app (TSM Backup - see my
previous post) I'm looking for a way to compile a kernel/system to a
state as it was several weeks ago.
To be specific I'd like to build my system/kernel using the
source-files of FreeBSD 6.2 as
Quoting Erik Cederstrand [EMAIL PROTECTED]:
Should be tag=RELENG_6_2
...
That should suffice.
This assumes you're already running 6.2. As long as you don't switch
branches (or choose a date before the branch occurred!), you should be
good to go.
Erik
i would agree with erik's advice,
Jonathan Horne wrote:
...
IMO, (and forgive me, i generally dont spew my opinions where they arent
welcome or asked for), RELENG_6_2 is better for a server over RELENG_6
(aka, -STABLE), as it doesnt include items that are not critically
required for secure and stable operation. remember,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok, I kind of worked myself into a corner by only bringing a USB
keyboard and accidentally making logins impossible via the network (bad
firewall setup with IPFilter).
Basically I have a disk with FreeBSD 7-CURRENT on it and I have a
working machine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Garrett Cooper wrote:
Ok, I kind of worked myself into a corner by only bringing a USB
keyboard and accidentally making logins impossible via the network (bad
firewall setup with IPFilter).
Basically I have a disk with FreeBSD 7-CURRENT on it
On 2006-08-21 16:28, beno [EMAIL PROTECTED] wrote:
Hi;
I just barely finished upgrading from 5.3 to 6.1 and all is well,
however, now I realize I have to rebuild my kernel again to accommodate
PF. I've edited the correct GENERIC file (I'm on an i386 box).
Don't edit GENERIC. It's very rarely
Giorgos Keramidas wrote:
On 2006-08-21 16:28, beno [EMAIL PROTECTED] wrote:
Hi;
I just barely finished upgrading from 5.3 to 6.1 and all is well,
however, now I realize I have to rebuild my kernel again to accommodate
PF. I've edited the correct GENERIC file (I'm on an i386 box).
Don't
On 2006-08-22 18:00, Mikhail Goriachev [EMAIL PROTECTED] wrote:
Giorgos Keramidas wrote:
On 2006-08-21 16:28, beno [EMAIL PROTECTED] wrote:
make buildkernel
make installkernel
sh /etc/rc.shutdown
pkill sendmail
pkill syslogd
mergemaster -p
make installworld
mergemaster
reboot
Giorgos Keramidas wrote:
On 2006-08-21 16:28, beno [EMAIL PROTECTED] wrote:
Hi;
I just barely finished upgrading from 5.3 to 6.1 and all is well,
however, now I realize I have to rebuild my kernel again to accommodate
PF. I've edited the correct GENERIC file (I'm on an i386 box).
On 2006-08-22 08:43, beno [EMAIL PROTECTED] wrote:
Giorgos Keramidas wrote:
Don't edit GENERIC. It's very rarely a good idea. If you spend
some time to fine tune GENERIC to your own particular setup,
matching your own preferences, you may be surprised in a very bad
way after the next CVSup
Hi;
I just barely finished upgrading from 5.3 to 6.1 and all is well,
however, now I realize I have to rebuild my kernel again to accommodate
PF. I've edited the correct GENERIC file (I'm on an i386 box). Are these
commands sufficient?
make buildkernel
make installkernel
or do I need to
beno [EMAIL PROTECTED] writes:
Hi;
I just barely finished upgrading from 5.3 to 6.1 and all is well,
however, now I realize I have to rebuild my kernel again to
accommodate PF. I've edited the correct GENERIC file (I'm on an i386
box). Are these commands sufficient?
make buildkernel
make
BEFORE you do:
make delete-old-libs
be SURE portmanager has everything updated. I had to run portmanager
multiple times to get all my ports completely rebuilt.
-Derek
At 03:28 PM 8/21/2006, beno wrote:
Hi;
I just barely finished upgrading from 5.3 to 6.1 and all is well, however,
I've just put together a new amd64 machine in an ASUS Vintage-ae1 barebones
system. After giving up on FreeBSD 5.4 when it gagged on my hard drive, I
decided to try going all the way to 6.0beta4. Almost everything went without
incident except for mounting usb sticks and the on-board network card
Hello Lei,
it's working out great now !
thanks :)
=1 was missing in the previous post
Friday, July 22, 2005, 8:15:50 PM, you wrote:
LS This thread helped
LS http://archives.neohapsis.com/archives/freebsd/2005-05/0037.html
LS On 7/22/05, Lei Sun [EMAIL PROTECTED] wrote:
Yes, I read that
Hi,
I wanted to enable the second logical CPU on my P4 HT. and...
Something seems to be strange to me as:
All of the processes are running with CPU0 and none is working with CPU1
-
last pid:
On Fri, 2005-07-22 at 00:12 -0700, Lei Sun wrote:
Hi,
I wanted to enable the second logical CPU on my P4 HT. and...
Something seems to be strange to me as:
All of the processes are running with CPU0 and none is working with CPU1
Here is the steps and places I read and followed
1. I
Yes, I read that security advisory as well, and I see
---
NOTE: For users that are certain that their environment is not affected
by this vulnerability, such as single-user systems, Hyper-Threading
Technology may be re-enabled by setting the tunable
Hello Lei,
i agree with you. I have he same trouble.
kern.threads.virtual_cpu: 2
kern.smp.cpus: 2
hw.ncpu: 2
hw.acpi.cpu.cx_supported: C1/0
hw.acpi.cpu.cx_lowest: C1
hw.acpi.cpu.cx_usage: 100.00%
machdep.cpu_idle_hlt: 0
machdep.hlt_cpus: 2
machdep.hlt_logical_cpus: 0
machdep.logical_cpus_mask: 2
This thread helped
http://archives.neohapsis.com/archives/freebsd/2005-05/0037.html
On 7/22/05, Lei Sun [EMAIL PROTECTED] wrote:
Yes, I read that security advisory as well, and I see
---
NOTE: For users that are certain that their environment is not affected
by this
In rebuilding a kernel, how do you know exactly what modules you need?
The Handbook is a good start, and a lot of them are obvious (i.e. if
I have no SCSI disks, disable all SCSI modules). Others aren't so
easy, particularly serial devices, and the pseudo devices. How can I
find out exactly
On Thursday 31 March 2005 19:43, Pat Maddox wrote:
In rebuilding a kernel, how do you know exactly what modules you need?
The Handbook is a good start, and a lot of them are obvious (i.e. if
I have no SCSI disks, disable all SCSI modules). Others aren't so
easy, particularly serial devices,
Thanks for the info. My terminology is off...apparently what I really
meant is I'm wondering what drivers I need to compile into the kernel.
I've done what you've suggested - removed SCSI support, all of the
NIC drivers besides the one I need, etc. I'm just wondering how I can
find out EXACTLY
On Friday 01 April 2005 00:45, Pat Maddox wrote:
Thanks for the info. My terminology is off...apparently what I really
meant is I'm wondering what drivers I need to compile into the kernel.
I've done what you've suggested - removed SCSI support, all of the
NIC drivers besides the one I need,
26 matches
Mail list logo
