Re: [arch-general] [arch-releng] Default Bootloader for AIF

2011-03-29 Thread David Campbell
Excerpts from Dieter Plaetinck's message of 2011-03-28 12:06:21 -0400:
> Hmm, and does it have a proper UI in ncurses or something? to replace
> cfdisk in aif?

It will when cparted is proper. Whether cparted will be ported to
use libparted directly, rather than using Python bindings, is yet
to be seen. I certainly prefer writing/maintaining Python code
over C though, and I don't see any benefit to translating it into
C other than avoiding Python as a dependency.

> I know about the newt-based nparted but I'm told it's badly maintained.

As far as I could tell, nparted is dead.
-- 
David Campbell


Re: [arch-general] Display "Flicker" with 2.6.37.5-1 & nvidia 270.30-3 (dual head)

2011-03-29 Thread Heiko Baums
Am Tue, 29 Mar 2011 07:07:39 +0900
schrieb Jason Melton :

> It may be a card-specific or similar issue?

Is it probably related to this bug?
https://bugs.archlinux.org/task/22967

Heiko


Re: [arch-general] [arch-releng] Partition tools in AIF (was: Default Bootloader for AIF)

2011-03-29 Thread KESHAV P.R.
On Tue, Mar 29, 2011 at 15:07, David Campbell  wrote:
> Excerpts from Dieter Plaetinck's message of 2011-03-28 12:06:21 -0400:
>> Hmm, and does it have a proper UI in ncurses or something? to replace
>> cfdisk in aif?
>
> It will when cparted is proper. Whether cparted will be ported to
> use libparted directly, rather than using Python bindings, is yet
> to be seen. I certainly prefer writing/maintaining Python code
> over C though, and I don't see any benefit to translating it into
> C other than avoiding Python as a dependency.
>

Instead of duplicating efforts, you can try hacking on
http://www.gnu.org/software/fdisk/ which uses libparted as backend
(fdisk and cfdisk present but no sfdisk though). That project is
inactive but not discontinued.

>> I know about the newt-based nparted but I'm told it's badly maintained.
>
> As far as I could tell, nparted is dead.
> --
> David Campbell
>

Regards.

Keshav


Re: [arch-general] Removing network utilities from base group?

2011-03-29 Thread Grigorios Bouzakis
Daniel Isenmann wrote:
> Hi,
>
> I have a feature request (https://bugs.archlinux.org/task/22481) since 
> January which stated that rp-pppoe should be removed from the base 
> group. Described in the details he stated that every network package 
> should be removed from the base group and should only be in core.
>
> I'm not really have a opinion to that topic, so what do you think about 
> it? For me we can leave it as it is and do nothing at this topic, then I 
> will close this feature request as "won't implement".
>
>   -Daniel
>

My own plan, originally brain0's but i adopted it and probably extended
it as well, has been fully implementing https://bugs.archlinux.org/task/12890
Nevermind that its closed now, its only half done as far as i am concerned.
Eventually make every package of core, besides the library dependencies,
be part of a group, like base, base-networking etc. I dont know how much
of a realistic plan it still is today, but i intend to look at it at
some point. And that was part of the reason i opened those feature
requests (theres similar ones for ppp, wpa_supplicant and dash as well).

The core repo keeps growing and growing. Bootloaders, file system support
utilities, dependencies like libedit get added. Yet the installer has
only 1 package selection dialogue with all the applications.
That works fine for packages in base and base-devel which are tagged as such,
but not so much for the other packages which dont belong in a group, and
especially libraries which are nothing more than dependencies to other packages.
The installer has changed lately and from what i've read it includes the
description of the packages.I had opened https://bugs.archlinux.org/task/12942
at the time about adding a seperate selection dialogue for each group, but i
havent seen the new installer in action so i dont know if any of the above
still apply, but that was my initial motivation from what i can
remember.


Greg


Re: [arch-general] New Kernel - Virtualbox VM kernel crash on shutdown

2011-03-29 Thread Aljosha Papsch
David C. Rankin wrote:

>Guys,

>
>  kernel26-2.6.37.5-1 running in a virtualbox vm is causing a kernel crash on 
>shutdown. The full screen of the crash is here:
>
> http://www.3111skyline.com/dl/arch/bugs/kernel/vbox-crash-on-shutdown.jpg
>
> The Call Trace: shows the likes of:
>
> shrink_dcache_for_unmount_subtree
> shrink_dcache_for_unmount
> generic_shutdown_super
> 
>
>  I'm not great at reading the screens, so if you are interested in the full 
>error, it is shown in the link about.
>
>  Has anyone else found a workaround?
>
> -- David C. Rankin, J.D.,P.E.

Are you sure it's a kernel bug? Your screen says segmentation fault in umount, 
so there must be some bug in that tool, not linux. Also, if the kernel panicks, 
the system won't shutdown at all.
BTW, I recommend using png files instead of jpg. :)



Re: [arch-general] New Kernel - Virtualbox VM kernel crash on shutdown

2011-03-29 Thread C Anthony Risinger
On Tue, Mar 29, 2011 at 10:38 AM, Aljosha Papsch  wrote:
> David C. Rankin wrote:
>
>>Guys,
>
>>
>>  kernel26-2.6.37.5-1 running in a virtualbox vm is causing a kernel crash on
>>shutdown. The full screen of the crash is here:
>>
>> http://www.3111skyline.com/dl/arch/bugs/kernel/vbox-crash-on-shutdown.jpg
>>
>> The Call Trace: shows the likes of:
>>
>> shrink_dcache_for_unmount_subtree
>> shrink_dcache_for_unmount
>> generic_shutdown_super
>> 
>>
>>  I'm not great at reading the screens, so if you are interested in the full
>>error, it is shown in the link about.
>>
>>  Has anyone else found a workaround?
>>
>> -- David C. Rankin, J.D.,P.E.
>
> Are you sure it's a kernel bug? Your screen says segmentation fault in umount,
> so there must be some bug in that tool, not linux. Also, if the kernel 
> panicks,
> the system won't shutdown at all.
> BTW, I recommend using png files instead of jpg. :)

doesn't vbox have to be rebuilt everytime the kernel changes or
something?  or the guest additions?  or both?

btw, have you tried KVM + libvirt[virtmanager/]?  there are a lot of great options out there now -- i
haven't had a single issue with my local KVM setup, and am in the
process of moving my companies infrastructure to it as well (+ some
LXC goodness) ... when i used vbox it was nice, but ... yeah :-)

... libvirt can handle vbox images in transition, too; just an idea,
it's been good to me.

C Anthony


Re: [arch-general] New Kernel - Virtualbox VM kernel crash on shutdown

2011-03-29 Thread Paulo Santos
C Anthony Risinger wrote:
> 
> btw, have you tried KVM + libvirt[virtmanager/ good webapps>]?  there are a lot of great options out there now -- i
> haven't had a single issue with my local KVM setup, and am in the
> process of moving my companies infrastructure to it as well (+ some
> LXC goodness) ... when i used vbox it was nice, but ... yeah :-)
> 

OT:

Just to vouch for KVM + libvirt (and virtmanager). Implemented it in my
company a month or so ago, longer ago personally, and works like a charm. :)

Paulo Santos


Re: [arch-general] New Kernel - Virtualbox VM kernel crash on shutdown

2011-03-29 Thread Heiko Baums
Am Tue, 29 Mar 2011 12:26:41 -0500
schrieb C Anthony Risinger :

> doesn't vbox have to be rebuilt everytime the kernel changes or
> something?  or the guest additions?  or both?

When using virtualbox `/etc/rc.d/vboxdrv setup` has to be run after
every kernel update on the host system.

And on the guest systems the guest additions have to be updated, too.

Heiko


Re: [arch-general] New Kernel - Virtualbox VM kernel crash on shutdown

2011-03-29 Thread David C. Rankin

On 03/29/2011 12:26 PM, C Anthony Risinger wrote:

doesn't vbox have to be rebuilt everytime the kernel changes or
something?  or the guest additions?  or both?


Oh, yes,

  If not rebuilt - you won't be able to get the
 started. Here, the vm runs, but there are shared folder issues and it crashes 
on shutdown.


  This all *started* with kernel26-3.7.4. I can reload kernel26-3.7.3 and all 
is good. There is something new that vbox doesn't like...


--
David C. Rankin, J.D.,P.E.


Re: [arch-general] New Kernel - Virtualbox VM kernel crash on shutdown

2011-03-29 Thread David C. Rankin

On 03/29/2011 06:56 PM, David C. Rankin wrote:

On 03/29/2011 12:26 PM, C Anthony Risinger wrote:

doesn't vbox have to be rebuilt everytime the kernel changes or
something? or the guest additions? or both?


Oh, yes,

If not rebuilt - you won't be able to get the
started. Here, the vm runs, but there are shared folder issues and it crashes on
shutdown.

This all *started* with kernel26-3.7.4. I can reload kernel26-3.7.3 and all is
good. There is something new that vbox doesn't like...



And just to be clear -- this is Arch installed as the "guest". There is 
something that is causing problems with Arch running inside vbox with 
kernel26-2.7.4 and kernel26-2.7.5.


Sorry for the "3" kernel typos above :p

--
David C. Rankin, J.D.,P.E.


Re: [arch-general] New Kernel - Virtualbox VM kernel crash on shutdown

2011-03-29 Thread Isaac Dupree

On 03/29/11 20:00, David C. Rankin wrote:

On 03/29/2011 06:56 PM, David C. Rankin wrote:

On 03/29/2011 12:26 PM, C Anthony Risinger wrote:

doesn't vbox have to be rebuilt everytime the kernel changes or
something? or the guest additions? or both?


Oh, yes,

If not rebuilt - you won't be able to get the
started. Here, the vm runs, but there are shared folder issues and it
crashes on
shutdown.

This all *started* with kernel26-3.7.4. I can reload kernel26-3.7.3
and all is
good. There is something new that vbox doesn't like...



And just to be clear -- this is Arch installed as the "guest". There is
something that is causing problems with Arch running inside vbox with
kernel26-2.7.4 and kernel26-2.7.5.

Sorry for the "3" kernel typos above :p


Kernel versions resemble 2.6.33.2.  Or kernel26 package versions 
resemble 2.6.33.2-1 .  Your typoes are much worse than 2 vs 3. :-D


Re: [arch-general] New Kernel - Virtualbox VM kernel crash on shutdown

2011-03-29 Thread David C. Rankin

On 03/29/2011 07:25 PM, Isaac Dupree wrote:

Sorry for the "3" kernel typos above :p


Kernel versions resemble 2.6.33.2.  Or kernel26 package versions resemble
2.6.33.2-1 .  Your typoes are much worse than 2 vs 3. :-D


Oh God -- and I've been doing the books today  :)

--
David C. Rankin, J.D.,P.E.