Discussion:
YAST_IS_RUNNING possible values????
Roberto Angelino
2013-01-10 00:13:45 UTC
Permalink
Yast Gurus,
I have a question from my customer about this variable and what possible values & their meaning are? Do we have any documentation available?

Thanks

--
Roberto Angelino
Novell Dedicated Partner Engineer
--
To unsubscribe, e-mail: yast-devel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: yast-devel+owner-***@public.gmane.org
Arvin Schnell
2013-01-10 09:24:18 UTC
Permalink
Post by Roberto Angelino
Yast Gurus,
I have a question from my customer about this variable and what possible values & their meaning are? Do we have any documentation available?
Possible values set by YaST are "yes" and "instsys". One place
where the variable is used is parted: It behaves different during
filesystem resize if it's set. AFAIR some RPM macros also use it.

I'm not aware of any documentation.

Regards,
Arvin
--
Arvin Schnell, <aschnell-***@public.gmane.org>
Senior Software Engineer, Research & Development
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
--
To unsubscribe, e-mail: yast-devel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: yast-devel+owner-***@public.gmane.org
Lukas Ocilka
2013-01-10 09:46:01 UTC
Permalink
Post by Arvin Schnell
Post by Roberto Angelino
Yast Gurus,
I have a question from my customer about this variable and what possible values & their meaning are? Do we have any documentation available?
Possible values set by YaST are "yes" and "instsys". One place
where the variable is used is parted: It behaves different during
filesystem resize if it's set. AFAIR some RPM macros also use it.
I'm not aware of any documentation.
According to this bugreport
https://bugzilla.novell.com/show_bug.cgi?id=639579

it can also be

YAST_IS_RUNNING=1

which is then used by parted.

In fact the patch
http://bugzillafiles.novell.org/attachment.cgi?id=389782 says:

int always_resize = getenv( "YAST_IS_RUNNING" ) != NULL;

which means it can actually be anything (also "yes" / "1")

According to
https://build.opensuse.org/package/view_file?file=rpm-suse_macros&package=rpm&project=openSUSE%3AFactory%3APowerPC&rev=90aa982d51941b1f56f22cc8fb540f70

There is a special handling for case when

"$YAST_IS_RUNNING" != "instsys"

HTH
Lukas
--
Lukas Ocilka, Cloud & Systems Management Department
SUSE LINUX s.r.o., Praha
--
To unsubscribe, e-mail: yast-devel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: yast-devel+owner-***@public.gmane.org
Thomas Goettlicher
2013-01-10 09:51:14 UTC
Permalink
Post by Lukas Ocilka
Post by Arvin Schnell
Post by Roberto Angelino
Yast Gurus,
I have a question from my customer about this variable and what
possible values & their meaning are? Do we have any
documentation available?
Possible values set by YaST are "yes" and "instsys". One place
where the variable is used is parted: It behaves different during
filesystem resize if it's set. AFAIR some RPM macros also use it.
I'm not aware of any documentation.
According to this bugreport
https://bugzilla.novell.com/show_bug.cgi?id=639579
it can also be
YAST_IS_RUNNING=1
which is then used by parted.
In fact the patch
int always_resize = getenv( "YAST_IS_RUNNING" ) != NULL;
which means it can actually be anything (also "yes" / "1")
According to
https://build.opensuse.org/package/view_file?file=rpm-suse_macros&package=r
pm&project=openSUSE%3AFactory%3APowerPC&rev=90aa982d51941b1f56f22cc8fb540f7
0
There is a special handling for case when
"$YAST_IS_RUNNING" != "instsys"
HTH
Lukas
And kiwi uses YAST_IS_RUNNING=true according to
https://github.com/openSUSE/kiwi/blob/master/modules/KIWIManagerZypper.pm

Cheers,
Thomas
--
Thomas Goettlicher
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer,
HRB 16746 (AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
--
To unsubscribe, e-mail: yast-devel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: yast-devel+owner-***@public.gmane.org
Roberto Angelino
2013-01-10 22:02:53 UTC
Permalink
Post by Roberto Angelino
Post by Roberto Angelino
Yast Gurus,
I have a question from my customer about this variable and what possible
values & their meaning are? Do we have any documentation available?
Possible values set by YaST are "yes" and "instsys". One place
where the variable is used is parted: It behaves different during
filesystem resize if it's set. AFAIR some RPM macros also use it.
Followup question from customer regarding YAST_IS_RUNNING values
in sles9.sp3, sles10.sp3 & sles11.sp1? They are all the same between
each sles of these versions?





----
Roberto Angelino
Dedicated Partner Engineer
Developer Support
(310) 529-3527
--
To unsubscribe, e-mail: yast-devel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: yast-devel+owner-***@public.gmane.org
Lukas Ocilka
2013-01-16 13:07:52 UTC
Permalink
Post by Roberto Angelino
Post by Roberto Angelino
Post by Roberto Angelino
Yast Gurus,
I have a question from my customer about this variable and what possible
values & their meaning are? Do we have any documentation available?
Possible values set by YaST are "yes" and "instsys". One place
where the variable is used is parted: It behaves different during
filesystem resize if it's set. AFAIR some RPM macros also use it.
Followup question from customer regarding YAST_IS_RUNNING values
in sles9.sp3, sles10.sp3 & sles11.sp1? They are all the same between
each sles of these versions?
Depends on what you ask for. The easy answer is "possibly yes" and
"probably not". Some features were added during the YaST development and
SLE 9 (definitely) and SLE 10 (sometimes) seem to be rather old code.

Bye
Lukas
--
Lukas Ocilka, Cloud & Systems Management Department
SUSE LINUX s.r.o., Praha
--
To unsubscribe, e-mail: yast-devel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: yast-devel+owner-***@public.gmane.org
Loading...