On Tue, 19 Oct 2010, Alexander Best wrote:
does this limitation still exist?
Sysctls can be added dynamically using the sysctl_add_oid(9) KPI, which has
existed (as far as I'm aware) at least since FreeBSD 4.x. It could be that
this KPI provides the functionality required to do what the
Alexander Best arun...@freebsd.org writes:
since there seems no way to distinguish between these two states in ATA(4)
it's
probably better to leave it as it is, since doing spin downs upon reboot might
be even worse than not doing spindowns upon shutdown.
No. Where did you get that idea?
On Thu Oct 21 10, Dag-Erling Smørgrav wrote:
Alexander Best arun...@freebsd.org writes:
since there seems no way to distinguish between these two states in ATA(4)
it's
probably better to leave it as it is, since doing spin downs upon reboot
might
be even worse than not doing spindowns
Alexander Best arun...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
No. Where did you get that idea? To repeat what I've said before -
several times - in this thread, a modern disk drive can handle hundreds
of thousands of controlled unloads but only a few hundred emergency
On Thu, 21 Oct 2010 14:33:49 +0200
Dag-Erling Smørgrav d...@des.no wrote:
The problem with setting a short idle timeout is that, on a typical
laptop or desktop system, you end up spinning the disk down and back
up several hundred times a day, which increases power consumption, I/O
latency and
On Thu Oct 21 10, Dag-Erling Smørgrav wrote:
Alexander Best arun...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
No. Where did you get that idea? To repeat what I've said before -
several times - in this thread, a modern disk drive can handle hundreds
of thousands of
On Thu Oct 21 10, Bruce Cran wrote:
On Thu, 21 Oct 2010 14:33:49 +0200
Dag-Erling Smørgrav d...@des.no wrote:
The problem with setting a short idle timeout is that, on a typical
laptop or desktop system, you end up spinning the disk down and back
up several hundred times a day, which
On Thu, 21 Oct 2010 13:41:14 +
Alexander Best arun...@freebsd.org wrote:
personally i still think something like the attached patch would be
nice to have. there's a chance users might type the following:
'atacontrol spindown device 10'
thinking the timeout value is measured in
On Thu, 21 Oct 2010 12:21:10 +
Alexander Best arun...@freebsd.org wrote:
atacontrol(8) says that:
You should not set a spindown timeout on a disk with / or syslog
logging on it as the disk will be worn out spinning down and up all
the time.
this seems to indicate that spinning
Bruce Cran br...@cran.org.uk writes:
Do we think our users are silly enough to set a short timeout of just a
few minutes? I'd think most would use a setting of 20-30 minutes at
a minimum. I never did understand why there were so many warnings;
after all, some laptops even come with a default
Alexander Best arun...@freebsd.org writes:
no need to get upset. you asked where i found the information regarding the
wear impact of spinning down disks and i gave you the answer.
I am upset by your claim that doing spin downs upon reboot might be
even worse than not doing spindowns upon
RW rwmailli...@googlemail.com writes:
Alexander Best arun...@freebsd.org wrote:
this seems to indicate that spinning down a disk has quite an impact.
That's mostly likely a hang-over from older disk technologies when the
heads touched the surface on spinning down.
They still do, although
On Thu, 21 Oct 2010 16:35:06 +0200
Dag-Erling Smørgrav d...@des.no wrote:
Really? That would make the system close to unusable, and the disk's
life expectancy would be reduced to a few months; a disk that performs
two load / unload cycles per minute on average will need replacing
after three
Bruce Cran br...@cran.org.uk writes:
The Ubuntu issue was what I was thinking of - I got that mixed up with
the aggressive power management of the WD EARS drives.
The entire Green series, actually, which includes models such as the
EADS, AARS etc., but there's more to them than that - the
On Thu, Oct 21, 2010 at 05:20:54PM +0200, Dag-Erling Smørgrav wrote:
Bruce Cran br...@cran.org.uk writes:
The Ubuntu issue was what I was thinking of - I got that mixed up with
the aggressive power management of the WD EARS drives.
The entire Green series, actually, which includes models
this patch fixes the following issues:
- unbreak 'kldstat -i 999 -v' output
- remove an unnecessary set of { and }
- change printfile() to blend into the overall style used in kldstat.c
- add a kldstat(8) entry to document the relationship between the -i and -n
flags
cheers.
alex
--
a13x
diff
On Mon, 11.10.2010 at 11:35:42 +0200, Erik Cederstrand wrote:
Den 11/10/2010 kl. 10.47 skrev Kostik Belousov:
My personal opinion that the feature is nice to have. Unless the changes to
get this working are too large, and, more importantly, unless the
maintenance
cost of having this
On Thu, Oct 21, 2010 at 10:46 AM, Alexander Best arun...@freebsd.org wrote:
this patch fixes the following issues:
- unbreak 'kldstat -i 999 -v' output
- remove an unnecessary set of { and }
- change printfile() to blend into the overall style used in kldstat.c
- add a kldstat(8) entry to
On Thu, 14.10.2010 at 15:23:23 -0500, Brooks Davis wrote:
One of the side effects of increasing NGROUPS_MAX is that it's possible
for a process to be in more groups that can be transmitted over NFS
(4). When that happens users are mostly denied access to things they
should have access to.
Hello,
I have on my laptop a kernel based on CVS from May 2009, i.e. 8-CURRENT
at this time.
I now need support for Atheros AR813x/AR815x PCIe
Ethernet, the kmod if_alc.ko. That's why I did:
# cd /usr/src/sys/dev
# cvs update -d -r RELENG_8_0_0_RELEASE alc
and have now:
# ls -l alc
total
On Thu Oct 21 10, Garrett Cooper wrote:
On Thu, Oct 21, 2010 at 10:46 AM, Alexander Best arun...@freebsd.org wrote:
this patch fixes the following issues:
- unbreak 'kldstat -i 999 -v' output
- remove an unnecessary set of { and }
- change printfile() to blend into the overall style
On 10/21/10, Matthias Apitz g...@unixarea.de wrote:
Hello,
I have on my laptop a kernel based on CVS from May 2009, i.e. 8-CURRENT
at this time.
I now need support for Atheros AR813x/AR815x PCIe
Ethernet, the kmod if_alc.ko. That's why I did:
# cd /usr/src/sys/dev
# cvs update -d -r
El día Thursday, October 21, 2010 a las 08:35:09PM +0200, Paul B Mahol escribió:
# cd /usr/src
# make buildkernel KERNCONF=GENERIC
does not build the module if_alc.ko
What I'm missing? Or what is the correct way to get this module for my
kernel level?
/sys/modules/alc
Yes,
On 10/21/10, Matthias Apitz g...@unixarea.de wrote:
El dia Thursday, October 21, 2010 a las 08:35:09PM +0200, Paul B Mahol
escribio:
# cd /usr/src
# make buildkernel KERNCONF=GENERIC
does not build the module if_alc.ko
What I'm missing? Or what is the correct way to get this module
Den 21/10/2010 kl. 19.57 skrev Ulrich Spörlein:
On Mon, 11.10.2010 at 11:35:42 +0200, Erik Cederstrand wrote:
I'm beginning to think that it should at least be optional. Removing e.g.
build times, mtimes and path to OBJDIR or SRCDIR might not make everyone
happy.
The problem with
On 10/21/10 15:20, Dag-Erling Smørgrav wrote:
Bruce Cranbr...@cran.org.uk writes:
The Ubuntu issue was what I was thinking of - I got that mixed up with
the aggressive power management of the WD EARS drives.
The entire Green series, actually, which includes models such as the
EADS, AARS
26 matches
Mail list logo
