On Sun, Nov 4, 2012 at 12:28 PM, Rainer Duffner wrote:
>
> Oh - will were be an 8.4 release? That would be interesting.
History shows that every release, since 4.x has gone to at least .4.
I'd be willing to bet we will see an 8.4. The branch is still being
developed.
http://en.wikipedia.org/wik
Hello, George.
You wrote 5 ноября 2012 г., 0:07:00:
GM> Gosh, I'm SO looking forward to depending on svn instead of csup for
GM> software updates.-- George
It is planned server outage (migration).
--
// Black Lion AKA Lev Serebryakov
__
On 4 Nov 2012 20:12, "George Mitchell" wrote:
>
> On 11/04/12 14:59, FreeBSD Tinderbox wrote:
>>
>> TB --- 2012-11-04 19:53:34 - tinderbox 2.9 running on
freebsd-stable.sentex.ca
>> TB --- 2012-11-04 19:53:34 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE
FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58
TB --- 2012-11-04 20:15:59 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-11-04 20:15:59 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE
FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-11-04 20
TB --- 2012-11-04 20:10:27 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-11-04 20:10:27 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE
FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-11-04 20
TB --- 2012-11-04 20:04:49 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-11-04 20:04:49 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE
FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-11-04 20
On 11/04/12 14:59, FreeBSD Tinderbox wrote:
TB --- 2012-11-04 19:53:34 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-11-04 19:53:34 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE
FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012
mdtan...@freebsd-stable.sentex.ca:/usr/obj/
TB --- 2012-11-04 19:59:03 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-11-04 19:59:03 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE
FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-11-04 19
TB --- 2012-11-04 19:53:34 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-11-04 19:53:34 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE
FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-11-04 19
TB --- 2012-11-04 19:48:09 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-11-04 19:48:09 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE
FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-11-04 19
TB --- 2012-11-04 19:42:16 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-11-04 19:42:16 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE
FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-11-04 19
Hi,
after upgrading Kernel from 9.1-RC2
# freebsd-update upgrade -r 9.1-RC3
# freebsd-update install
# shutdown -r now
the Kernel ist not booting. It just reboot's after the boot loader.
There no kernel.old. Safe mode also reboots. What can I do to
recover the machine? (It was booting/running
Hi,
I've just tried to upgrade a machine running an older 8-stable to
9-stable@r242549M without success.
It runs an apache with mod_fcgid in a jail and the latter can't start
with the error message of:
[Sun Nov 04 16:09:12 2012] [emerg] (78)Function not implemented:
mod_fcgid: Can't create sha
Hi!
> >Oh - will were be an 8.4 release? That would be interesting.
>
> I'd like to see a trend toward more point versions of FreeBSD.
> Particularly in 9.x, because it incorporates most of the items that
> have been on people's wish lists. 4.11 was one of the most robust
> and stable releases
At 10:28 AM 11/4/2012, Rainer Duffner wrote:
Oh - will were be an 8.4 release? That would be interesting.
I'd like to see a trend toward more point versions of FreeBSD.
Particularly in 9.x, because it incorporates most of the items that
have been on people's wish lists. 4.11 was one of the m
Am Sat, 3 Nov 2012 21:56:45 -0400
schrieb Rick Miller :
> On Fri, Nov 2, 2012 at 4:10 AM, Rainer Duffner
> wrote:
> > Am Thu, 1 Nov 2012 20:14:51 -0600 (MDT)
> > schrieb Brett Glass :
> >
> >> I need to build up a few servers and routers, and am wondering how
> >> FreeBSD 9.1 is shaping up. Will
On 11/04/2012 04:33 PM, Zoran Kolic wrote:
>> Just rebooting to single user mode after the install and then tunefs -j
>> disable /dev/ada0p2 works for me.
>> After a reboot then I just removed /.sujournal
> That crystillized to me as a correct way in this situation.
> Just one "fsck" at the very be
> Just rebooting to single user mode after the install and then tunefs -j
> disable /dev/ada0p2 works for me.
> After a reboot then I just removed /.sujournal
That crystillized to me as a correct way in this situation.
Just one "fsck" at the very beginning? Manual says about
some options availabl
On 11/04/2012 03:43 PM, George Mitchell wrote:
> On 11/03/12 15:09, Jeremy Chadwick wrote:
>> (Please keep me CC'd, as I'm not subscribed to -stable)
>>
>> I've CC'd Nathan Whitehorn, who according to bsdinstall(8) is the
>> author (not sure if maintainer) of the code.
>>
>> This default has alread
On 11/03/12 15:09, Jeremy Chadwick wrote:
(Please keep me CC'd, as I'm not subscribed to -stable)
I've CC'd Nathan Whitehorn, who according to bsdinstall(8) is the
author (not sure if maintainer) of the code.
This default has already begun to bite users/SAs in the ass:
http://lists.freebsd.org
Imho, at least wiki page (http://wiki.freebsd.org/) on
setting up FreeBSD on SSDs is needed.
Lots of confusion and different opinions (sector size!)...
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Why-is-SU-J-undesirable-on-SSDs-tp5757733p5757907.html
Sent from the fr
Hi Bas, thank you for your response.
>When taking a snapshot of a SU+J filesystem we already get the nice not
>supported error instead of getting into trouble.
It's not nice.
Hiding problem will never solve problem.
Currently we have no choice.
If we have a way to choose (e.g. through sysctl),
On 11/04/2012 01:13 PM, HATANO Tomomi wrote:
> Hi all.
>
> The point is:
>
> There is completely no way to take a snapshot of SU+J partition
> unless modify one's kernel.
>
> Whether some issue still exist or not,
> how about enabling snapshoting SU+J partition
> through sysctl variable?
Hi all.
The point is:
There is completely no way to take a snapshot of SU+J partition
unless modify one's kernel.
Whether some issue still exist or not,
how about enabling snapshoting SU+J partition
through sysctl variable?
Would you mind to see patch attached?
1. Taking a snapshot of
On 11/04/2012 12:08 PM, jb wrote:
> Bas Smeelen ose.nl> writes:
>
>> ...
>> To file a PR it will require some work to find out exactly what the PR
>> should be about.
>> Since freebsd-update is meant to update the system I don't really see a
>> point to make it install sources (or others things) i
Bas Smeelen ose.nl> writes:
> ...
> To file a PR it will require some work to find out exactly what the PR
> should be about.
> Since freebsd-update is meant to update the system I don't really see a
> point to make it install sources (or others things) if they are not
> present on the system
Dear FreeBSD Community Friends,
It is FreeBSD 9.1 RC3, i get the following warning in the message log
file. i need assistance to understand the meaning of this error, how
serious is it?
acpi_throttle23: failed to attach P_CNT
History:
This error is following FreeBSD for long time because when i
On 11/04/2012 11:25 AM, jb wrote:
> Bas Smeelen ose.nl> writes:
>
>> ...
>> Can't this be accomplished by setting
>> StrictComponents yes
>> in /etc/freebsd-update.conf ?
>>
>> Then feebsd-update does not try to figure out the components to update
>> by itself, but updates the components mentioned
On 11/4/2012 5:32, Karl Denninger wrote:
It is utter insanity to enable, by default, filesystem options that
break _*the canonical backup solution*_ in the handbook ("dump", when
used with "-L", which it must be to dump a live filesystem SAFELY.)
Exactly.
--
Adam Strohl
http://www.ateamsystem
Bas Smeelen ose.nl> writes:
> ...
> Can't this be accomplished by setting
> StrictComponents yes
> in /etc/freebsd-update.conf ?
>
> Then feebsd-update does not try to figure out the components to update
> by itself, but updates the components mentioned in
> Components src world kernel
>
> I
Quoting Dimitry Andric :
On 2012-11-02 19:22, Oleg V. Nauman wrote:
...
/usr/src/lib/libc++/../../contrib/libc++/include/cstdlib:134:9: error:
no member named
'at_quick_exit' in the global namespace
using ::at_quick_exit;
~~^
This was fixed in head by r242472, I will merge it as
On 11/3/2012 1:31, Mateusz Guzik wrote:
Currently when you try to take a snapshot, the kernel checks whether SUJ
is enabled on specified mount-point, and if yes it returns EOPNOTSUPP.
See this commit (MFCed as r230725):
http://svnweb.freebsd.org/base?view=revision&revision=230250
Ahhh excelle
On 11/04/2012 06:19 AM, Zoran Kolic wrote:
>> There's an existing checkbox to disable it. There was substantial
>> consensus for 9.0 that SUJ was something we wanted
> Nice to hear. I assume you mean check box during install
> process? Not mentioned in install guide in handbook.
> So, after I accep
I personally let it be enabled during installation. I noticed that I was
getting errors on fsck even after clean shutdown. After noticing it, I disabled
it and the problems go away. Also, fsck works really fast so I don't see much
advantage with SU+J.
--
Sent from my phone. Please excuse my bre
On 11/03/2012 05:03 PM, jb wrote:
> Eugene Grosbein grosbein.net> writes:
>
>> ...
>> My real question is how make freebsd-update download sources they are not
>> installed?
> I am not 110% sure, but you can not.
> When freebsd-update runs, it checks its config file /etc/freebsd-update.conf
> and
35 matches
Mail list logo
