I don't want to use jigdo. Maybe when I download the next version, but for now please keep this simple without throwing in extra steps.
The reason for this is that Debian doesn't have the resources for providing all the images. Do you know what's on the images? Packages. Hosting full images would double the size of the archive... Now, mirroring this will be insanity. Especially for sid, which is a rapidly moving target. AFAIK, this is going to change, though, at least for stable releases.
Oh, and you won't *have* to use images when you upgrade to a new version. apt-get dist-upgrade is your friend.
WTF is in Debian that takes 11 CDs?
Well... Everything...
... and find a page saying you shouldn't install unstable directly, but install stable first then switch your install over.
The main reason for this is that there is a complete rewrite of the installer going on for sarge, and thus there is no boot-floppies (as the old installer is called) installer for sarge and sid. And, of course, at any given time, the installer for stable will be more tested than any other version.
Of course, if you feel like it, pretty please help us test the new installer.:-)
The same thing applies to upgrading distro versions. I'm hardly a naive user, yet I have been unsuccessful in every attempt to upgrade my Debian potato systems to woody. I've now given up - I just do a clean install of woody.
That's odd. I upgraded my parents' potato box (my father uses it to write LaTeX) to woody without any glitches. apt-zip is your friend! Trust apt-zip!
The way I recall it, the instructions for compiling gcc on solaris, is to compile a basic gcc with Sun's compiler, and then compile a new gcc with the gcc you just got. Probably compile a new one with that one, just to be on the safe side:-)
I may be wrong of course, I haven't compiled gcc myself for ages.
Don't pick courses because of what you think you'll get paid after graduating, I have several friends who have done that. All of them have regretted it later.
You study because
1) It's fun (at least that's what I think)
2) You learn stuff.
The best advice I can give is to try to find an education that gives you as many choices as possible (hrmm... isn't that what my old man used to say to me?), and I don't just mean work opportunities after you've graduated, but also many choices as to exactly which courses to take.
I'm a comp.sci. major myself (at a university in Sweden) and this program has a lot of freedom and choices, there's zillions of kickass courses I want to take... Ah, I wish I had more time...
Basically, the differences have been pointed out fairly well by a lot of people, albeit with some differences. Oh, I'd say there's more maths at CS than CE, mostly algebra and discrete mathematics. AFAIK, CS is also much more theoretical than CE, but things like algorithm complexity and data structures are really important if you want to design good, fast applications.
My advice is, pick whatever education that gives you the most choices, that's what I did. I started out with maths and now I'm a comp.sci. major.
Slashdot Mirror
Oh, and you won't *have* to use images when you upgrade to a new version. apt-get dist-upgrade is your friend.
Well... Everything... The main reason for this is that there is a complete rewrite of the installer going on for sarge, and thus there is no boot-floppies (as the old installer is called) installer for sarge and sid. And, of course, at any given time, the installer for stable will be more tested than any other version.Of course, if you feel like it, pretty please help us test the new installer. :-)
That's odd. I upgraded my parents' potato box (my father uses it to write LaTeX) to woody without any glitches. apt-zip is your friend! Trust apt-zip!
The (highly unofficial!) small ISO I have put up works fine in vmware. It won't let you do net installs, but it will let you do a CD install.
The way I recall it, the instructions for compiling gcc on solaris, is to compile a basic gcc with Sun's compiler, and then compile a new gcc with the gcc you just got. Probably compile a new one with that one, just to be on the safe side :-)
I may be wrong of course, I haven't compiled gcc myself for ages.
Don't pick courses because of what you think you'll get paid after graduating, I have several friends who have done that. All of them have regretted it later.
You study because
1) It's fun (at least that's what I think)
2) You learn stuff.
The best advice I can give is to try to find an education that gives you as many choices as possible (hrmm... isn't that what my old man used to say to me?), and I don't just mean work opportunities after you've graduated, but also many choices as to exactly which courses to take.
I'm a comp.sci. major myself (at a university in Sweden) and this program has a lot of freedom and choices, there's zillions of kickass courses I want to take... Ah, I wish I had more time...
Basically, the differences have been pointed out fairly well by a lot of people, albeit with some differences. Oh, I'd say there's more maths at CS than CE, mostly algebra and discrete mathematics. AFAIK, CS is also much more theoretical than CE, but things like algorithm complexity and data structures are really important if you want to design good, fast applications.
My advice is, pick whatever education that gives you the most choices, that's what I did. I started out with maths and now I'm a comp.sci. major.
Good luck!
Amen brother :-)