the drive has reallocated some sectors and normally drives should never
reallocate sectors unless it has trouble reading/writing to them. also,
that drive has known firmware problems so it sounds like the drive needs
replacing
On Feb 9, 2012 10:38 AM, Mike Tancsa m...@sentex.net wrote:
On
On Thu, Feb 09, 2012 at 10:24:11PM -0800, Jeremy Chadwick wrote:
On Thu, Feb 09, 2012 at 04:02:12PM -0800, Julian Elischer wrote:
On 2/9/12 1:56 PM, Jeremy Chadwick wrote:
On Thu, Feb 09, 2012 at 01:48:29PM -0800, Julian Elischer wrote:
does anyone know of problems with freebsd and this
Hi,
during some big discussions in the last monts on various lists, one of
the problems was that some people would like to use freebsd-update but
can't as they are using a custom kernel. With all the kernel modules
we provide, the need for a custom kernel should be small, but on the
On Fri, Feb 10, 2012 at 02:56:04PM +0100, Alexander Leidinger wrote:
The question is, is this enough? Or asked differently, why are you
compiling a custom kernel in a production environment (so I rule out
debug options zhich are not enabled in GENERIC)? Are there options
which you add
On Fri, Feb 10, 2012 at 02:56:04PM +0100, Alexander Leidinger wrote:
Hi,
during some big discussions in the last monts on various lists, one
of the problems was that some people would like to use
freebsd-update but can't as they are using a custom kernel. With all
the kernel modules we
On 2012-02-10 14:56:04 (+0100), Alexander Leidinger alexan...@leidinger.net
wrote:
The question is, is this enough? Or asked differently, why are you
compiling a custom kernel in a production environment (so I rule out
debug options zhich are not enabled in GENERIC)? Are there options
which
2012/2/10 Marek 'Buki' Kozlovský free...@dev.null.cz
On Fri, Feb 10, 2012 at 02:56:04PM +0100, Alexander Leidinger wrote:
Hi,
during some big discussions in the last monts on various lists, one
of the problems was that some people would like to use
freebsd-update but can't as they are
Le 10 févr. 2012 à 15:36, Marek 'Buki' Kozlovský a écrit :
On Fri, Feb 10, 2012 at 02:56:04PM +0100, Alexander Leidinger wrote:
The question is, is this enough? Or asked differently, why are you
compiling a custom kernel in a production environment (so I rule out
debug options zhich are
On Fri, Feb 10, 2012 at 02:56:04PM +0100, Alexander Leidinger wrote:
Hi,
during some big discussions in the last monts on various lists, one of
the problems was that some people would like to use freebsd-update but
can't as they are using a custom kernel. With all the kernel modules
On 10/2/2012 15:56, Alexander Leidinger wrote:
Hi,
during some big discussions in the last monts on various lists, one of
the problems was that some people would like to use freebsd-update but
can't as they are using a custom kernel. With all the kernel modules we
provide, the need for a custom
Alexander Leidinger wrote:
during some big discussions in the last monts on various lists, one of
the problems was that some people would like to use freebsd-update but
can't as they are using a custom kernel. With all the kernel modules we
provide, the need for a custom kernel should be small,
On Fri, February 10, 2012 11:56, Alexander Leidinger wrote:
Hi,
during some big discussions in the last monts on various lists, one of
the problems was that some people would like to use freebsd-update but
can't as they are using a custom kernel. With all the kernel modules
we provide, the
On 10. Feb 2012, at 15:56 , Panagiotis Christias wrote:
On 10/2/2012 15:56, Alexander Leidinger wrote:
Hi,
during some big discussions in the last monts on various lists, one of
the problems was that some people would like to use freebsd-update but
can't as they are using a custom kernel.
On 10. Feb 2012, at 13:56 , Alexander Leidinger wrote:
Hi,
during some big discussions in the last monts on various lists, one of the
problems was that some people would like to use freebsd-update but can't as
they are using a custom kernel. With all the kernel modules we provide, the
2012/2/10 Andreas Nilsson andrn...@gmail.com:
IPFIREWALL_DEFAULT_TO_ACCEPT, DEVICE_POLLING and HZ=1000.
HZ can be set via /boot/loader.conf, and I think via sysctl as well.
--
Freddie Cash
fjwc...@gmail.com
___
freebsd-stable@freebsd.org mailing list
On Fri, Feb 10, 2012 at 8:23 AM, Slawa Olhovchenkov s...@zxy.spb.ru wrote:
On Thu, Feb 09, 2012 at 10:24:11PM -0800, Jeremy Chadwick wrote:
On Thu, Feb 09, 2012 at 04:02:12PM -0800, Julian Elischer wrote:
On 2/9/12 1:56 PM, Jeremy Chadwick wrote:
On Thu, Feb 09, 2012 at 01:48:29PM -0800,
Guys,
This should really be reverted to sysinstall until the new installer is
at least in a state where it consistently works... the most important
part of a new users experience is the installer and the few new installs
I have done lately I've just installed 8.2 and upgraded from there as
Joe Holden wrote:
Guys,
This should really be reverted to sysinstall until the new installer is
at least in a state where it consistently works... the most important
part of a new users experience is the installer and the few new installs
I have done lately I've just installed 8.2 and
On 02/10/2012 06:56 PM, Joe Holden wrote:
Guys,
This should really be reverted to sysinstall until the new installer
is at least in a state where it consistently works... the most
important part of a new users experience is the installer and the few
new installs I have done lately I've just
Alex Samorukov wrote:
On 02/10/2012 06:56 PM, Joe Holden wrote:
Guys,
This should really be reverted to sysinstall until the new installer
is at least in a state where it consistently works... the most
important part of a new users experience is the installer and the few
new installs I have
Joe Holden wrote:
Alex Samorukov wrote:
On 02/10/2012 06:56 PM, Joe Holden wrote:
Guys,
This should really be reverted to sysinstall until the new installer
is at least in a state where it consistently works... the most
important part of a new users experience is the installer and the few
I've done this a few times.
The /boot/loader takes a _long_ time to suck in the 25 odd modules my
eeepc requires to load a completely modular kernel. It takes a _very
long_ time to suck these in over USB.
It's a great idea and I think we should start down this path in the
10-CURRENT trajectory
On 2/9/2012 1:37 PM, Mike Tancsa wrote:
On 2/9/2012 11:34 AM, Jeremy Chadwick wrote:
You will probably need to track these drives on a regular basis. That
is to say, set up some cronjob or similar that logs the above output to
a file (appends data to it), specifically output from smartctl -A
Alex Samorukov m...@os2.kiev.ua writes:
On 02/10/2012 06:56 PM, Joe Holden wrote:
Guys,
This should really be reverted to sysinstall until the new installer
is at least in a state where it consistently works... the most
important part of a new users experience is the installer and the
few
On Fri, Feb 10, 2012 at 02:56:04PM +0100, Alexander Leidinger wrote:
during some big discussions in the last monts on various lists, one
of the problems was that some people would like to use
freebsd-update but can't as they are using a custom kernel. With all
the kernel modules we provide,
On 02/10/2012 12:13, Adrian Chadd wrote:
I've done this a few times.
The /boot/loader takes a _long_ time to suck in the 25 odd modules my
eeepc requires to load a completely modular kernel.
For those modules not directly related to booting you're better off
putting them in kld_list in
On Fri, Feb 10, 2012 at 04:25:21PM -0700, Ian Lepore wrote:
On Fri, 2012-02-10 at 15:10 -0800, Jeremy Chadwick wrote:
* Addition: device ichwd
- Note: We do not use features of this driver given known problems
with the watchdog firing during ddb and similar environments. I
have
On Fri, 2012-02-10 at 15:10 -0800, Jeremy Chadwick wrote:
* Addition: device ichwd
- Note: We do not use features of this driver given known problems
with the watchdog firing during ddb and similar environments. I
have no idea if this has been fixed, but I do remember it being
Mike,
I wanted to make you aware of this commit that just came through:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cam/ata/ata_da.c
I would recommend trying this out first to see if it improves your
situation with disks on the PM. mav@ might be able to state with more
certainty if that
On 2/10/2012 8:27 PM, Jeremy Chadwick wrote:
Mike,
I wanted to make you aware of this commit that just came through:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cam/ata/ata_da.c
Thanks, I did see that. I was going to wait until Monday to csup up
once all the weekend level zeros are
Hi,
I was reliably seeing a hang during panic in stable/8 -r231144 (and 8.2
release) with an active ssh session. The SCHEDULER_STOPPED patch fixed it, once
I found it:
http://lists.freebsd.org/pipermail/freebsd-current/2011-December/030127.html
is there a recipe for moving from i386 to amd64?
on a very remote system, i made the migration from 7.4 to 8.2 to 9.0,
all 32-bit. it was done with repeated
make buildworld
make kernel.new [0]
nextboot -k kernel.new
reboot
make installworld
etc
[0] - well, there were
On 02/10/2012 20:56, Randy Bush wrote:
is there a recipe for moving from i386 to amd64?
Other than backup and reinstall, no. As you already discovered the old
world won't run on the new kernel. Installing the new world before
reboot isn't safe either, as at some point in the process it'll blow
On Feb 11, 2012, at 12:48 AM, Doug Barton wrote:
On 02/10/2012 20:56, Randy Bush wrote:
is there a recipe for moving from i386 to amd64?
Other than backup and reinstall, no. As you already discovered the old
world won't run on the new kernel. Installing the new world before
reboot isn't
On 11. Feb 2012, at 05:48 , Doug Barton wrote:
On 02/10/2012 20:56, Randy Bush wrote:
is there a recipe for moving from i386 to amd64?
Other than backup and reinstall, no. As you already discovered the old
world won't run on the new kernel. Installing the new world before
reboot isn't safe
In the last episode (Feb 10), Randy Bush said:
is there a recipe for moving from i386 to amd64?
on a very remote system, i made the migration from 7.4 to 8.2 to 9.0, all
32-bit. it was done with repeated
make buildworld
make kernel.new [0]
nextboot -k kernel.new
reboot
heh? An i386 world should run (almost) fine on an amd64 kernel. I
know people who have done that update (but I know of no one done it
headless).
i am not sure i want to be the first :)
PS: do you happen to know why the amd64 kernel did hang on boot?
nope. dmesg -a did not help on reset
Sorry, I wasn't clear.
There are various hacky solutions that you can use if you're safely
within shouting distance of the system. But Randy specified very
remote, thus the answer to his question is no.
Doug
--
It's always a long day; 86400 doesn't fit into a short.
Breadth
The cleanest upgrade path is to prepare your 32-bit root to be bootable by
both 32- and 64-bit kernels: copy the ld-elf32.so that was built during your
buildworld over to /libexec/ld-elf32.so, and also make copies of
/lib and /usr/lib to /lib32 and /usr/lib32 respectively. That way when you
After recent merges to stable/8 I am now seeing errors on bootup of
the following for three interfaces that will never see the light of
DHCP. ?
/etc/rc.d/dhclient: ERROR: 'dc1' is not a DHCP-enabled interface
Can someone please revert these changes or some other action. ?
--
;s =;
On Sat, Feb 11, 2012 at 12:02:07AM -0600, Dan Nelson wrote:
In the last episode (Feb 10), Randy Bush said:
is there a recipe for moving from i386 to amd64?
on a very remote system, i made the migration from 7.4 to 8.2 to 9.0, all
32-bit. it was done with repeated
make
41 matches
Mail list logo
