Mailinglist Archive: opensuse-factory (626 mails)

< Previous Next >
Re: [opensuse-factory] Re: Lime JeOS: The openSUSE based JeOS
  • From: Jordi Massaguer <jordimassaguerpla@xxxxxxxx>
  • Date: Tue, 18 Mar 2008 14:46:16 +0000 (GMT)
  • Message-id: <808654.62215.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Ok. I'll send the email to Adrian next week. Meanwhile I'll try to set up my
own buildservice on a virtual machine and see how difficult would be to add the
appliance things. By the way, JeOS is about 350MB. I think there is still some
stuff that can be remove, but I'll try that on a later stage (like
documentation and some Perl-Modules).

I do have a question for the factory guys. AppArmor is in the minimal system.
Should be this way? If we create a software appliance and not configure
properly AppArmor, would not that be a problem more than a benefit? Or is it a
good idea to have AppArmor even though it is not configured (or configured with
the default configuration)?

thanks,

jordi massaguer i pla
http://jordimassaguerpla.blogspot.com/
lin.cat: Serveis professionals en linkat
http://www.lin.cat

----- Mensaje original ----
De: Andreas Jaeger <aj@xxxxxxx>
Para: Jordi Massaguer <jordimassaguerpla@xxxxxxxx>
CC: opensuse-factory@xxxxxxxxxxxx; adrian@xxxxxxx
Enviado: martes, 18 de marzo, 2008 15:37:22
Asunto: Re: [opensuse-factory] Re: Lime JeOS: The openSUSE based JeOS

Jordi Massaguer <jordimassaguerpla@xxxxxxxx> writes:

Hi AJ,

thanks for the email. Actually I am basing the JeOS on the minimal pattern. I
tried to set up a project on the buildservice that was linking all the
minimal pattern rpms (and dependencies), so software appliances could be
projects on the buildservice that where build on JeOs project (from a
technical point of view. The UI may be a new web application). However, some
rpms are missing (the kernel for example) and it looked like I could not set
up my project as a build platform.

This is something to discuss with the Build Service guys - perhaps on
their list.

That makes me consider installing my own build service and define JeOS as a
build platform and then modify the web UI or make a new one that runs the
kiwi and is more software appliance oriented. That will have a lot of sense,
especially when multiple build services can be connected.

Meanwhile, I've started conversations with possible sponsors, so I am looking
for a very good server with very good bandwith, and that is not costless ;) .
However the conversations are still in a very early stage.

So, what do you think is the best approach? Especially for updating to the
new versions of JeOS to the new openSUSE versions.

I suggest you talk with Adrian next week (he's currently travelling) and
see what's possible,

Andreas
--
Andreas Jaeger, Director Platform / openSUSE, aj@xxxxxxx
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126





______________________________________________
Enviado desde Correo Yahoo!
El buzón de correo sin límite de almacenamiento.
http://es.docs.yahoo.com/mail/overview/index.html
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups