The Jackass! Project for Intel ~x86

Bob P · Posted: Sun Apr 24, 2005 12:29 pm Post subject:

AAAAAAAAAAAAAARRRRRRRRRRRRRGGGGGG \
GGGGGGGGHHHHHHHHHHHHH!!!!!!!!!!!!!!

another portage "enhancement": https://forums.gentoo.org/viewtopic-p-2344587.html

mod edit: Split scream in the middle to make it not screw up page width

--Earthwings
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

Sade · Posted: Sun Apr 24, 2005 1:47 pm Post subject:

Sith_Happens · Posted: Sun Apr 24, 2005 3:30 pm Post subject:

Bob P · Posted: Sun Apr 24, 2005 7:01 pm Post subject:

yeah, the recent changes to portage caused its behavior to dramatically change when emerging ebuilds. the old default for portage was "-strict", while the new feature implements "+strict" by default. this wouldn't cause any problems if all of the ebuilds worked according to specification. unfortunately, there are a large number of them that don't.

evidently, not all of the ebuild maintainers managed to fix their ebuilds by the time that the change was implemented in portage.

i posted bug reports for three b0rked ebuilds, but i gave up being the Don Quixote of the portage tree -- as you know, you cannot "emerge --resume --skipfirst" after a break in "emerge -e system", so it was just too cumbersome to keep finding the errors, fixing the ebuilds, and restarting the emerge. in the long run, its much easier just to revert to portages "normal" behavior by setting "-strict" as a FEATURES statement during the emerge.

looking at the ebuilds, one of them (IIRC it was either gettext or gnuconfig) had files in the ebuild that were not listed on the manifest and were 2-3 years older than the rest of the ebuild. :!:

this is just crappy maintenance on the part of the guy responsible for the ebuild. :evil:

The PentiumPro/i686 tarball and the Pentium-MMX tarball shouldn't take very long to get out. They'll definitely be out in a few days for testing. They would have been released today if the upstream devs for GLIBC hadn't released version 2.3.5 right after I finished building the PPro and MMX tarballs. Instead of releasing them, I had to start building them over again.

I'd still like to get the status bar and icons fixed during the boot cycle on the install CD if we can swing that. Assuming that we get the tarballs fixed and the ISOs fixed, I'm thinking that releasing Jackass! as a testing-branch CD may be right around the corner...
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

obsidianblackhawk · Posted: Sun Apr 24, 2005 10:09 pm Post subject:

Bob P · Posted: Sun Apr 24, 2005 10:30 pm Post subject:

the Jackass! boot CD is designed to mimic the bootup behavior of the Gentoo 2005.0 install CD. namely, as the system boots up with the silent splash screens, icons are supposed to illuminate and a blue status bar is supposed to be drawn across the bottom of the screen. we've been using the Gentoo Catalyst utility to create our install CD in the same way that the Gentoo install CD was created, so that our CD would have the same illuminating icons and the blue on purple status bar. unfortunately, there seem to be some problems with the most recent uptade to Catalyst so that the funtion of the bootsplash sometimes malfunctions.

all things considered, this is a Catalyst problem and not a Jackass! problem. the problems in Catalyst are causing cosmetic issues at boot and not a functionality issue with the install CD. if the problem can be fixed in Catalyst before the RC-03 tarballs are ready, we'd like to include the fix on the Jackass! CDs. but we're not going to hold up the release of Jackass! just because Catalyst is buggy and some of the boot-time eye candy is having problems. we'll relase Jackass! when Jackass! works, and not hold it up because Catalyst is broken.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

outspoken · Guru Joined: 14 Feb 2004 Posts: 464 Location: orlando, fl

Bob P · Posted: Wed Apr 27, 2005 5:07 pm Post subject:

Attention Testers: The RC-03 tarballs are ready for the first round of testing.

Revisions from RC-02 to RC-03 include:

1. an Update to GCC
2. an Update to GLIBC
3. an integrated Portage Snapshot

These tarballs are expected to contain the final changes to Jackass! before we put it onto an Installation CD.

The 686 CHOST tarballs (aka Pentium-Pro, Pentium 2, Pentium 3 and Pentium 4) will feature the following toolkit components:

gcc-3.4.3.20050110-r2
glibc-2.3.5

The 586 CHOST tarballs (aka Pentium and Pentium-MMX) will feature the following toolkit components:

gcc-3.4.3.20050110-r2
glibc-2.3.4.20050125-r1

The difference in the toolkit between the 586-class tarballs and the 686-class tarballs is due to the fact that glibc-2.3.5 is not yet stable on 586.

For the first round of testing, we need to test the following tarballs:

1) the 686 CHOST tarball that it optimized for Pentium-Pro. this tarball is the basis for the P2, P3, and P4 tarballs.
2) the 586 CHOST tarballs that are optimized for Pentium or Pentium-MMX.

All testers are requested to send me a PM with a description of their available computers so that I can make tarball testing assignements.

Thanks!

Edit: GCC 3.4.3, not GCC 3.1.3. D'Oh! :oops:

_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

obsidianblackhawk · Posted: Wed Apr 27, 2005 5:15 pm Post subject:

Hey bob, did you ever get that last PM i sent you?

Bob P · Posted: Wed Apr 27, 2005 5:17 pm Post subject:

yes, i have the one with your IP address, but late last night i realized that i have not completely configured my FTP server, and I haven't had a chance to work on that yet. :oops:

PM me with the arches of your test boxes, ok?
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

96140 · Retired Dev Joined: 23 Jan 2005 Posts: 1324

Bob P · Posted: Thu Apr 28, 2005 1:52 am Post subject:

yeah, i meant GCC 3.4.3. that was a typo. :oops:

_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

obsidianblackhawk · Posted: Thu Apr 28, 2005 2:00 am Post subject:

Okay Bob my installs are now offically under way. Maybe i'll post a little later tonight.

siegefried · n00b Joined: 08 Apr 2005 Posts: 19

how about Jackass with 4.0?

Bob P · Posted: Thu Apr 28, 2005 2:13 pm Post subject:

Not a chance. 4.0 is both unreliable and slower than 3.4.3. There's no point in it.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

Sith_Happens · Posted: Thu Apr 28, 2005 2:43 pm Post subject:

96140 · Retired Dev Joined: 23 Jan 2005 Posts: 1324

Heya. Back in the install, and this time the files have downloaded properly, so thanks to Sith and Bob for that!

However, I notice that when I md5sum the stage, the .md5 looks for a file that matches the tarball except that it is missing the "-rc3-" bit of the filename. md5sum thus can't find the file, since the new rc3 tarballs have -rc3- after the processor designation, and the md5 is looking for just a "pentium-20050425" not "pentium-rc3-20050425". A minor point, but one I thought worth mentioning.

Also, as I still wasn't able to get my danged printer to spit out the .pdf, is there any way of getting a text-only version of the guide on the server? As this new tarball has, to the best of my knowledge, a couple of things in it that the official Gentoo tarballs don't (like a Portage snapshot), I am proceeding very reluctantly with the regular Stage 1/3 Guide. I assume that there were extra instructions in the .pdf that's hosted on Sith's server, so I sure don't want to miss those!

I'm ready to untar the freshly downloaded stage, but I'm thinking that there is probably some way I'm to go about extracting it to the right place AND move the Snapshot within the file to its own proper location. So I don't just want to proceed with the normal step 5.3 just yet; I figure the Jackass guide has a slightly different instruction. Or maybe that's just my extreme caution talking.

Bob P · Posted: Fri Apr 29, 2005 4:37 am Post subject:

96140 · Retired Dev Joined: 23 Jan 2005 Posts: 1324

obsidianblackhawk · Posted: Fri Apr 29, 2005 2:42 pm Post subject:

Okay i'm not sure what but i fu*ked something up last night. I have to start the pentium-mmx install all over again when i get home.

Bob P · Posted: Fri Apr 29, 2005 2:56 pm Post subject:

i'm glad to hear that everything went well with the pentium-pro install.

lemme know as soon as you find out what the problem was with your box using the pentium-mmx tarball. i want to be sure that there's not a problem in the tarball, so send me a PM as soon as you know what's up.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

96140 · Retired Dev Joined: 23 Jan 2005 Posts: 1324

Bob P · Posted: Fri Apr 29, 2005 4:28 pm Post subject:

okay, i need to clarify something --

Jeremy has identified a problem with KERNEL INSTALLATION with the gentoo-sources 2.6.11-r6 kernel. Fwict, it is NOT a problem in Jackass!, as I had encountered the exact same problem yesterday on my development box that has never had Jackass! installed on it while performing a kernel upgrade using the same kernel version. i had considered it a fluke, but if other people are having the same problem, then its bugworthy.

Jeremy's oberserved the problem where the kernel correctly compiles, but fails to actually be installed in /boot. This seems to be a problem with the script improperly parsing the command:

Bob P · Posted: Fri Apr 29, 2005 4:37 pm Post subject:

Bob P · Posted: Fri Apr 29, 2005 5:16 pm Post subject:

OK - you guys scared me into performing a test install of the pentium-mmx tarball onto my P3 box. i've just completed the install without any errors, and the toolkit appears to be compiling xorg just fine. so it seems that there aren't any problems in the tarball or its toolkit, just some user configuration problems/errors with kernels.

let me know if i'm wrong on this, but i don't think we've found any errors in jackass.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks