From: Michael T. Halligan (michael_at_halligan.org)
Date: Tue Apr 10 2007 - 05:52:25 CEST
Message-Id: <B3C16B1E-9969-417E-8299-00B36A1C4433@halligan.org> From: "Michael T. Halligan" <michael@halligan.org> Date: Mon, 9 Apr 2007 20:52:25 -0700 Subject: Re: [suse-sles-e] Adding SDK to a SLES10 AutoYast repository? Is it even possible?
On Apr 9, 2007, at 8:36 PM, Alexei_Roudnev wrote:
> I am not surprised.
>
> For example, I am testing iscsi in SLES10 and found many wonderfull
> things:
> - it is not documented properly (because it is open-iscsi and not
> cisco
> iscsi)
> - no way to mount file system when using multipath and lvm
> - more important, it works 10 times slower vs RHEL4 (and SLES9)
> when used by
> Oracle.
> It is still mistery for me, because simple 'dd' command shows the
> same disk
> io, but shows much logner io query and awaiting time.
> - in any case, SLES10 IS NOT READY for use in iSCSI environment and
> oracle.
> I don't know what to do with al this mess - I can't open a bug for
> such
> things, because it can be not a bug but a future... -:) but system is
> unusable for me (albsolutely). Which is a bad thing because it
> (SLES10) have
> many usefull improvements.
>
> But you should try SLES10 SP1 (read Novell news, looks as they
> began to
> listen and made open beta period in the end of SP1 testing and
> before SP1
> release). As I could see, yast2 installation subsystem was
> dramatically
> improved in SP1, so may be your issue is resolved too.
So can we actually get SP1? It seems to me that SP1 for SLES19 and
SP4 for SLES9 only
exist as teases on UWE's page.
>
> For me, conclusion is 100% clean - no any SLES10 in production for
> now, only
> SLES9 and possible RHEL or UL4.4 (SLES9 is better in many ways,
> except the
> collection of available software). On the other hand, SLES10 looks
> very
> attractive for developers. May be, we wil do usual 'jump over' and
> count on
> next SLES11 / RHEL6 (skipping RHEL5 and SLES10, as we skipped
> FreeBSD 5 and
> Solaris 2.8).
>
The main reason I'm jumping to SLES10 is we're rebuilding all of our
customers from scratch right now
while migrating to a new datacenter.. That, and I'm tired of all the
SATA driver problems inherent in the
2.6.5 kernel that SLES9 is based upon. Also at issue are the rather
ancient versions of apache/php/ruby/openssl
that we end up having to replace manually in SLES9.
>
>
> ----- Original Message -----
> From: "Michael T. Halligan" <michael@halligan.org>
> To: "Alexei_Roudnev" <Alexei_Roudnev@exigengroup.com>
> Cc: "Michael T. Halligan" <michael@halligan.org>; "suse-sles-e"
> <suse-sles-e@suse.com>
> Sent: Monday, April 09, 2007 7:06 PM
> Subject: Re: [suse-sles-e] Adding SDK to a SLES10 AutoYast
> repository? Is it
> even possible?
>
>
>> So this doesn't work with AutoYast at all. This only works when
>> you're configuring a system manually. If I manually add an SDK
>> installation source to
>> an existing system, it's fine. If I add that same source to an
>> autoyast file, any way I do it, the system dies a painful, poorly
>> documented death.
>>
>> On Apr 9, 2007, at 6:58 PM, Alexei_Roudnev wrote:
>>
>>> Import it as a separate product. Just open yas2 -> Installation
>>> server and
>>> add SDK as a separate product, then add installation source into
>>> the yast2.
>>> Worked fine (but with numerous glitches, so I am not surprised).
>>>
>>> In addition, you can found and use all network installation sources
>>> for
>>> OpenSuSe 10.1 (they have a lot of things, such as Jboss etc). And in
>>> addition, upgrade to SP1 (beta rc1 is already available as I
>>> know) - I
>>> noticed a few bug fixes , related to yast2, in it (some rely to
>>> installation
>>> soucers).
>>>
>>> But I have my own questions to SUse.
>>> How can I:
>>> - set up installation soucers order in new yast2?
>>> - disable re-reading all sourcs on opening 'installation' or
>>> 'installation
>>> sources menu' (it is very, very slow)?
>>>
>>>
>>>
>>> ----- Original Message -----
>>> From: "Michael T. Halligan" <michael@halligan.org>
>>> To: "suse-sles-e" <suse-sles-e@suse.com>
>>> Cc: "Michael halligan" <michael@halligan.org>
>>> Sent: Monday, April 09, 2007 6:23 PM
>>> Subject: [suse-sles-e] Adding SDK to a SLES10 AutoYast repository?
>>> Is it
>>> even possible?
>>>
>>>
>>>> So, as with several other oddities, I've found my standard SLES9
>>>> method of using Yast2 to import the SDK as an add-on product is no
>>>> longer possible. How would one go about adding SLES10's SDK to an
>>>> autoyast repository properly? I've attempted using yast2 to
>>>> create an
>>>> installation source, and adding this (actually `yast autoyast`
>>>> added
>>>> this) following xml to an autoinstall.xml, but with no luck:
>>>>
>>>> <add-on>
>>>> <add_on_products config:type="list">
>>>> <listentry>
>>>> <media_url>ftp://10.1.100.9/SLES10SDK>
>>>> <product>SUSE-Linux-Enterprise-SDK-x86_64</product>
>>>> <product_dir>/</product_dir>
>>>> </listentry>
>>>> </add_on_products>
>>>> </add-on>
>>>>
>>>>
>>>> What am I doing wrong? All I get is a very useless "Error:
>>>> Failed to
>>>> Add Add-On Product". I've attempted to build the installation
>>>> repository manually, using autoyast, I've even done a voodoo dance.
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
>>>> For additional commands, e-mail: suse-sles-e-help@suse.com
>>>>
>>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
>>> For additional commands, e-mail: suse-sles-e-help@suse.com
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
>> For additional commands, e-mail: suse-sles-e-help@suse.com
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Tue Apr 10 2007 - 07:56:30 CEST