On Fri, Jul 5, 2013 at 9:26 PM, Thomas Bächler wrote:
> Am 05.07.2013 21:22, schrieb Karol Blazewicz:
>> Should I open a bug report?
>> If you don't plan on fixing it immediately, please post a message on
>> arch-dev-public, because not everyone is reading arch-general even
>> though this seems to
Am 05.07.2013 21:22, schrieb Karol Blazewicz:
> Should I open a bug report?
> If you don't plan on fixing it immediately, please post a message on
> arch-dev-public, because not everyone is reading arch-general even
> though this seems to be only an annoyance, not a system-breaking bug.
This shoul
On Fri, Jul 5, 2013 at 8:26 PM, Thomas Bächler wrote:
> Am 05.07.2013 20:24, schrieb Karol Blazewicz:
>> I'm using syslinux for my bootloader. I'm using BIOS, not UEFI, on a
>> 32-bit system.
>> After updating syslinux 5.10-3 -> 6.01-1 the modules' symlinks in
>> /boot/syslinux didn't get updated
Am 05.07.2013 20:24, schrieb Karol Blazewicz:
> I'm using syslinux for my bootloader. I'm using BIOS, not UEFI, on a
> 32-bit system.
> After updating syslinux 5.10-3 -> 6.01-1 the modules' symlinks in
> /boot/syslinux didn't get updated and still point to
> /usr/lib/syslinux/ instead of to /usr/li
I'm using syslinux for my bootloader. I'm using BIOS, not UEFI, on a
32-bit system.
After updating syslinux 5.10-3 -> 6.01-1 the modules' symlinks in
/boot/syslinux didn't get updated and still point to
/usr/lib/syslinux/ instead of to /usr/lib/syslinux/bios e.g. menu.c32
-> /usr/lib/syslinux/menu.
On Thu, Jul 4, 2013 at 7:54 PM, F. Gr. wrote:
> Hi,
> I've noticed that there are some warning during the halt/reboot
> process. How can I read these messages?
>
https://bbs.archlinux.org/viewtopic.php?id=164545
On Jul 5, 2013 3:40 AM, "Oon-Ee Ng" wrote:
>
> On Fri, Jul 5, 2013 at 12:56 AM, Dave Reisner wrote:
> > On Wed, Jul 03, 2013 at 02:44:12PM -0400, Dave Reisner wrote:
> >> On Wed, Jul 03, 2013 at 12:48:49PM -0400, Dave Reisner wrote:
> >> > Hey all,
> >> >
> >> > systemd 205 was just tagged, and b
7 matches
Mail list logo