Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-embedded
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
To: gentoo-embedded@g.o
From: Sebastian Rodriguez <sniper.mdr@...>
Subject: Re: GUI for development - kembeddedgentoo
Date: Tue, 26 Jul 2005 08:29:10 +0200
<div>Thats a great idea. </div>
<div>You can also add the part of fdisk / installing mbr in your gui, wich would be used with a sudo for example. just an idea thought<br><br>&nbsp;</div>
<div><span class="gmail_quote">On 7/25/05, <b class="gmail_sendername">Heath Holcomb</b> &lt;<a href="mailto:liquidcable@...">liquidcable@...</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I'm writing a little QT/KDE based app to automate some of the basic commands<br>for build the x86 development rootfs and embedded rootfs.&nbsp;&nbsp;I'm using the x86
<br>how-to, comand by command (at least were I can).&nbsp;&nbsp;I got a preview of the GUI<br>(not finished yet, of course) at my site:<br><a href=""></a>
<br><br>Just thought I would let everyone know.<br><br>latter,<br><br>--<br>heath holcomb<br>liquidcable at <a href=""></a><br><a href=""></a><br>--<br><a href="mailto:gentoo-embedded@g.o">
gentoo-embedded@g.o</a> mailing list<br><br></blockquote></div><br><br clear="all"><br>-- <br>S├ębastien Rodriguez 
GUI for development - kembeddedgentoo
-- Heath Holcomb
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
GUI for development - kembeddedgentoo
Next by thread:
GNAP livecd-stage2 packages build problem
Previous by date:
Re: GNAP livecd-stage2 packages build problem
Next by date:
Re: Cross-dev sys-devel/gdb?

Updated Jun 17, 2009

Summary: Archive of the gentoo-embedded mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.