Tutvustus - Redigeerimiste ajalugu

Jj – 26. mai 2011, kell 13:25

2011-05-26T13:25:48Z

←Vanem redaktsioon		Redaktsioon: 26. mai 2011, kell 13:25
19. rida:		19. rida:
	Make this directory writable and sticky. “Sticky” means that even if multiple users have write permission on a directory, only the owner of a file can delete the file within a sticky directory. The following command will enable the write and sticky modes:		Make this directory writable and sticky. “Sticky” means that even if multiple users have write permission on a directory, only the owner of a file can delete the file within a sticky directory. The following command will enable the write and sticky modes:

	Muudame kausta kirjutatavaks ja "kleepuvaks" (sticky). Kleepuv tähendab seda, et isegi ~~kui mitmetel~~		Muudame kausta kirjutatavaks ja "kleepuvaks" (sticky). Kleepuv tähendab seda, et isegi teistel
	kasutajatel on ~~kirjutusõigused kaustale~~ siis vaid faili omanik saab neid "kleepuvast" kaustast kustutada. Järgnev käsk lubab kirjutamise ja muudab kausta kleepuvaks.		kasutajatel on kirjutamisõigused siis vaid faili õige omanik saab neid "kleepuvast" kaustast kustutada. Järgnev käsk lubab kirjutamise ja muudab kausta kleepuvaks.

	chmod -v a+wt $LFS/sources		chmod -v a+wt $LFS/sources

	An easy way to download all of the packages and patches is by using wget-list as an input to wget. For example:		An easy way to download all of the packages and patches is by using wget-list as an input to wget. For example:

			Lihtne viis kõikide pakettide ja paikade tõmbamiseks on kasutada wget-listi.

	wget -i wget-list -P $LFS/sources		wget -i wget-list -P $LFS/sources

Jj – 26. mai 2011, kell 13:23

2011-05-26T13:23:38Z

←Vanem redaktsioon		Redaktsioon: 26. mai 2011, kell 13:23
9. rida:		9. rida:
	Downloaded packages and patches will need to be stored somewhere that is conveniently available throughout the entire build. A working directory is also required to unpack the sources and build them. $LFS/sources can be used both as the place to store the tarballs and patches and as a working directory. By using this directory, the required elements will be located on the LFS partition and will be available during all stages of the building process.		Downloaded packages and patches will need to be stored somewhere that is conveniently available throughout the entire build. A working directory is also required to unpack the sources and build them. $LFS/sources can be used both as the place to store the tarballs and patches and as a working directory. By using this directory, the required elements will be located on the LFS partition and will be available during all stages of the building process.

	Allatõmmatud paketid ja paigad vajavad kohta kuhu need ajutisel paigutada nii, et nad oleksid kättesaadavad kogu ehitusprotsessi käigus.		Allatõmmatud paketid ja paigad vajavad kohta kuhu need ajutisel paigutada nii, et nad oleksid kättesaadavad kogu ehitusprotsessi käigus. Kataloogi on samuti vaja sellejaoks, et sinna algkoodi lahti pakkida ning kompileerida. $LFS/sources on kasutatav mõlemaks ülesandeks - nii pakitud algkoodi ja paikade säilitamiseks, kui töökaustaks.

	To create this directory, execute the following command, as user root, before starting the download session:		To create this directory, execute the following command, as user root, before starting the download session:
18. rida:		18. rida:

	Make this directory writable and sticky. “Sticky” means that even if multiple users have write permission on a directory, only the owner of a file can delete the file within a sticky directory. The following command will enable the write and sticky modes:		Make this directory writable and sticky. “Sticky” means that even if multiple users have write permission on a directory, only the owner of a file can delete the file within a sticky directory. The following command will enable the write and sticky modes:

			Muudame kausta kirjutatavaks ja "kleepuvaks" (sticky). Kleepuv tähendab seda, et isegi kui mitmetel
			kasutajatel on kirjutusõigused kaustale siis vaid faili omanik saab neid "kleepuvast" kaustast kustutada. Järgnev käsk lubab kirjutamise ja muudab kausta kleepuvaks.

	chmod -v a+wt $LFS/sources		chmod -v a+wt $LFS/sources

Jj – 26. mai 2011, kell 12:20

2011-05-26T12:20:18Z

←Vanem redaktsioon		Redaktsioon: 26. mai 2011, kell 12:20
8. rida:		8. rida:

	Downloaded packages and patches will need to be stored somewhere that is conveniently available throughout the entire build. A working directory is also required to unpack the sources and build them. $LFS/sources can be used both as the place to store the tarballs and patches and as a working directory. By using this directory, the required elements will be located on the LFS partition and will be available during all stages of the building process.		Downloaded packages and patches will need to be stored somewhere that is conveniently available throughout the entire build. A working directory is also required to unpack the sources and build them. $LFS/sources can be used both as the place to store the tarballs and patches and as a working directory. By using this directory, the required elements will be located on the LFS partition and will be available during all stages of the building process.

			Allatõmmatud paketid ja paigad vajavad kohta kuhu need ajutisel paigutada nii, et nad oleksid kättesaadavad kogu ehitusprotsessi käigus.

	To create this directory, execute the following command, as user root, before starting the download session:		To create this directory, execute the following command, as user root, before starting the download session:

			Et selline kataloog luua käivita enne tarkvara allalaadimise alustamist järgnev käsk administraatori (root) õigustes.

	mkdir -v $LFS/sources		mkdir -v $LFS/sources

Jj – 26. mai 2011, kell 11:49

2011-05-26T11:49:13Z

←Vanem redaktsioon		Redaktsioon: 26. mai 2011, kell 11:49
1. rida:		1. rida:
	This chapter includes a list of packages that need to be downloaded in order to build a basic Linux system. The listed version numbers correspond to versions of the software that are known to work, and this book is based on their use. We highly recommend against using newer versions because the build commands for one version may not work with a newer version. The newest package versions may also have problems that require work-arounds. These work-arounds will be developed and stabilized in the development version of the book.		This chapter includes a list of packages that need to be downloaded in order to build a basic Linux system. The listed version numbers correspond to versions of the software that are known to work, and this book is based on their use. We highly recommend against using newer versions because the build commands for one version may not work with a newer version. The newest package versions may also have problems that require work-arounds. These work-arounds will be developed and stabilized in the development version of the book.

	~~See~~ peatükk sisaldab nimekirja pakettidest mis on vaja tõmmata ~~selleks~~, et koostada ~~lihtne~~ linuxi		Järgnev peatükk sisaldab nimekirja pakettidest mis vaja tõmmata, et koostada kergekaauline linuxi süsteem. Iga paketi juurde on märgitud versiooninumber mille kohta on kindlalt teada, et see toimib. Tugevalt soovitaks mitte paigaldada neist uuemaid versioone sest kompileerimise süntaks võib olla vahepeal muutunud. Uuematel versioonidel võib lisaks olla ka muid probleeme mis vajavad täiendavat lisauurimist.
	süsteem. ~~Ära~~ on ~~toodud versiooninumbrid millede~~ kohta on teada, et ~~nad toimuvad~~. Tugevalt
	soovitaks mitte paigaldada uuemaid versioone sest kompileerimise süntaks võib ~~nendega mitte toimida~~. Uuematel versioonidel võib lisaks olla muid probleeme mis vajavad lisauurimist.

	Download locations may not always be accessible. If a download location has changed since this book was published, Google (http://www.google.com/) provides a useful search engine for most packages. If this search is unsuccessful, try one of the alternative means of downloading discussed at http://www.linuxfromscratch.org/lfs/packages.html#packages.		Download locations may not always be accessible. If a download location has changed since this book was published, Google (http://www.google.com/) provides a useful search engine for most packages. If this search is unsuccessful, try one of the alternative means of downloading discussed at http://www.linuxfromscratch.org/lfs/packages.html#packages.

Jj – 26. mai 2011, kell 11:46

2011-05-26T11:46:46Z

←Vanem redaktsioon		Redaktsioon: 26. mai 2011, kell 11:46
7. rida:		7. rida:
	Download locations may not always be accessible. If a download location has changed since this book was published, Google (http://www.google.com/) provides a useful search engine for most packages. If this search is unsuccessful, try one of the alternative means of downloading discussed at http://www.linuxfromscratch.org/lfs/packages.html#packages.		Download locations may not always be accessible. If a download location has changed since this book was published, Google (http://www.google.com/) provides a useful search engine for most packages. If this search is unsuccessful, try one of the alternative means of downloading discussed at http://www.linuxfromscratch.org/lfs/packages.html#packages.

	Programmide allalaadimiste veebisaidid ei pruugi olla alati kättesaadavad.		Programmide allalaadimiste veebisaidid ei pruugi olla alati kättesaadavad. Kui allalaadimise asukoht ei vasta või on muutunud võib kasutada vajaliku paketi leidmiseks googlet. Kui ka see ei anna mingit tulemust võib proovida mõnd lahendust mis kirjeldatud lingil http://www.linuxfromscratch.org/lfs/packages.html#packages.

	Downloaded packages and patches will need to be stored somewhere that is conveniently available throughout the entire build. A working directory is also required to unpack the sources and build them. $LFS/sources can be used both as the place to store the tarballs and patches and as a working directory. By using this directory, the required elements will be located on the LFS partition and will be available during all stages of the building process.		Downloaded packages and patches will need to be stored somewhere that is conveniently available throughout the entire build. A working directory is also required to unpack the sources and build them. $LFS/sources can be used both as the place to store the tarballs and patches and as a working directory. By using this directory, the required elements will be located on the LFS partition and will be available during all stages of the building process.

Jj – 26. mai 2011, kell 11:42

2011-05-26T11:42:35Z

←Vanem redaktsioon		Redaktsioon: 26. mai 2011, kell 11:42
6. rida:		6. rida:

	Download locations may not always be accessible. If a download location has changed since this book was published, Google (http://www.google.com/) provides a useful search engine for most packages. If this search is unsuccessful, try one of the alternative means of downloading discussed at http://www.linuxfromscratch.org/lfs/packages.html#packages.		Download locations may not always be accessible. If a download location has changed since this book was published, Google (http://www.google.com/) provides a useful search engine for most packages. If this search is unsuccessful, try one of the alternative means of downloading discussed at http://www.linuxfromscratch.org/lfs/packages.html#packages.

			Programmide allalaadimiste veebisaidid ei pruugi olla alati kättesaadavad.

	Downloaded packages and patches will need to be stored somewhere that is conveniently available throughout the entire build. A working directory is also required to unpack the sources and build them. $LFS/sources can be used both as the place to store the tarballs and patches and as a working directory. By using this directory, the required elements will be located on the LFS partition and will be available during all stages of the building process.		Downloaded packages and patches will need to be stored somewhere that is conveniently available throughout the entire build. A working directory is also required to unpack the sources and build them. $LFS/sources can be used both as the place to store the tarballs and patches and as a working directory. By using this directory, the required elements will be located on the LFS partition and will be available during all stages of the building process.
12. rida:		14. rida:

	mkdir -v $LFS/sources		mkdir -v $LFS/sources

	Make this directory writable and sticky. “Sticky” means that even if multiple users have write permission on a directory, only the owner of a file can delete the file within a sticky directory. The following command will enable the write and sticky modes:		Make this directory writable and sticky. “Sticky” means that even if multiple users have write permission on a directory, only the owner of a file can delete the file within a sticky directory. The following command will enable the write and sticky modes:

	chmod -v a+wt $LFS/sources		chmod -v a+wt $LFS/sources

	An easy way to download all of the packages and patches is by using wget-list as an input to wget. For example:		An easy way to download all of the packages and patches is by using wget-list as an input to wget. For example:

	wget -i wget-list -P $LFS/sources		wget -i wget-list -P $LFS/sources

Jj: Uus lehekülg: 'This chapter includes a list of packages that need to be downloaded in order to build a basic Linux system. The listed version numbers correspond to versions of the software that ar...'

2011-05-26T11:39:37Z

Uus lehekülg: 'This chapter includes a list of packages that need to be downloaded in order to build a basic Linux system. The listed version numbers correspond to versions of the software that ar...'

Uus lehekülg

This chapter includes a list of packages that need to be downloaded in order to build a basic Linux system. The listed version numbers correspond to versions of the software that are known to work, and this book is based on their use. We highly recommend against using newer versions because the build commands for one version may not work with a newer version. The newest package versions may also have problems that require work-arounds. These work-arounds will be developed and stabilized in the development version of the book.

See peatükk sisaldab nimekirja pakettidest mis on vaja tõmmata selleks, et koostada lihtne linuxi
süsteem. Ära on toodud versiooninumbrid millede kohta on teada, et nad toimuvad. Tugevalt
soovitaks mitte paigaldada uuemaid versioone sest kompileerimise süntaks võib nendega mitte toimida. Uuematel versioonidel võib lisaks olla muid probleeme mis vajavad lisauurimist.

Download locations may not always be accessible. If a download location has changed since this book was published, Google (http://www.google.com/) provides a useful search engine for most packages. If this search is unsuccessful, try one of the alternative means of downloading discussed at http://www.linuxfromscratch.org/lfs/packages.html#packages.

Downloaded packages and patches will need to be stored somewhere that is conveniently available throughout the entire build. A working directory is also required to unpack the sources and build them. $LFS/sources can be used both as the place to store the tarballs and patches and as a working directory. By using this directory, the required elements will be located on the LFS partition and will be available during all stages of the building process.

To create this directory, execute the following command, as user root, before starting the download session:

mkdir -v $LFS/sources
Make this directory writable and sticky. “Sticky” means that even if multiple users have write permission on a directory, only the owner of a file can delete the file within a sticky directory. The following command will enable the write and sticky modes:

chmod -v a+wt $LFS/sources
An easy way to download all of the packages and patches is by using wget-list as an input to wget. For example:

wget -i wget-list -P $LFS/sources