On 14.10.2011 02:52, Hiroki Sato wrote:
Can you please send me the results of the following commands:
Please see the output below each command. I forgot to
mention that the ipv6 uplink is a 6to4 tunnel, as you can
see below from the 2002: prefix.
% ifconfig
[tykling@tykburk ~]$ ifconfig
Thomas Steen Rasmussen tho...@gibfest.dk wrote
in 4e97cffc.5020...@gibfest.dk:
th On 14.10.2011 02:52, Hiroki Sato wrote:
th Can you please send me the results of the following commands:
th
th Please see the output below each command. I forgot to
th mention that the ipv6 uplink is a 6to4
On 14.10.2011 08:14, Hiroki Sato wrote:
telnet www.freebsd.org 80 /dev/null
[tykling@tykburk ~]$ telnet www.freebsd.org 80 /dev/null
Trying 69.147.83.34...
Connected to red.freebsd.org.
Escape character is '^]'.
Connection closed by foreign host.
/Thomas
On Oct 13, 2011, at 9:40 PM, Arnaud Lacombe wrote:
Hi,
On Thu, Oct 13, 2011 at 2:00 PM, lacom...@gmail.com wrote:
From: Arnaud Lacombe lacom...@gmail.com
Hi folks,
There is many case recently when I really wished timestamp were present in
the
post-mortem msgbuf. Such situation
on 30/08/2011 13:01 Andriy Gapon said the following:
So, just to re-iterate, I think that this is indeed a regression and the one
that could be particularly unhelpful for a new release - the time when people
are much more likely to end up at the mountroot prompt during an installation
of
a
Thomas Steen Rasmussen tho...@gibfest.dk wrote
in 4e97d9f3.4020...@gibfest.dk:
th On 14.10.2011 08:14, Hiroki Sato wrote:
th telnet www.freebsd.org 80 /dev/null
th [tykling@tykburk ~]$ telnet www.freebsd.org 80 /dev/null
th Trying 69.147.83.34...
th Connected to red.freebsd.org.
th Escape
On 14-10-2011 10:09, Hiroki Sato wrote:
Thanks. There is no problem with the source address selection. The
last questions are:
% route get -inet www.freebsd.org
[tykling@tykburk ~]$ route get -inet www.freebsd.org
route to: red.freebsd.org
destination: default
mask: default
On Fri Oct 14 11, Nikolay Denev wrote:
On Oct 13, 2011, at 9:40 PM, Arnaud Lacombe wrote:
Hi,
On Thu, Oct 13, 2011 at 2:00 PM, lacom...@gmail.com wrote:
From: Arnaud Lacombe lacom...@gmail.com
Hi folks,
There is many case recently when I really wished timestamp were
In message 20111014085609.ga3...@freebsd.org, Alexander Best writes:
1) would it be possible to prepend those timestamps to the actual console
output and not only to the output of demsg? maybe via a sysctl toggle?
The kernel does not know enough about timezones to emit anything
but UTC
On Fri Oct 14 11, Poul-Henning Kamp wrote:
In message 20111014085609.ga3...@freebsd.org, Alexander Best writes:
1) would it be possible to prepend those timestamps to the actual console
output and not only to the output of demsg? maybe via a sysctl toggle?
The kernel does not know enough
On Fri Oct 14 11, Alexander Best wrote:
On Fri Oct 14 11, Poul-Henning Kamp wrote:
In message 20111014085609.ga3...@freebsd.org, Alexander Best writes:
1) would it be possible to prepend those timestamps to the actual console
output and not only to the output of demsg? maybe via a sysctl
On Fri Oct 14 11, Alexander Best wrote:
On Fri Oct 14 11, Poul-Henning Kamp wrote:
In message 20111014085609.ga3...@freebsd.org, Alexander Best writes:
1) would it be possible to prepend those timestamps to the actual console
output and not only to the output of demsg? maybe via a sysctl
On Thu, Oct 13, 2011 at 04:11:40PM +0200, Dag-Erling Smørgrav wrote:
Pawel Jakub Dawidek p...@freebsd.org writes:
I'm still in opinion that EWOULDBLOCK and EAGAIN (which is the same
value on FreeBSD) should be converted to EEXIST on pidfile_open()
return.
The historical (and documented)
That's ok, a more aggressive fsck-from-a-rescue-disk strategy managed
to clean things up.
J Anderson
On 6 October 2011 15:58, Benjamin Kaduk ka...@mit.edu wrote:
On Thu, 6 Oct 2011, Jonathan Anderson wrote:
On 5 October 2011 23:50, Jonathan Anderson jonat...@freebsd.org wrote:
I was about
On Thursday, October 13, 2011 6:26:26 pm Doug Barton wrote:
On 10/12/2011 08:20, Michael Butler wrote:
SVN r226302 solves the ichwd failure to attach issue ..
Still failing for me:
ichwd0: Intel ICH10DO watchdog timer on isa0
ichwd0: unable to reserve GCS registers
device_attach: ichwd0
Pawel Jakub Dawidek p...@freebsd.org writes:
After proposed changes it would look like this, what do you think?
http://people.freebsd.org/~pjd/patches/pidfile.3.patch
Looks OK to me, but you should also remove the paragraph about EAGAIN in
the man page.
DES
--
Dag-Erling Smørgrav -
Alexander Best arun...@freebsd.org writes:
On Fri Oct 14 11, Poul-Henning Kamp wrote:
In message 20111014085609.ga3...@freebsd.org, Alexander Best writes:
1) would it be possible to prepend those timestamps to the actual console
output and not only to the output of demsg? maybe via a
On Oct 14, 2011, at 12:51 AM, Andriy Gapon wrote:
on 30/08/2011 13:01 Andriy Gapon said the following:
So, just to re-iterate, I think that this is indeed a regression and the one
that could be particularly unhelpful for a new release - the time when people
are much more likely to end up
on 14/10/2011 16:37 Marcel Moolenaar said the following:
On Oct 14, 2011, at 12:51 AM, Andriy Gapon wrote:
on 30/08/2011 13:01 Andriy Gapon said the following:
So, just to re-iterate, I think that this is indeed a regression and the one
that could be particularly unhelpful for a new
That's what most people think.
Hi!
I would like to say that most freebsd users don't try CURRENT, but try
BETAs-x, RCs-x.
Why? Because most users don't like compile new kernel and world. It's
tediously.
You need to download a CURRENT snapshot iso, to install, csup, and then to
build kernel and
Andry Gapon wrote:
Simple: revert to the previous behavior. If a user enters incorrect device
name
(i.e. root mounting fails), then return back to the prompt instead of panicing.
That should do the job.
- Arnaud
---
sys/kern/vfs_mountroot.c | 45
Hi,
On Fri, Oct 14, 2011 at 11:54 AM, Arnaud Lacombe lacom...@gmail.com wrote:
Andry Gapon wrote:
Simple: revert to the previous behavior. If a user enters incorrect device
name
(i.e. root mounting fails), then return back to the prompt instead of
panicing.
That should do the job.
On Fri, Oct 14, 2011 at 11:55:28AM +0400, Pavel Timofeev wrote:
That's what most people think.
Could be. But to the extent that it's true, I have no reason to believe
that it's a perspective that is held uniquely (or even principally) about
FreeBSD.
Hi!
I would like to say that most
Hi,
On Fri, Oct 14, 2011 at 8:52 AM, Nali Toja nalit...@gmail.com wrote:
Alexander Best arun...@freebsd.org writes:
On Fri Oct 14 11, Poul-Henning Kamp wrote:
In message 20111014085609.ga3...@freebsd.org, Alexander Best writes:
1) would it be possible to prepend those timestamps to the
Hi,
On Fri, Oct 14, 2011 at 12:05 PM, David Wolfskill da...@catwhisker.org wrote:
On Fri, Oct 14, 2011 at 11:55:28AM +0400, Pavel Timofeev wrote:
That's what most people think.
Could be. But to the extent that it's true, I have no reason to believe
that it's a perspective that is held
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/14/11 04:35, John Baldwin wrote:
On Thursday, October 13, 2011 6:26:26 pm Doug Barton wrote:
On 10/12/2011 08:20, Michael Butler wrote:
SVN r226302 solves the ichwd failure to attach issue ..
Still failing for me:
ichwd0: Intel ICH10DO
Hi,
On Fri, 14 Oct 2011 17:09:11 +0900 (JST)
Hiroki Sato h...@freebsd.org said:
hrs Thomas Steen Rasmussen tho...@gibfest.dk wrote
hrs in 4e97d9f3.4020...@gibfest.dk:
th On 14.10.2011 08:14, Hiroki Sato wrote:
hrs th telnet www.freebsd.org 80 /dev/null
th [tykling@tykburk ~]$ telnet
On 10/14/2011 10:35, Xin LI wrote:
On 10/14/11 04:35, John Baldwin wrote:
On Thursday, October 13, 2011 6:26:26 pm Doug Barton wrote:
On 10/12/2011 08:20, Michael Butler wrote:
SVN r226302 solves the ichwd failure to attach issue ..
Still failing for me:
ichwd0: Intel ICH10DO watchdog
On Friday, October 14, 2011 1:35:19 pm Xin LI wrote:
On 10/14/11 04:35, John Baldwin wrote:
On Thursday, October 13, 2011 6:26:26 pm Doug Barton wrote:
On 10/12/2011 08:20, Michael Butler wrote:
SVN r226302 solves the ichwd failure to attach issue ..
Still failing for me:
ichwd0:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/14/11 10:58, John Baldwin wrote:
On Friday, October 14, 2011 1:35:19 pm Xin LI wrote:
On 10/14/11 04:35, John Baldwin wrote:
On Thursday, October 13, 2011 6:26:26 pm Doug Barton wrote:
On 10/12/2011 08:20, Michael Butler wrote:
SVN
On Wed, 5 Oct 2011, Ian FREISLICH wrote:
In no particular order:
It's a shame that nobody has yet picked up on this, it is a very useful
list of bugs in 9.0. Is there any chance you could log these three issues
as three separate PRs so that they don't get lost? Please tag them with
On 10/14/2011 12:03, Xin LI wrote:
Hmm, is your isab device behind a PCI-PCI bridge?
Me either:
isab0: PCI-ISA bridge at device 31.0 on pci0
isa0: ISA bus on isab0
--
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
Breadth of IT
I'm planning commit this -CURRENT if there an no objections.
In the current implementation, phandle is used to store a pointer to
the location inside the device tree. Since phandle_t is u32, this
will not work on 64 bit platforms. With this fix, the phandle is the
offset from the start of device
On Friday, October 14, 2011 3:03:00 pm Xin LI wrote:
On 10/14/11 10:58, John Baldwin wrote:
On Friday, October 14, 2011 1:35:19 pm Xin LI wrote:
On 10/14/11 04:35, John Baldwin wrote:
On Thursday, October 13, 2011 6:26:26 pm Doug Barton wrote:
On 10/12/2011 08:20, Michael Butler wrote:
On 10/14/2011 10:38, Hajimu UMEMOTO wrote:
AFAIK, recent Firefox implements Happy Eyeballs. So, I suspect it
doesn't obey RFC 3484, anymore.
My understanding is that they added it, then turned it off because it
didn't work as expected.
--
Nothin' ever doesn't change, but nothin'
On 14/10/2011 19:58, Gavin Atkinson wrote:
3. PF doesn't expire state. The state table on my older host (pre
OpenBSD-4.5) has the following stats:
Status: Enabled for 0 days 00:37:17 Debug: Urgent
State Table Total Rate
On 10/14/11 14:10, Jayachandran C. wrote:
I'm planning commit this -CURRENT if there an no objections.
In the current implementation, phandle is used to store a pointer to
the location inside the device tree. Since phandle_t is u32, this
will not work on 64 bit platforms. With this fix, the
On Fri, Oct 14, 2011 at 10:55 AM, Pavel Timofeev tim...@gmail.com wrote:
That's what most people think.
I think we hurry. Imo, BETA/RC period for !NEW! STABLE branch should be
longer. Six months, for example.
New STABLE branch is very important!
IMHO different OS releases (Unix or not) are
38 matches
Mail list logo
