I bought a brand new Jaguar in the summer of 1997. I bought it because I was so-called "collecting" older consoles (I also bought Nintendo's Virtual Boy - don't laugh).
I had all of three games for the Jaguar, I can't even remember the exact names because once I bought it, it sat in a corner while I played Wild Arms and FF7 for PSX.
I even had the store where I got it from (Software Etc.) order me a Jaguar CD-ROM drive from a different store, but I chickened out when I saw the $75 price tag.
My Atari "64-bit" Jaguar now sits dismantled (I had my way with my trusty Phillips), broken, abused, and shattered in a dusty corner of the closet in my computer room.
I hadn't even thought about it until Slashdot posted this article (Damn you Slashdot:). The rest of my 5 minutes thinking about this worthless piece of 68K+Tom+Jerry crap is ruined! The fact that someone released a *NEW* game for it, when we now have true 128-bit consoles is...
...pathetic!
I'm a budding console programmer (currently with my PSX), and even though I'm not a professional, I know that all games have a time and a place - as previous posters mentioned, Jaguar's place was in 1993-94, not 2000 (how in God's name did it make it this far?!).
I've always thought that it would be cool to have a web application that could select either a "generic" GNU base (just the apps, no kernel), or an already existing distribution (have a layout of it's filesystems, etc.) and generate an ISO image or individual packages tailored to the apps you want.
Such an app would have to be enormous to handle all those distros and every package that ships with most distros.
I suppose it could start by *strictly* adhering to the Filesystem Hierarchy Standard, excuse my ignorance (I've used SlackWare in the past and RedHat currently) but I haven't seen many distros that fully *comply* with FHS (even though FHS gives you a lot of leeway).
I have a fairly simple machine, PII 333 with two 4gig harddrives. I have it dual booted with Linux (Redhat 6.0) and NT 4.0 with LILO being the bootloader.
Here's the interesting part: when I boot under NT I can use VMWare to get at the raw Linux partition, and when I boot under Linux I can use VMWare to get to the raw NT partition. Each OS has a specific configuration depending on whether it's a guest or host (using Hardware Profiles under NT and VMWare's dualconf under Linux).
Then it starts getting complex with host-only networking under VMWare for each environment. I actually have 5 different IPs for my one machine:
192.168.0.2: Native (host) NT or native Linux
192.168.101.1: VMNet Bridge 192.168.101.2: NT host/Linux host 192.168.101.3: Linux guest 192.168.101.4: NT guest
So while I have NT as a host, I can use samba to send files to Linux and then test them out. As far as development goes on NT, I have Visual Studio 6.0, Borland's free compiler, and Cygnus's cygwin (with mingw32 built under cygwin). I also have cross tools under cygwin that target Linux and MSDOS (djgpp).
When I use Linux as a host (99.5% of the time), again I can use samba to send executables to the NT guest and try them out *immediately* after compilation. This is a plus for libraries such as SDL, etc. I use pgcc-2.95.2 targetted to mingw32, cygwin (for the hell of it), ms-dos, and Sony PlayStation.
The main reason I use this setup is for hardware/processor feasibility, I have a TNT2 Ultra that isn't supported in any way under VMWare, therefore booting NT means I get 3DSMax, etc. that takes full advantatge of my hardware. Also, I have an ISA card that talks to my PlayStation, and the majority of dev-tools (with the major exception of psxdev) for the PSX are Win32 only (VMWare can't handle non-standard hardware).
How I set this up:
Install NT on the second harddrive
Configure all drivers, etc. for NT (might want to wait for this step to make creating Hardware Profiles easier)
Install Linux on the first harddrive w/ LILO
Setup VMWare on Linux to talk to NT as a guest (using raw disk partitions)
Boot *NATIVELY* into NT and copy your existing profile into a new Hardware Profile (System Control Panel)
Disable any devices in your new profile (call it "Virtual Machine") that VMWare doesn't support (Devices Control Panel)
At this point if you want you can setup VMWare for NT to access Linux as a raw partition
Boot into Linux and test your NT under VMWare, if some drivers fail, disable them under the Devices Control Panel
If you installed VMWare for NT, tweak your Linux dualconf configuration (I had to manually add a condition for switching the links to the X server)
Setup Host-only networking, samba, etc.
I know I didn't go into any detail, I don't have the time to write everything out and I'm not at my machine so I might have missed something. I'll post a couple articles at my site, etc. when I have some time (this weekend?).
Slashdot Mirror
I had all of three games for the Jaguar, I can't even remember the exact names because once I bought it, it sat in a corner while I played Wild Arms and FF7 for PSX.
I even had the store where I got it from (Software Etc.) order me a Jaguar CD-ROM drive from a different store, but I chickened out when I saw the $75 price tag.
My Atari "64-bit" Jaguar now sits dismantled (I had my way with my trusty Phillips), broken, abused, and shattered in a dusty corner of the closet in my computer room.
I hadn't even thought about it until Slashdot posted this article (Damn you Slashdot :). The rest of my 5 minutes thinking about this worthless piece of 68K+Tom+Jerry crap is ruined! The fact that someone released a *NEW* game for it, when we now have true 128-bit consoles is...
I'm a budding console programmer (currently with my PSX), and even though I'm not a professional, I know that all games have a time and a place - as previous posters mentioned, Jaguar's place was in 1993-94, not 2000 (how in God's name did it make it this far?!).
Marcus
Such an app would have to be enormous to handle all those distros and every package that ships with most distros.
I suppose it could start by *strictly* adhering to the Filesystem Hierarchy Standard, excuse my ignorance (I've used SlackWare in the past and RedHat currently) but I haven't seen many distros that fully *comply* with FHS (even though FHS gives you a lot of leeway).
This could bring us a little closer to the the universal source package.
Also, the "Distro-O-Matic" would allow you to choose your kernel, from a predefined list (SMP, pgcc optimized, full networking, etc.).
Probably a pipe dream :)
Marcus
I have a fairly simple machine, PII 333 with two 4gig harddrives. I have it dual booted with Linux (Redhat 6.0) and NT 4.0 with LILO being the bootloader.
Here's the interesting part: when I boot under NT I can use VMWare to get at the raw Linux partition, and when I boot under Linux I can use VMWare to get to the raw NT partition. Each OS has a specific configuration depending on whether it's a guest or host (using Hardware Profiles under NT and VMWare's dualconf under Linux).
Then it starts getting complex with host-only networking under VMWare for each environment. I actually have 5 different IPs for my one machine:
So while I have NT as a host, I can use samba to send files to Linux and then test them out. As far as development goes on NT, I have Visual Studio 6.0, Borland's free compiler, and Cygnus's cygwin (with mingw32 built under cygwin). I also have cross tools under cygwin that target Linux and MSDOS (djgpp).
When I use Linux as a host (99.5% of the time), again I can use samba to send executables to the NT guest and try them out *immediately* after compilation. This is a plus for libraries such as SDL, etc. I use pgcc-2.95.2 targetted to mingw32, cygwin (for the hell of it), ms-dos, and Sony PlayStation.
The main reason I use this setup is for hardware/processor feasibility, I have a TNT2 Ultra that isn't supported in any way under VMWare, therefore booting NT means I get 3DSMax, etc. that takes full advantatge of my hardware. Also, I have an ISA card that talks to my PlayStation, and the majority of dev-tools (with the major exception of psxdev) for the PSX are Win32 only (VMWare can't handle non-standard hardware).
How I set this up:
Install NT on the second harddrive
Configure all drivers, etc. for NT (might want to wait for this step to make creating Hardware Profiles easier)
Install Linux on the first harddrive w/ LILO
Setup VMWare on Linux to talk to NT as a guest (using raw disk partitions)
Boot *NATIVELY* into NT and copy your existing profile into a new Hardware Profile (System Control Panel)
Disable any devices in your new profile (call it "Virtual Machine") that VMWare doesn't support (Devices Control Panel)
At this point if you want you can setup VMWare for NT to access Linux as a raw partition
Boot into Linux and test your NT under VMWare, if some drivers fail, disable them under the Devices Control Panel
If you installed VMWare for NT, tweak your Linux dualconf configuration (I had to manually add a condition for switching the links to the X server)
Setup Host-only networking, samba, etc.
I know I didn't go into any detail, I don't have the time to write everything out and I'm not at my machine so I might have missed something. I'll post a couple articles at my site, etc. when I have some time (this weekend?).
Marcus