| View previous topic :: View next topic |
| Author |
Message |
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
 Posted: Sun Jun 05, 2005 4:43 pm Post subject: |
 |
|
and now for the reason that I logged-on today:
Whether to Upgrade to GCC 3.4.4
GCC 3.4.4 is still pretty buggy, and i wouldn't recommend an upgrade at this point. If you try to update GCC right now than you WILL be burned by the fact that the GCC 3.4.4 ebuild fails to update some of the system configuration files and leaves you with the infamous libstdc++.so.6 not found error. (Even though the file is actually present!)
In all respects, right now GCC 3.4.3 is a better version of GCC than 3.4.4. I would not recommend and update until the bugs in GCC 3.4.4 are fixed.
Nonetheless, if you just can't live without GCC 3.4.4 and you're intent on upgrading now, you should expect to run into problems that can be solved using the methods listed in this thread: http://forums.gentoo.org/viewtopic-t-345046-highlight-libstdc.html
If you are using a 686 CHOST version of Jackass!, then you may be able to avoid the problem altogether by changing the first line of /etc/portage/package.keywords so that instead of looking like this:
it looks like this:
| Code: | | sys-devel/gcc ~x86 multislot |
Note that this solution is only proposed for 686 based systems. The 586 CHOST versions of Jackass! were restricted to a specfic version of GCC and GLIBC because of bugs in herent in later versions of GCC and GLIBC on 586 systems at the time that Jackass! was built. I have no idea whether or not the bugs have been adequately addressed since that time, so if you should choose to upgrade, you do so at your own risk.
It is important to bear in mind that if you choose to upgrade your Jackass! Toolkit from the Official Jackass! specification to a more recent version of any of the toolkit components, you will no longer be using a Jackass! Toolkit -- you will then be using a Gentoo testing branch toolkit. Once you update any of your toolkit components to over-write the Jackass! Toolkit you can no longer rely on the Jackass! Support Group thread for help -- all of your support requests will need to go into an appropriate Gentoo Forum thread related to a toolkit upgrade.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
 |
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Sun Jun 05, 2005 4:53 pm Post subject: |
|
|
| rbiswarup wrote: | | I have always believed that there's some bug in my PC hardware because applications crashed (or "hanged") frequently, not only under windows but also under redhat and mandrake.But after i installed gentoo with the Jackass! toolkit the reliability with which the machine is operating is unbelievable-it's like a dream! |
Thanks for the feedback. its always been my personal belief that Gentoo is an extremely rock-solid and reliable operating system when it is installed correctly. In my experience, the only time that Gentoo fails in that regard is when it is built improperly. The whole idea behind Jackass! was to build an optimized Gentoo system properly, so that the user wouldn't have to go through all of the trouble, and so that the user wouldn't have the opportunity to make a mistake that would b0rk their system. So far, it looks like we can say, "Mission Accomplished!" 
| Quote: | | I have just one concern.The first thing I did after booting into the Jackass! installation was to run the command "emerge firefox".I didn't set any package specific USE flags hoping the defaults in the make.conf will be sufficient. I have noted that the precompiled firefox-bin is much more responsive and fast than the firefox i compiled using the Jackass! toolkit. Do you suggest any package specific settings for firefox? |
this kind of question is more related to Xorg, windowing, and firefox than it is to Jackass!, so you're really asking this question in the wrong place. My recommendation would be to look for a detailed answer in the Desktop Environments forum. With that said, if you perform a verbose pretend emerge for any application, all of the relevant USE flags and their status will be displayed onscreen. That should help you get started-off in the right direction. For follow-up, look for help in Desktop Environments.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
Sith_Happens
Veteran
Joined: 15 Dec 2004
Posts: 1807
Location: The University of Maryland at College Park
|
| Posted: Sun Jun 05, 2005 6:11 pm Post subject: |
|
|
| Bob P wrote: | | we're giving away both our software and our support for free |
I just wanted to comment that Jackass! isn't "our software". Jackass! is a repackaging of a standard Gentoo Linux 2005.0 stage 3 with certain upgrades and enhancements, slapped on a modified Gentoo 2005.0 Minimal Install cd. Just wanted to make it clear that Jackass! is still Gentoo. 
_________________
"That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Sun Jun 05, 2005 8:56 pm Post subject: |
|
|
| Sith_Happens wrote: | | Bob P wrote: | | we're giving away both our software and our support for free |
I just wanted to comment that Jackass! isn't "our software". Jackass! is a repackaging of a standard Gentoo Linux 2005.0 stage 3 with certain upgrades and enhancements, slapped on a modified Gentoo 2005.0 Minimal Install cd. Just wanted to make it clear that Jackass! is still Gentoo. |
Yes, Jackass! is indeed still Gentoo. But the toolkit that we built is still "our software," and we've given it back to Gentoo Community via the GPL.
Even though we copied the layout of the Live CD format from Gentoo, and although the file list of what file names are archived into the Stage 3 tarball is the same, the actual binary contents of the Gentoo Stage 3 tarball and the Jackass! Stage 3 tarball differ dramatically. The Jackass! Stage 3 tarballs were built using an identifiably unique method, and the binaries that were produced using the Jackass! Toolkit specifications are identifiably unique and comprise a new software product that did not exist before. The Jackass! binaries are so unique that they are even copyrighted, and released via a GPL license.
Early on in the project I checked with a software attorney about this. If we had decided to do so, we could have relased Jackass! as our own sub-distro, just like the other independent linux distribution that is Gentoo-based. Instead of choosing to release Jackass! as our own distribution, we chose to give Jackass! back to the Gentoo Community by releasing it as an unofficial Gentoo Community Project. Regardless of whether we chose to release it as our own distribution or to release it as a Community Project for Gentoo, it legally remains "our software." From a legal perspective, it would require a unanimous written statement signed by all 3 members of the Jackass! Development Team to change the terms of the Copyright. Not that this matters, really, as I know that we're all on the same page about the GPL and giving something back to Gentoo.
To say that Jackass! is anything less than "our software" would be philosophically accurate yet legally imprecise, and sells us short for what we actually did. We took something that was good, and made something that was unique and better. Yes, it was based on Gentoo, and we gave it back to Gentoo, and yes it is our intent to make our software a part of Gentoo and not to keep it for ourselves. But the Jackass! Toolkit is still our software, licensed via the GPL. The copyrights on the software adequately address any potential ambiguity about that.
IMHO, the coolest thing about the Jackass! Project is that it instantly reverts back to something Gentoo as soon as you emerge new toolkit components.  But until you actually recompile, you're still using "our software." Personally, I like the idea of reversion back to the origin from which Jackass! was derived. That was actually part of the system's conceptual design.
Looking at this from a different perspective, if it weren't our software, what in the heck are we doing maintaining a support thread in Unsupported Software? 
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
djpharoah
Apprentice
Joined: 24 Nov 2004
Posts: 186
Location: Irvine, California USA
|
| Posted: Sun Jun 05, 2005 10:28 pm Post subject: |
|
|
first of all i just want to thank everyone related in some way, shape or form to the Jackass! project.
having performed 3 stage 1/3 installs on my family laptops i was a bit tired from all the waiting. then one day saw Bob P's sig about jackass...tried it out on my personal laptop and
WOWWW
s**t ...so much faster to install than the stage 1/3...especially since my laptop is a P3-M 800...so not much brute force there...
guys once again thanks as its just beautiful to have all this stuff setup in less time than the stage 1/3 which was always partial to errors as it just took soo long
also loved how the stage3 tarball included portage and everything in it...
A++ |
|
| Back to top |
|
|
Sith_Happens
Veteran
Joined: 15 Dec 2004
Posts: 1807
Location: The University of Maryland at College Park
|
| Posted: Mon Jun 06, 2005 3:05 am Post subject: |
|
|
| djpharoah wrote: | first of all i just want to thank everyone related in some way, shape or form to the Jackass! project.
having performed 3 stage 1/3 installs on my family laptops i was a bit tired from all the waiting. then one day saw Bob P's sig about jackass...tried it out on my personal laptop and
WOWWW
s**t ...so much faster to install than the stage 1/3...especially since my laptop is a P3-M 800...so not much brute force there...
guys once again thanks as its just beautiful to have all this stuff setup in less time than the stage 1/3 which was always partial to errors as it just took soo long
also loved how the stage3 tarball included portage and everything in it...
A++ |
_________________
"That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Mon Jun 06, 2005 4:37 pm Post subject: |
|
|
in response to somebody's PM asking for hyperlinks to put in signature files, i thought i'd post them here. if anyone is interested in promoting Jackass! using a hyperlink in their signature line, you can use any of the following signatures.
i've used the tinyurl.com website to shorten the links, so that we don't monopolize your signatures. enjoy!
This one goes to The Jackass! Project's Home Page:
| Code: | | [url=http://tinyurl.com/7z97v]The Jackass! Project[/url] |
This one goes to the Release Announcement on the Forum:
| Code: | | [url=http://tinyurl.com/9dous]The Jackass! Has Landed![/url] |
This one goes to the Jackass! Support Group:
| Code: | | [url=http://tinyurl.com/aph8s]Jackass! Support Group[/url] |
Enjoy!
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Mon Jun 06, 2005 4:42 pm Post subject: |
|
|
| djpharoah wrote: | first of all i just want to thank everyone related in some way, shape or form to the Jackass! project.
having performed 3 stage 1/3 installs on my family laptops i was a bit tired from all the waiting. then one day saw Bob P's sig about jackass...tried it out on my personal laptop and
WOWWW
s**t ...so much faster to install than the stage 1/3...especially since my laptop is a P3-M 800...so not much brute force there...
guys once again thanks as its just beautiful to have all this stuff setup in less time than the stage 1/3 which was always partial to errors as it just took soo long
also loved how the stage3 tarball included portage and everything in it...
A++ |
oops. i'm blushing. 
hey, if you think that a P3-800 doesn't have enough brute strength to do a Stage 1/3 install, I'd just like to point out that a P3-800 is the fastest machine that I have, and that I used it to compile the Stage 1/3 installs that were used to make the Pentium, Pentium-MMX, and Pentium-Pro tarballs. Sith did the P2, P3, P4 tarballs on his P4, and Obsidianblackhawk and I did the Athlon-XP via SSH on his AMD64 box.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
anyNiXwilldo
Tux's lil' helper
Joined: 20 Feb 2004
Posts: 117
Location: Roswell, GA
|
| Posted: Mon Jun 06, 2005 6:17 pm Post subject: Very Nice Indeed |
|
|
A big thanks to the Jackass! developers. I just finished installing my Jackass! system and couldn't be more pleased. I installed from the Jackass! CD. I edited the USE flags and features to include "pic" and "prelink," then rebuilt the toolkit according to the instructions found in the stage1 on stage 3 install. I next rebuilt the entire system and upgraded everything except for gcc. (I didn't upgrade gcc to 3.4.4, as my first couple of attempts at gcc 3.4.4 failed with Jackass! - not due to Jackass!, but because gcc 3.4.4 didn't set the environment variables correctly.) I then emerged bits and pieces of the KDE 3.4.1 split ebuilds, gimp, firefox, mplayer, k3b, and even openoffice from source. Once the system was built, I emerged prelink and prelinked the whole thing. You would not believe how fast KDE or OpenOffice load now. All I have to say is "EXCELLENT!" A prelinked Jackass! system is VERY, VERY, FAST!! Keep up the great work guys!
_________________
Just pretend that FisherPrice or Hasbro or Mattel rewrote UNIX for 5 year olds. That's all windows is. When you start thinking of it as a pretty, underpowered version of UNIX for "special" people, it's very easy to use |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Mon Jun 06, 2005 6:21 pm Post subject: Re: Very Nice Indeed |
|
|
| anyNiXwilldo wrote: | | ... I then emerged bits and pieces of the KDE 3.4.1 split ebuilds, gimp, firefox, mplayer, k3b, and even openoffice from source. |
OpenOffice is a pretty good test that the toolkit works. Lots of people have problems compiling it, and I'm glad to hear that Jackass! works on such a brutal test of the toolkit.
| Quote: | | You would not believe how fast KDE or OpenOffice load now. |
yes i would!
thanks for the feedback.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
anyNiXwilldo
Tux's lil' helper
Joined: 20 Feb 2004
Posts: 117
Location: Roswell, GA
|
| Posted: Mon Jun 06, 2005 6:25 pm Post subject: Re: Very Nice Indeed |
|
|
| Bob P wrote: | | OpenOffice is a pretty good test that the toolkit works. Lots of people have problems compiling it, and I'm glad to hear that Jackass! works on such a brutal test of the toolkit. ] |
Well it didn't compile straight through when I was attempting to build it from chroot on my (previous) main Gentoo system. So I rebooted into Jackass!, then "ebuild openoffice.whatever.ebuild package" and the build continued from where it had previously stopped and completed.
_________________
Just pretend that FisherPrice or Hasbro or Mattel rewrote UNIX for 5 year olds. That's all windows is. When you start thinking of it as a pretty, underpowered version of UNIX for "special" people, it's very easy to use |
|
| Back to top |
|
|
nightmorph
Developer
Joined: 23 Jan 2005
Posts: 1382
Location: SoCal
|
| Posted: Mon Jun 06, 2005 9:18 pm Post subject: |
|
|
| Bob P wrote: | | Looking at this from a different perspective, if it weren't our software, what in the heck are we doing maintaining a support thread in Unsupported Software? |
Good point! 
_________________
<UzzaDead> What is CONFIG_USB_MON?
<petteyg> A Jamaican USB configuration?
dirtyepic: "We have more cupholders."
GDP || PR |
|
| Back to top |
|
|
Euphemism
n00b
Joined: 06 Jun 2005
Posts: 22
|
| Posted: Tue Jun 07, 2005 1:22 am Post subject: |
|
|
This being my second attempt at installing Gentoo, I found installing it using jackass and its documentation much easier (and maybe even faster). Now I just have to figure out what to do next.
By the way, on booting up I get:
Warning: The dma on your hard drive is turned off. This may really slow down the fsck process.
I have in /etc/conf.d/hdparm:
disc0_args="-a256A1c1d1m16ul"
cdrom0_args="-d1c1u1"
as stated in the installation guide. Looking at the comments in the file, there is listed hda_args and disc1_args - should I be using one of those instead?
Also, the HD I'm using is the WD1600JB, so are the hdparm parameters good for that? If not, is there a page where I can find the appropriate parameters?
*scratches head* After logging in as root and running hdparm, it seems that none of the settings were toggled. Plus udma mode is set at 4, and trying to turn on dma doesn't work. I'm fairly sure it was working earlier, before I installed jackass, though.
Oh well, time to figure out what to do next. |
|
| Back to top |
|
|
nightmorph
Developer
Joined: 23 Jan 2005
Posts: 1382
Location: SoCal
|
| Posted: Tue Jun 07, 2005 1:47 am Post subject: |
|
|
Euphemism, add the line hda_args=" " to your hdparm.conf, specifying your desired options. AFAIK, disc0 isn't used by anything; I don't know if it's supposed to default to a hard disk or a cdrom, but I know it's never been helpful on any of my installs.
Remember to replace hda with your own drive if necessary, and don't forget to do rc-update add hdparm boot when you've finished.
_________________
<UzzaDead> What is CONFIG_USB_MON?
<petteyg> A Jamaican USB configuration?
dirtyepic: "We have more cupholders."
GDP || PR |
|
| Back to top |
|
|
Clyde
n00b
Joined: 06 Jan 2005
Posts: 15
Location: Greenville, SC
|
| Posted: Tue Jun 07, 2005 2:29 am Post subject: |
|
|
| Bob P wrote: | | It is important to bear in mind that if you choose to upgrade your Jackass! Toolkit from the Official Jackass! specification to a more recent version of any of the toolkit components, you will no longer be using a Jackass! Toolkit -- you will then be using a Gentoo testing branch toolkit. |
I know this will likely aggravate you as much or more than my previous posts here and elsewhere, but in all humility, I must point out that (at least in my experience so far) upon completion of a by-the-book Jackass Toolkit install, the simple process of running emerge --sync followed by an emerge (not an update, just an emerge) of almost any package (e.g., xorg-x11) automatically updated gcc, making the Jackass Toolkit (according to the above) no longer a Jackass Toolkit. Is that sort of upgrade (eg, emerge --sync && emerge xorg-x11) meant to be included here?
I understand and wholeheartedly agree that Jackass is not for newbs, that by definition it is a testing branch toolkit, that it's the user's responsibility to know what may cause a tookchain component to be updated, that a good emerge wrapper is highly recommended, etc. And I could easily be wrong, in which case, just ignore me. All I hope to do is contribute in some small way to your team efforts by way of feedback, and one of the few things a relative newb can offer is a perspective on what might trip up others, even veterans. It just seems worth it to mention the risks of an emerge --sync in the Jackass doc. |
|
| Back to top |
|
|
Sith_Happens
Veteran
Joined: 15 Dec 2004
Posts: 1807
Location: The University of Maryland at College Park
|
| Posted: Tue Jun 07, 2005 4:18 am Post subject: |
|
|
| Clyde wrote: | | Bob P wrote: | | It is important to bear in mind that if you choose to upgrade your Jackass! Toolkit from the Official Jackass! specification to a more recent version of any of the toolkit components, you will no longer be using a Jackass! Toolkit -- you will then be using a Gentoo testing branch toolkit. |
I know this will likely aggravate you as much or more than my previous posts here and elsewhere, but in all humility, I must point out that (at least in my experience so far) upon completion of a by-the-book Jackass Toolkit install, the simple process of running emerge --sync followed by an emerge (not an update, just an emerge) of almost any package (e.g., xorg-x11) automatically updated gcc, making the Jackass Toolkit (according to the above) no longer a Jackass Toolkit. Is that sort of upgrade (eg, emerge --sync && emerge xorg-x11) meant to be included here?
I understand and wholeheartedly agree that Jackass is not for newbs, that by definition it is a testing branch toolkit, that it's the user's responsibility to know what may cause a tookchain component to be updated, that a good emerge wrapper is highly recommended, etc. And I could easily be wrong, in which case, just ignore me. All I hope to do is contribute in some small way to your team efforts by way of feedback, and one of the few things a relative newb can offer is a perspective on what might trip up others, even veterans. It just seems worth it to mention the risks of an emerge --sync in the Jackass doc. |
What are you talking about? What updates are being made to GCC by emerging xorg? What are the risks of an emerge --sync? Am I missing something here? What your saying makes absolutely no sense. 
_________________
"That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
| Back to top |
|
|
rpcyan
n00b
Joined: 29 Aug 2004
Posts: 31
Location: Massachusetts, USA
|
| Posted: Tue Jun 07, 2005 6:23 am Post subject: |
|
|
Based on the ~x86 keyword on GCC any emerge -uD command will inevitably want to upgrade GCC to 3.4.4. Can such an upgrade be done without comprimisng the perforamnce of Jackass?
BTW, just redid my Gentoo box with Jackass over the weekend. So far things are running great! |
|
| Back to top |
|
|
Sith_Happens
Veteran
Joined: 15 Dec 2004
Posts: 1807
Location: The University of Maryland at College Park
|
| Posted: Tue Jun 07, 2005 7:02 am Post subject: |
|
|
| rpcyan wrote: | Based on the ~x86 keyword on GCC any emerge -uD command will inevitably want to upgrade GCC to 3.4.4. Can such an upgrade be done without comprimisng the perforamnce of Jackass?
BTW, just redid my Gentoo box with Jackass over the weekend. So far things are running great! |
Not true. Read your /etc/portage/package.keywords file again. | Code: | | ~sys-devel/gcc-3.4.3.20050110 ~x86 |
That line says accept the ~x86 keyword for all packages up until gcc 3.4.3.20050110, but allow for bugfix revisions (r1, r2....). We were a bit smarter than that.
_________________
"That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
| Back to top |
|
|
Raftysworld
Apprentice
Joined: 27 Feb 2005
Posts: 236
Location: Snohomish, WA
|
| Posted: Tue Jun 07, 2005 1:12 pm Post subject: |
|
|
| I have a knack for discovering meaningless flaws. I just noticed that at the top of the athlon-xp installation cd, it says "Welcome to the Pentium Pro installation CD" (Or something along those lines, i dont have the cd handy. |
|
| Back to top |
|
|
Clyde
n00b
Joined: 06 Jan 2005
Posts: 15
Location: Greenville, SC
|
| Posted: Tue Jun 07, 2005 2:50 pm Post subject: |
|
|
| Sith_Happens wrote: | Not true. Read your /etc/portage/package.keywords file again. | Code: | | ~sys-devel/gcc-3.4.3.20050110 ~x86 |
That line says accept the ~x86 keyword for all packages up until gcc 3.4.3.20050110, but allow for bugfix revisions (r1, r2....). We were a bit smarter than that. |
Sorry, but the package.keywords file provided in the Jackass Pentium4 2005.0 ISO I downloaded, and in the corresponding PDF doc, only has "sys-devel/gcc ~x86", which allows any testing branch update to gcc, including 3.4.4. And that's why I posted the crazy feedback above. |
|
| Back to top |
|
|
Sith_Happens
Veteran
Joined: 15 Dec 2004
Posts: 1807
Location: The University of Maryland at College Park
|
| Posted: Tue Jun 07, 2005 3:55 pm Post subject: |
|
|
| Clyde wrote: | | Sith_Happens wrote: | Not true. Read your /etc/portage/package.keywords file again. | Code: | | ~sys-devel/gcc-3.4.3.20050110 ~x86 |
That line says accept the ~x86 keyword for all packages up until gcc 3.4.3.20050110, but allow for bugfix revisions (r1, r2....). We were a bit smarter than that. |
Sorry, but the package.keywords file provided in the Jackass Pentium4 2005.0 ISO I downloaded, and in the corresponding PDF doc, only has "sys-devel/gcc ~x86", which allows any testing branch update to gcc, including 3.4.4. And that's why I posted the crazy feedback above. |
In your "crazy" feedback above you said that emerging xorg or syncing your portage tree will update gcc, which just isn't true.
_________________
"That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall
Last edited by Sith_Happens on Tue Jun 07, 2005 4:50 pm; edited 1 time in total |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Tue Jun 07, 2005 4:36 pm Post subject: |
|
|
| Sith_Happens wrote: | | rpcyan wrote: | Based on the ~x86 keyword on GCC any emerge -uD command will inevitably want to upgrade GCC to 3.4.4. Can such an upgrade be done without comprimisng the perforamnce of Jackass?
BTW, just redid my Gentoo box with Jackass over the weekend. So far things are running great! |
Not true. Read your /etc/portage/package.keywords file again. | Code: | | ~sys-devel/gcc-3.4.3.20050110 ~x86 |
That line says accept the ~x86 keyword for all packages up until gcc 3.4.3.20050110, but allow for bugfix revisions (r1, r2....). We were a bit smarter than that. |
well, he is actually correct for the 686-chost versions of jackass, and incorrect for the 586-chost versions of jackass. but this was in no way the result of a mistake on our part, and none of the package.keywords files on any of the CDs need to be fixed.
when we were building the -rc03 version of the toolkit (the one that ended up being the release version of jackass), we found that the most recent versions of gcc and glibc in the portage tree worked on 686-chosts, but not on 586-chosts. so we locked down the versions of gcc and glibc that we used to build the pentium-class versions of jackass by modifying the contents of package.keywords to name specific versions of the software, as Sith mentioned in his post.
on the 686-chost versions of jackass, we left gcc and glibc enabled as testing branch packages, without any restrictions to the version numbers -- just like the documentation says.
these actions were taken to lock down the toolkit specifications to use packages that worked properly at the time that jackass was built, not at some point in the future. our objective was to facilitate a stable build of the jackass toolkit using the portage snapshot that we used to build the system, not to protect the user from some unforseeable event that would inevitably occur when the portage tree would eventually be updated.
so technically, clyde is right, but for the wrong reason.
as far as updating the toolkit goes, the user remains responsible for what he does to his system. i have repeated over and over again that nobody should ever perform an emerge -uD world on a gentoo system. if a user refuses to take my advice about that, then they will get what's coming to them.
now about the crazy feedback -- i also got the impression from the syncing and emerging xorg comment that the user was confused and really didn't understand what was happening during an emerge --sync or during an individual package emerge. that seems to be a Gentoo Fundamentals issue, and not a Jackass! Support issue.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Tue Jun 07, 2005 4:39 pm Post subject: |
|
|
| rpcyan wrote: | Based on the ~x86 keyword on GCC any emerge -uD command will inevitably want to upgrade GCC to 3.4.4. Can such an upgrade be done without comprimisng the perforamnce of Jackass?
BTW, just redid my Gentoo box with Jackass over the weekend. So far things are running great! |
i would recommend AGAINST ever performing an emerge -uD world command on your Gentoo system. this subject has been beaten to death, so i won't reiterate the reasons why. leave it to say that its a really BAD idea, and if you don't understand why, you should re-read this entire thread.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Tue Jun 07, 2005 5:03 pm Post subject: |
|
|
| Euphemism wrote: | By the way, on booting up I get:
Warning: The dma on your hard drive is turned off. This may really slow down the fsck process.
I have in /etc/conf.d/hdparm:
disc0_args="-a256A1c1d1m16ul"
cdrom0_args="-d1c1u1"
as stated in the installation guide. Looking at the comments in the file, there is listed hda_args and disc1_args - should I be using one of those instead?
Also, the HD I'm using is the WD1600JB, so are the hdparm parameters good for that? If not, is there a page where I can find the appropriate parameters? |
the commands listed in the documentation are 100% correct for a WD1600JB drive that is installed as hd0 on your system and for a CDROM that is installed as cdrom0 on your system. in that case, you can ignore the commands in the sample file that comes with Gentoo.
if your drives are named properly and you've done everything in the Jackass! Installation Manual and you still have no DMA, then you have a kernel configuration problem, not a Jackass! problem. i would search for "HDIO_SET_DMA". you'll find plenty of hits. if you need more help configuring your kernel, i'd recommend the Kernel & Hardware forum.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
djpharoah
Apprentice
Joined: 24 Nov 2004
Posts: 186
Location: Irvine, California USA
|
| Posted: Wed Jun 08, 2005 2:51 am Post subject: |
|
|
man...this is the fastest setup i have ever installed on any of my family laptops...all due to the jackass..
compiled gnome overnight which usually would take a day and a bit on a regular stage 3 install..
lovin it guy..totally recommending to all my buddies in CA |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Unsupported Software
