Re: success w/ sle12sp1

On Jan 19, 2016, at 7:47 AM, Robert Klein <[email protected]> wrote:
> 
> Hi,
> 
> is there anyone successfully installing sle12sp1 with autoyast?
> 
> I don't seem to get the services_manager and scripts sections to be
> used.   Any updates in the queue?
> 
> PS: there were/are issues with Leap 42.1 and those sections, too.  The
> update for the scripts section (init-scripts) isn't there, yet.  My
> bug-reports now point as duplicate to bugs I'm not authorized to
> access :(   Anything I can do about that?

I’ve successfully used this services_manager section for SLES 12 GA/SP1 and Leap 42.1:
  <services-manager>
    <!-- 'graphical' or 'multi-user' -->
    <default_target>multi-user</default_target>
    <services>
      <enable config:type="list">
        <service>sshd</service>
      </enable>
  </services>
  </services-manager>

Re: scripts, post-scripts works fine for me, but I haven’t tried init-scripts under SLES 12 yet.

It is most unfortunate that bugs reported against SLES are private, and doubly so when a public bug gets closed as a duplicate of a private one.  AFAIK RHEL bugzilla is open except for security embargoes before a patch is released.  As a (paying) customer it’s frustrating to see bnc#NNN in the RPM changelog and/or patch description but there’s a probably 75% chance I can’t actually see it.  Even on a paid support request where they sent me a testing RPM with a fix, they wouldn’t grant me access to the bug mentioned in the RPM changelog, which had been filed internally for my issue.
</rant>

At least with a late-stage bug like init-scripts, when a fix does go out to the update repo, your install should work without needing a driver update or install media fix, assuming you enable the update repo during installation.


-Andrew

-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]