Just wondering if this release is going to do away with init.d scripts and make the transition to complete systemd service implementation?
Also any possibility of a completely stripped down, entirely bare-bones version of this system?
I do understand what you mean with your first version (though I doubt that “they” will drop the backwards compatibility so soon).
But fort the second question, I think you have to define what you think is “a completely stripped down, entirely bare-bones version of this system”. I am even not sure what you mean by “this system”. openSUSE 13.3, or just systemd?
Well I suppose my question is, how to get the most minimal install from an openSUSE system.
I’ve only managed to get down to OpenBox thus far. Yet there’s a lot of network functionality installed and all round general-purpose compatibility which I want to try and understand and remove any unnecessary stuff that I’m never going to use. 
QUOTE=bananaosx;2551323]stuff that I’m never going to use. ;)[/QUOTE]
I think that says it all. How can you assume that anybody else here, or amongst the developers, can know what you are ever going to use when you do not specify it?
I hope you understand that this “completely stripped down, entirely bare-bones version of openSUSE” is something very personal to you. Something like the kernel, maybe GRUB and some openSUSE branding to make it look like openSUSE?
[quote="“hcvv,post:4,topic:89824”]
I think that says it all. How can you assume that anybody else here, or amongst the developers, can know what you are ever going to use when you do not specify it?
I hope you understand that this “completely stripped down, entirely bare-bones version of openSUSE” is something very personal to you. Something like the kernel, maybe GRUB and some openSUSE branding to make it look like openSUSE?[/QUOTE]
Hoe is’t??
Couldn’t care much about branding. Consistency of pre-built packages and package manager is what I’m in favour of in this distro. Something which most other distros I’ve tried do rather shabbily. Hence I’m looking for “ultimate customisation” of this platform.
You didn’t answer my question other than attacking from a philosophical POV. Maybe I’ll ask a simpler more specific question: Which packages does the installer deploy if you choose the Minimal Text Mode option?
Thx!!
Although I don’t follow how each openSUSE version is released, you might find a clue in the timetable for 12.3.
12.3 (released in Mar 2013) implemented systemd v.195 which included features which were blogged by the systemd project authors in February. This suggests that 12.3 was released with systemd code marked “stable” as recently as maybe 2-3 months before official release.
Then consider <what> was integrated with each systemd implementation in openSUSE
- 1`(unknown version, I haven’t checked) - Bare implementation of an integration structure, hardly any actual Units.
12.2 systemd v.44 - Largely integrated the bootup (target) Units, replacing bash scripts with Units written with C code. Started introducing Units which called init scripts so the scripts wouldn’t be called through the legacy SysVinit backwards compatibility Unit.
12.3. systemd v 195 Introduction of a number of core systemd functionality, including the journal, watchdog, systemd-nspawn, more. IMO more or less largely completes very early objectives of systemd roadmap.
So, what’s going to happen with future systemd integration?
- Continue to replace init scripts with C compiled Units
- Expand replacement of subsystems beyond original objectives.
IMO based on history, it’s far too early to know what systemd will be doing in the next version of openSUSE. Possibly the most difficult integration problems have already been addressed, the main focus likely will be as I described.
In any case, if you wanted to experiment with your own version of systemd integrating the latest releases instead of waiting for official openSUSE integration, IMO it’d likely be very easy with hardly any risk… as the previous posts suggest you’d have to build it yourself but I’d consider the possibility of problems much smaller than other wild integration ideas because of systemd’s fundamental support for backwards compatibility.
Otherwise, you can always run the latest versions of Fedora (even in a VM). Fedora is leading the world in rushing systemd changes into its releases.
Without any inside systemd info but making educated guesses,
TSU
Pretty much “old style Linux.”
Minimal plus YAST. For my purposes I usually also add wget, find-utils-locate and git and from there build whatever I want on top of that base.
Recommend for starters install it and see what repos it pulls from (IIRC only the OSS and maybe something else, maybe not even an Update repo).
If you want to go even more “minimal” you can lookup and install a bootstrap image which further allows you to remove whatever you want.
Once you have a clear idea exactly what you do or don’t want, you can optionally create an Open Studio version for templating.
HTH,
TSU
Ha lovely post…! That’s more like. Thanks, time to get down & dirty.
TY.
On 2013-04-26 18:26, bananaosx wrote:
> You didn’t answer my question other than attacking from a philosophical
> POV. Maybe I’ll ask a simpler more specific question: Which packages
> does the installer deploy if you choose the Minimal Text Mode option?
I don’t think anybody “attacked” you. You simply asked a difficult and
imprecise question, somewhat philosophical 
The best manner of obtaining an exact answer to your question above,
which is a very precise question, thanks, is to fire up an installation,
choosing that pattern. You do not need to actually install anything, but
just click in the detailed package view in the install display, and you
will see the exact list of packages.
If you want that list from me, I would have to install a virtual machine
with that configuration, and then obtain the list of packages (because I
don’t know anywhere where it is published). I can do that perhaps in
under an hour, but so can you
Keep in mind that openSUSE is a general purpose distro, so even the
minimal install is not that minimal. Other people say that it is too
minimal… it’s up to you to choose
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
If you have openSUSE 13.1 installed add the kiwi package and run as root
kiwi --build suse-13.1-JeOS -d temp/mytest --set-repo http://download.opensuse.org/factory/repo/oss --set-repotype yast2 --add-pattern yast2_basis --add-pattern enhanced_base --add-package YaST2 --add-package YaST2-network
That will build an iso image with the bare essentials with the ability to configure your network via yast
On 05/01/2013 06:26 PM, dale14846 wrote:
> If you have openSUSE 13.1 installed
since there is currently no openSUSE 13.1, how would one have that
installed?
installing Factory today is not installing even openSUSE 13.1 RC1
–
dd
dale@linux-x2n5:~> cat /etc/SuSE-release
openSUSE 13.1 Milestone 0 (x86_64)
VERSION = 13.1
CODENAME = Dartmouth
dale@linux-x2n5:~> ls /usr/share/kiwi/image
isoboot rhel-06.0-JeOS suse-12.2-JeOS suse-13.1-JeOS suse-SLE11-JeOS
rhel-05.4-JeOS suse-12.1-JeOS suse-12.3-JeOS suse-SLE10-JeOS vmxboot
It’s good enough for me.
13.1 is already out AFAIC.
;)
On 05/02/2013 02:26 PM, dale14846 wrote:
>
>> installing Factory today is not installing even openSUSE 13.1 RC1
>>
>
> ‘Index of /factory/iso’ (http://download.opensuse.org/factory/iso/)
>
> openSUSE 13.1 Milestone 0 (x86_64)
> VERSION = 13.1
yes, as i said: installing today is not even openSUSE 13.1 RC1
it is installing whatever is in factory today which is experimental
pre-Milestone Zero code… everything before final release (now
expected to be in Nov 2013) is not 13.1, instead it is “13.1
[something]” with ‘something’ being something like “Milestone n”,
“Beta n”, “RCn”
–
dd
openSUSE®, the “German Engineered Automobile” of operating systems!
On 05/02/2013 03:36 PM, bananaosx wrote:
> 13.1 is already out
Have a lot of fun!
Knock yourself out!!
–
dd