Sorry, dude.

Been using your mirror.sh script to mirror -current, and make cdrom iso's....

CD1 image is fine, at 667MB
CD2 though, now is too big, gives me 755 MB image.

Any ideas on how to shuffle some files from iso2 to iso1? Or what to modify in your script? And if shuffling, how? (Ran into something similar to this earlier, found out nobody had an app to read iso images and modify them, without mounting, reading in one prog, changing in another, writing a new image in a third,etc... Ain't gonna go that route.)

Yeah I'd noticed after I returned from holiday, that CD2 ISO is too big. Must be that 2.6 kernel in there. I was too lame to do something about it :-) We're into our second week of > 30 degrees centigrade here.

But now I've refactored the script, shuffled the images' contents and basically left out the kernels directory on CD2 since that is also contained on CD1. The kdei series is still omitted from CD2, but it stays of course on the produced DVD image which holds all of the slackware-current directory tree.

The image size of CD2 is barely small enough for a 80 minute CD... if Pat keeps adding stuff I'll have to take out /extra from CD2 and just keep the extra/linux-2.6.16.xx ...

Updated version 1.19 of the script: http://www.slackware.com/~alien/tool...are-current.sh

Eric

You da man....


Thanks

I haven't tried the script yet, but I guess current = version 11 soon so I will be shortly.

So if there is no KDE I then just log in to my newly loaded slack off the new cd's in fluxbox or console if I'm feeling hard-core, and then put in KDE from a few manual downloads of the KDE & QT & Arts packages from current and then use "ye ole installpkg *.tgz"

Yeah, but I like having "hardcopy" of stuff. I'll try the new script later tonite...

We've reached the point where a DVD burner is a necessity. It's actually easier to use growisofs than cdrecord and the drives are dirt cheap now.

Of course, it won't be long before Slack 13 requires two DVDs.

Dennisk

I still am grateful for the CDROM approach. Many server-grade hardware I've used (and still use) has only a CDROM drive, and only recently I've seen DVD drives appearing in for instance the IBM X-series servers I run.

Eric

Well with the latest slackware-current update batch, the ISO image for CD#2 again crossed the 80 minute CD size limit:-(

I modified the script again, but not by taking out /extra.
Actually all I had to do is exclude the '/extra/aspell-word-lists' which is 163MB of data tha you don't need for testing Slackware-current... I was tempted to re-include the '/testing' directory since there is now again room for it, but I left it out. The CD#1 is nearly full and I might have to move stuff from there to CD#2 in future.

New revision 1.20 available (as usual) at http://www.slackware.com/~alien/tool...are-current.sh

Eric

I think from now on, I'll avoid the issue entirely and burn DVDs.

However, your exploits brings up an interesting question: Since 11 is near, how will it fit on 2 cd's w/out loss of something?

Just a thunk.....

Maybe KDE will be dropped from the cd, and just probably posted on Slackware's sites/mirrors with a download script? Or maybe Pat will decide to just finally make DVD isos instead of CD isos. Who knows, I am just guessing here.

DVD only prob won't happen, due to most servers only use cdrom drives...

As for KDE, it's too popular to 'drop'. But maybe /kdei... Eric, how about that? For a 'testing' distro, might that be a more elegant way? Since the internationalizations wouldn't be needed to 'test' the -current state....

May have to go to three cds....EEK!!!! When will the madness end????? As long as I don't need 7 cd's to do a install.....

For 10.2, Pat avoided compiling the aspell word lists, and just gave the sources and instructions for building, stating that they were too big to fit on the CD.

Maybe he'll do the same for 11?

One quick question:

What if the mirroring is inturrupted? In my case, the box doing the mirroring (one of three, at least it didn't kill them all) was shutdown by one of my kids hitting the power button...

So now when I try to run the mirror script, it says "Nothing changed" and quits because the ChangeLog.txt is the same. Ideas?

I know others may run into this too, like if your 'net goes down, it just hangs there for days, or power inturruptions, or whatever.

EDIT***

I can start the whole process over again if I rm the changelog, but that just d/l's the entire -current again....

Update.

I got the current ChangeLog.txt, edited out the newest stuff, then restarted the script...

Will update you on whats happening. (I think I'll make backups of the changelog just in case of this same thing happening...)

Run the script as and it will show you that the "-f" option is meant to go on even if the script determined that the ChangeLog.txt did not change.
If you have all of the -current tree, rsync will find out after a short while and no files will be transfered (you won't be downloading those gigs all over again).

If re-running the script is meant as a resume after an interrupted previous attempt (as was the purpose for adding the '-f' switch) then you're OK too: rsync is intelligent enough to just download the missing stuff and will not download again what you already have!

Eric