Posts tagged gentoo
Posts tagged gentoo
13 notes &
Yup. Just got bitten by this nasty inconvenience.
I upgraded my firewall to sys-kernel/hardened-sources-2.6.39-r13, and after rebooting … all hell broke loose.
My (yet to be released) WallMator (firewall automator) script failed, and thus I lost all connectivity to the outside world. Can’t even ping the next hop gateway!
3 notes &
Finally! After 2 whole days lost, I managed to emerge gcc-4.5.1-r1!
Apparently, emerge-ing gcc needs a quite-hefty hardware requirement:
1 note &
I was so happy yesterday that I’ve successfully figured out what was needed to upgrade gcc on my Gentoo system.
Boy, was I in for an unpleasant surprise.
2 notes &
Gentoo graybeards (you know who you are) are undoubtedly familiar with the mirrorselect utility. This simple program (script, actually) attempts to determine which Gentoo mirror is the fastest for you. By specifying a -D option, it will even try to download a 100 KB file to measure the throughput.
The problem is: It’s not 100% reliable.
2 notes &
Short dispatch, this:
Yesterday I tried to upgrade gcc on a fresh Gentoo installation. In fact, it was a raw installation, not yet fresh (e.g., extract stage3, extract portage, sync, update portage, upgrade gcc).
I had used a 4 GB virtual hard disk. Guess what? I ran out of space in the midst of emerge -avuN gcc) >.<
Oh well. Now I’m trying to upgrade gcc using a 5 GB virtual hard disk. If this fails again, I’ll use a 6 GB vhd, and so on.
(Yeah, trying to find out how much space I actually need to upgrade gcc).
I’ll update you with the results.
In the meantime, keep strong!
Update: It works! Apparently, if you want to upgrade gcc, you need to use a 5 GB vHD (free space approximately 4.6 GB).
27 notes &
There are good times, and there are bad times. Lately I’ve been having more of the former, and now it’s time for the latter:
I have to re-make my Gentoo vFirewall VM :(
10 notes &
Earlier today, I ran head-first into my first serious emerge block: Portage refuses to update because it is blocked by logrotate.
The ‘standard’ way to resolve a block is to unmerge whatever’s blocking Portage (logrotate in this case), update Portage, then re-emerge the unmerged package.
Problem is: logrotate is a dependency of squid, and the squid must not be interrupted.
5 notes &
First, some explanation re: ‘stage3.5’. I had planned on calling this a ‘stage4’, but there are some confusion regarding the term ‘stage4’, even amongst Gentoo users. To prevent howls of protests that might possibly be raised by Gentoo graybeards, I decided to call this a ‘stage3.5’ instead.
Okay, what the heck is a ‘stage3.5’? The numbering implied that it’s a continuation of ‘stage3’. And in fact, it is. It’s a tarball containing:
/etc/make.conf
/etc/portage/ (accepted keywords, package-specific use flags, rsync excludes, etc)emerge -uDN and revdep-rebuild
In other words, all the stuffs just before emerging the kernel sources.
Here’s how:
