On 10/03/2012 08:52 PM, Genes MailLists wrote:
...
https://lkml.org/lkml/2012/10/2/194
For those not following the entire thread - there seems to be some
debate about firmware loading in udev vs in kernel space and some recent
changes leading to some problems. Best I can tell, while there
[2012-10-03 12:01:55 +1000] Allan McRae:
> All post to the mailing list are now moderated. As this takes time away
> from us actually maintaining the distribution, this will only occur
> intermittently.
I have disabled full list moderation but turned on everyone's moderation
bit. Therefore, the n
There is also some noise around udev as well and firmware loading:
https://lkml.org/lkml/2012/10/2/194
(it's a bit of a long thread)
gene
On 03/10/12, Thomas Bächler wrote:
| First of all, once you add the mdadm.conf file, the mdX names will
| follow the naming usual scheme - the md126+ names will only be used when
| the array is not mentioned in mdadm.conf.
|
| Second, you can always use /dev/disk/by-uuid/.
Cool, makes sense, and
> On 03/10/12, Thomas B?chler wrote:
>
>> You need to create a file /etc/mdadm.conf. mdadm --examine --scan will
>> generate the right lines for you. This file will be added to the
>> initramfs and your names will be fine again.
>
> Yep, that's what I've done, and I've used the mdadm hook as I ha
I have not been hit by this - but there is some buzz around the
symlink security addition - see this thread for more details:
https://lkml.org/lkml/2012/10/3/473
gene
Am 03.10.2012 22:07, schrieb Simon Perry:
> Based on the mkinitcpio wiki page, and the forum post, I'm under the
> impression that using mdadm_udev to auto-assemble the arrays is what I
> should be using (and is what will be supported in the future).
>
> The mdadm_udev hook does work as advertised
On 03/10/12, Thomas Bächler wrote:
| You need to create a file /etc/mdadm.conf. mdadm --examine --scan will
| generate the right lines for you. This file will be added to the
| initramfs and your names will be fine again.
Yep, that's what I've done, and I've used the mdadm hook as I have in the
p
On 03/10/12||07:33, Genes MailLists wrote:
>
> kernel 3.6-1 testing report:
>
> I am running 3.6 from testing on 3 machines. 1 laptop and 2
> desktops. All are fully updated from testing repo.
>
> 1 of the desktop didn't come up right - seemed to have trouble
> with root filesystem (initis
I'm suffering from this regression:
https://lkml.org/lkml/2012/9/26/53
https://bugzilla.kernel.org/show_bug.cgi?id=47961
which causes my HDA intel sound to be distorted and cracky. Reverting
the change mentioned in the LKML thread fixes it. I already mailed the
Arch linux kernel maintainer about
On Wed, Oct 3, 2012 at 4:40 PM, mike cloaked wrote:
> Today I tried to update with pacman -Syu
>
> I got this:
> :: Starting full system upgrade...
> resolving dependencies...
> warning: cannot resolve "kdegames-knavalbattle", a dependency of
> "kde-meta-kdegames"
> warning: cannot resolve "kdegam
Today I tried to update with pacman -Syu
I got this:
:: Starting full system upgrade...
resolving dependencies...
warning: cannot resolve "kdegames-knavalbattle", a dependency of
"kde-meta-kdegames"
warning: cannot resolve "kdegames-ksnakeduel", a dependency of
"kde-meta-kdegames"
:: The following
Hey everyone!
It's that time again for arch to get the latest ghc!
GHC 7.6.1 comes with a bunch of new and exciting features:
http://www.haskell.org/ghc/docs/7.6.1/html/users_guide/release-7-6-1.html
This morning, all the haskell packages should have been rebuilt
against the latest ghc and I have
On Wed, Oct 3, 2012 at 12:33 PM, Genes MailLists wrote:
>
> kernel 3.6-1 testing report:
>
> I am running 3.6 from testing on 3 machines. 1 laptop and 2 desktops. All
> are fully updated from testing repo.
>
> 1 of the desktop didn't come up right - seemed to have trouble with root
> filesys
Am 03.10.2012 14:41, schrieb Simon Perry:
> Hi,
>
> I've just been re-installing a box, and saw that the wiki says regarding
> using the mdadm_udev hook:
>
>> "This is the preferred method of mdadm assembly (rather than using the
>> above mdadm hook). "
>
> I've tried to use the mdadm_udev hook,
Hi,
I've just been re-installing a box, and saw that the wiki says regarding
using the mdadm_udev hook:
> "This is the preferred method of mdadm assembly (rather than using the
> above mdadm hook). "
I've tried to use the mdadm_udev hook, but the devices get named:
> normal md0 (/boot)
kernel 3.6-1 testing report:
I am running 3.6 from testing on 3 machines. 1 laptop and 2 desktops.
All are fully updated from testing repo.
1 of the desktop didn't come up right - seemed to have trouble with
root filesystem (initiscripts still not systemd). On second reboot it
came up
[spinymouse@archlinux ~]$ uname -a
Linux archlinux 3.5.5-1-ARCH #1 SMP PREEMPT Tue Oct 2 22:30:55 CEST 2012 x86_64
GNU/Linux
I get two waiting periods at startup, one short waiting period regarding
to ATA not ready and a relatively long waiting period for raw EDIT.
Apart from that everything star
18 matches
Mail list logo
