Doug Barton wrote:
> loading modules through loader.conf is
> veeryy slooww ...
Is it noticeably slower to load (say) a 6MB kernel + 2MB of
modules than to load an 8MB kernel? If so, any idea why?
___
freebsd-hackers@freebs
Added a check if ntfs-3g is available, if not then mount_ntfs is used instead.
Added deleting of empty directories at ${MNTPREFIX}.
Added ${MNTPREFIX} to be set to /mnt or /media according to preference
#! /bin/sh
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
MNTPREFIX="/media
On Saturday 18 February 2012 10:48:11 vermaden wrote:
> Added a check if ntfs-3g is available, if not then mount_ntfs is used
> instead. Added deleting of empty directories at ${MNTPREFIX}.
> Added ${MNTPREFIX} to be set to /mnt or /media according to preference
>
> #! /bin/sh
>
> PATH=/bin:/sbin
On 2012-02-18 14:09, Hans Petter Selasky wrote:
On Saturday 18 February 2012 10:48:11 vermaden wrote:
Added a check if ntfs-3g is available, if not then mount_ntfs is used
instead. Added deleting of empty directories at ${MNTPREFIX}.
Added ${MNTPREFIX} to be set to /mnt or /media according to
On (18/02/2012 10:48), vermaden wrote:
> Added a check if ntfs-3g is available, if not then mount_ntfs is used instead.
> Added deleting of empty directories at ${MNTPREFIX}.
> Added ${MNTPREFIX} to be set to /mnt or /media according to preference
>
> #! /bin/sh
>
> PATH=/bin:/sbin:/usr/bin:/usr/
Just want to double-check myself.
It seems that currently, thanks to event timers, we mostly should be able to
schedule a hardware timer to fire at almost arbitrary moment with very fine
precision.
OTOH, our callout subsystem still seems to be completely tick oriented in the
sense that all timeout
Very very inefficient BIOS and loader behaviour?
I'm not sure libufs is caching anything?
Adrian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-un
On 18.02.2012 21:05, Andriy Gapon wrote:
Just want to double-check myself.
It seems that currently, thanks to event timers, we mostly should be able to
schedule a hardware timer to fire at almost arbitrary moment with very fine
precision.
OTOH, our callout subsystem still seems to be completely t
On Sat, Feb 18, 2012 at 06:06:23PM +0100, Uffe Jakobsen wrote:
>
>
> On 2012-02-18 14:09, Hans Petter Selasky wrote:
> > On Saturday 18 February 2012 10:48:11 vermaden wrote:
> >> Added a check if ntfs-3g is available, if not then mount_ntfs is used
> >> instead. Added deleting of empty directori
on 18/02/2012 21:42 Alexander Motin said the following:
> On 18.02.2012 21:05, Andriy Gapon wrote:
>> Just want to double-check myself.
>> It seems that currently, thanks to event timers, we mostly should be able to
>> schedule a hardware timer to fire at almost arbitrary moment with very fine
>> p
,--- b. f. (Sat, 18 Feb 2012 20:50:01 +) *
| Most of these questions are more suitable for the freebsd-stable or
| freebsd-questions mailing lists, rather than freebsd-hackers.
I hesitated about starting this "8 to 9" thread here or on *-stable,
and decided to use this list only because I
On Tue, Feb 14, 2012 at 3:25 PM, Matthew Story wrote:
> On Tue, Feb 14, 2012 at 2:37 PM, Matthew Story wrote:
>
>> On Tue, Feb 14, 2012 at 2:35 PM, Jilles Tjoelker wrote:
>>
>>> On Tue, Feb 14, 2012 at 01:34:49PM -0500, Matthew Story wrote:
>>> > After reading the man-page, and browsing around th
Most of these questions are more suitable for the freebsd-stable or
freebsd-questions mailing lists, rather than freebsd-hackers.
Alex Goncharov wrote:
> What I see in 9 now is very confusing for me; e.g.:
>
> * Why 'snd_hda.ko' even exists, if the whole 'snd_hda' implementation lives in
> 'kern
On 18 February 2012 12:50, b. f. wrote:
>> I will use this -- thank you!
>
> You should be aware that kld_list doesn't always work. For example,
> my Nvidia nForce MCP61 network adapter works with nfe(4) when I load
> if_nfe.ko from loader.conf, but fails to function properly if the same
> modul
On Thu, Jan 26, 2012 at 09:45:47PM +1000, Da Rock wrote:
> 1. Incidentally, what exactly does constitute a major release?
That point in time where we guarantee that we break a certain degree
of backwards compatibility. (Well, that's the key component. Feature-
additions ride on top of that.)
>
The individual maintainers of each architecture have the right to make
a "PRE-RELEASE" of the system at any time. Come to think of it,
anyone who can has that right- that is to make a pre-release.
On 2/18/12, Mark Linimon wrote:
> On Thu, Jan 26, 2012 at 09:45:47PM +1000, Da Rock wrote:
>> 1. In
On 02/18/2012 10:43, per...@pluto.rain.com wrote:
> Doug Barton wrote:
>
>> loading modules through loader.conf is
>> veeryy slooww ...
>
> Is it noticeably slower to load (say) a 6MB kernel + 2MB of
> modules than to load an 8MB kernel?
I don't know, that wasn't t
On 18.02.2012 22:40, Andriy Gapon wrote:
on 18/02/2012 21:42 Alexander Motin said the following:
On 18.02.2012 21:05, Andriy Gapon wrote:
Just want to double-check myself.
It seems that currently, thanks to event timers, we mostly should be able to
schedule a hardware timer to fire at almost ar
18 matches
Mail list logo
