Hello,
I want to remind to the kern/132934-PR. Are we the only ones that have
Problems with the NFS-Locking? I try every week the latest -STABLE
code but nothing changed so far.
Are there any chances to get NFS-locking working with HP-UX 11.11
machines again with 7.2-RELEASE?
Greetings
On Thu, 16 Apr 2009 16:32:09 GMT
p...@citylink.dinoex.sub.org (Peter Much) wrote:
> Every time I switch from X to a virtual console and back, I get
> some characters dropped into my command-line in the X window,
> and have to delete them with the backspace key.
> These characters read: ^[[20~
>
>
On Tue, 14 Apr 2009 20:52:38 +1000, Andrew MacIntyre wrote
> Michal Varga wrote:
> > 2009/4/13 :
> >> Yes, I'm 100% positive I tried plugging mouse after the boot up had
> >> finished. Honestly I am late asking here. I was struggling with
> >> this and looking for cases online for more than 2 week
Hi all,
to make a long story short, I got trapped in the Xorg upgrade
problems (concerning HAL etc.) that were widely reported during
January.
After reading thru the material I figured out that there are
not much chances that somebody would take effort and fix these
things for a 6.3 Release.
So
Hi folks, hi Freddy,
sorry, missed Your note last year this time.
aka Freddie Cash schrieb
mit Datum Wed, 26 Mar 2008 14:04:00 -0700 in m2n.fbsd.stable:
|On March 22, 2008 01:01 pm Peter Much wrote:
|> Both of them were running Release 5.5, and they were doing all that
|> is needed, and I was
Maxim Sobolev wrote:
Dennis Melentyev wrote:
Could be worth an entry in UPDATING and/or explicitly added to GENERIC.
My point is that if the option is mandatory for compiling ath(4)
driver, then there is no point in having this option in the first place.
There is an entry in UPDATING and it
2009/4/16 Maxim Sobolev :
> Dennis Melentyev wrote:
>>
>> Could be worth an entry in UPDATING and/or explicitly added to GENERIC.
>
> My point is that if the option is mandatory for compiling ath(4) driver,
> then there is no point in having this option in the first place.
Well, fair.
+1 from me :
Dennis Melentyev wrote:
Could be worth an entry in UPDATING and/or explicitly added to GENERIC.
My point is that if the option is mandatory for compiling ath(4) driver,
then there is no point in having this option in the first place.
-Maxim
___
fre
Hi Max,
Also seen that.
Fixed with careful merging on my kernel config with GENERIC one.
There are additional strings involved:
device ath
device ath_rate_sample
After adding the later one (and probably, the first one too (?)) compiled ok.
Could be worth an entry in UPDATING and/or explicitly add
(Sorry for not directly replying to the thread, just subscribed to the list)
I've had this panic myself, on a system that would run 7.1 for weeks at
a time. More importantly, this is a very standard desktop system with
very simple apps for casual use:
FreeBSD atlantis.dyndns.org 7.2-PRERELEASE Fr
Sam,
What is the reason to have this option in the kernel config if kernel
compilation fails when this option is enabled? It also affects 7-stable.
cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g
-Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prot
Sam,
What is the reason to have this option in the kernel config if kernel
compilation fails when this option is enabled? It also affects 7-stable.
cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g
-Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototyp
12 matches
Mail list logo
