I think, ideally, I would block the saving of any file on the hard drive unless it has certain extensions (.doc,.xls,.ppt if you use M$ Office), prevent running files from home, etc., that all can be done with the right software, I think Fortres Grand can do that.
Our local public library has the following blocks in place with Fortres Grand:
console apps
saving exe, com, sys, dll, and some other extensions
running apps from A:
the Start Menu, except for Shut Down
MS-DOS Mode
Add a heavy dose of AV automagically updated daily without their knowledge and which cannot be disabled.
Block everything they do not need to complete their job. It's possible.
Well, the least RAM I ever saw on a IIgs - and schools were known to scrimp on their computers back then - was 512K. We had a 1.25 MB original (unsigned) and a 512K ROM 1.
Only one other IIgs, a 512K ROM 1, in the entire school.
More correctly, Apple's adaptation of Miro$oft BASIC-6502. Yeah. From 1977. No wonder it was teh suxor. But it was nice to cut my teeth on, although I would've killed for a C compiler back when I was using the ][...or the IIgs later...
BTW the BASIC on the IIgs doesn't take any advantage of the 65816. *sigh*
-uso. Want an Apple//e emulator? See my link above!
It's theoretically possible. The IIgs's CPU is a 65816, a 16-bit variant of the 65C02. It has 24-bit memory addressing (like the 286). The IIgs came standard with 512K RAM, not too shabby for 1986. If GNO can run on top of GS/OS, I don't see why Minix can't be ported to it.
I suggest someone might want to download KEGS and a 65816 assembler, and maybe the GNO tools and try to bootstrap Minix on it.
GNO contains components that originate with a variety of flavors of UNIX. These include 4.3BSD, XINU, and SYSV. It is mostly BSD. As of GNO v2.0.6, GNO has become closer to 4.4BSD. Work is in progress to make it as compliant as possible to POSIX 1003.1 and POSIX 1003.2.
I'm surprised that you haven't been modded Flamebait right now, but I firmly agree with you.
We do not necessarily know it all. It is possible that God is deliberately hiding knowledge from our eyes. He knows all, and who are we to question his infallible (at least IMHO) Word?
Personally, I don't like the GNU coding style. (In face I have at one time passed RMF-COM through Indent.)
But it's a testament to my terseness that a typical program might be #include <stdio.h>
void main(void) {
int foo,bar;
printf ("test\n");
for (foo=0;foo which is very odd-looking but functional. I feel function is more important than form, but readability *is* important and not something to be shrugged off. And I don't think I'd be too prone to play "Perl Golf" either.
Look at part of my RMF-COM,
if (filespec1[1]==':') drv=filespec1[0]; else drv=0;
if (!strrchr (filespec1, '\\'))
{
if (drv)/* drive and file */
retv=prepare_for_rename (drv-64, &zero, filespec1 + 2, filespec2);
else/* file */
retv=prepare_for_rename (0, &zero, filespec1, filespec2);
} else {
file=strrchr (filespec1, '\\') + 1;
for (travel2=2*(drv!=0); (filespec1+travel2) != (file-1); travel2++)
path[travel2-(2 * (drv != 0))]=filespec1[travel2];
path[travel2-(2 * (drv != 0))]=0;
if (drv)/* drive, path and file */
retv=prepare_for_rename (drv, path, file, filespec2);
else/* path and file */
retv=prepare_for_rename (0, path, file, filespec2);
}
Pretty ugly code. And I haven't changed it since I dropped it in there. I don't think a real programmer, or a commercial developer, would ever put code THAT ugly in there, because it's TEH SUX0R when you have to read it to fix bugs etc.,...
Just imagine if I could code in ASM. That can get a might uglier. At least I don't mutate C into my own language with #ifdefs like Bourne did with the V7 shell.
Slashdot Mirror
I've seen that GNOME file dialog before.
Windows 3.1. Yeah. It was teh suxor there too.
KDE though ripped off Win98...
Gotta stop cloning Big Evil, guys!!
-uso.
Add a second space after each period, and the exclamation point. Bingo, 120 characters.
-uso.
*hides pegleg* Well, someone had to write a M$ Agent interface tailored to my needs...
Like a big parking lot, a barren desert, or one hell of an ocean, I'm not sure which.
However the last is unlikely IMHO.
-uso.
No, not in the neck, in the forehead or the hand. Trust me though, it's coming.
-uso.
Yep.
http://www.digitalmars.com/d/index.html
-uso.
My usual variation is "If you aren't part of the solution, you are ... the problem."
-uso.
I think, ideally, I would block the saving of any file on the hard drive unless it has certain extensions (.doc,
Our local public library has the following blocks in place with Fortres Grand:
- console apps
- saving exe, com, sys, dll, and some other extensions
- running apps from A:
- the Start Menu, except for Shut Down
- MS-DOS Mode
Add a heavy dose of AV automagically updated daily without their knowledge and which cannot be disabled.Block everything they do not need to complete their job. It's possible.
-uso.
For bloodsuckers like D'ohl, nah hell, we need the whole shebang. Garlic anyone?
"Vampires hate garlic, and that means...Korean barbecue!!" (Sailor Moon special)
-uso.
Then why couldn't they have gone back to BSD where they came from? Doesn't FreeBSD support enough hardware? Why do they need to buy from SCOrdure?
-uso.
Well, the least RAM I ever saw on a IIgs - and schools were known to scrimp on their computers back then - was 512K. We had a 1.25 MB original (unsigned) and a 512K ROM 1.
Only one other IIgs, a 512K ROM 1, in the entire school.
-uso.
Ninjaforce? Ye gads, didn't they do the sound for Wolfenstein 3-D GS?
Ghod, I love that game. *g*
-uso.
Ah yes. Applesoft BASIC.
//e emulator? See my link above!
More correctly, Apple's adaptation of Miro$oft BASIC-6502. Yeah. From 1977. No wonder it was teh suxor. But it was nice to cut my teeth on, although I would've killed for a C compiler back when I was using the ][...or the IIgs later...
BTW the BASIC on the IIgs doesn't take any advantage of the 65816. *sigh*
-uso.
Want an Apple
Minix is BSD-licensed now.
It's theoretically possible. The IIgs's CPU is a 65816, a 16-bit variant of the 65C02. It has 24-bit memory addressing (like the 286). The IIgs came standard with 512K RAM, not too shabby for 1986. If GNO can run on top of GS/OS, I don't see why Minix can't be ported to it.
I suggest someone might want to download KEGS and a 65816 assembler, and maybe the GNO tools and try to bootstrap Minix on it.
From the
FAQ:
GNO contains components that originate with a variety of flavors of UNIX. These include 4.3BSD, XINU, and SYSV. It is mostly BSD. As of GNO v2.0.6, GNO has become closer to 4.4BSD. Work is in progress to make it as compliant as possible to POSIX 1003.1 and POSIX 1003.2.
-uso.
AFAICT you are right, but I do recall seeing a GPL disclaimer. (At this time, I can't find it.)
-uso.
Freeware? Nay, I say, GNO is GPL!
FP
-uso.
I'm surprised that you haven't been modded Flamebait right now, but I firmly agree with you.
:)
We do not necessarily know it all. It is possible that God is deliberately hiding knowledge from our eyes. He knows all, and who are we to question his infallible (at least IMHO) Word?
-uso.
If you like the Bible you'll love the 1576 Tomson NT.
You mean
The Catholic Church's line has been open to the prospect of evolutionism, while the fundies have flatly denied it.
-uso.
Wolfenstein came out, I played it.
Mortal Kombat II came out, I played it.
Samurai Shodown came out, I played it.
All of these games feature blood and gore and involve killing people. Have I become more violent as a result?
I think I have become less violent, because I can take out my anger at a computer instead of going at someone's throat.
And I have a pretty damn short fuse.
-uso.
"Never underestimate the bandwidth of a 747 filled brimful of DVD-R discs."
Hmm, anyone know the usable volume of a 747 and the volume of a DVD-R disc?
-uso.
"Waht? Teihr's a preveiw button?"
#include <stdio.h>
void main(void)
{
int foo,bar;
printf ("test\n");
for (foo=0;foo<100;foo++)
for (bar=0;bar<foo;bar++)
{
printf ("%d ",bar);
if (bar==foo)
printf ("* ");
}
}
Man, I have to get my head out into the clear, this stench is overbearing...
-uso.
Personally, I don't like the GNU coding style. (In face I have at one time passed RMF-COM through Indent.)
But it's a testament to my terseness that a typical program might be
#include <stdio.h>
void main(void)
{
int foo,bar;
printf ("test\n");
for (foo=0;foo
which is very odd-looking but functional. I feel function is more important than form, but readability *is* important and not something to be shrugged off. And I don't think I'd be too prone to play "Perl Golf" either.
-uso.
Still trying to write a libc for CP/M-86
C can be pretty bad too.
/* drive and file */ /* file */ /* drive, path and file */ /* path and file */
...
Look at part of my RMF-COM,
if (filespec1[1]==':') drv=filespec1[0]; else drv=0;
if (!strrchr (filespec1, '\\'))
{
if (drv)
retv=prepare_for_rename (drv-64, &zero, filespec1 + 2, filespec2);
else
retv=prepare_for_rename (0, &zero, filespec1, filespec2);
} else {
file=strrchr (filespec1, '\\') + 1;
for (travel2=2*(drv!=0); (filespec1+travel2) != (file-1); travel2++)
path[travel2-(2 * (drv != 0))]=filespec1[travel2];
path[travel2-(2 * (drv != 0))]=0;
if (drv)
retv=prepare_for_rename (drv, path, file, filespec2);
else
retv=prepare_for_rename (0, path, file, filespec2);
}
Pretty ugly code. And I haven't changed it since I dropped it in there. I don't think a real programmer, or a commercial developer, would ever put code THAT ugly in there, because it's TEH SUX0R when you have to read it to fix bugs etc.,
Just imagine if I could code in ASM. That can get a might uglier. At least I don't mutate C into my own language with #ifdefs like Bourne did with the V7 shell.
-uso.
Apparently they fixed the bug (  without semicolon).
-uso.
Bingo, you hit the nail on the head...
Believe me, I always thought a keyboard/menu interface (a la MultiMate Advantage) was more intuitive than a WIMP GUI anyway.
Then again I learned GUIs with GS/OS (Apple IIgs, 1988).
-uso.