We all know the situation with dcron (it can't keep time properly) and
it still is broken. No fix (or any changes for that matter) have gone
into its upstream git for over a year now. There have been multiple
yeah-I'll-take-a-looks from various people as well as its upstream
maintainer and no work
On 04/04/2011 05:01 AM, Matthew Gyurgyik wrote:
> On 04/04/2011 12:04 AM, Brendan Long wrote:
>> On 03/27/2011 01:47 AM, KESHAV P.R. wrote:
>>> On a side note, I think it is also useful to have GPT
>>> partitioning as default now since it is way superior to MBR (see
>>> logical partitions linked-li
Hey all,
A heads up for anyone using systemd, I've just pushed the latest tag to
[community-testing]. It's going to be hanging out there until we at
least see udev-167. More notably, there's been a fairly silly change [1]
in place that will muck up the formatting of log facilities in dmesg and
sys
On Mon, 4 Apr 2011, Tobias Powalowski wrote:
> Just out of interest, are you only booting this kernel with lilo or
> others too?
>
>> I forgot to mention that the previous kernel 2.6.38.1-1 LILO can use.
I booted 2.6.38.2-1 with syslinux, it went fine.
--
Adrian C. (anrxc) | anrxc..sysphere.or
On 04/04/2011 03:08 PM, Adrian C. wrote:
On Mon, 4 Apr 2011, Matthew Gyurgyik wrote:
> I don't think Lilo should be a show stopper. Use a more modern
> bootloader such as Syslinux (if you want simple), Grub 1 or Grub 2.
Modern, like grub? LILO is in [core], and is actively being developed.
It
On Mon, 4 Apr 2011, Adrian C. wrote:
> > Just out of interest, are you only booting this kernel with lilo or
> > others too?
>
> Just LILO, I haven't tried grub, but did wrote a menu.lst in advance
> if I had to.
Sorry, for the second time I forgot to mention that the previous kernel
2.6.38.1
On Mon, 4 Apr 2011, Matthew Gyurgyik wrote:
> I don't think Lilo should be a show stopper. Use a more modern
> bootloader such as Syslinux (if you want simple), Grub 1 or Grub 2.
Modern, like grub? LILO is in [core], and is actively being developed.
It was also a part of the Arch installation f
On Mon, Apr 4, 2011 at 5:35 PM, Heiher wrote:
> Hello,
>
> Could you tell me why gtk3-engines doesn't work? Seems the gtk3 not
> load it by 'strace'.
>
> --
> Best regards!
> Heiher
>
Hello,
Wrong ML. This package is in AUR.
Regards,
--
Cédric Girard
Hello,
Could you tell me why gtk3-engines doesn't work? Seems the gtk3 not
load it by 'strace'.
--
Best regards!
Heiher
Hi,
The current packages for eina, evas, ecore, etc in community are -svn, and
since the enlightenment team released the 1.0 (
http://www.enlightenment.org/p.php?p=news/show&l=en&news_id=28) and later
the 1.0.1 (http://www.enlightenment.org/p.php?p=news/show&l=en&news_id=29)
version of their toolki
Am Montag 04 April 2011 schrieb Adrian C.:
> On Thu, 31 Mar 2011, Tobias Powalowski wrote:
> > Hi guys,
> > please signoff 2.6.38 series for both arches.
>
> Can't signoff i686. LILO can not boot it.
>
> # /sbin/lilo -v
> ...
> Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite b
On Mon, 4 Apr 2011 10:08:09 +0200, Adrian C. wrote:
On Thu, 31 Mar 2011, Tobias Powalowski wrote:
Hi guys,
please signoff 2.6.38 series for both arches.
Can't signoff i686. LILO can not boot it.
# /sbin/lilo -v
...
Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite
boot loae
I installed vim-peaksea from the AUR the other day and couldn't use
it, because it installed in /usr/share/vim/colors/peaksea.vim. This
seems a fairly standard directory, but its not in runtimepath on a
fresh install (AFAIK).
Checked out some other vim colour-themes on the AUR, the majority seem
t
Heiko Baums wrote:
>
> Not a good idea. Syslinux doesn't work on multiboot systems and grub2
> is not marked as stable as far as I know.
>
No version of GRUB legacy has ever been marked as stable either.
Its been marked as alpha software from its inception, until its
deprecation in favour of GRUB2
On 04/04/2011 12:04 AM, Brendan Long wrote:
On 03/27/2011 01:47 AM, KESHAV P.R. wrote:
On a side note, I think it is also useful to have GPT
partitioning as default now since it is way superior to MBR (see
logical partitions linked-list info) and supports multiple primary
partitions.
I'm not su
Am Mon, 4 Apr 2011 14:07:03 +0530
schrieb "KESHAV P.R." :
> I want your opinion regarding whether grub-legacy (core/grub)
> package should be deprecated (downgrade it to extra/community/AUR) now
> that syslinux is in core.
Not a good idea. Syslinux doesn't work on multiboot systems and g
grub legacy is all that will install on my amd k8 computer for some
strange reason at least according to debian when I try upgrading grub.
On Mon, 4 Apr 2011, KESHAV P.R. wrote:
> Hi all,
> I want your opinion regarding whether grub-legacy (core/grub)
> package should be deprecated (dow
Hi all,
I want your opinion regarding whether grub-legacy (core/grub)
package should be deprecated (downgrade it to extra/community/AUR) now
that syslinux is in core. THe actual upstream has been dead for 4
years and every fork (grub4dos, super grub disk, grub-fedora) is
either lacking in
On Thu, 31 Mar 2011, Tobias Powalowski wrote:
> Hi guys,
> please signoff 2.6.38 series for both arches.
Can't signoff i686. LILO can not boot it.
# /sbin/lilo -v
...
Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite boot loaer
Machines would be left in a constant state of reb
19 matches
Mail list logo
