[opensuse] adding links in /etc/init.d/rc*.d/
Sorry, I've been struggling to find any information on this, mainly because it is difficult to find proper search terms. Say I've installed some software, like PostgreSQL, that adds a beautiful script to /etc/init.d/ that starts or stops the server. Now I want to start the server in, say runlevel 3, so I know I need to add links to /etc/init.d/rc3.d/ but I'm having trouble finding information on the proper way of doing this. Can anyone point me to some documentation, or give a quick explanation of the numbers, letters etc. used in these symlinks? thanks, --Jason -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jason Craig wrote:
Sorry, I've been struggling to find any information on this, mainly because it is difficult to find proper search terms.
Say I've installed some software, like PostgreSQL, that adds a beautiful script to /etc/init.d/ that starts or stops the server. Now I want to start the server in, say runlevel 3, so I know I need to add links to /etc/init.d/rc3.d/ but I'm having trouble finding information on the proper way of doing this. Can anyone point me to some documentation, or give a quick explanation of the numbers, letters etc. used in these symlinks?
Unlike the old school unices where you tediously create symlinks by hand, linux distros provide gui and cli tools to automate the process. In yast, suse provides a runlevel editor under "system", or you can simply issue a chkconfig or insserv command to set the runlevels for a particular program. See the man pages on those commands for more info. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sloan wrote:
Jason Craig wrote:
Sorry, I've been struggling to find any information on this, mainly because it is difficult to find proper search terms.
Say I've installed some software, like PostgreSQL, that adds a beautiful script to /etc/init.d/ that starts or stops the server. Now I want to start the server in, say runlevel 3, so I know I need to add links to /etc/init.d/rc3.d/ but I'm having trouble finding information on the proper way of doing this. Can anyone point me to some documentation, or give a quick explanation of the numbers, letters etc. used in these symlinks?
Unlike the old school unices where you tediously create symlinks by hand, linux distros provide gui and cli tools to automate the process. In yast, suse provides a runlevel editor under "system", or you can simply issue a chkconfig or insserv command to set the runlevels for a particular program.
See the man pages on those commands for more info.
Joe
Thanks, I forgot to mention that the main idea was that I couldn't use YaST in this particular context. --Jason -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jason Craig wrote:
Sloan wrote:
Jason Craig wrote:
Sorry, I've been struggling to find any information on this, mainly because it is difficult to find proper search terms.
Say I've installed some software, like PostgreSQL, that adds a beautiful script to /etc/init.d/ that starts or stops the server. Now I want to start the server in, say runlevel 3, so I know I need to add links to /etc/init.d/rc3.d/ but I'm having trouble finding information on the proper way of doing this. Can anyone point me to some documentation, or give a quick explanation of the numbers, letters etc. used in these symlinks?
Unlike the old school unices where you tediously create symlinks by hand, linux distros provide gui and cli tools to automate the process. In yast, suse provides a runlevel editor under "system", or you can simply issue a chkconfig or insserv command to set the runlevels for a particular program.
See the man pages on those commands for more info.
Joe
Thanks, I forgot to mention that the main idea was that I couldn't use YaST in this particular context.
How odd - I'd love to know what context that might be (boggle). In any case, you can use one of the commands mentioned. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sloan wrote:
Jason Craig wrote:
Sloan wrote:
Thanks, I forgot to mention that the main idea was that I couldn't use YaST in this particular context.
How odd - I'd love to know what context that might be (boggle).
In any case, you can use one of the commands mentioned.
Joe
My playground VPS allowed me to choose from a pretty significant list of operating systems, and I decided to run SUSE to see how it behaved in a server environment. I haven't figured out why yet (I assume it has something to do with how the VPS is set up and administered by the host) but the YaST control center does not have all the same modules that are available on my desktop, System Services being one that is missing. Also, YaST has (during attempts of usage of the "Software Management" module) overgrown my limited free memory resources, and that's just no fun. --Jason -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jason Craig wrote:
but the YaST control center does not have all the same modules that are available on my desktop, System Services being one that is missing.
are you root?
Also, YaST has (during attempts of usage of the "Software Management" module) overgrown my limited free memory resources, and that's just no fun.
in ncurse mode??? jdd -- http://www.dodin.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jason Craig wrote:
My playground VPS allowed me to choose from a pretty significant list of operating systems, and I decided to run SUSE to see how it behaved in a server environment. I haven't figured out why yet (I assume it has something to do with how the VPS is set up and administered by the host) but the YaST control center does not have all the same modules that are available on my desktop, System Services being one that is missing. Also, YaST has (during attempts of usage of the "Software Management" module) overgrown my limited free memory resources, and that's just no fun.
What version of suse do you have there? 10.1 had serious issues with package management, 10.2 was improved, and 10.3 is quite nice actually, as long as you do not install zmd, but zypper instead, for your package management needs. If you're using sles 10, they have done some work on that to fix some of the more egregious shortcomings. Terminal mode yast is pretty lightweight. Perhaps if you're in a virtual environment, they have removed some tools, and in that case you should ask what happened to the yast runlevel editor. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sloan wrote:
What version of suse do you have there? 10.1 had serious issues with package management, 10.2 was improved, and 10.3 is quite nice actually, as long as you do not install zmd, but zypper instead, for your package management needs. If you're using sles 10, they have done some work on that to fix some of the more egregious shortcomings.
It is 10.2, and the host installed it (from an image I imagine) when requested. Thus, I am unsure of whether zmd or zypper is used. How do I tell? Sorry, I am a programmer and consider myself and expert user (maybe not an expert LINUX user), and some of the finer points of *nix administration are still unknown to me; simply have been learning as I go. --Jason -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jason Craig wrote:
Sloan wrote:
What version of suse do you have there? 10.1 had serious issues with package management, 10.2 was improved, and 10.3 is quite nice actually, as long as you do not install zmd, but zypper instead, for your package management needs. If you're using sles 10, they have done some work on that to fix some of the more egregious shortcomings.
It is 10.2, and the host installed it (from an image I imagine) when requested. Thus, I am unsure of whether zmd or zypper is used. How do I tell? Sorry, I am a programmer and consider myself and expert user (maybe not an expert LINUX user), and some of the finer points of *nix administration are still unknown to me; simply have been learning as I go.
No worries - just give the results of the commands "rpm -qa | grep zmd" and "zypper sl" Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello,
Say I've installed some software, like PostgreSQL, that adds a beautiful script to /etc/init.d/ that starts or stops the server. Now I want to start the server in, say runlevel 3, so I know I need to add links to /etc/init.d/rc3.d/ but I'm having trouble finding information on the proper way of doing this. Can anyone point me to some documentation, or give a quick explanation of the numbers, letters etc. used in these symlinks?
Unlike the old school unices where you tediously create symlinks by hand, linux distros provide gui and cli tools to automate the process. In yast, suse provides a runlevel editor under "system", or you can simply issue a chkconfig or insserv command to set the runlevels for a particular program.
There is another reason you should use insserv; with openSuSE 10.3 it could happen that a symlink to rc3.d (or which runlevel you want) simply is not enough to get the scrip executed at system start. If parallel startup of independend services is enabled (that is, in /etc/sysconfig/boot "RUN_PARALLEL" is set to "yes") your service needs an entry in .depend.start. insserv or chkconfig writes the corect entries (using the "Required-start" tags from the skript). (Please correct me if I'm wrong, but we had some service that simply would not start even though we had it linkdes to rc3.d until we made an entry in .depend.start. Well, it would allso work to set "RUN_PARALLEL" to "no", but this would increase the startup time.)
Thanks, I forgot to mention that the main idea was that I couldn't use YaST in this particular context.
How odd - I'd love to know what context that might be (boggle).
Well, as for YaST I think there are some reasons why someone wants to avoid it; if I want to change something quick, I usually don't start YaST as I am to impatient to wait for it to complete. (insserv mostly does the job and is much quicker.) Another reason could be another Distro - this stuff isn't exactly SuSE-specific. The last possibility comming to my mind would be acces from a text-terminal with extremly spartanic encoding, so YaST would simply be unusable. (As strange as this might sound, we have a customer with such a terminal to access his servers. Most of his boxes are AIX, but some are SuSE Linux, and if we don't want to run several corridors to the server-room we simply use this terminal.) So, I think the possibility of a SuSE-Box with seldom used YaST is not as far-fetched as it seems to be. Till then, Ortwin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ortwin Ebhardt wrote:
Well, as for YaST I think there are some reasons why someone wants to avoid it; if I want to change something quick, I usually don't start YaST as I am to impatient to wait for it to complete. (insserv mostly does the job and is much quicker.) Another reason could be another Distro - this stuff isn't exactly SuSE-specific. The last possibility comming to my mind would be acces from a text-terminal with extremly spartanic encoding, so YaST would simply be unusable. (As strange as this might sound, we have a customer with such a terminal to access his servers. Most of his boxes are AIX, but some are SuSE Linux, and if we don't want to run several corridors to the server-room we simply use this terminal.) So, I think the possibility of a SuSE-Box with seldom used YaST is not as far-fetched as it seems to be.
Good point - I hadn't thought about the poor blokes who don't have the comfort of a linux desktop from which to perform their system administration tasks. Personally, I most often use the chkconfig command for enabling services, but I do occasionally like to fire up the full yast GUI for hosts on the local lan, and I do use the terminal based yast for remote servers. All 3 approaches have their place. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jason Craig wrote:
Sloan wrote:
Jason Craig wrote:
Sorry, I've been struggling to find any information on this, mainly because it is difficult to find proper search terms.
Say I've installed some software, like PostgreSQL, that adds a beautiful script to /etc/init.d/ that starts or stops the server. Now I want to start the server in, say runlevel 3, so I know I need to add links to /etc/init.d/rc3.d/ but I'm having trouble finding information on the proper way of doing this. Can anyone point me to some documentation, or give a quick explanation of the numbers, letters etc. used in these symlinks?
Unlike the old school unices where you tediously create symlinks by hand, linux distros provide gui and cli tools to automate the process. In yast, suse provides a runlevel editor under "system", or you can simply issue a chkconfig or insserv command to set the runlevels for a particular program.
See the man pages on those commands for more info.
Joe
Thanks, I forgot to mention that the main idea was that I couldn't use YaST in this particular context.
S for start K for kill When entering a run-level, the S* scripts are executed. When leaving a run-level, the K* scripts are executed. K scripts are run in the reverse order of the S scripts. The numeric parts of the name are used to control the order of execution of the S* and K* scripts. When adding some new software, if I have to add the links by hand, then I just give them a higher S-number and lower K-number than any of the other scripts in the directory. This method works on all systems which use the Unix System V style init system. BSD systems have a different mechanism for init, and it's been too long since I last played with one to make any comment on BSD init and /etc/rc.d on those systems.
--Jason
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Nov 26, 2007 at 02:23:20PM -0700, Jason Craig wrote:
Sloan wrote:
Jason Craig wrote:
Sorry, I've been struggling to find any information on this, mainly because it is difficult to find proper search terms.
Say I've installed some software, like PostgreSQL, that adds a beautiful script to /etc/init.d/ that starts or stops the server. Now I want to start the server in, say runlevel 3, so I know I need to add links to /etc/init.d/rc3.d/ but I'm having trouble finding information on the proper way of doing this. Can anyone point me to some documentation, or give a quick explanation of the numbers, letters etc. used in these symlinks?
Unlike the old school unices where you tediously create symlinks by hand, linux distros provide gui and cli tools to automate the process. In yast, suse provides a runlevel editor under "system", or you can simply issue a chkconfig or insserv command to set the runlevels for a particular program.
See the man pages on those commands for more info.
Joe
Thanks, I forgot to mention that the main idea was that I couldn't use YaST in this particular context.
Use the "insserv" and/or "chkconfig" commandline tools. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jason Craig wrote:
Sorry, I've been struggling to find any information on this, mainly because it is difficult to find proper search terms.
Say I've installed some software, like PostgreSQL, that adds a beautiful script to /etc/init.d/ that starts or stops the server. Now I want to start the server in, say runlevel 3, so I know I need to add links to /etc/init.d/rc3.d/ but I'm having trouble finding information on the proper way of doing this. Can anyone point me to some documentation, or give a quick explanation of the numbers, letters etc. used in these symlinks?
thanks, --Jason
man insserv and man chkconfig -- kr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mandag 26 november 2007 21:06 skrev Jason Craig:
Sorry, I've been struggling to find any information on this, mainly because it is difficult to find proper search terms.
Say I've installed some software, like PostgreSQL, that adds a beautiful script to /etc/init.d/ that starts or stops the server. Now I want to start the server in, say runlevel 3, so I know I need to add links to /etc/init.d/rc3.d/ but I'm having trouble finding information on the proper way of doing this. Can anyone point me to some documentation, or give a quick explanation of the numbers, letters etc. used in these symlinks?
thanks, --Jason
I'd put it somewhere late in the runlevel sequence of events. Like, say 30 or so. On my SLES10 it's killed as no 10 and started as no 12. As root, goto /etc/init.d/rc3.d and do: ln -s ../postgresql S30postgresql Symlinks preceded by an "S" starts stuff. "K" kills stuff. See "man init.d" Actually I wouldn't do it by hand at all. I'd use YaST under System, Runlevel services. In there, I'd set it to run in runlevel 3 (and 5 for that matter). I'd also use YaST to start and stop the service. That should really do it. -- ------------------------------------------------------------------------- Med venlig hilsen/Best regards Verner Kjærsgaard Novell Certified Linux Professional 10035701 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I'd put it somewhere late in the runlevel sequence of events. Like, say 30 or so. On my SLES10 it's killed as no 10 and started as no 12.
As root, goto /etc/init.d/rc3.d and do:
ln -s ../postgresql S30postgresql
Symlinks preceded by an "S" starts stuff. "K" kills stuff. See "man init.d"
Actually I wouldn't do it by hand at all. I'd use YaST under System, Runlevel services. In there, I'd set it to run in runlevel 3 (and 5 for that matter). I'd also use YaST to start and stop the service. That should really do it.
One correction to this: better not do ln -s by hand, because next time you run either yast or chkconfig, it can change the service priority unexpectedly. I just got burned by that recently. If you really want to control the order in which services start, then first edit the script header, and on the # Required-Start: line (there will be one on top) add names all the services you want to start before this script. Then run either insserv or yast system services module to enable the script. Myrosia -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-11-26 at 21:13 +0100, Verner Kjærsgaard wrote:
I'd put it somewhere late in the runlevel sequence of events. Like, say 30 or so. On my SLES10 it's killed as no 10 and started as no 12.
As root, goto /etc/init.d/rc3.d and do:
ln -s ../postgresql S30postgresql
Don't do that on a suse system. Suse use an automatic method to determine the appropiate number to use. And, actually, if you make the links yourself, they will not work, and they might be removed by Yast. - -- Cheers. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHS2W3tTMYHG2NR9URAvOUAJ9CbkEnqJ3ZM4K+PX2YtIPMOYovfwCffQk1 5z/9XBoLPrZWNiyE67fYUKQ= =nj5q -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-11-26 at 13:06 -0700, Jason Craig wrote:
Say I've installed some software, like PostgreSQL, that adds a beautiful script to /etc/init.d/ that starts or stops the server. Now I want to start the server in, say runlevel 3, so I know I need to add links to /etc/init.d/rc3.d/ but I'm having trouble finding information on the proper way of doing this. Can anyone point me to some documentation, or give a quick explanation of the numbers, letters etc. used in these symlinks?
Ok. Faster doc is "man init.d". Then there is a chapter in the reference book (which nowdays is not paper, but html and pdf, if you install the appropiate package, or browse to somewhere in the net I forgot), named "The SuSE boot concept". Mmm... I think the chapter is named differently now: Chapter 12. Booting and Configuring a Linux System 12.2. The init Process Each script (see the example file /etc/init.d/skeleton) contains a block like this: ### BEGIN INIT INFO # Provides: FOO # Required-Start: $syslog $remote_fs # Required-Stop: $syslog $remote_fs # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Description: Start FOO to allow XY and provide YZ ### END INIT INFO The information there defines the runlevels in which this script will be called, and the order, ie, afther which other services. Any script must be inserted properly using "insserv", or easier and recomended, "chkconfig". You do not need Yast. You can use "chkconfig - --edit", for instance (mind: it uses "vi", ignoring the "EDITOR" variable). Or simply "chkconfig servicename on" to activate a service, and "--list" will produce a coloured chart. But never try to insert services manually creating the symlinks yourself: it may not work, and they may be removed. It is nowdays quite more complex, it uses a makefile approach in order to start several services in parallel (see "man startpar"). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHS2p+tTMYHG2NR9URApE+AJ0TllxBFU+/WtMGu7ZoRWphuSW6MQCgjnqN s9o+sImruxqvU6+YIj6keBE= =dIvH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 26 Nov 2007 13:06:10 -0700, Jason Craig wrote:
Say I've installed some software, like PostgreSQL, that adds a beautiful script to /etc/init.d/ that starts or stops the server. Now I want to start the server in, say runlevel 3, so I know I need to add links to
It depends on how you installed the software. If it's a rpm for openSUSE, the header of the init script contains all the needed info so you just use either chkconfig or insserv to create the necessary symlinks. If you compiled the software from source, check that the init script has a LSB conforming header (see /etc/init.d/skeleton for a template) and otherwise add such a header to the init script. Afterwards just use insserv or chkconfig to create the runlevel symlinks. Manually created symlinks will be removed the next time insserv gets run! Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Nov 29, 2007, at 9:50 PM, Philipp Thomas wrote:
Manually created symlinks will be removed the next time insserv gets run!
Philipp
Is there anyway to circumvent this behaviour? I recently discovered that when a machine gets rebooted its missing the first NFS mount point because the nfs client is booting in parallel to nscd which is causing a race condition the always misses the first mount point ( I can't statically define IP in /etc/hosts because it points to a dynamic nameserver which returns one of many IPs to mount from ). Moving the nfs services to the back of the init process in runlevels 3 & 5 and turning of the parallel boot flag in /etc/sysconfig/boot seems to have done the trick, but insserv keeps messing up my linking and in turn I have a bunch of people showing up at my door unable to login (home directories are the first mount point in the fstab). Cheers Todd Smith Systems Administrator --------------------------------------------- Soho VFX - Visual Effects Studio 99 Atlantic Avenue, Suite 303 Toronto, Ontario, M6K 3J8 (416) 516-7863 http://www.sohovfx.com --------------------------------------------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Dec 3, 2007, at 1:44 PM, M. Todd Smith wrote:
On Nov 29, 2007, at 9:50 PM, Philipp Thomas wrote:
Manually created symlinks will be removed the next time insserv gets run!
Philipp
Is there anyway to circumvent this behaviour? I recently discovered that when a machine gets rebooted its missing the first NFS mount point because the nfs client is booting in parallel to nscd which is causing a race condition the always misses the first mount point ( I can't statically define IP in /etc/hosts because it points to a dynamic nameserver which returns one of many IPs to mount from ).
Moving the nfs services to the back of the init process in runlevels 3 & 5 and turning of the parallel boot flag in /etc/sysconfig/boot seems to have done the trick, but insserv keeps messing up my linking and in turn I have a bunch of people showing up at my door unable to login (home directories are the first mount point in the fstab).
To answer my own question, you change the Required-Start option in / etc/init.d/nfsboot and /etc/init.d/nfs to $all, run insserv and make sure the parallel boot of unrelated services is set to 'no'. This will set the symlinks and keep them proper. Cheers Todd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
M. Todd Smith wrote:
On Nov 29, 2007, at 9:50 PM, Philipp Thomas wrote:
Manually created symlinks will be removed the next time insserv gets run!
Philipp
Is there anyway to circumvent this behaviour?
you may have to test it (it's simple, just write a dummy one), because I used to write such scripts myself and have never it deleted (but may be this is new) (in fact I had to write 'boot.final', that is a script like boot.local, but run at the end of the boot sequence) jdd -- http://www.dodin.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-12-03 at 13:44 -0500, M. Todd Smith wrote:
Is there anyway to circumvent this behaviour?
Of course there is, it is documented, and I explained it in this very thread a few days ago. You just have to read it :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHVIOQtTMYHG2NR9URAoBQAJ9cMvjAc8NgO8LrzN8oLfI/fXmy3wCeMVPg oFOaHHISZJx4FkuuK7UxGGE= =QS2I -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Dec 3, 2007, at 5:30 PM, Carlos E. R. wrote:
Of course there is, it is documented, and I explained it in this very thread a few days ago.
You just have to read it :-)
- -- Cheers, Carlos E. R.
My apologies, I just deleted my archive of suse mail this past week. Nevertheless the proper solution is now all scripted up and ready to be pushed out with some new installs later this evening. Cheers Todd Systems Administrator --------------------------------------------- Soho VFX - Visual Effects Studio 99 Atlantic Avenue, Suite 303 Toronto, Ontario, M6K 3J8 (416) 516-7863 http://www.sohovfx.com --------------------------------------------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (12)
-
Aaron Kulkis -
Carlos E. R. -
Jason Craig -
jdd -
K.R. Foley -
M. Todd Smith -
Marcus Meissner -
Myrosia Dzikovska -
Ortwin Ebhardt -
Philipp Thomas -
Sloan -
Verner Kjærsgaard