Konstantin Belousov wrote:
>>> On Thu, Dec 27, 2012 at 12:28:54PM +0100, Andreas Longwitz wrote:
>> db> alltrace (pid 18 and 7126)
>>
>> Tracing command g_journal switcher pid 18 tid 100076 td 0xff0002bd5000
>> sched_switch() at sched_switch+0xde
>> mi_switch() at mi_switch+0x186
>> sleepq_wait
On Fri, Dec 28, 2012 at 10:19:31AM +0100, Andreas Longwitz wrote:
> Konstantin Belousov wrote:
> >>> On Thu, Dec 27, 2012 at 12:28:54PM +0100, Andreas Longwitz wrote:
> >> db> alltrace (pid 18 and 7126)
> >>
> >> Tracing command g_journal switcher pid 18 tid 100076 td 0xff0002bd5000
> >> sched_
On Thu, Dec 27, 2012 at 6:07 PM, Jakub Lach wrote:
> xf86-input-mouse-1.8.1 is in dev trunk xorg tree. (see -x11).
This is the only sensible solution to use new driver. HAL and
AllowEmptyInput are EXCLUSIVE and cause very strange behavior - I have
just noticed that again on another desktop - scre
1.8.1 is in staging area (dev trunk). It will be not in packages distributed
with 9.1. They were just apps which happened to be in ports tree
at packages building for release time. There is only one branch of ports.
hal is less and less used/supported and it was never meant to be
used with Allow
On Fri, Dec 28, 2012 at 1:33 PM, CeDeROM wrote:
> On Thu, Dec 27, 2012 at 6:07 PM, Jakub Lach wrote:
>> xf86-input-mouse-1.8.1 is in dev trunk xorg tree. (see -x11).
>
> This is the only sensible solution to use new driver. HAL and
> AllowEmptyInput are EXCLUSIVE and cause very strange behavior -
On Fri, Dec 28, 2012 at 12:42 PM, Kimmo Paasiala wrote:
> You're misunderstanding a few things. There are no "release packages"
> for any release of FreeBSD. What you have on the install discs are
> just "snapshot" packages built from the ports tree as it happened (...)
I know, I hoped 1.7.2 driv
On 9/10/2012 2:05 AM, Kenneth D. Merry wrote:
On Mon, Sep 10, 2012 at 23:09:04 +0930, Benjamin Close wrote:
Hi Folks,
I've facing an intermittent hang with a USB port which seems cam
related:
Event's that happen are:
o USB modem (HUAWEI E220) plugged into PC
ugen3.2: at usbus3
u3g0
On Fri, Dec 28, 2012 at 1:51 PM, CeDeROM wrote:
> On Fri, Dec 28, 2012 at 12:42 PM, Kimmo Paasiala wrote:
>> You're misunderstanding a few things. There are no "release packages"
>> for any release of FreeBSD. What you have on the install discs are
>> just "snapshot" packages built from the ports
On Fri, Dec 28, 2012 at 1:02 PM, Kimmo Paasiala wrote:
> It doesn't look like the FreeBSD ports SVN repository is used to its
> full potential. (...)
Yea, btw why FreeBSD does not use GIT? I have been using it for some
time and I have not seen better source code revision utility. GIT is
really am
On Fri, Dec 28, 2012 at 2:08 PM, CeDeROM wrote:
> On Fri, Dec 28, 2012 at 1:02 PM, Kimmo Paasiala wrote:
>> It doesn't look like the FreeBSD ports SVN repository is used to its
>> full potential. (...)
>
> Yea, btw why FreeBSD does not use GIT? I have been using it for some
> time and I have not
xorg trunk repo predates SVN for ports.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-1-RC3-xorg-input-mouse-xfce4-panel-tp5772549p5772797.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
freebsd-stab
http://wiki.freebsd.org/Git
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-1-RC3-xorg-input-mouse-xfce4-panel-tp5772549p5772798.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
freebsd-stable@freebsd.o
Am Thu, 27 Dec 2012 16:01:43 -0500 (EST)
schrieb Garrett Wollman :
> In article <20121227162311$6...@grapevine.csail.mit.edu>,
> rai...@ultra-secure.de writes:
>
> >I'm creating my own repository and have created a key for it.
> [...]
> >What does pkg expect to be in this file?
>
> A public key.
> What you are seeing is behind-the-scenes preparation.
> The release is official when, and only when, a security-signed email is
> sent to freebsd-annou...@freebsd.org from the Release Engineering team.
Yeah, Mark. You're right.
Further, I'm right too. What should I install on blank
node? Beta? N
On 27/12/2012 21:01, Garrett Wollman wrote:
>> I'm creating my own repository and have created a key for it.
> [...]
>> >What does pkg expect to be in this file?
> A public key. It does not use X.509 (nor is there any reason why it
> should, although I suppose it could be made to at the cost of
>
In an ideal world, the bits that will almost certainly become FreeBSD 9.1
would not appear on the masters, or any of the mirrors, until the same
instant that the release announcement is set to freebsd-annou...@freebsd.org.
In practice this doesn't happen. If there is some clever way for that to
h
On Fri, Dec 28, 2012 at 9:28 AM, Matthew Seaman wrote:
> On 27/12/2012 21:01, Garrett Wollman wrote:
>>> I'm creating my own repository and have created a key for it.
>> [...]
>>> >What does pkg expect to be in this file?
>
>> A public key. It does not use X.509 (nor is there any reason why it
>>
Many months ago, I believe some *very bad hardware* caused corruption of a
file on one of my zfs file systems. I've isolated the corrupted file and
can reliably induce a kernel panic with "touch bad.file", "rm bad.file", or
"ls -l" in the bad.file's directory (ls in bad.file's dir doesn't cause
pa
Konstantin Belousov wrote:
>
> Please try the following patch. It is against HEAD, might need some
> adjustments for 8. I do the resume and write accounting atomically,
> not allowing other suspension to intervent between.
>
> diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c
> index 3f65b
On Fri, Dec 28, 2012 at 12:46 PM, Greg Bonett wrote:
> However, I can't figure out how to destroy the /tank filesystem without
> destroying /tank/tempfs (and the other /tank children). Is it possible to
> destroy a parent without destroying the children? Or, create a new parent
> zfs file system
ahh, unfortunately the filesystem I want to destroy is the top-most file
system for the pool. Does this mean I'll need to set up another pool with
enough free space to move everything over?
Any ideas for a way to remove the corrupted file without destroying the
file system?
thanks!
On Sat, Dec
> It has happened in the past that even as the release bits were propogating,
> One Last Big Bug was found and those bits had to be pulled and re-done. It
> would have looked like you had FreeBSD Release X.Y but you wouldn't have had
> the final bits that everyone else did.
I'm aware of this. I s
On 28 December 2012 04:02, Kimmo Paasiala wrote:
> It doesn't look like the FreeBSD ports SVN repository is used to its
> full potential. SVN allows branching and creation of experimental
> versions of the tree very easily and cheaply, yet all the experimental
> repositories references so far are
On Fri, Dec 28, 2012 at 2:46 PM, Greg Bonett wrote:
> Many months ago, I believe some *very bad hardware* caused corruption of a
> file on one of my zfs file systems. I've isolated the corrupted file and
> can reliably induce a kernel panic with "touch bad.file", "rm bad.file", or
> "ls -l" in th
24 matches
Mail list logo