User Tools

Site Tools


faq

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
faq [2005-01-28 18:29]
patrys
faq [2012-10-31 09:37]
jajcus [How to check from which .spec file was package X built?] outdated information replaced
Line 1: Line 1:
 /* pragma: section-numbers on */ /* pragma: section-numbers on */
 +**Frequently Asked Questions** ​
  
 +/* UndefinedMacro:​ TableOfContents(None) */ 
  
-====== Frequently Asked Questions ====== 
  
  
 ===== Polish version ===== ===== Polish version =====
-Polish version of this FAQ (which should be kept in sync most of the times) is available [[:​pl:​FAQ|here]]. ​+Polish version of this FAQ (which should be kept in sync most of the time) is available [[:​pl:​FAQ|here]]. ​
  
  
Line 18: Line 19:
  
  
-==== Why are there two different PLD projects? ==== +==== What is difference with LiveCD and RescueCD? ====
-Up until May 2003 all crucial decisions concerning PLD were made by its (now former) leader, Tomasz Kłoczko. Many developers didn't agree with his way of handling things and, after finding repeated attempts to change the situation a failure, decided to stop using the parts of infrastructure controlled by Tomasz (including the most critical part - the CVS repository) and, by doing so, render him unable to force any decisions upon anyone. Tomasz was offered a position as a developer within the new structures (of course without the power he previously had) and decided, together with one other developer that refused to switch, to keep developing his own version of PLD under the original domain (the old site can be found at [[http://​www.pld.org.pl/​|http://​www.pld.org.pl/​]]). ​+
  
 +
 +<​file>​13:​33:​17 <​@glen>​ what's livecd and rescuecd difference?
 +13:33:35 <​@evilbohater>​ live is for life and rescue is for fun
 +13:33:36 <​@evilbohater>​ ;)
 +13:34:19 < evilabram>​ rescue is for install ;-)
 +</​file>​
 +
 +  * [[http://​rescuecd.pld-linux.org/​download/​current/​|RescueCD]] ​
 +  * [[http://​livecd.pld-linux.org/​|LiveCD]] ​
  
  
 ===== Practical issues ===== ===== Practical issues =====
 +
 +
 +==== How to install PLD Th ? ====
 +
 +  * Use [[http://​cri.pld-linux.org/​|ChRoot Installer]] for PLD/Linux Th installation. ​
 +  * Graphical installation using Anaconda from [[http://​livecd.pld-linux.org/​|LiveCD]] ​
 +  * [[:​Docs:​man:​Installing_PLD_Linux_based_on_Rescue_CD| '​Classic'​ chroot installation]] ​
  
  
Line 32: Line 48:
  
 ==== How to check from which .spec file was package X built? ==== ==== How to check from which .spec file was package X built? ====
-First of all, one should check whether there exists a spec file named just like the package. If not, the name of the spec file can be found in the output of one of these commands: ​ 
  
 +''​rpm -qi package''​ command ​ will show various information about the package, including the source RPM name. You can check the
 +source RPM name also with ''​rpm -q --queryformat '​%{sourcerpm}\n'​ package''​. The base name of the source RPM (with version and the '​.src.rpm'​ suffix stipped) is also the name for the GIT repository and the spec file.
  
 +==== How to check which package contains a particular file? ====
 +If the package is installed, you can invoke ''​rpm''​ as shown below: ​
  
-<​file>​rpm -q --changelog package package2 | grep '​$Log'​ +<​file>​rpm -qf /​path/​to/​file
-# for already installed packages +
- +
-rpm -q --changelog -p package.rpm package2.rpm | grep '​$Log'​ +
-# for packages available as files+
 </​file>​ </​file>​
-One can also use a more sophisticated command (just like beforeadding a "​-p"​ switch after the "​--changelog"​ command and giving full file names allows ​one to query packages from disk)+Keep in mind howeverthat if you do not specify ​the path, ''​rpm''​ will also check the list of installed packages for one matching the provided file name. That's why you should always use either absolute paths or paths relative ​to current directory (like //​./​filename//​)
  
-<​file>​rpm -q --changelog package package2 | awk '/​^\$Log:/​ {spec=$2;​gsub(",​v$","",​spec);​print spec}'+If the package is not yet installed, you will have to use ''​poldek''​. Start ''​poldek''​ and type the following at the command prompt:  
 + 
 +<​file>​poldek> search ​-f *filename
 </​file>​ </​file>​
  
  
-===== How to check which package contains a particular file ===== +==== Why can't I use su, sudo and ssh to access my root account? ​==== 
-If the package is installed you can invoke ​''​rpm''​ as shown below: ​+Our security policy requires ​the user to be a member of the //wheel// group in order to be able to use root priviledges gained by invoking ​''​su'' ​and ''​sudo''​. This way compromising your machine requires the attacker to guess three parameters instead of just one (your user name, your password and root password ​as opposed to only the root password). ​
  
-<​file>​rpm -qf /​path/​to/​file +Additionallynoone is able to remotely log in as root (for the same security reasons)Root is also unable ​to remotely use other services ​(ftp, imap, pop3, smtpas they do not provide strong connection encryption
-</​file>​ +
-Be warnedhowever, that if you don't specify the path, ''​rpm''​ will also check the list of installes packages ​for one matching ​the provided file nameThat's why you should always use an absolute path or paths relative ​to current directory ​(like //​./​filename//​). +
  
-If the package is not yet installes you will have to use ''​poldek''​. Start ''​poldek''​ and type the following at the command prompt: ​ 
  
-<​file>​poldek> search ​-f *filename+ 
 +==== How can I check the package description in an other language than my locales are ? ==== 
 + 
 + 
 +<​file>​LANG="​de_DE"​ rpm -q --qf %{description} package1 package2 
 +# if package1 package2 are installed 
 + 
 +LANG="​de_DE"​ rpm -q --qf %{description} ​-p package1.rpm package2.rpm 
 +# if package1 package2 are on your hard drive and not installed
 </​file>​ </​file>​
 +The language can be any other of course (if the package supports it ex. pl_PL). ​
 +
  
faq.txt · Last modified: 2012-10-31 10:55 by glen