SCIENTIFIC-LINUX-DEVEL Archives

December 2016

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Oleg Sadov <[log in to unmask]>
Reply To:
Oleg Sadov <[log in to unmask]>
Date:
Wed, 28 Dec 2016 15:24:30 +0300
Content-Type:
text/plain
Parts/Attachments:
text/plain (44 lines)
Actually, "your" == "our" in this context -- we are all in the same SL
community :)

Sincerely,
--Oleg

2016-12-28 13:35 GMT+03:00 aleksander.baranowski
<[log in to unmask]>:
> Hi,
> Sorry for spamming and
> Sorry for writing
> "I saved our scripts"
> instead of
> "I saved your scripts"
>
> Bests,
> Alex
>
> PS. Yours would be probably even better :).
>
> On 12/28/2016 11:29 AM, aleksander.baranowski wrote:
>> Hi,
>>
>> Sorry for such late answer, but I tried to figured it out on my own (I
>> hate to admit it but I failed :(.). I prefer revisor/pungi way of making
>> iso because, it allow me to make iso from "bare" repo, and it fitted
>> perfectly my pipelines. But because time is short and making not working
>> isos is time consuming I assumed, that change SL5.11 iso might be better
>> way.
>>
>> After a few tries My iso get SIGSEGV after checking(first test in
>> installation process) ISO, or bad context for repodata without checking it.
>>
>> Mark - I would appreciate any help, working script especially :), it
>> might save me a few days of searching/reading/scripting.
>>
>> Oleg - Thanks for your help, I saved our scripts, and in case of further
>> failures I will make it your sane way, i.e. making iso from scratch.
>>
>> All Best,
>> Alex
>
>

ATOM RSS1 RSS2