openSUSE - Recent changes [en]

openSUSE:Project meeting

2012-05-16T12:22:11Z

← Older revision		Revision as of 12:22, 16 May 2012
Line 18:		Line 18:
	* Revising and managing the artwork pages (by art team)		* Revising and managing the artwork pages (by art team)
	* Brief mention of the possible new widget style for opensuse (by art team)		* Brief mention of the possible new widget style for opensuse (by art team)
		+	* handling of SLE12 bugs (make them public?)

	==Minutes/Transcripts==		==Minutes/Transcripts==

openSUSE:ARM distribution howto

2012-05-16T08:02:20Z

Main Problems:

← Older revision		Revision as of 08:02, 16 May 2012
(One intermediate revision by one user not shown)
Line 9:		Line 9:
	Currently all packages are built in qemu emulation without any acceleration tricks. Using native assembler and compiler backends is on our plan.		Currently all packages are built in qemu emulation without any acceleration tricks. Using native assembler and compiler backends is on our plan.

−	~~Current main problems are~~	+	==Main Problems==
−	* ~~Please~~ use osc, build, qemu, qemu-linux-user and build-initvm from openSUSE:Tools:Unstable project to get all required fixes.	+	* You must use osc, build, qemu, qemu-linux-user and build-initvm from openSUSE:Tools:Unstable project to get all required fixes.
−	* armv5el seems to a have a ~~misscompilation~~ which can break the rpm database on build up of the build system	+	* armv5el seems to a have a miscompilation which can break the rpm database on build up of the build system

−	~~In general you can check~~ what is not building ~~by clicking~~ on [https://build.opensuse.org/project/monitor?commit=Filter%3A&failed=1&pkgname=&repo_armv5el=1&repo_armv7hl=1&repo_images=1&arch_armv5el=1&arch_armv7hl=1&arch_local=1&project=openSUSE%3AFactory%3AARM&defaults=0 the monitor page].	+	To see what is not building, click on [https://build.opensuse.org/project/monitor?commit=Filter%3A&failed=1&pkgname=&repo_armv5el=1&repo_armv7hl=1&repo_images=1&arch_armv5el=1&arch_armv7hl=1&arch_local=1&project=openSUSE%3AFactory%3AARM&defaults=0 the monitor page].
−	To fix a package, ~~please~~ submit it to the standard openSUSE:Factory project because openSUSE:Factory:ARM links against it and uses all sources from there.	+	To fix a package, submit it to the standard openSUSE:Factory project because openSUSE:Factory:ARM links against it and uses all sources from there.

	For example to fix the package hello run the following commands:		For example to fix the package hello run the following commands:
−	* osc bco openSUSE:Factory hello # note NOT to use openSUSE:Factory:ARM here	+	osc bco openSUSE:Factory hello # note NOT to use openSUSE:Factory:ARM here
−	* cd home:<username>:branches:<branched base project name>/hello	+	cd home:<username>:branches:<branched base project name>/hello
−	* fix the stuff	+	Then fix the stuff, produce a test build, and submit it to the Build Service. NOTE: the local build works only on arm hardware or on x86_64 systems (using qemu-linux-user):
−	* osc build ~~--alternative-project=openSUSE:Factory:ARM standard armv7l hello~~.~~spec~~	+	osc build --alternative-project=openSUSE:Factory:ARM standard armv7l hello.spec
−	NOTE: the local build works only on arm hardware or on x86_64 systems (using qemu-linux-user).	+	osc vc # to comment your change to the end user
−	* osc vc # to comment your change to the end user	+	osc ci # checkin your stuff
−	* osc ci # checkin your stuff	+	osc sr # submit it to the devel project which will forward it to factory
−	* osc sr # submit it to the devel project which will forward it to factory.	+

	[[Category:ARM\|{{PAGENAME}}]]		[[Category:ARM\|{{PAGENAME}}]]
	[[Category:Build Service\|ARM]]		[[Category:Build Service\|ARM]]

openSUSE:Project meeting

2012-05-16T03:12:59Z

← Older revision		Revision as of 03:12, 16 May 2012
(2 intermediate revisions by one user not shown)
Line 15:		Line 15:

	* Forum infrastructure stability [[User:Hendersj\|Hendersj]] 12:39, 21 April 2012 (MDT)		* Forum infrastructure stability [[User:Hendersj\|Hendersj]] 12:39, 21 April 2012 (MDT)
		+	* Documenting the New Branding and design guidelines. Wiki, or similar setup. (by art team)
		+	* Revising and managing the artwork pages (by art team)
		+	* Brief mention of the possible new widget style for opensuse (by art team)

	==Minutes/Transcripts==		==Minutes/Transcripts==

SDB:Installing Java

2012-05-15T22:07:57Z

openSUSE 12.1:

← Older revision		Revision as of 22:07, 15 May 2012
Line 3:		Line 3:

	=== openSUSE 12.1 ===		=== openSUSE 12.1 ===
−	In openSUSE 12.1, Oracle (Sun) Java JRE 6 is no longer included in the openSUSE Non-OSS repository.	+	In openSUSE 12.1, Oracle (Sun) Java JRE is no longer included in the openSUSE Non-OSS repository.

−	You can use an alternative, such as this easy step-by-step how-to, for manual installation of the latest and secure version: [http://sites.google.com/site/easylinuxtipsproject/java-for-opensuse Install Oracle (Sun) Java JRE 6 for openSUSE]	+	You can use an alternative, such as this easy step-by-step how-to, for manual installation of the latest and secure version: [http://sites.google.com/site/easylinuxtipsproject/java-for-opensuse Install Oracle (Sun) Java JRE 7 for openSUSE]

−	Note: do NOT use the dedicated Java repository of openSUSE, as it contains an outdated and insecure version ~~(6u26)~~.	+	Note: do NOT use the dedicated Java repository of openSUSE, as it contains an outdated and insecure version.

	----		----

openSUSE:LinuxTag

2012-05-15T21:42:08Z

Notice: You have to book the hotel yourself!:

← Older revision		Revision as of 21:42, 15 May 2012
Line 150:		Line 150:
	\|}		\|}

−	~~Notice~~ that you have to book the hotel yourselves!!! Ask on -project or -ambassadors if someone wants to share a room...	+	note: I've ordered passes for everyone who had subscribed for the booth up to Cornelius.
		+
		+	Note that you have to book the hotel yourselves!!! Ask on -project or -ambassadors if someone wants to share a room...

	{{Section\|Booth/Material}}		{{Section\|Booth/Material}}

openSUSE:LinuxTag

2012-05-15T13:09:45Z

Notice: You have to book the hotel yourself!:

← Older revision		Revision as of 13:09, 15 May 2012
Line 133:		Line 133:
	\| train		\| train
	\|		\|
		+	\|-
		+	\| [[User:cschum\|Cornelius Schumacher]]
		+	\| Tuesday
		+	\| Sunday
		+	\| Group hotel
		+	\| train
		+	\| speaker
	\|-		\|-
	\| ''You?''		\| ''You?''

openSUSE:LinuxTag

2012-05-14T22:15:49Z

← Older revision		Revision as of 22:15, 14 May 2012
Line 17:		Line 17:
	** End: May 27th		** End: May 27th
	** Opening Times: Mi.-Fr.: 9:45 - 18:00; Sa.: 9:45- 17:00		** Opening Times: Mi.-Fr.: 9:45 - 18:00; Sa.: 9:45- 17:00
−	* '''Do we have a booth?''' Yes	+	* '''Do we have a booth?''' Yes, booth 202 'openSUSE Community' in 7.2a
	* '''Who is organizing this event?''' [[User:jospoortvliet\|Jos Poortvliet]]		* '''Who is organizing this event?''' [[User:jospoortvliet\|Jos Poortvliet]]
	* '''Will there be any openSUSE related talks?''' Yes		* '''Will there be any openSUSE related talks?''' Yes
Line 147:		Line 147:
	{{Section\|Booth/Material}}		{{Section\|Booth/Material}}

−	I (jos) have applied for a booth and tickets. We've got the booth confirmed. It will be 14m2 and have 2 tables and 6 chairs. Everything else we'll have to get ourselves.	+	I (jos) have applied for a booth and tickets. We've got the booth confirmed. It will be 14m2 and have 2 tables and 6 chairs. Everything else we'll have to get ourselves. Number 202, hall 7.2a!

	Some material is needed for the booth setup. Please add things you are able to provide.		Some material is needed for the booth setup. Please add things you are able to provide.

SDB:Configure openSSH

2012-05-14T19:48:17Z

just corrected a typo.

← Older revision		Revision as of 19:48, 14 May 2012
Line 49:		Line 49:
	===Reloading Configuration===		===Reloading Configuration===
	Whenever you made a change to <tt>/etc/ssh/sshd_config</tt> you must restart the SSHD or let it reload his configuration by typing:		Whenever you made a change to <tt>/etc/ssh/sshd_config</tt> you must restart the SSHD or let it reload his configuration by typing:
−	{{shell\|$ rcsshd restart}}	+	{{shell\|# rcsshd restart}}
	or		or
−	{{shell\|$ rcsshd reload}}	+	{{shell\|# rcsshd reload}}
	You can do this with a running SSH connection and you don't need to log out. But the changes will only take effect for each user, the next time they try to log in.		You can do this with a running SSH connection and you don't need to log out. But the changes will only take effect for each user, the next time they try to log in.
	----		----

openSUSE:Map/Coordinates

2012-05-14T17:37:35Z

← Older revision		Revision as of 17:37, 14 May 2012
Line 461:		Line 461:
	{{map_user\|41.878114\|-87.629798\|suseROCKs\|Bryen M Yunashko\|http:/en.opensuse.org/User:Byunashko}}		{{map_user\|41.878114\|-87.629798\|suseROCKs\|Bryen M Yunashko\|http:/en.opensuse.org/User:Byunashko}}
	{{map_user\|46.229964\|17.357159\|cuxer\|Nagyatád, Hungary\|https://connect.opensuse.org/pg/profile/cuxer}}		{{map_user\|46.229964\|17.357159\|cuxer\|Nagyatád, Hungary\|https://connect.opensuse.org/pg/profile/cuxer}}
		+	{{map_user\|-37.957564\|-57.575526\|Tavomazzei\|Mar del Plata, Argentina\|https://connect.opensuse.org/pg/profile/Tavomazzei}}

openSUSE:Testing meeting

2012-05-14T17:28:58Z

Next meeting:

← Older revision		Revision as of 17:28, 14 May 2012
Line 6:		Line 6:
	==Next meeting==		==Next meeting==
	{{Point here\|[[Image:Icon-event.png\|48px]]\|		{{Point here\|[[Image:Icon-event.png\|48px]]\|
−	===2012-05-07 17:00 UTC===	+	===2012-05-15 17:00 UTC===

	'''Agenda'''		'''Agenda'''

openSUSE:Synology NAS

2012-05-14T13:02:57Z

Backup: add link to obs package

← Older revision		Revision as of 13:02, 14 May 2012
Line 23:		Line 23:

	# Enable the ''Network Backup'' in Synology's ''Control Panel''		# Enable the ''Network Backup'' in Synology's ''Control Panel''
−	# Install ''luckybackup'' from the [[KDE repositories\|KDE:Extra package repository]] that fits your KDE repo	+	# Install ''[http://software.opensuse.org/download/package?project=KDE:Extra&package=luckybackup luckybackup]'' from the [[KDE repositories\|KDE:Extra package repository]] that fits your KDE repo
	# Start luckybackup and create a new task. As destination enter ''NetBackup'' click on ''Advanced'' and enter ''rsync'' or ''admin'' as username in the ''Remote''-tab, enable ''Remote module'' and point it to a file with the password. The file must only contain the password and a line break after it. Further it has to be readable to the owner only, i.e. you have to change the file's permissions with dolphin by right-clicking it ''Properties > Permissions'' and setting group and others to denied.		# Start luckybackup and create a new task. As destination enter ''NetBackup'' click on ''Advanced'' and enter ''rsync'' or ''admin'' as username in the ''Remote''-tab, enable ''Remote module'' and point it to a file with the password. The file must only contain the password and a line break after it. Further it has to be readable to the owner only, i.e. you have to change the file's permissions with dolphin by right-clicking it ''Properties > Permissions'' and setting group and others to denied.

openSUSE:KDE team

2012-05-14T09:36:44Z

Added lost colon

← Older revision		Revision as of 09:36, 14 May 2012
Line 33:		Line 33:
	* [[User:Wstephenson\|Will Stephenson]] ([http://www.kdedevelopers.org/blog/77 Blog], IRC: wstephenson)		* [[User:Wstephenson\|Will Stephenson]] ([http://www.kdedevelopers.org/blog/77 Blog], IRC: wstephenson)
	* [[:en:User:Cartman\|Ismail Donmez]] (IRC: Cartman)		* [[:en:User:Cartman\|Ismail Donmez]] (IRC: Cartman)
−	* [[~~UserMlin7442~~\|Max Lin]] (IRC: maxlin)	+	* [[User:Mlin7442\|Max Lin]] (IRC: maxlin)

	From the community:		From the community:

openSUSE:Boosters team

2012-05-14T04:09:34Z

Add myself to the list

← Older revision		Revision as of 04:09, 14 May 2012
Line 64:		Line 64:
	\|-		\|-
	\| style="border: 1px solid gray; text-align: left;" \| http://a2.twimg.com/profile_images/1269164014/8d1b0cd0-9734-4719-a1da-3d9e8479fa0e_normal.png [[User:Namtrac\|Ismail Dönmez]] \|\| style="border: 1px solid gray;" \| cartman \|\| style="border: 1px solid gray;" \| - \|\| style="border: 1px solid gray;" \| - \|\| style="border: 1px solid gray;" \| [http://twitter.com/#!/divildivil @divildivil] \|\| style="border: 1px solid gray;" \| idoenmez@		\| style="border: 1px solid gray; text-align: left;" \| http://a2.twimg.com/profile_images/1269164014/8d1b0cd0-9734-4719-a1da-3d9e8479fa0e_normal.png [[User:Namtrac\|Ismail Dönmez]] \|\| style="border: 1px solid gray;" \| cartman \|\| style="border: 1px solid gray;" \| - \|\| style="border: 1px solid gray;" \| - \|\| style="border: 1px solid gray;" \| [http://twitter.com/#!/divildivil @divildivil] \|\| style="border: 1px solid gray;" \| idoenmez@
		+	\|-
		+	\| style="border: 1px solid gray; text-align: left;" \| [[User:mlin7442\|Max Lin]] \|\| style="border: 1px solid gray;" \| maxlin \|\| style="border: 1px solid gray;" \| http://maxlin.tumblr.com/ \|\| style="border: 1px solid gray;" \| - \|\| style="border: 1px solid gray;" \| [http://twitter.com/nilxam @nilxam] \|\| style="border: 1px solid gray;" \| mlin@
	\|}		\|}

openSUSE:Evergreen 11.2

2012-05-13T19:34:37Z

← Older revision		Revision as of 19:34, 13 May 2012
Line 9:		Line 9:
	!style="background:#669900;color:#fff;width:11em"\| CVE		!style="background:#669900;color:#fff;width:11em"\| CVE
	!style="background:#669900;color:#fff"\|		!style="background:#669900;color:#fff"\|
		+	\|-
		+	\| style="text-align:left;padding-left:1em;" \| opera
		+	\| released
		+	\| {{Bug\|761633}}
		+	\| see changelog
		+	\| ver. 11.64
	\|-		\|-
	\| style="text-align:left;padding-left:1em;" \| php5		\| style="text-align:left;padding-left:1em;" \| php5

openSUSE:Ambassadors events

2012-05-13T18:09:57Z

← Older revision		Revision as of 18:09, 13 May 2012
Line 445:		Line 445:
	\| <!-- Type --> Booth + Presentations		\| <!-- Type --> Booth + Presentations
	\| <!-- Report and material -->		\| <!-- Report and material -->
		+	\|-
		+	\| <!-- Continent --> NA
		+	\| <!-- Country --> US
		+	\| <!-- Event --> GSLUG
		+	\| <!-- Date --> 12 May
		+	\| <!-- City/Town --> Fremont (Seattle) WA
		+	\| <!-- Ambassador --> [[User:Brando\|Brandon Fouts]]
		+	\| <!-- Page in the Wiki -->
		+	\| <!-- Type --> putting Linux on ZipIt Z2
		+	\| <!-- Report and material --> http://en.wikipedia.org/wiki/Zipit_wireless_messenger_(Z2)
	\|-		\|-
	\| <!-- Continent --> NA		\| <!-- Continent --> NA

User:Medwin

2012-05-13T03:41:30Z

About me:

← Older revision		Revision as of 03:41, 13 May 2012
(One intermediate revision by one user not shown)
Line 5:		Line 5:

	Use SuSE since 6.2 <br>		Use SuSE since 6.2 <br>
−	Currently maintain some machines with ~~10.3,~~ 11.0, ~~11.~~1, 11.2, 11.3, SLES 10, SLES 11	+	Currently maintain some machines with 11,1, 11.2, 11.3, 11.4, 12.1, SLES 10, SLES 11-SP1
		+	Large deployment of openSUSE (mainly Li-f-e 11.3, 11.4): http://ict-eqep.com/locations/map_350.html

	* [https://users.opensuse.org/show/Medwin openSUSE Member] <br>		* [https://users.opensuse.org/show/Medwin openSUSE Member] <br>
−	* [http://en.opensuse.org/OpenSUSE_Weekly_News/Team openSUSE Weekly News Team], [http://en.opensuse.org/OpenSUSE_Weekly_News/Translators OWN Coordinator for Indonesia Translation] ~~well I'm a bit busy~~ right now, ~~but will be back soon~~<br>	+	* [http://en.opensuse.org/OpenSUSE_Weekly_News/Team openSUSE Weekly News Team], [http://en.opensuse.org/OpenSUSE_Weekly_News/Translators OWN Coordinator for Indonesia Translation] Not active right now, a bit busy<br>
	* co-administrator milis@lists.opensuse-id.org, http://opensuse.or.id <br>		* co-administrator milis@lists.opensuse-id.org, http://opensuse.or.id <br>
−	* Blog: http://medwinz.~~blogsome~~.com <br>	+	* Indonesia Translation Team for openSUSE documentation: http://opensuse.or.id/2012/04/03/selamat-bekerja-para-pejuang-opensuse-indonesia/ <br>
		+	* Blog: http://medwinz.blogspot.com <br>
	* IRC: slowhand, opensuse/member/medwin <br>		* IRC: slowhand, opensuse/member/medwin <br>
	* Mail: medwin@opensuse.org, medwinz@gmail.com<br>		* Mail: medwin@opensuse.org, medwinz@gmail.com<br>

NFS

2012-05-12T14:26:01Z

it link added, reformatted section titles, added notes about yast2-nfs-server and shell template

← Older revision		Revision as of 14:26, 12 May 2012
Line 1:		Line 1:
−	~~=About=~~
	[[NFS\|Network File System]] ([[NFS]]) is a protocol originally developed by Sun Microsystems in 1984 and defined in RFCs [http://www.ietf.org/rfc/rfc1094.txt 1094], [http://www.ietf.org/rfc/rfc1813.txt 1813], and [http://www.ietf.org/rfc/rfc3530.txt 3530] (obsoletes [http://www.ietf.org/rfc/rfc3010.txt 3010]), as a distributed file system which allows a computer to access files over a [[Network\|network]] as easily as if they were on its local disks. [[NFS]] is one of many protocols built on the Open Network Computing Remote Procedure Call system (ONC RPC).		[[NFS\|Network File System]] ([[NFS]]) is a protocol originally developed by Sun Microsystems in 1984 and defined in RFCs [http://www.ietf.org/rfc/rfc1094.txt 1094], [http://www.ietf.org/rfc/rfc1813.txt 1813], and [http://www.ietf.org/rfc/rfc3530.txt 3530] (obsoletes [http://www.ietf.org/rfc/rfc3010.txt 3010]), as a distributed file system which allows a computer to access files over a [[Network\|network]] as easily as if they were on its local disks. [[NFS]] is one of many protocols built on the Open Network Computing Remote Procedure Call system (ONC RPC).

	The term "network file system" is also often used as a generic term.		The term "network file system" is also often used as a generic term.
−	=Install NFS kernel server=	+	==Install NFS kernel server==
−	Sucessful NFS installations often include <code>nfs-kernel-server</code> package from openSUSE repositories. Simply install from YaST, or from command line type:	+	Sucessful NFS installations often include <code>nfs-kernel-server</code> package from openSUSE repositories. Simply install from YaST, or from command line type (as root):
−	~~zypper in nfs-kernel-server~~	+

−	=Configure /etc/exports file=	+	{{Shell\|zypper in nfs-kernel-server}}
		+
		+	Anyway this package will be automatically installed if you decide to use the NFS Server Configuration YaST2 module (or you would like to have it at hand). In this case you can simply install <tt>yast2-nfs-server</tt> package from YaST, or from command line type (as root):
		+
		+	{{Shell\|zypper in yast2-nfs-server}}
		+
		+	==Configure /etc/exports file==
	Editing the <code>/etc/exports</code> file is quite easy. Each line contains an export point and a whitespace-separated list of clients allowed to mount the file system at that point. Each listed client may be immediately followed by a parenthesized, comma-separated list of export options for that client. No whitespace is permitted between a client and its option list.		Editing the <code>/etc/exports</code> file is quite easy. Each line contains an export point and a whitespace-separated list of clients allowed to mount the file system at that point. Each listed client may be immediately followed by a parenthesized, comma-separated list of export options for that client. No whitespace is permitted between a client and its option list.
		+	Examples:
	/export/this/directory (ro)		/export/this/directory (ro)
	This shares the directory read-only to '''ALL''' hosts, including those on the Internet! You may also include a <code>*</code> immediately before <code>(ro)</code>.		This shares the directory read-only to '''ALL''' hosts, including those on the Internet! You may also include a <code>*</code> immediately before <code>(ro)</code>.
Line 17:		Line 22:
	See <code>man exports</code> for a greater list of options.		See <code>man exports</code> for a greater list of options.

−	= Versions and variations =	+	==Versions and variations==
	Version 2 of the protocol originally operated entirely over [[UDP]] and was meant to keep the protocol stateless, with locking (for example) implemented outside of the core protocol.		Version 2 of the protocol originally operated entirely over [[UDP]] and was meant to keep the protocol stateless, with locking (for example) implemented outside of the core protocol.

Line 30:		Line 35:
	WebNFS is an extension to Version 2 and Version 3 which allows [[NFS]] to be more easily integrated into Web browsers and to enable operation through firewalls.		WebNFS is an extension to Version 2 and Version 3 which allows [[NFS]] to be more easily integrated into Web browsers and to enable operation through firewalls.

−	= Platforms =	+	==Platforms==
	[[NFS]] is strongly associated with UNIX systems, though it can be used on any platform such as Macintosh, Windows and [[Novell]] [[NetWare]] operating systems. The [[Samba\|Server Message Block]] (SMB also known as CIFS) and [[NetWare Core Protocol]] (NCP), similar protocols, are equivalent implementations of a network file system under other operating systems. Cross-platform compatibility makes [[NFS]] an ideal network file system implementation.		[[NFS]] is strongly associated with UNIX systems, though it can be used on any platform such as Macintosh, Windows and [[Novell]] [[NetWare]] operating systems. The [[Samba\|Server Message Block]] (SMB also known as CIFS) and [[NetWare Core Protocol]] (NCP), similar protocols, are equivalent implementations of a network file system under other operating systems. Cross-platform compatibility makes [[NFS]] an ideal network file system implementation.
−	=Automatically mounting NFS at boot-up=	+	==Automatically mounting NFS at boot-up==
	There is some widespread difficulty about automatically mounting NFS share at boot up. You MUST enable <code>nfs</code> daemon like this:		There is some widespread difficulty about automatically mounting NFS share at boot up. You MUST enable <code>nfs</code> daemon like this:
−	chkconfig nfs	+	{{Shell\|# chkconfig nfs}}
	If you see '''off''', then you must:		If you see '''off''', then you must:
−	chkconfig nfs on	+	{{Shell\|# chkconfig nfs on}}
	Your <code>/etc/fstab</code> must include (at least):		Your <code>/etc/fstab</code> must include (at least):
	remotehost:/path/to/export /local/mountpoint nfs auto 0 0		remotehost:/path/to/export /local/mountpoint nfs auto 0 0
Line 46:		Line 51:
	*[[Samba\|SMB]]/[[CIFS]]		*[[Samba\|SMB]]/[[CIFS]]

−	= External links =	+	==External links==

	* [http://www.tldp.org/ The Linux Documentation Project] has several [[howto]] articles on NFS in different formats.		* [http://www.tldp.org/ The Linux Documentation Project] has several [[howto]] articles on NFS in different formats.
Line 62:		Line 67:

	[[Category:LAN and Internet]]		[[Category:LAN and Internet]]
		+	[[it:NFS]]

SDB:Configure openSSH

2012-05-12T13:30:26Z

corrected a typo

← Older revision		Revision as of 13:30, 12 May 2012
Line 29:		Line 29:
	'''SSHD''' ('''Secure Shell Daemon''') should be run on the server. (Remote host). The SSHD manages incoming connections, authentication, rules and encryption.		'''SSHD''' ('''Secure Shell Daemon''') should be run on the server. (Remote host). The SSHD manages incoming connections, authentication, rules and encryption.

−	The SSHD has only one configuration file, which can be found in <tt>/etc/ssh/sshd_config</tt>. You can edit this file by using your favorite editor as root. The configuration of the SSHD quite general and only to build in limitations for the users that (try) to login. The actual connection parameters will be set from the client side. When setting up the SSHD you must keep in mind what you think is save or appropriate to allow. For instance: if you prohibit X forwarding in SSHD, setting up the client for X forwarding would be useless. So think wisely for what you are going to use the SSH connection when setting up the SSHD.	+	The SSHD has only one configuration file, which can be found in <tt>/etc/ssh/sshd_config</tt>. You can edit this file by using your favorite editor as root. The configuration of the SSHD is quite general and only to build in limitations for the users that (try) to login. The actual connection parameters will be set from the client side. When setting up the SSHD you must keep in mind what you think is save or appropriate to allow. For instance: if you prohibit X forwarding in SSHD, setting up the client for X forwarding would be useless. So think wisely for what you are going to use the SSH connection when setting up the SSHD.
	{{Info\|It is also possible to configure the SSHD under Yast2 by installing the yast2-sshd package. This is a GUI which will update <tt>/etc/ssh/sshd_config</tt> for you. In this article we will stick to editing <tt>/etc/ssh/sshd_config</tt> directly.}}		{{Info\|It is also possible to configure the SSHD under Yast2 by installing the yast2-sshd package. This is a GUI which will update <tt>/etc/ssh/sshd_config</tt> for you. In this article we will stick to editing <tt>/etc/ssh/sshd_config</tt> directly.}}
		+
	===SSH – The Client===		===SSH – The Client===
	'''SSH''' ('''Secure Shell''') Is one of the client programs of the openSSH package. This program is used to login in to a remote shell or to directly run a remote command. In this article we will refer to the SSH configuration files, although they also apply to [[SDB:SFTP usage\|SFTP]] and [[SDB:SCP usage\|SCP]].		'''SSH''' ('''Secure Shell''') Is one of the client programs of the openSSH package. This program is used to login in to a remote shell or to directly run a remote command. In this article we will refer to the SSH configuration files, although they also apply to [[SDB:SFTP usage\|SFTP]] and [[SDB:SCP usage\|SCP]].

Packaging/Users And Groups

2012-05-12T11:44:32Z

Created page with "{{Packaging_navbar}} = Users and groups = Creating users and groups during package install is one of the major parts for packages containing daemons. If you package contains a ..."

New page

{{Packaging_navbar}}

= Users and groups =

Creating users and groups during package install is one of the major parts for packages containing daemons. If you package contains a daemon, consider creating a special user/group running this daemon to improve security.

== Specfile snipplets ==

== Creating group during package install ===

<pre>
Requires(Pre): pwdutils
%define daemon_group bar
...
%pre
# create daemon group, if not existing
if
getent group %{daemon_group} >/dev/null
then
: OK group %{daemon_group} already present
else
groupadd -r %{daemon_group} 2>/dev/null || :
fi
</pre>

=== Creating user during package install ===

Please note that this example uses a special group that was created before via the snipplet above.

Users should get a home directory with at least read access. Sometimes it makes also sense to use a directory that is writable by the daemon user. This makes debugging easier (think about a "su - $daemon_user").

<pre>
Requires(Pre): pwdutils
%define daemon_user foo
...
%pre
# create daemon user, if not existing
if
getent passwd %{daemon_user} >/dev/null
then
: OK user %{daemon_user} already present
else
useradd -r -o -g %{daemon_group} -s /bin/false -c "FOO daemon" -d %{_var}/lib/%{name} %{daemon_user} 2> /dev/null || :
fi
</pre>

= List of already used users and groups =

A list of currently allowed users and groups in openSUSE Factory can be found inside the package [https://build.opensuse.org/ please_find_me].

User:Pjessen

2012-05-12T09:56:12Z

open source and me:

← Older revision		Revision as of 09:56, 12 May 2012
(3 intermediate revisions by one user not shown)
Line 13:		Line 13:
	== Contact info ==		== Contact info ==

−	* email: [mailto:per@~~opensuse~~.org per@~~opensuse~~.org]	+	* email: [mailto:per@computer.org per@computer.org]
	<div style="display:none">mailto:zinc.anode@jessen.ch please do not send emails to this address</div>		<div style="display:none">mailto:zinc.anode@jessen.ch please do not send emails to this address</div>

−	== ~~SUSE~~ and me ==	+	== SuSE and I ==

	It's been a long time since I - more or less by accident - picked up a copy of SuSE Linux 4.4.1 in the [http://www.hugendubel.de/ Hugendubel bookstore] on Marienplatz in München. I think it must have been around 1996, but I'm not sure. Since then I believe I've bought versions 5.3, 6.1, 6.4, 7.0, 7.1, 7.3, 8.0, 8.1, 8.2, 9.1, and 9.3. I still have most of the CDs, the boxes and manuals from those. Starting with 10.0, I've been fairly active in the alpha- and beta-test programme, and as a thank you for my efforts, Novell has been kind enough to send me a copy of 10.0 etc.		It's been a long time since I - more or less by accident - picked up a copy of SuSE Linux 4.4.1 in the [http://www.hugendubel.de/ Hugendubel bookstore] on Marienplatz in München. I think it must have been around 1996, but I'm not sure. Since then I believe I've bought versions 5.3, 6.1, 6.4, 7.0, 7.1, 7.3, 8.0, 8.1, 8.2, 9.1, and 9.3. I still have most of the CDs, the boxes and manuals from those. Starting with 10.0, I've been fairly active in the alpha- and beta-test programme, and as a thank you for my efforts, Novell has been kind enough to send me a copy of 10.0 etc.
Line 22:		Line 22:
	Today I use only openSUSE and SUSE Linux. In fact, in my company we use only Linux and open source software, perhaps with one or two exceptions (our double entry book-keeping software is a Windows product). I've had occasional flings with Gentoo, Debian, Mandrake and Ubuntu, but never for very long and I've always returned to SUSE.		Today I use only openSUSE and SUSE Linux. In fact, in my company we use only Linux and open source software, perhaps with one or two exceptions (our double entry book-keeping software is a Windows product). I've had occasional flings with Gentoo, Debian, Mandrake and Ubuntu, but never for very long and I've always returned to SUSE.

−	== Linux and me ==	+	== Linux and I ==

	* Linux S/390		* Linux S/390
Line 28:		Line 28:
	It's probably worth mentioning my interest in Linux S/390. I've spent the majority of my professional life writing software for IBM operating systems (MVS, TPF), so when I started working for [http://www.bea.com/ BEA Systems] in 2001, it wasn't long before I began to look at running Weblogic on the mainframe. This quickly led to a couple of minor contributions to the [http://www.hercules-390.org/ Hercules System/390 emulator], and somehow I also got involved in an initial effort of getting [http://www.sapdb.org/ SAPDB] (now [http://www.sdn.sap.com/irj/sdn/maxdb MAXDB]) to build and run on Linux-390.		It's probably worth mentioning my interest in Linux S/390. I've spent the majority of my professional life writing software for IBM operating systems (MVS, TPF), so when I started working for [http://www.bea.com/ BEA Systems] in 2001, it wasn't long before I began to look at running Weblogic on the mainframe. This quickly led to a couple of minor contributions to the [http://www.hercules-390.org/ Hercules System/390 emulator], and somehow I also got involved in an initial effort of getting [http://www.sapdb.org/ SAPDB] (now [http://www.sdn.sap.com/irj/sdn/maxdb MAXDB]) to build and run on Linux-390.

−	* Linux ~~IA32~~	+	* Linux Intel

−	Running Linux on ~~32bit~~ Intel-compatible hardware is the basis of how I make a living. I maintain a production environment the two datacentres - locally, mostly HP Proliants, remotely leased boxes with AMD and Intel processors.	+	Running Linux on Intel-compatible hardware is the basis of how I make a living. I maintain a production environment the two datacentres - locally, mostly HP Proliants, remotely leased boxes with AMD and Intel processors.

−	== open source and me ==	+	== open source and I ==

	Since the late 90s, I have contributed to a number of open source projects, some of which are: hercules, dosemu, etherboot, maxdb, spamassassin and clamav. There's probably more, but those are what I remember right now.		Since the late 90s, I have contributed to a number of open source projects, some of which are: hercules, dosemu, etherboot, maxdb, spamassassin and clamav. There's probably more, but those are what I remember right now.

Configuring graphics cards/Monitor Settings

2012-05-11T21:43:11Z

it link added, reformatted some preformatted text, category added

← Older revision		Revision as of 21:43, 11 May 2012
Line 1:		Line 1:
	Sometimes X-server may be having a problem with the monitor's Extended Display Identification Data (EDID) and falling back to a safe resolution which is much lower than what it is capable of.		Sometimes X-server may be having a problem with the monitor's Extended Display Identification Data (EDID) and falling back to a safe resolution which is much lower than what it is capable of.

−	If this is the case then the '''/etc/X11/xorg.conf.d//50-monitor.conf''' file may have to be modified.	+	If this is the case then the '''<tt>/etc/X11/xorg.conf.d/50-monitor.conf</tt>''' file may have to be modified.

	For exmple, an Acer X223w with a resolution of 1680x1050 needs to have its HorizSync and VertRefresh defined to display its native resolution.		For exmple, an Acer X223w with a resolution of 1680x1050 needs to have its HorizSync and VertRefresh defined to display its native resolution.

−	Section "Monitor"	+	Section "Monitor"
−	Identifier "Monitor1"	+	Identifier "Monitor1"
−	VendorName "Unknown"	+	VendorName "Unknown"
−	ModelName "Acer X223W"	+	ModelName "Acer X223W"
−	HorizSync 31.0 - 84.0	+	HorizSync 31.0 - 84.0
−	VertRefresh 56.0 - 77.0	+	VertRefresh 56.0 - 77.0
−	EndSection	+	EndSection

	You will have to search for what the correct HorizSync and VertRefresh for your own monitor.		You will have to search for what the correct HorizSync and VertRefresh for your own monitor.
Line 19:		Line 19:
	You can also add a modeline if needed, but try the above first.		You can also add a modeline if needed, but try the above first.

−	To calculate the modeline you need to use the cvt command. See the discussion here about it's usage. http://forums.opensuse.org/english/get-technical-help-here/how-faq-forums/unreviewed-how-faq/430150-opensuse-graphic-card-practical-theory-guide-users-6.html#post2280876	+	To calculate the modeline you need to use the <code>cvt</code> command. See the discussion here about it's usage. http://forums.opensuse.org/english/get-technical-help-here/how-faq-forums/unreviewed-how-faq/430150-opensuse-graphic-card-practical-theory-guide-users-6.html#post2280876

	So for a resolution of 1680x1050:		So for a resolution of 1680x1050:

		+	{{Shell\|$ cvt 1680 1050}}
		+	Answer:
		+	# 1680x1050 59.95 Hz (CVT 1.76MA) hsync: 65.29 kHz; pclk: 146.25 MHz
		+	Modeline "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync

−	~~cvt 1680 1050~~

−	~~# 1680x1050 59~~.~~95 Hz (CVT 1~~.~~76MA) hsync: 65~~.~~29 kHz; pclk: 146~~.~~25 MHz~~	+	The '''<tt>/etc/X11/xorg.conf.d/50-monitor.conf</tt>''' file now looks like this.
−	~~Modeline "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync~~	+

		+	Section "Monitor"
		+	Identifier "Monitor1"
		+
		+	VendorName "Unknown"
		+	ModelName "Acer X223W"
		+	HorizSync 31.0 - 84.0
		+	VertRefresh 56.0 - 77.0
		+
		+	ModeLine "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync
		+
		+	EndSection

−	~~The '''~~/~~etc/X11/xorg.conf.d//50-monitor.conf''' file now looks like this.~~	+	[[Category:Graphic_cards]]
−		+	[[it:Configurare_le_schede_grafiche/Impostazioni_del_monitor]]
−	~~Section "Monitor"~~	+
−	~~Identifier "Monitor1"~~	+
−	~~VendorName "Unknown"~~	+
−	~~ModelName "Acer X223W"~~	+
−	~~HorizSync 31.0 - 84.0~~	+
−	~~VertRefresh 56.0 - 77.0~~	+
−	~~ModeLine "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync~~	+
−		+
−	~~EndSection~~	+

openSUSE:Documentation Emacs Docbook Macros

2012-05-11T21:36:05Z

Corrected link

← Older revision		Revision as of 21:36, 11 May 2012
Line 1:		Line 1:
	Here is a macro package to insert the most often used DocBook snippets. The goal was to find the most efficient shortcut for often used tag combinations. All the code inserted to your documents will be indented correctly and the cursor is placed in a way that you can start typing immediately.		Here is a macro package to insert the most often used DocBook snippets. The goal was to find the most efficient shortcut for often used tag combinations. All the code inserted to your documents will be indented correctly and the cursor is placed in a way that you can start typing immediately.

−	The macros require the psgml-mode (package psgml). When the macros are loaded, you will see a new menu "DocBook" listing all the macros and the corresponding keyboard shortcuts. Of course you can load the macros with M-x <function-name> as well. The function names all start with "docbook-" followed by an element string: docbook-remark, docbook-table, docbook-step, etc.	+	The macros require the nxml-mode or, alternatively, the psgml-mode (package psgml). When the macros are loaded, you will see a new menu "DocBook" listing all the macros and the corresponding keyboard shortcuts. Of course you can load the macros with M-x <function-name> as well. The function names all start with "docbook-" followed by an element string: docbook-remark, docbook-table, docbook-step, etc.

−	The lisp file is located ~~in svn.opensuse.org~~ at [~~[http~~://~~svn~~.~~opensuse.org~~/~~viewvc~~/~~opensuse-doc~~/~~trunk~~/~~tools~~/~~docmaker/etc/emacs_docbook_macros.el~~ /trunk/~~tools~~/~~docmaker~~/~~etc/emacs_docbook_macros~~.el/]] and is also available with the ~~daps~~ package. To load it, put the following line to your emacs customization file (~/.emacs or ~/.gnu-emacs, ...):	+	The lisp file is located at the DAPS repository on SourceForge: [https://sourceforge.net/p/daps/svn/1472/tree/trunk/daps/misc/docbook_macros.el?force=True docbook_macros.el] and is also available with the DAPS package. To load it, put the following line to your emacs customization file (~/.emacs or ~/.gnu-emacs, ...):

	{{shell\|(load "PATH/emacs_docbook_macros.el" t t)}}		{{shell\|(load "PATH/emacs_docbook_macros.el" t t)}}

openSUSE:LinuxTag

2012-05-11T20:01:07Z

General Program:

← Older revision		Revision as of 20:01, 11 May 2012
(One intermediate revision by one user not shown)
Line 81:		Line 81:
	\| Thursday morning		\| Thursday morning
	\| Saturday		\| Saturday
−	\| ~~Not sure yet~~	+	\| Speakers hotel
	\| night train from / ICE to Karlsruhe		\| night train from / ICE to Karlsruhe
	\|		\|
Line 213:		Line 213:
	There will be several talks from/about our distribution, community and tools in the general program.		There will be several talks from/about our distribution, community and tools in the general program.
	* Installing and setting up your ownCloud (Jos)		* Installing and setting up your ownCloud (Jos)
−		+	* 1001 Bugs - oder: die goldenen Regeln für schlechte Programmierung (Christian Boltz)

	===Booth Program===		===Booth Program===

openSUSE:LinuxTag

2012-05-11T14:31:35Z

← Older revision		Revision as of 14:31, 11 May 2012
Line 65:		Line 65:
	\|-		\|-
	\| [[User:liquidsky89\|Jan Krings]]		\| [[User:liquidsky89\|Jan Krings]]
−	\| ~~Not sure yet~~	+	\| 22.5
−	\| ~~Not sure yet~~	+	\| 27.5
	\| Group hotel		\| Group hotel
	\| ICE from Düsseldorf		\| ICE from Düsseldorf
Line 74:		Line 74:
	\| Not sure yet		\| Not sure yet
	\| Not sure yet		\| Not sure yet
−	\| ~~maybe~~ Group hotel	+	\| Group hotel
	\| train		\| train
	\|		\|

SDB:GDI Printers

2012-05-11T13:03:53Z

← Older revision		Revision as of 13:03, 11 May 2012
Line 9:		Line 9:
	If the printer manufacturer does not provide the printer with standard printer language support but uses a proprietary protocol, the printer is a so called "GDI printer". Such printers only work under the operating systems for which the manufacturer provides driver support. GDI is an API developed by Microsoft. The problem with "GDI printers" has nothing to do with the GDI API. The problem is that GDI printers are exclusively accessible via a proprietary protocol. Therefore, GDI printers should actually be called "printers exclusively accessible via a proprietary protocol".		If the printer manufacturer does not provide the printer with standard printer language support but uses a proprietary protocol, the printer is a so called "GDI printer". Such printers only work under the operating systems for which the manufacturer provides driver support. GDI is an API developed by Microsoft. The problem with "GDI printers" has nothing to do with the GDI API. The problem is that GDI printers are exclusively accessible via a proprietary protocol. Therefore, GDI printers should actually be called "printers exclusively accessible via a proprietary protocol".

−	There is no such thing as "the GDI printer protocol". Each kind of GDI printer model usues its own special proprietary protocol so that each kind of GDI printer model needs its own special driver.	+	There is no such thing as "the GDI printer protocol". Each kind of GDI printer model usues its own special proprietary protocol so that each kind of GDI printer model needs its own special driver. See also http://www.openprinting.org/printer/Generic/Generic-GDI_Printer

	There are somewhat crippled printers that "understand" only rudimentary elements of a standard printer language (i.e., only those commands necessary for the output of raster graphics data). This kind of printer can sometimes be deployed in an ordinary way, since many printer drivers merely use the commands required for the output of raster graphics data. These printers may pose a problem if they must be previously switched to a special mode with specific control sequences. This can only be done with a specially adapted printer driver. Since this is not a standard protocol, these printers belong to the GDI printers.		There are somewhat crippled printers that "understand" only rudimentary elements of a standard printer language (i.e., only those commands necessary for the output of raster graphics data). This kind of printer can sometimes be deployed in an ordinary way, since many printer drivers merely use the commands required for the output of raster graphics data. These printers may pose a problem if they must be previously switched to a special mode with specific control sequences. This can only be done with a specially adapted printer driver. Since this is not a standard protocol, these printers belong to the GDI printers.
Line 35:		Line 35:
	* [[Portal:Printing]]		* [[Portal:Printing]]
	* [[Concepts hardware]]		* [[Concepts hardware]]
−		+	* http://www.openprinting.org/printer/Generic/Generic-GDI_Printer

	[[Category:SDB:Printing\|GDI]]		[[Category:SDB:Printing\|GDI]]

openSUSE:LinuxTag

2012-05-10T21:44:09Z

Booth Program:

← Older revision		Revision as of 21:44, 10 May 2012
Line 272:		Line 272:
	\|jos		\|jos
	\|-		\|-
−	\|~~what~~	+	\|AppArmor Crashkurs
	\|15:00		\|15:00
−	\|~~who~~	+	\|Christian Boltz
	\|-		\|-
	\|}		\|}
Line 291:		Line 291:
	\|jos		\|jos
	\|-		\|-
−	\|~~what~~	+	\|AppArmor Crashkurs
	\|15:00		\|15:00
−	\|~~who~~	+	\|Christian Boltz
	\|-		\|-
	\|}		\|}
Line 302:		Line 302:
	!Who?		!Who?
	\|-		\|-
−	\|~~AppArmor-Crashkurs~~	+	\|what
−	\|~~Christian Boltz~~	+	\|who
	\|-		\|-
	\|what		\|what
Line 312:		Line 312:
	\|-		\|-
	\|}		\|}
−

	===Additional Program===		===Additional Program===

Portal:Tumbleweed/Topics

2012-05-10T21:31:36Z

added sudo to all root-commands (for consistency)

← Older revision		Revision as of 21:31, 10 May 2012
Line 27:		Line 27:
	- Add Tumbleweed to your YaST or zypper installation repositories and enable autorefresh:		- Add Tumbleweed to your YaST or zypper installation repositories and enable autorefresh:
	<pre>		<pre>
−	zypper ar --refresh \	+	sudo zypper ar --refresh \
	http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ \		http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ \
	Tumbleweed		Tumbleweed
Line 57:		Line 57:
	The only supported method of repo use for Tumbleweed is to have only the main repos (Oss, Non-oss, and Update) and the Tumbleweed repo active. For that situation a simple		The only supported method of repo use for Tumbleweed is to have only the main repos (Oss, Non-oss, and Update) and the Tumbleweed repo active. For that situation a simple
	<pre>		<pre>
−	zypper dup	+	sudo zypper dup
	</pre>		</pre>
	will update your packages, and if any packages are ever reverted from Tumbleweed zypper dup will also handle that.		will update your packages, and if any packages are ever reverted from Tumbleweed zypper dup will also handle that.
Line 63:		Line 63:
	Despite it being unsupported, if you do choose to have other repos enabled, this command is safer:		Despite it being unsupported, if you do choose to have other repos enabled, this command is safer:
	<pre>		<pre>
−	zypper dup --from Tumbleweed	+	sudo zypper dup --from Tumbleweed
	</pre>		</pre>

openSUSE:Snapper Development

2012-05-10T09:36:59Z

cap SUSE in git urls

← Older revision		Revision as of 09:36, 10 May 2012
Line 5:		Line 5:
	===Browse git repository===		===Browse git repository===

−	http://github.com/~~opensuse~~/snapper	+	http://github.com/openSUSE/snapper

	===Anonymous clone===		===Anonymous clone===

−	git clone git://github.com/~~opensuse~~/snapper.git	+	git clone git://github.com/openSUSE/snapper.git

	===Authorized clone===		===Authorized clone===

−	git clone git@github.com:~~opensuse~~/snapper.git	+	git clone git@github.com:openSUSE/snapper.git

	===Building the source from git checkout===		===Building the source from git checkout===

User:Alexander Naumov

2012-05-10T08:41:12Z

← Older revision		Revision as of 08:41, 10 May 2012
Line 10:		Line 10:
	He studied security of the telecommunications systems in Saint-Petersburg, where learned about free software and wrote first programs for GNU/Linux in C/C++ and Assembler.		He studied security of the telecommunications systems in Saint-Petersburg, where learned about free software and wrote first programs for GNU/Linux in C/C++ and Assembler.

−	When he's not at work, Alex help [http://lizards.opensuse.org/2010/03/30/russian-opensuse-community/ Russian openSUSE community], help on the forums, translate documentation, motivate another guys to hack and make free software better and better. For example, so created he [http://forums.opensuse.org/p-russian/ Russian forum] on the forums.opensuse.org and [http://~~planetsuse~~.org/ru/ Russian part] on the planet.opensuse.org. Also, he is author and initiator of the [http://ru.kernelnewbies.org/ ru.kernelnewbies.org].	+	When he's not at work, Alex help [http://lizards.opensuse.org/2010/03/30/russian-opensuse-community/ Russian openSUSE community], help on the forums, translate documentation, motivate another guys to hack and make free software better and better. For example, so created he [http://forums.opensuse.org/p-russian/ Russian forum] on the forums.opensuse.org and [http://planet.opensuse.org/ru/ Russian part] on the planet.opensuse.org. Also, he is author and initiator of the [http://ru.kernelnewbies.org/ ru.kernelnewbies.org].

	His free time he devotes to his wife and son.		His free time he devotes to his wife and son.

Template:Wiki maintenance navbar/doc

2012-05-10T08:38:46Z

Added link to greek translated version of the page.

← Older revision		Revision as of 08:38, 10 May 2012
Line 4:		Line 4:
	<noinclude>		<noinclude>
	[[Category:Template documentation]]		[[Category:Template documentation]]
		+	[[el:Template:Wiki maintenance navbar/doc]]
	</noinclude>		</noinclude>

Template:Wiki maintenance navbar

2012-05-10T08:33:16Z

Added link to greek translated version of the page.

← Older revision		Revision as of 08:33, 10 May 2012
Line 3:		Line 3:
	{{{{PAGENAME}}/doc}}		{{{{PAGENAME}}/doc}}
	[[Category:Navigational bars]]		[[Category:Navigational bars]]
		+	[[el:Template:Wiki maintenance navbar]]
	</noinclude>		</noinclude>

Template:Cleanup

2012-05-10T08:22:56Z

Added link to greek translated version of the page.

← Older revision		Revision as of 08:22, 10 May 2012
Line 6:		Line 6:
	{{{{PAGENAME}}/doc}}		{{{{PAGENAME}}/doc}}
	[[Category:Wiki_maintenance_templates]]		[[Category:Wiki_maintenance_templates]]
		+	[[el:Template:Cleanup]]
	</noinclude>		</noinclude>
	<includeonly>[[Category:Pages to cleanup]]</includeonly>		<includeonly>[[Category:Pages to cleanup]]</includeonly>

Template:Delete

2012-05-09T22:58:00Z

Added link to greek translated version of the page.

← Older revision		Revision as of 22:58, 9 May 2012
Line 7:		Line 7:
	{{{{PAGENAME}}/doc}}		{{{{PAGENAME}}/doc}}
	[[Category:Wiki_maintenance_templates]]		[[Category:Wiki_maintenance_templates]]
		+	[[el:Template:Delete]]
	</noinclude>		</noinclude>
	<includeonly>[[Category:Pages to delete]]</includeonly>		<includeonly>[[Category:Pages to delete]]</includeonly>

Template:Intro/doc

2012-05-09T22:52:24Z

← Older revision		Revision as of 22:52, 9 May 2012
(One intermediate revision by one user not shown)
Line 5:		Line 5:
	<noinclude>		<noinclude>
	[[Category:Template documentation]]		[[Category:Template documentation]]
		+	[[el:Template:Intro/doc]]
	</noinclude>		</noinclude>

openSUSE:Build Service private installation

2012-05-09T16:50:47Z

Configuring the OBS instance names:

← Older revision		Revision as of 16:50, 9 May 2012
Line 170:		Line 170:
	/etc/slp.reg.d/obs.repo_server.reg		/etc/slp.reg.d/obs.repo_server.reg
	/etc/slp.reg.d/obs.source_server.reg		/etc/slp.reg.d/obs.source_server.reg
		+
		+	'''Note:''' Never use "_" character into the $HOSTNAME for an OBS sever.

	====Configuring the cache to use the SSD====		====Configuring the cache to use the SSD====

openSUSE:LinuxTag

2012-05-09T13:48:17Z

add oy

← Older revision		Revision as of 13:48, 9 May 2012
Line 126:		Line 126:
	\| Train		\| Train
	\| ?		\| ?
		+	\|-
		+	\| [[User:bekun\|Kai-Uwe Behrmann]]
		+	\| Tuesday
		+	\| Saturday
		+	\| Group hotel
		+	\| train
		+	\|
	\|-		\|-
	\| ''You?''		\| ''You?''

Git

2012-05-09T11:05:50Z

Usage:

← Older revision		Revision as of 11:05, 9 May 2012
Line 32:		Line 32:
	* [http://www.chem.helsinki.fi/~jonas/git_guides/HTML/git_guide/ Git in a Nutshell], by Jonas Jusélius, very concise.		* [http://www.chem.helsinki.fi/~jonas/git_guides/HTML/git_guide/ Git in a Nutshell], by Jonas Jusélius, very concise.
	* [http://www-cs-students.stanford.edu/~blynn/gitmagic/ git Magic, by Ben Lynn, very detailed]		* [http://www-cs-students.stanford.edu/~blynn/gitmagic/ git Magic, by Ben Lynn, very detailed]
		+	* [http://git-scm.com/book/ Pro Git], by Scott Chacon

	* Federico Mena posts:		* Federico Mena posts:

User:Guillaume G

2012-05-09T08:16:34Z

Some ideas:

← Older revision		Revision as of 08:16, 9 May 2012
Line 40:		Line 40:

	It would be nice to:		It would be nice to:
−	* Replace x-loader by u-boot SPL for MLO since x-loader is deprecated (for beagleboards and pandaboards). IF U-boot SPL is working fine. It seems there are some problems with SPL.	+	* Have a bootsplash (with openSUSE) in u-boot
		+	* Replace x-loader by u-boot SPL for MLO since x-loader is deprecated (for beagleboards and pandaboards). IF u-boot SPL is working fine. It seems there are some problems with SPL for the first revisions of boards/SoC.
	* Add support to Device Tree (DT) kernels (u-boot needs to give some special parameters to the kernel)		* Add support to Device Tree (DT) kernels (u-boot needs to give some special parameters to the kernel)
	* Have some non-JeOS images : Desktop with Xfce, LXDE, E17, JWM or IceWM or something else which is light) (and server in text mode?)		* Have some non-JeOS images : Desktop with Xfce, LXDE, E17, JWM or IceWM or something else which is light) (and server in text mode?)

openSUSE:Evergreen 11.2

2012-05-09T05:00:51Z

← Older revision		Revision as of 05:00, 9 May 2012
Line 9:		Line 9:
	!style="background:#669900;color:#fff;width:11em"\| CVE		!style="background:#669900;color:#fff;width:11em"\| CVE
	!style="background:#669900;color:#fff"\|		!style="background:#669900;color:#fff"\|
		+	\|-
		+	\| style="text-align:left;padding-left:1em;" \| php5
		+	\| released
		+	\| {{Bug\|760536}}
		+	\| {{NVD\|CVE-2012-2311}} {{NVD\|CVE-2012-1823}}
		+	\|
		+	\|-
		+	\| style="text-align:left;padding-left:1em;" \| flash-player
		+	\| released
		+	\| {{Bug\|760777}} {{Bug\|758645}}
		+	\| {{NVD\|CVE-2012-0779}}
		+	\| ver. 11.2.202.235
	\|-		\|-
	\| style="text-align:left;padding-left:1em;" \| flash-player		\| style="text-align:left;padding-left:1em;" \| flash-player

Category:Applications:Office

2012-05-09T03:58:54Z

← Older revision		Revision as of 03:58, 9 May 2012
(One intermediate revision by one user not shown)
Line 1:		Line 1:
	[[Category:Applications\|O]]		[[Category:Applications\|O]]
		+
		+	[[ru:Категория:Приложения:Офисные программы]]

← Older revision		Revision as of 17:37, 14 May 2012
Line 461:		Line 461:
	{{map_user\|41.878114\|-87.629798\|suseROCKs\|Bryen M Yunashko\|http:/en.opensuse.org/User:Byunashko}}		{{map_user\|41.878114\|-87.629798\|suseROCKs\|Bryen M Yunashko\|http:/en.opensuse.org/User:Byunashko}}
	{{map_user\|46.229964\|17.357159\|cuxer\|Nagyatád, Hungary\|https://connect.opensuse.org/pg/profile/cuxer}}		{{map_user\|46.229964\|17.357159\|cuxer\|Nagyatád, Hungary\|https://connect.opensuse.org/pg/profile/cuxer}}
		+	{{map_user\|-37.957564\|-57.575526\|Tavomazzei\|Mar del Plata, Argentina\|https://connect.opensuse.org/pg/profile/Tavomazzei}}

← Older revision		Revision as of 05:00, 9 May 2012
Line 9:		Line 9:
	!style="background:#669900;color:#fff;width:11em"\| CVE		!style="background:#669900;color:#fff;width:11em"\| CVE
	!style="background:#669900;color:#fff"\|		!style="background:#669900;color:#fff"\|
		+	\|-
		+	\| style="text-align:left;padding-left:1em;" \| php5
		+	\| released
		+	\| {{Bug\|760536}}
		+	\| {{NVD\|CVE-2012-2311}} {{NVD\|CVE-2012-1823}}
		+	\|
		+	\|-
		+	\| style="text-align:left;padding-left:1em;" \| flash-player
		+	\| released
		+	\| {{Bug\|760777}} {{Bug\|758645}}
		+	\| {{NVD\|CVE-2012-0779}}
		+	\| ver. 11.2.202.235
	\|-		\|-
	\| style="text-align:left;padding-left:1em;" \| flash-player		\| style="text-align:left;padding-left:1em;" \| flash-player