>From Daniel Bond <[EMAIL PROTECTED]>, Thu, Sep 07, 2006 at 08:13:11PM +0200:
> Hi,
>
> I just setup GBDE on my laptop, encrypting my 512M cf-card.
> This works like a charm, but I felt the need to enchance the rc-script a
> little to automatically mount the encrypted drive(s), if you have the
> f
>From Kris Kennaway <[EMAIL PROTECTED]>, Fri, Sep 29, 2006 at 09:42:42PM -0400:
> On Fri, Sep 29, 2006 at 08:34:39PM -0500, Craig Boston wrote:
> > On Fri, Sep 29, 2006 at 08:19:04PM -0500, Craig Boston wrote:
> > > On Thu, Sep 28, 2006 at 01:48:42PM -0600, Scott Long wrote:
> > > > http://people.f
Well, I suspect that most people with the resources to do what you ask
have already moved on precisely because the EoL has been published.
i.e., faced with that limited commitment, we had no choice but to
(grudgingly and at the last minute) move on.
I think the most likely path of success is, as y
>From Robert Watson <[EMAIL PROTECTED]>, Fri, Oct 20, 2006 at 12:51:13AM +0100:
>
> On Tue, 17 Oct 2006, security wrote:
>
> > You'll have the sources. If you're using 4.11 in a business, you need
> > to decide if it's more cost effective to move on to 6 or hire someone to
> >keep 4.11 runni
>From Mike Jakubik <[EMAIL PROTECTED]>, Mon, Oct 23, 2006 at 07:44:45PM -0400:
> Chuck Swiger wrote:
> >On Oct 23, 2006, at 4:01 PM, Mike Jakubik wrote:
> >> So, first of all, am i crazy for choosing fbsd+mysql for this
> >>rather than something like Solaris + Oracle? :)
> >
> >Moderately...it k
Has anyone else observed that fusefs appears to suffer from
the race-to-root problem that used to plague NFS prior to rev
1.39 of vfs_lookup.c?
Paul
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman
While performing a sequential read from a compact flash disk over
cardbus (cbb), I observe the following:
iostat reports transfer rate of 0.72MB/s with average transaction size of 32K
top -S reports 80% interrupt time. 78% of which is attributed to irq11
vmstat -i reports about an order of magnit
>From Doug Barton <[EMAIL PROTECTED]>, Mon, Jun 04, 2007 at 01:55:01PM -0700:
> Chris wrote:
>
> > So my question remains when we have 7.0 and 6.3 both STABLE releases
> > will the ports tree not be supported in 6.3 a just released version of
> > FreeBSD?
> You are focusing on released version num
> There are various degrees of stability:
>
> 7-CURRENT: active development, lots of experimental and possibly unsafe
> things in there.
>
> 6-STABLE: proven changes from 7-CURRENT go in here. API is mandated to
> be stable, and only well tested and fucntionally stable changes should
> go in.
This was originally mentioned in amd64/76224 which was closed by obrien with the
terse remark: "We don't yet support building 32-bit apps on a 64-bit system. We
only barely support *running* them at this point."
Really this deserves an errata mention at the very least. It just simply
isn't intuit
> >Is anyone aware of any regressions in laptop functionality going from 5.4
> >to
> >6.x?
If you're worried, just burn a FreeSBIE first.
Paul
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fr
One detail of this has to do with version numbering.
The FreeBSD version number says a lot more about the
userland than it does about the kernel per se.
If we were to version the kernel arch, I think it would
look more like this:
'94 1.1.5.1 (Last Net/2) Version 0
Nov '94 2.0
>From Scott Long <[EMAIL PROTECTED]>, Sun, May 21, 2006 at 11:44:27PM -0600:
> I share this frustration with you. I was once told that the pain in
> upgrading is due largely to a somewhat invisible difference between
> installing a pre-compiled package, and building+installing a port. In
> theory
>From Doug Hardie <[EMAIL PROTECTED]>, Sun, May 21, 2006 at 11:48:51PM -0700:
> Failover sounds good in theory but has significant issues in practice
> that make it sometimes worse than the alternative. Take mail
> spools. If you failover, mail the user saw before has disappeared.
> Then w
>From Jonathan Noack <[EMAIL PROTECTED]>, Thu, May 25, 2006 at 07:56:07PM -0400:
> I am currently running with the following in /etc/rc.conf and haven't
> experienced any problems:
> tmpmfs_flags="-S -o async"
Is there a way to accomplish this with an fstab entry?
md /tmpmfs
>From "M.Hirsch" <[EMAIL PROTECTED]>, Tue, Jun 27, 2006 at 01:38:35AM +0200:
> Sticks don't just break on a single bit. From my experience, a stick
> that's got any problems at all, will cause even more trouble soon...
> If a hardware problem isn't worth panick'ing, what else is?
> (don't answer t
>From Mike Jakubik <[EMAIL PROTECTED]>, Sun, Jul 09, 2006 at 05:53:38PM -0400:
> Mathieu Arnold wrote:
> >| Exactly, its nice being able to see the current values. How else can i
> >| see what the values are set to?
> >
> >As I previously said, it's 512M on i386, and 1G on 64 bit platforms.
> >
> >
>From Mike Jakubik <[EMAIL PROTECTED]>, Mon, Jul 10, 2006 at 01:16:47PM -0400:
> Chuck Swiger wrote:
> >512MB is more than enough for almost all processes to run just fine,
> >and is only really inappropriate for the case where you've got 1-plus
> >GB of physical RAM and want to dedicate the syst
>From "Julian H. Stacey" <[EMAIL PROTECTED]>, Thu, Jul 27, 2006 at 01:45:16AM
>+0200:
> Negative isnt an example of programming error, just that the system
> is now using the last bit only root can use.
>
> for insight try for example
> man tunefs
> reboot
> boot -s
>
19 matches
Mail list logo
