A newb like me would rather just based a distro on an existing one. You need to use the SU or root password. You forgot to include the step for mounting the partitions. There is just a screenshot but you skipped that step in your guide. I finally found it in the tiny font of the screenshot. Good effort though but you should really fix that if you are going to call it an installation guide because without the step it makes it awfully confusing considering there is a step along with each screenshot for everything else.
Thanks for posting. It was very useful to me. Good luck i havent tried gentoo in ages it had an installer back then i believe this was hmm perhaps 7 years ago give or take now i miss it and its capabilities trying it again alongside my windows good luck CJ this guide makes it much easier in case a hiccup browser next to u for reference : if using live dvd tat is.
Wish me luck. Very complicated but much appreciated. I just followed the links in this tutorial, and will do so again for part 2, but I learned a little bit. Thanks for posting this. Have a question or suggestion? Please leave a comment to start the discussion. Please keep in mind that all comments are moderated and your email address will NOT be published.
Save my name, email, and website in this browser for the next time I comment. Notify me of followup comments via e-mail. That's untidy but otherwise harmless. Going the other way is hard for lots of reasons. There is nowhere for the 32 bit code to go. You need a 32 bit toolchain in one step. A 64 bit only gcc cannot build 32 bit code and a 32 bit capable gcc needs a glibc with 32 bit support and so on.
It can be done, there is an old howto on the forums somewhere. Hu Moderator Joined: 06 Mar Posts: Slightly off topic question. Everybody tells WINE needs 32 bit. Useless WINE? Please learn how to denote units correctly! Jaglover wrote:. That's my understanding. Can't run 32 bit applications, but can run 16 bit DOS games in dosbox. Posted: Wed Jan 12, pm Post subject:.
Furthermore, for most of these tasks, Portage operates in a 'sandbox' mode, where attempts to write directly to the real root filesystem rather than the temporary work area are detected, and cause an error to be thrown NB this is not intended as a security system per se , but it does help prevent accidental filesystem corruption. The first tree level is the package category , which is used to organize packages into groups which have broadly similar functionality. The next tree level is the package name itself.
Within that subdirectory we have the actual per-package content, specifically:. So what does an ebuild file actually look like, then? Not a lot to see, is there? That's because diffstat uses a standard 'Autotools' -style build, without patches, so the default ebuild control flow and invoked 'hook' functions can do almost everything for us.
Therefore, all that has to be done is:. That's all that is needed in this case, because the default ebuild functions will automatically pull down the tarball, unpack it, issue a. There are then two main ways to invoke the diffstat ebuild. The first and more common way is via emerge : typically, you would issue:.
This is an example of a qualified version atom, discussed below. On the other side of the coin, it is possible to leave off the category qualifier when using emerge , but that's not recommended due to occasional ambiguities, where the same name occurs in multiple categories.
The second lower level way is invoke the ebuild directly; for example, you could issue:. The diffstat example above is about as simple as a real-world ebuild gets! However, one common additional requirement is the need to apply patches. For example, consider the sign package, which provides a file signing and signature verification utility. It lives in the app-crypt category. Let's examine version 1. Most of this should be familiar enough from the diffstat example, but there are some new elements too.
What if you want to modify an ebuild yourself, or add a new one? You could of course submit the ebuild to Gentoo using Bugzilla, but that only really applies to completed work you want to share. For work in progress, or private ebuilds, a different approach is required.
Instead, Portage supports the concept of ebuild repositories historically known as "overlays" to address just this issue. Then, when referring to or installing diffstat , Portage would use your version, rather than the 'official' ebuild however, if you had created an ebuild with a lower version number, say 1.
We'll exploit this ability shortly, when we add the sakaki-tools ebuild repository which will contain a number of useful tools used in this installation walk-through. Portage provides you, the user, with a great deal of flexibility. As our installation process is going to involve using Portage via the command-line tool emerge to download, then build and install up-to-date versions of all core system software, we first need to set up these configuration files appropriately. The most important Portage configuration files you'll need to know about now are as follows this is not complete - see this list for more information, and also the Portage manpage [3] :.
To ease the problem of setting things up correctly for your particular use case e. It is also possible to specify overrides for certain elements of Portage's operation on a per-package basis, through the use of the following configuration files:.
Finally for this background overview, there are a few Portage package management terms that are worth a brief recap:. For more information on atom naming, see the ebuild 5 manpage.
That's about it for this sidebar on atoms and versioning, apart from one last point: unlike other Linux distributions, you'll see no reference to 'releases' of Gentoo itself - there's nothing similar to Ubuntu's "Xenial Xerus" or "Artful Aardvark" , Debian's "Stretch" or "Buster" , Fedora's "Heisenbug" or "v26" etc.
The upside of this is that you can get access to the latest and often greatest versions of software as soon as new ebuilds get released into the tree. The downside is that particularly on the 'testing' rather than the 'stable' branch , sometimes updates fail to complete successfully, an occurrence that is very rare indeed when using binary distributed, release-based distributions such as Ubuntu.
That primarily means taking advantage of whatever parallelism your system can offer. There are two main dimensions to this - the maximum number of concurrent Portage jobs that will be run at any one time, and the maximum number of parallel threads executed by the make process invoked by each ebuild itself. As has been recommended, we'll set our number of concurrent jobs and parallel make threads to attempt, to be equal to the number of CPUs on the system, plus one. These are often defined in the make.
Since Portage doesn't support fancy bash features like command substitution, [8] we'll set and export these variables in root's.
Start up your favourite editor: in this tutorial we'll be assuming nano :. At this point, enter y and Enter to exit, saving changes, or n to exit without making changes.
For some more information on the nano editor, see this Wiki entry. Save and exit the nano editor. Next, we need to make sure that the. Next, on to the make. The stage 3 tarball we extracted already contains a skeleton configuration. We'll open this file with nano feel free to substitute your favourite alternative editor , delete the existing lines in nano , Ctrl k can be used to quickly cut the current line , and enter our alternative configuration instead see after for a line-by-line explanation.
Save the file and exit nano. Here is a brief summary of the shipped 'stage 3' values are, and what our version achieves:. Now we have these options configured, we're ready to chroot into our 'stage 3' environment and start building! Note You can use the system binaries and libraries shipped in the stage 3 as is, without rebuilding them, if you like - only the kernel build is mandatory.
However, we give instructions here to rebuild everything, from the toolchain upwards, to achieve the same effect as an old 'stage 1' bootstrap. The parts that are optional will be flagged.
0コメント