~CONRAD~ Stage 3 on 87 "Drei/Tres/3" INSTALL DOC | REL: #4.1

Message

StifflerStealth · Post by **StifflerStealth** » Sun Jul 20, 2008 2:19 pm

cheater1034 wrote:Anyway, the upgrade to gcc 4.3.1 _before_ the boostrap is a pretty significant change which will bump it to REL3.1, it will allow us to use -march=native in make.conf.

Great suggestion! I didn't think about doing that. -march=native is one of the best options in existence for GCC. As always, thanks for taking the time to update and support your guide.

Also, the switch to funtoo tarballs is another good option. They are more updated than Gentoo ones and thus make switching to ~Arch easier.

Have you thought about using paludis or pkgcore from the start instead of Portage? Portage Dep handling has a lot to be desired.

I broke my system doing a stage 1 install and using emerge. I had to use paludis to fix everything. This was a couple weeks ago.

FallenWizard · Post by **FallenWizard** » Sun Jul 20, 2008 6:41 pm

Really nice guide, but I have some additions:

# For Overlays
mkdir /usr/local/portage
wget conrad.whitesouls.com/overlay/portage.tar.bz2
tar jxvf portage.bz2 -C /mnt/gentoo/usr/local/portage

should be

# For Overlays
mkdir /mnt/gentoo/usr/local/portage
wget conrad.whitesouls.com/overlay/portage.tar.bz2
tar jxvf portage.tar.bz2 -C /mnt/gentoo/usr/local/portage

You forgot to use mkdir /mnt/gentoo/usr/local/portage and
you forgot to unpack portage.tar.bz2 instead of portage.bz2

tar jxvf config.bz2 -C /mnt/gentoo/etc/portage

the same

cheater1034 · Post by **cheater1034** » Mon Jul 21, 2008 2:20 am

Thanks, made those corrections ^^

Yeah, it seems the boostrap script really does not like any gcc upgrades (glibs/binutils doesn't seem to be a problem)

Anyway, i figure it makes more sense to build gcc 4.3 first anyway, as long as you do it with build being the only use flag, and the remove-wno-overlength patch there should be no problems, that way when you boostrap everything is built with gcc 4.3*

Also, i don't personally use pkgcore or paludis, and i don't want to restrict user choice, i'm contemplating making stage1 tarballs for use with the guide (with gcc 4.3.1), but I don't really want to since I don't constrict anything.

_if_ I added pkgcore or paludis documentation it would be because:
1) Someone else wrote the installation instructions for it
2) It's _optional_ and isn't required
3) The overlays were converted for paludis (and the configs)
4) The written section is tested by me

If someone wants, write a section for me (it has to be before emerge -e system, because i don't want to have a local chroot and have to emerge -e system before i can test it), tell me where the section is supposed to belong in the guide, and i'll test it up, if it looks good i'll format it and slap it in there making other changes throughout the guide myself.

cheater1034 · Post by **cheater1034** » Mon Jul 21, 2008 3:31 am

Now have NTP and NTFS-3g

Added upgrade guides, made several minor improvements just now too.

Upgrade guides can be found at the bottom of the guide (right above the changes log)

eremini · Post by **eremini** » Tue Jul 22, 2008 9:04 am

Minor correction
tar jxvf config.bz2 -C /mnt/gentoo/etc/portage
should be
tar jxvf config.tar.bz2 -C /mnt/gentoo/etc/portage

the.ant · Post by **the.ant** » Tue Jul 22, 2008 2:20 pm

cheater1034 wrote: It's really easy to setup too, just disable also in kernel, and make sound card support a module <M>, then emerge oss-devel (will be in conrad overlay), add it to runlevel and that's it. (also USE="oss" for applications)

I finally got my system up and running and so far it looks all very nice, although I still need to do some configuration. Thanks again for this guide!
Anothercomment on the guide though, when I tried to install oss, it wanted to pull in the xserver, which I did not want at that time, first get everything else running. Just emerged oss later and it looked ok, however, when I try do start it, I get an error message

Code: Select all

/dev/mixer: No such file or directory

edit: Problem solved, OSS had crashed after the initial initialisation, but removing the file from that and rebooting helped, now OSS is starting.

Nick C · Post by **Nick C** » Tue Jul 22, 2008 9:03 pm

awesome guide as ever

One suggestion though, remove the kde overlay from your overlay and instead refer people to relevant overlay (depending on if they have portage or paludis), the reference to the wiki is more than enough and for some reason i was getting odd errors while i had your overlay and the kdesvn-portage overlay together, removing your version seemed to fix everything. Plus its surely easier to let someone else maintain the kde ebuilds rather than having to deal with any problems yourself

cheater1034 · Post by **cheater1034** » Tue Jul 22, 2008 9:10 pm

the.ant wrote:
cheater1034 wrote: It's really easy to setup too, just disable also in kernel, and make sound card support a module <M>, then emerge oss-devel (will be in conrad overlay), add it to runlevel and that's it. (also USE="oss" for applications)
I finally got my system up and running and so far it looks all very nice, although I still need to do some configuration. Thanks again for this guide!
Anothercomment on the guide though, when I tried to install oss, it wanted to pull in the xserver, which I did not want at that time, first get everything else running. Just emerged oss later and it looked ok, however, when I try do start it, I get an error message
Code: Select all
/dev/mixer: No such file or directory
edit: Problem solved, OSS had crashed after the initial initialisation, but removing the file from that and rebooting helped, now OSS is starting.

I just added a message for now, i'll take care of it later on in a better way.

It really is stupid, i should contact the maintainer of the ebuild and teach him about USE flags :-p.

Nick C wrote:awesome guide as ever

One suggestion though, remove the kde overlay from your overlay and instead refer people to relevant overlay (depending on if they have portage or paludis), the reference to the wiki is more than enough and for some reason i was getting odd errors while i had your overlay and the kdesvn-portage overlay together, removing your version seemed to fix everything. Plus its surely easier to let someone else maintain the kde ebuilds rather than having to deal with any problems yourself

Will do

Nick C · Post by **Nick C** » Tue Jul 22, 2008 9:43 pm

I think OSS wants X due to the included ossxmix applet that comes as standard (and nicely gives you per-app volume controls). Ive not looked at the build system or ebuild though so ive no idea if it can be excluded/moved to a use flag.

the.ant · Post by **the.ant** » Wed Jul 23, 2008 11:34 am

I was really happy with the system, but only for so long, it fell apart again...

I used zen-kernel from git (2.6.26-rc9-zen1) and it started up ok, but soon became incredibly laggy. I tried to copy from a ntfs-esata disk to a XFS partition, so nothing to do with reiser4, but the copying just stopped after a while and I got Reiser4 error messages. In the console I could not do anything anymore because no command was recognized ('/usr/bin not found', etc...). Rebooted the rescue-disk and did fsck.reiser4 which demanded to rebuild the whole fs.
After that I tried zenmm kernel but it refused to load any modules.

So... *sigh* I guess I have to repeat the whole process again...
The question is, do I abandon Reiser4 or do I wait for a newer zen-kernel? (Yes, I know about Hitchhiker sources as resier4 alternative, but the whole reason why I switched to zen is that I got tons of section-mismatch errors with hitchhiker)
Anyone experienced similar problems?

cheater1034 · Post by **cheater1034** » Wed Jul 23, 2008 4:28 pm

the.ant wrote:I was really happy with the system, but only for so long, it fell apart again...

I used zen-kernel from git (2.6.26-rc9-zen1) and it started up ok, but soon became incredibly laggy. I tried to copy from a ntfs-esata disk to a XFS partition, so nothing to do with reiser4, but the copying just stopped after a while and I got Reiser4 error messages. In the console I could not do anything anymore because no command was recognized ('/usr/bin not found', etc...). Rebooted the rescue-disk and did fsck.reiser4 which demanded to rebuild the whole fs.
After that I tried zenmm kernel but it refused to load any modules.

So... *sigh* I guess I have to repeat the whole process again...
The question is, do I abandon Reiser4 or do I wait for a newer zen-kernel? (Yes, I know about Hitchhiker sources as resier4 alternative, but the whole reason why I switched to zen is that I got tons of section-mismatch errors with hitchhiker)
Anyone experienced similar problems?

2.6.26-rc9-zen1 is extremely broken, when i run it i get a nasty dmesg.

What modules did it refuse to load? that seems like an unlikely error.

the.ant · Post by **the.ant** » Wed Jul 23, 2008 4:44 pm

Most importantly the module for the ethernet card, but sound as well.
IIRC the error message was "device not found" even though it showed up with lspci.
I could not say if this was a problem of the Kernel or the broken Filesystem.
I guess I will give it another try, or are there other showstoppers with the current zenmm?

cheater1034 · Post by **cheater1034** » Thu Jul 24, 2008 2:41 am

the.ant wrote:Most importantly the module for the ethernet card, but sound as well.
IIRC the error message was "device not found" even though it showed up with lspci.
I could not say if this was a problem of the Kernel or the broken Filesystem.
I guess I will give it another try, or are there other showstoppers with the current zenmm?

If you have problems with zen/zenmm i can't argue with you that they are not in their most "Stable" states right now.
----

You can use any kernel, vanilla, gentoo, thinkpad, etc.

i would emerge gentoo-sources and use the patch i made below:

----

Download the patch here: http://omploader.org/vbW1v
Just apply with patch -p1 -i

It's the latest reiser4 you can get (from -mm), it's diffed against the latest -gentoo, but will apply on any other vanilla-based patchset as well, or vanilla itself.
And it's tested working.

Series:

Code: Select all

reiser4-sb_sync_inodes.patch
reiser4-export-remove_from_page_cache.patch
reiser4-export-find_get_pages.patch
reiser4.patch
reiser4-kgdb-fix.patch
reiser4-portion-of-zero_user-cleanup-patch.patch
reiser4-replace-uid==0-check-with-capability.patch
jens-broke-reiser4patch-added-to-mm-tree.patch
reiser4-make-methods-supplied-to-vfs-invariant.patch
reiser4-new-export-ops.patch
reiser4-new-export-ops-update.patch
reiser4-new-export_ops-fixup.patch
reiser4-specify-splice-file-operations.patch
reiser4-fix-dummy-ioctl_cryptcompress.patch
reiser4-granulate-rw-serialization-when-accessing-file-conversion-set.patch
reiser4-fix-disk-cluster-synchronization.patch
reiser4-use-balance_dirty_pages_ratelimited_nr.patch
reiser4-correct-references-to-filemap_nopage.patch
reiser4-fix-null-pointer-dereference-in-reiser4_write_extent.patch
reiser4-code-cleanups.patch
reiser4-tree_lock-fixes.patch
reiser4-tree_lock-fixes-fix.patch
reiser4-semaphore-fix.patch  
reiser4-fix-kill_hook_internal.patch

cheater1034 · Post by **cheater1034** » Fri Jul 25, 2008 2:15 am

I'm re-installing gentoo at the moment due to what is most likely reiser4 breakage.

I've heard a lot of similar results, and i wanted to go amd64 anyway.

In the process of re-install, i am going to make the guide multiple filesystems compatible (reiser4,ext4,ext3, jfs (why?), xfs, reiserfs, etc)

Also, i am going to be using paludis after i bootstrap, so there will be a paludis guide as well (optional), i will have configurations setup for both i686 and x86_64 (paludis configurations), instead of using the portage2paludis script, i think this is the best way. I will also maintain an overlay set for portage and for paludis.

Mr. Tao · Post by **Mr. Tao** » Fri Jul 25, 2008 8:16 am

That's great idea. I dropped emerge right after bootstrap.sh and at the moment I'm installing ~amd64 on zen with paludis.

Strayer · Post by **Strayer** » Fri Jul 25, 2008 10:58 am

I'm also currently reinstalling with the new version of the guide..

May I suggest to add --jobs=X to the "emerge -e system"-Part?

http://planet.gentoo.org/developers/zme ... lel_builds
http://jolexa.wordpress.com/2008/07/24/ ... s-feature/

It seems it produces some nice results

Edit:
Fixed second link *whistles innocently*

cheater1034 · Post by **cheater1034** » Fri Jul 25, 2008 4:10 pm

Mr. Tao wrote:That's great idea. I dropped emerge right after bootstrap.sh and at the moment I'm installing ~amd64 on zen with paludis.

I'm installing ~amd64 right now too, i dropped portage after emerge -e system because i couldn't get paludis to emerge before, it was having too many dependency problems, but after installing the system it's all fine.

I plan on having 3 downloadable configs available for paludis when i start writing that part, they will be: paludis-i686, paludis-amd64, paludis-amd64-nomultilib. I already have all the configs done, i need to upload them and write the guide for paludis.

Strowi · Post by **Strowi** » Fri Jul 25, 2008 6:45 pm

Nice Guide!
I installed my Thinkpad x31 following the 3.0 guide (first on my amd64 in 32bit chroot, afterwards when i had the time i rebuild with -march=native on my x31). All went very smooth except for some error with the latest dbus/hal + xorg.
Ia was testing reiser4 on lvm2 but seems to not as stable as needed, i think i am going back to ext4 or reiserfs (does reiserfs support online-resizing?).
Next week i will go for my amd64 reinstall as it is pretty buggy as i had to change hardware etc...

Also i think i will give paludis a try... although i still have to keep portage around.... does anyone know if there is a timeline/plan to completely replace portage?( i know, possibly wrong thread...)

I really think the native compiler flag is a great improvement, as this was the first time i was able to emerge -eD world all 571 packages without an error.

Keep up the good work!

@cheater1034: i think there is an coding error in your first post at the changelog for 3.0->3.1

Strayer · Post by **Strayer** » Fri Jul 25, 2008 8:11 pm

Strowi wrote:(does reiserfs support online-resizing?).

Yes, I did that two days ago

Strowi wrote:does anyone know if there is a timeline/plan to completely replace portage?( i know, possibly wrong thread...)

As far as I read there are no plans to throw portage over the board

I already tried paludis and it seemed to be stable and worked okay, but I see no reason to replace Portage with it.
Especially since there are coming so much cool features in Portage 2.2

Current status:
- zenmm boots okay.
- Installing X.org and Gnome (never tried that gnome overlay, I hope it's kind of stable

)

@cheater:
Hmm, always when I read your guide I want something like a table of contents...
Maybe you could migrate to gentoo-wiki or on some static homepage?

I think that would help the readability a bit.

Mr. Tao · Post by **Mr. Tao** » Fri Jul 25, 2008 9:01 pm

cheater1034 wrote:I'm installing ~amd64 right now too, i dropped portage after emerge -e system because i couldn't get paludis to emerge before, it was having too many dependency problems, but after installing the system it's all fine.

You can do USE=-python emerge paludis without python/boost dependecy problems.

I already tried paludis and it seemed to be stable and worked okay, but I see no reason to replace Portage with it.
Especially since there are coming so much cool features in Portage 2.2

So far I only know about one - --jobs which really is nice.

cheater1034 · Post by **cheater1034** » Sat Jul 26, 2008 3:53 am

Mr. Tao wrote:
cheater1034 wrote:I'm installing ~amd64 right now too, i dropped portage after emerge -e system because i couldn't get paludis to emerge before, it was having too many dependency problems, but after installing the system it's all fine.
You can do USE=-python emerge paludis without python/boost dependecy problems.
I already tried paludis and it seemed to be stable and worked okay, but I see no reason to replace Portage with it.
Especially since there are coming so much cool features in Portage 2.2
So far I only know about one - --jobs which really is nice.

Portage 2.2 also has --keep-going (which ahs been in paludis for a little while as --continue-something (idk the actual command)

portage 2.2 IMO is a definite step up from portage 2.1, the only reason to switch to paludis i can see is preference, as portage 2.2 seems just as fast/faster and it handles itself well.

cheater1034 · Post by **cheater1034** » Sat Jul 26, 2008 4:59 am

I do not like paludis myself, it seems really slow compared to portage 2.2 in every way, especially when resolving dependencies.

Also, i have the exact same configs on portage as paludis, but for some reason random packages (ie xorg-server) get compile failure in paludis, then when i use emerge they build fine (compile failure, which is really strange, even using paludis with the portage use flag so i could use portages configs directly fails)

I really don't see much benefit from it, but it's always good to add the option. I will maintain the paludis configs and guide for anybody interested (it's just not my cup of tea i guess), i will also add pkgcore usage as it's much easier to migrate to, although I find pkgcore sparse when compared to portage as it's missing some options, including the new options portage 2.2 is throwing out.

I've made several changes to the guide so far (my second time installing gentoo using it), just making it more clear, and describing multiple FS's, as reiser4 seems to be causing data loss, and eventual failure.)

On this install, i've done things differently:
1) Now i'm on multilib 64-bit (before i had been running i686 on my core 2 duo)
2) Now i'm running btrfs v15 (latest stable release), i do not reccomend people to follow suit as it is still in development and it is not backwards compatible when new releases come out (meaning you have to re-format the drive with the new version of btrfsprogs, and boot with the new version of the btrfs kernel patch).
3) I have completely setup paludis, although i do not like to use it as it fails randomly.
4) I moved the overlay from /usr/local/portage to /usr/local/overlays, this will affect the guide when i upload the new overlays.

Strayer · Post by **Strayer** » Sat Jul 26, 2008 8:29 am

cheater1034 wrote:Portage 2.2 also has --keep-going (which ahs been in paludis for a little while as --continue-something (idk the actual command)

portage 2.2 IMO is a definite step up from portage 2.1, the only reason to switch to paludis i can see is preference, as portage 2.2 seems just as fast/faster and it handles itself well.

It also finally has the ability to use sets, that was the only thing that I found interesting in paludis..

(Though I don't know exactly if they were included in 2.2 or earlier...)

Also: It (theoretically) avoids revdep-rebuild! (preserved-libs)
http://r0bertz.blogspot.com/2008/06/por ... tures.html

But I'm going off topic here... sorry

I'll compile gnome-light now

So far everything worked great.

I found a typo btw. in the kernel section:

Code: Select all

# cd /usr/src/linux
# emerge dev-util/git (USE="-gtk" if you do not want to pull a whole bunch of X packages, USE="-perl" if you don't want to pull perl packages)

for zen:
# git clone git://zen-sources.org/zen/kernel.git zen-sources

for zenMM
# git clone git://zen-sources.org/zen/kernel-mm.git zenmm-sources

for zenRT
# git clone git://zen-sources.org/zen/kernel-rt.git zenrt-sources

# ln -s zen*-sources/ linux

First line should be:
# cd /usr/src

Mr. Tao · Post by **Mr. Tao** » Sat Jul 26, 2008 9:03 am

cheater1034 wrote:I do not like paludis myself, it seems really slow compared to portage 2.2 in every way, especially when resolving dependencies.

Also, i have the exact same configs on portage as paludis, but for some reason random packages (ie xorg-server) get compile failure in paludis, then when i use emerge they build fine (compile failure, which is really strange, even using paludis with the portage use flag so i could use portages configs directly fails)

I'm not 100% sure, but performance issues might be associated with fact that you use legacy portage configurations with paludis. I also did complete ~amd64 system rebuild yesterday (yes, with reiser4

) without any xorg issues. When I encountered compilation problems in the past, they usually were result of fancy CFLAGS settings, so I had to add something like this in bashrc

Code: Select all

if [[ "${CATEGORY}/${PN}" == "sys-fs/udev" ]] ; then
	MAKEOPTS="-j1"
	LDFLAGS="-O1 ---hash-style=gnu --sort-common --as-needed -z now"
fi

Before I switched to paludis I also experiented with pkgcore (because I felt somehow lukewarm about paludis because of widely spread hoax of paludis devs being user enemies) but one day it sudenly died, probably as a result of python update or whatever and I haven't been able to resurrect it (too many dependecies).

As we were mentioning some of benefits of portage 2.2, even with all that progress I doubt it would have such an elegant support for repositories.

the.ant · Post by **the.ant** » Sat Jul 26, 2008 12:58 pm

cheater1034 wrote:I've made several changes to the guide so far (my second time installing gentoo using it), just making it more clear, and describing multiple FS's, as reiser4 seems to be causing data loss, and eventual failure.)

Well, I used to run my System on Reiser4 without problems for months (without compression though), I am not sure whether these data-loss problems are related to the kernel or the compression. Once you have a stable system running with reiser4 it is excellent, however, you never know whether a kernel-update might brake your system...

My current status is: reinstalled with latest version of the guide, reiser4 and zen-2.6.26-zen1. So far, everything moth things looks fine and I am compiling all programs I need. I'm still experiencing some problems with system services, shutdown and my external esata drive (connected with an pcmcia card), but I still have to try out different configurations. So far, I'm really happy, thanks again for the guide!

1) Now i'm on multilib 64-bit (before i had been running i686 on my core 2 duo)

What is the benefit of that?