Am 05.07.2013 04:28, schrieb Frank Peters:
My interpretation of this message in the nvidia-drivers ebuild is that
the maintainers assume that you switch to nouveau.
I think it means that the problem occurs so frequently that they
do not want to be bothered with bug reports -- and rightly
Am 01.07.2013 22:35, schrieb Frank Peters:
When I encountered this failure I expected that a huge outcry of bug reports
would ensue, but so far things have been rather quiet. There are only a few
postings of this problem with 3.10-rc1 and not much else.
Well, read the messages on the screen
My interpretation of this message in the nvidia-drivers ebuild is that
the maintainers assume that you switch to nouveau.
I think it means that the problem occurs so frequently that they
do not want to be bothered with bug reports -- and rightly so.
My great disappointment is that xorg or
Frank Peters posted on Mon, 01 Jul 2013 15:35:42 -0400 as excerpted:
Kernel-3.10 has just been released and I quickly grabbed the source and
compiled. I usually have no problems with a new kernel but this time
there were a few surprises.
First, there is a new kernel option called Kernel
On Tue, 2 Jul 2013 11:29:47 + (UTC)
Duncan 1i5t5.dun...@cox.net wrote:
First, there is a new kernel option called Kernel support for scripts
starting with #!.
And no, as you found out it's *NOT* initramfs-only. It's basic kernel
functionality that been assumed for (I guess)
Frank Peters posted on Tue, 02 Jul 2013 12:54:54 -0400 as excerpted:
(Thanks for the insight into your more direct boot scripts. I've done
that with some things here, including with my own custom suspend/
hibernate scripts, but not with my bootscripts.)
So what does the #! option accomplish?
