2013. szeptember 10. 0:47 napon John Andersen írta:

On 09/07/2013 10:22 AM, Istvan Gabor wrote:

...

Hello:

If I know correctly in systemd there are no runlevels.

Previously if I wanted to restart X server I switched to runlevel 3 then back to runlevel 5 (init 3, init 5).

How can I stop, start, and restart in openSUSE 12.2 with systemd?

Thanks,

Istvan

Quickest is to log out and log back in again, because the x server runs as a user task, not as a server.

Thanks. There are two reasons I'd like to do it in terminal command line: 1. If the desktop freezes or slows down extremely I can not log out, but if I still can switch to a terminal I can use the comand line to restart the server. 2. Usually the first desktop is created on vt7 but occasionally on vt8 which annoys me. In such cases I would like to restart X server to start on vt7. By the way, why dose the desktop start occasionally on vt8? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2013-09-11 20:55 (GMT+0400) Andrey Borzenkov composed:

÷ Wed, 11 Sep 2013 18:41:03 +0200 Istvan Gabor composed:

...

2. Usually the first desktop is created on vt7 but occasionally on vt8 which annoys me. In such cases I would like to restart X server to start on vt7.

...

By the way, why dose the desktop start occasionally on vt8?

Because something keeps vt7 open and busy. Most likely plymouth.

Starting on VT8 has happened to me on occasion too. I've never figured out what might be causing it, but it shouldn't be Plymouth, as I taboo it (and Splashy) at every installation. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

2013. szeptember 10. 1:04 napon Cristian Rodríguez írta:

El 07/09/13 13:22, Istvan Gabor escribió:

...

Hello:

If I know correctly in systemd there are no runlevels.

Previously if I wanted to restart X server I switched to runlevel 3 then back to runlevel 5 (init 3, init 5).

How can I stop, start, and restart in openSUSE 12.2 with systemd?

The same way you did before.

That is init 3, init 5? Could you explain, please why it is till workong with systemd? And how can I restart the server to start desktop0 on vt7 instead of vt8 which occasionally occurs? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata said the following on 09/11/2013 01:18 PM:

On 2013-09-11 18:43 (GMT+0200) Istvan Gabor composed:

...

That is init 3, init 5?

...

Could you explain, please why it is till workong with systemd?

I'm pretty sure some developer understood remembering 'init3; init 5' can be a lot easier than whatever lengthy typing is required to get systemd to do it, and created some sort of aliasing to make the easy to remember method keep working equivalent to how it did with sysvinit, maybe Frederic Crozat.

Of course if you look # ls -li init 125001 lrwxrwxrwx 1 root root 26 Sep 10 18:41 init -> ../usr/lib/systemd/systemd So the binary looks to see how its invoked and does some magic that manages backwards compatibility. I'm sure a peek at the source will make that a lot clearer. Running 'strings' I see program_invocation_name I also note that 'man init' takes me to the systemd page. Perhaps that should be construed as hint, eh? That page also says For compatibility with SysV, if systemd is called as init and a PID that is not 1, it will execute telinit and pass all command line arguments unmodified. That means init and telinit are mostly equivalent when invoked from normal login sessions. See telinit(8) for more information. Do note that the 'telinit' page says This is a legacy command available for compatibility only. It should not be used anymore, as the concept of runlevels is obsolete. -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata said the following on 09/11/2013 03:23 PM:

On 2013-09-11 13:55 (GMT-0400) Anton Aylward composed:

...

the concept of runlevels is obsolete.

So, what complicated mechanism will or have the the systemd people come up with to replace the simplicity of S or 1 or 2 or 3 or 5 on cmdline to override the default runl^H^H^H^Htarget? :-p

Well lets see, how simple are S, 1, 2, 3, 4, 5 and 6? They actually hide a whole pile of shell scripting. You've traded simplicity of expression for (a) obscurity of meaning and (b) the need to be a programmer to make any adjustments What does the systemd approach offer instead? Well for a start there's clarity of meaning that is absent from the sysvinit method: We've got multi-user.target or graphical.target either of which may linked normally to default.target depending on whether you are running a workstation or a server. That seems clearer to me than "3" or "5". And reboot.target seems clearer than "6" Then we have shutdown.target Between those extremes there is hibernate.target What systemd also offers are ways to turn on and off specific subsystems http-daemon.target sound.target mail-transfer-agent.target network.target and more. Personally I think that the setup of systemd in terms of what a target requires and what should precede it, as well as explicit documentation references, is much simpler than the shell script approach used by sysVinit or BSD. I say this as someone who has been writing shell script since the UNIX V6 days. Systemd is much easier to configure and debug and less prone to typographic errors because it is much more regular and has a remarkably simple syntax. It is also much easier to test and debug than shell scripting. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Ken Schneider - openSUSE [09-11-13 19:48]: [...]

Oh, so one need only type (at the cli):

multi-user.target

to get the equivalent of init 3

or (again at the cli)

graphical.target

to get the same as init 5.

you forgot <sarcasm> </sarcasm> -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Ken Schneider - openSUSE said the following on 09/11/2013 07:45 PM:

...

We've got

multi-user.target or graphical.target

Oh, so one need only type (at the cli):

multi-user.target

to get the equivalent of init 3

or (again at the cli)

graphical.target

to get the same as init 5.

That's right, Ken, you just type 3 or 5 That's all there is to it </sarcasm> -- "Did any of them kids have some space alien with a face like a friendly turd in a bike basket?" -- (Terry Pratchett & Neil Gaiman, Good Omens) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata said the following on 09/11/2013 08:21 PM:

/bin/sh cp -a /usr/lib/systemd/system/getty@.service /usr/lib/systemd/system/getty@tty1.service sed -i 's/TTYVTDisallocate=yes/TTYVTDisallocate=no/' /usr/lib/systemd/system/getty@tty1.service ln -sf /usr/lib/systemd/system/getty@tty1.service /etc/systemd/system/getty.target.wants/getty@tty1.service systemctl startgetty@tty1.service ln -sf /usr/lib/systemd/system/getty@.service

Why are you linking? Why not do it all with 'systemctl enable ......' ? And do it all at once not one at a time. Then start them. All at once. -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata said the following on 09/11/2013 08:57 PM:

On 2013-09-11 20:27 (GMT-0400) Anton Aylward composed:

...

Felix Miata said the following on 09/11/2013 08:21 PM:

...

...

/bin/sh cp -a /usr/lib/systemd/system/getty@.service /usr/lib/systemd/system/getty@tty1.service sed -i 's/TTYVTDisallocate=yes/TTYVTDisallocate=no/' /usr/lib/systemd/system/getty@tty1.service ln -sf /usr/lib/systemd/system/getty@tty1.service /etc/systemd/system/getty.target.wants/getty@tty1.service systemctl startgetty@tty1.service ln -sf /usr/lib/systemd/system/getty@.service

...

Why are you linking?

Maybe to do at least in part with configuration changes I make in /usr* getting wiped out by updates. Links are a way to "remember" where in the rats' nest of /usr and/or /var the originals are squirreled away.

...

Why not do it all with 'systemctl enable ......' ?

Haven't seen an example. Most man pages leave out the examples that are typically crucial to my understanding man page text.

Two tools I always use: 'apropos' and 'google' In this case googling for 'systemctl enable' turns up plenty of examples and discussion.

...

Then start them. All at once.

Show me? I have a big enough round tuit shortage that I don't need to force frustrate myself further with insufferably example-free man pages before urgency forces it.

'start', like 'enable' can take a list of parameters. systemctl start getty@tty5.service getty@tty6.service Please explain what so difficult about figuring that out from the man page where it says start [NAME...] Start (activate) one or more units specified on the command line. -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2013-09-11 20:33 (GMT-0400) Anton Aylward composed:

as Cristian says, things are dynamic not static.

For many, but not particularly me.

Its no longer just about single vs multi vs graphical, its about what services are running and what devices are connected.

Other that what hosts are booted, and what mode I want a CRT to run in, little changes here.

If you are running a laptop in graphical mode then plugin in a wifi USB device all of sudden networking is available. So all the network services can start ... dns ... postfix ... apache ... ntp and other clients. Or shut down when the USB device is removed.

USB here is limited to storage devices on hosts lacking eSATA. Wifi here is excluded entirely. Only my router has wireless capability, which has remained disabled its entire life. Cell service here is functionally non-existent for about 90% of its users.

So its about using systemctl to display whir are active or which have failed.

You mean list-units? I've yet to see more than a little of that output that I understand the way I understand 'chkconfig -l | sort' output.

The matrix you mention no longer makes any sense in a dynamic environment. Its not giving you the information you need - which is about what is running and what is not, and *why* what is not running is not running.

5 means everything started, and 3 means DM not started. It worked for me before. Their systemd equivalents work no better or worse that I've been able to tell, save for having had to figure out how to keep X off the vttys below #7 and stop #1 from being cleared when initialization has completed. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thursday, September 12, 2013 12:33:40 AM Cristian Rodríguez wrote:

El 11/09/13 21:21, Felix Miata escribió:

...

Written scripts, mature too. Sunk cost.

people that say this, have invariable never worked in the guts of a distribution.

...

So? Multi-user and graphical are clear enough, but who came up with target to summarize an operational configuration easily visualized via the simple chkconfig -l matrix? The word's usage is not clear to me, and thus, not easily memorable.

There is a complete stack to visualize what systemd does.

systemd-analyze plot > sd.svg

No such command exists on a stock 12.3

if that's not enough

systemctl dot | dot -Tsvg > systemd.svg

Seriously? Good thing you don't work for me son. if that is your perception of documentation.

read the svg files with a modern browser.

Still not enough ?

boot with init=/usr/lib/systemd/systemd-bootchart and then read the svg files in /run/log

Given your first two examples, I think I'll pass. Especially since that command doesn't exist on a stock 12.3 system either. --

From the Myth of Me -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thursday, September 12, 2013 01:18:27 AM Cristian Rodríguez wrote:

When you read my emails, please assume until I say otherwise that I am refering to the *current state* of development. (i.e factory or upcoming versions) I work almost exclusively on factory all the time.

When answering questions or trying to explain something to people on THIS LIST please assume non of us are running bleeding edge versions. --

From the Myth of Me -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2013-09-12 00:33 (GMT-0300) Cristian Rodríguez composed:

Felix Miata composed:

...

Written scripts, mature too. Sunk cost.

people that say this, have invariable never worked in the guts of a distribution.

That may be, but it still can be a lot easier for someone who is not a programmer and who learned what it means last century to remember what 3 on cmdline does than what to type at a Grub menu that can substitute for it.

...

So? Multi-user and graphical are clear enough, but who came up with target to summarize an operational configuration easily visualized via the simple chkconfig -l matrix? The word's usage is not clear to me, and thus, not easily memorable.

There is a complete stack to visualize what systemd does.

By visualize I meant an answer to a question arising working at a shell prompt, usually in runlevel 3.

systemd-analyze plot > sd.svg

if that's not enough

MC on tty3 won't open it.

systemctl dot | dot -Tsvg > systemd.svg

No exit until Ctrl-C. Only 837 bytes.

read the svg files with a modern browser.

Defeats my needs. Far more often than not when I want something from chkconfig -l output, X isn't running.

Still not enough ?

boot with init=/usr/lib/systemd/systemd-bootchart and then read the svg files in /run/log

Without X available, viewable how? One of the advantages of working on a vtty cmdline or in MC is a fullscreen's absence of distractions along with nice big easy to read text. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 09/12/2013 02:44 AM, Andrey Borzenkov wrote:

No, there is not. There is no way to answer the question - what happens when you try to start/stop unit *In current state*. Please show me how I can test - what will systemd do when you shutdown the system. Which units in which order will be stopped (and started!)?

There is halfhearted support for emulating "booting into specific target" with "systemd --test" but no way to start from some existing state (snapshot). .. At least, recent versions finally provided more or less usable way to visualize dependency tree, but you still need to sit down and follow the tree manually ... Again - I want to know what will be kicked off when I execute "systemct start one-of-dozens-of-unit-files-lying-around". Please show me how I can do it.

There is no "what will happen", but only "what actually happened" after things have actually executed and unless there are strict After='s Requires= Before=s etc relationships between units and/or targets no "test" run will be identical to the next, as units are started/stopped in parallel. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

...

...

Could you explain, please why it is till workong with systemd?

but also, can somebody explain what is the prefered way to use systemd to switch from tty only to gui session? I understood how to change this for good http://dodin.org/wiki/index.php?n=Doc.VirtualBoxGuest but how can one do this just once? thanks jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 11/09/2013 23:05, Patrick Shanahan a écrit :

* jdd [09-11-13 16:32]:

...

...

...

...

Could you explain, please why it is till workong with systemd?

but also, can somebody explain what is the prefered way to use systemd to switch from tty only to gui session?

perhaps systemctl start graphical.target

man 7 systemd.special

really interesting, thanks jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 12/09/2013 03:55, Cristian Rodríguez a écrit :

El 11/09/13 18:05, Patrick Shanahan escribió:

...

* jdd [09-11-13 16:32]:

...

...

...

...

Could you explain, please why it is till workong with systemd?

but also, can somebody explain what is the prefered way to use systemd to switch from tty only to gui session?

perhaps systemctl start graphical.target

man 7 systemd.special

systemctl isolate graphical.target

not "start".

from man page "isolate [NAME] Start the unit specified on the command line and its dependencies and stop all others. This is similar to changing the runlevel in a traditional init system. The isolate command will immediately stop processes that are not enabled in the new unit, possibly including the graphical environment or terminal you are currently using." I would like to add some remarks: * the init 3/5 openSUSE system is specific to openSUSE, at least Debian or Ubuntu did not use it (muc less levels) * I think systemd was not enough promoted. To promote a system mean explaining not his advantages but how to use it. I think specially that the rc<init> openSUSE shorts command should have been mimicked for systemd because the systemctl commands are unfriendly "rcmulti" and "rcgraphical" could be much more friendly jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 12/09/2013 15:26, Patrick Shanahan a écrit :

* jdd [09-12-13 03:49]:

...

"rcmulti" and "rcgraphical" could be much more friendly

But they have been, rcsshd {start,stop,restart,status,...} init {S,1,3,5,6} still perform as expected via replacement scripts linking to the actual systemctl command syntax.

yes, with a little less informations in fact these commands say "redirecting to systemd", if they could give the hole systemctl command, this would be a learning process :-) jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan wrote:

* jdd [09-12-13 11:07]:

...

in fact these commands say "redirecting to systemd", if they could give the hole systemctl command, this would be a learning process :-)

If you specify "status", you will be provided information.

I don't think it was the status that was wanted. I think the idea was that if it told you exactly what systemd command it was about to execute, you would learn that and not need to be redirected next time. Much more useful than a bland redirection notice. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

jdd wrote:

Le 12/09/2013 17:42, Dave Howorth a écrit :

...

Patrick Shanahan wrote:

...

* jdd [09-12-13 11:07]:

...

in fact these commands say "redirecting to systemd", if they could give the hole systemctl command, this would be a learning process :-)

If you specify "status", you will be provided information.

I don't think it was the status that was wanted.

I think the idea was that if it told you exactly what systemd command it was about to execute, you would learn that and not need to be redirected next time. Much more useful than a bland redirection notice.

exactly

jdd

Exactly NOT. The reason we have short commands to do complex tasks is because the commands are, wait for it,... SHORT. Not only that they are all of the same form. If echoing a stream of blather in response to a short command is such a marvelous teaching aid, perhaps we should run all our shell scripts in this mode! You seem to have forgotten that the reason we use computers is to get something done. Learning huge long command streams, much less using them day to day, is counterproductive. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

jdd said the following on 09/12/2013 11:04 AM:

Le 12/09/2013 15:26, Patrick Shanahan a écrit :

...

* jdd [09-12-13 03:49]:

...

...

"rcmulti" and "rcgraphical" could be much more friendly

But they have been, rcsshd {start,stop,restart,status,...} init {S,1,3,5,6} still perform as expected via replacement scripts linking to the actual systemctl command syntax.

yes, with a little less informations

in fact these commands say "redirecting to systemd", if they could give the hole systemctl command, this would be a learning process :-)

I think you misunderstand. Look at the inode number of the init command and the systemd command On my system, 12.3 its a symlink $ ls -li /sbin/init 125001 lrwxrwxrwx 1 root root 26 Sep 10 18:41 /sbin/init -> ../usr/lib/systemd/systemd That means when you think you are executing "init 3" what actually happens is the equivalent of char *argv[] = { "init", "3", NULL }; execve("/usr/lib/systemd/systemd", argv, environ); Then systemd looks at argv[0] and sees that its invocation 'name" -- from the command line -- is "init" but as you will see if you read 'man 1 init', it checks it PID to see it it is 1. It can't be because you've just invoked it, so For compatibility with SysV, if systemd is called as init and a PID that is not 1, it will execute telinit and pass all command line arguments unmodified. That means init and telinit are mostly equivalent when invoked from normal login sessions. See telinit(8) for more information. I think that adequately answers your question. -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2013-09-11 15:32 (GMT-0400) Istvan Gabor composed:

...

I'm pretty sure some developer understood remembering 'init3; init 5' can be a lot easier than whatever lengthy typing is required to get systemd to do it, and created some sort of aliasing to make the easy to remember method keep working equivalent to how it did with sysvinit, maybe Frederic Crozat.

Do I have to run the two on one line as

# init3; init5

or can I do as

# init 3 <ENTER> # init 5 >ENTER> ?

Or does not matter?

Apparently I made a typo. Both # init 3; init 5 and # init 3 # init 5 produce the same result, unless maybe you're hitting https://bugzilla.novell.com/show_bug.cgi?id=783862 or some other bug. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

2013. szeptember 11. 19:33 napon Cristian Rodríguez írta:

El 11/09/13 13:43, Istvan Gabor escribió:

...

That is init 3, init 5?

Yes.

...

Could you explain, please why it is till workong with systemd?

Because systemd has minimal sysvinit compatibility which among other things, includes this.

...

And how can I restart the server to start desktop0 on vt7 instead of vt8 which occasionally occurs?

Systemd is fast... really fast.. one of the side effects of that is it brings some really fun race conditions to the surface, plymouth used to race this way, it should be fixed by now though.

I don't know what plymouth is, I've never heard of it before. I will check it. Regarding fats boot speed: I think this is a kinf of cheeting. You get a login screen very soon, but if you login immediately, the system is still booting after you've logged in. For example when I log in, I have to wait for network connection ~ another 5-10 seconds or longer. That is it takes time after login to have a fully set up system. And this speed has the drawbacks you mentioned. I preferred/would prefer a system that boots slower but becomes stably set up until when I get the login screen. Does it really matter that ~30 seconds when you boot once or twice a day? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Cristian Rodríguez [09-11-13 13:34]:

El 11/09/13 13:43, Istvan Gabor escribió: [...]

...

And how can I restart the server to start desktop0 on vt7 instead of vt8 which occasionally occurs?

Systemd is fast... really fast.. one of the side effects of that is it brings some really fun race conditions to the surface, plymouth used to race this way, it should be fixed by now though.

It was but sadly is broken again recently... a quick return from vt8 to vt7 is: systemctrl restart xdm.service or rcxdm restart -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

El 11/09/13 23:56, Andrey Borzenkov escribió:

In 12.2?

in factory or 12.3 I think. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org