Be was going to be the source of income of herds of open source developers, me included. It was "get paid for be, and for linux on evenings". I can't speak for everyone else, but I have always been concious about it during coding, and made sure I never tied myself too much to a Linux or Win32, thinking I will have to port it to Be someday.
BeOS booted from within Windows, to encourage new commers to try it. It, of course, had its own partition and file system, but the trial version (don't hold me to this, I couldn't boot the BeOS CD that came with the developer's guide.) the trial version needed windows.
Read this site It was mentioned first in an/. post, a while ago, but but googled turned up the link, and not the post itself.
This is just how capitalism works; if they rejected to take the contract, they could have been sued by their share holders. But now, the guilt (if any) is spread, and every one shares the profit.
abuse, root, postmaster, 127.0.0.1, localhost, etc.
How many "tricky" emails can you form out of those?
chances are, they call can fit into an array, and
looked up against. any name that sounds tricky,
is dropped on the spot.
This device will let us single out particular bad guys who need killing, without all the collateral damage. I'm entirely supportive of this effort.
1) The Chinesse embassy in Yoguslavia
2) The recent death of 60 Afghani tribes leaders.
Those are just two modern examples of well planed
attacks which have singled out the "bad guys".
All sarcasm aside, there is no "perfect" attack
from space/distance, without a solid intelligence
to guide the missiles to the inded target.
America needs intelligence, and intelligence requires
diplomacy and making aliances. But then, with a
solid intelligence, our conventional weapons would
have sufficed.
Either way, this "new" weapon is simply uncalled
for. I think of it as an over-clocked wet-dream,
for irresponsible weapon geeks in th military.
when the m-16 was first introduced, there was some controversy over the design. a bullet, when fired from an m-16, would tend to wobble as it flew, making it more messy when it hit a target. when it entered the body, it would tumble, rather than simply spin right through. i think there were some questions of geneva convention-compatibility early in vietnam, but i don't recall the outcome. they might have redesigned the ballistics, but i don't recall.
Oh yes,
I am now an American, but once upon a time, I have
been under the attack of American soldiers, and
an oppressing 3rd world regime, with US weapons:-(
Please excuse my terminology (I don't know the
proper names, and I am not a gun expert, an ex-refugee yes, but not a gun expert.)
First, there are different kinds of bullets for
every gun. There are bullets which give an orange
color at night, some that drill concrete, some
that sound louder, etc.
The M-16 has all three kinds of bullets. Infact,
there are some M-16 that launch garnades.
The russian Klashnikov is not as versatile as the
american assault refiles (the M-16, the SAR-80, etc.)
But the AK-47 comes in tens of flavors, and is
enhanced by every military (the Libyan AK-47 is
closer to the M-16 in terms of bullet variaty, and
is much smaller. but it has a plastic coat -as opposed to the traditional wood-
and heats too quickly.)
So back to the topic. The M-16 might be more "humane"(sic)
than eastern weapons, but you can get "rogue" bullets
from any military establishment, that is compatible
with the M-16, and doesn't adhere to the standards.
(e.g. the Israeli M-16s launch plastic, and the
Pakistani ones can launch just about anything,
even compressed AOL coasters;-)
Don't touch me, I don't need your instantiation,
I am a big object now, full of features and attributes,
and YOU are the one who needs me, you crippled
abstract class.
Sorry parent object, you were just an interface
donor. Thanks to my decorator patterns and multiple
inheritance, I made it through instantiation,
and I don't need you now.
I am staying here on earth, and you capitalists
fly to the stars and mine them for gold, wood,
and soil, and give my backyard a rest.
Just because Jane Soccer mom wants her SUV well
fueled, and just because corporate funded "research"
is promising me a better future, doesn't mean I am
gonna give up protesting their exploitation of
everything and everyone on earth.
We are not going to conquer the galaxay folks, we
will be dying here of polution, hunger, and nuclear accidents.
Challenge for aspiring hackers.
on
FreeDOS
·
· Score: 1
I failed to do this in my teens, let's see if some
kid can revenge me.
Write a tiny 32-bit microkernel that runs 2 or more FreeDOS kernels,
each in their own virtual 86 mode, and
each accessible through an Fn (function) key.
I personally figured it too late (after I was
forced to modify a Linux kernel for work.)
But it would be cool to have some kid, still at
mom's basement full of energy do this for me, and
tell me I wasn't the only 17 year old who missed
way too many parties, hacking.
If we ignore the fixed system variables in MS-DOS,
and speak of FreeDOS as a configurable system,
the your statement wouldn't be as correct as otherwise.
Assuming that the server runs in extended memory,
and the kernel stays in its own real memorys. then the following can happen:
1) the overhead of context switch, from protected
to real mode. That envolves the saving of system
descriptor registors (some "megabytes" there.)
and making a far long jump.
2) each resources allocated by the serves, takes
some "marking" bytes off of the kernel memory, and
in the even of slashdoting, the available memory
will be exhausted and the pointers will wrap around
to low memory (this made intel hackers from the
early eighties weep like girls -- very nasty.)
Re:Special Device Drivers(?)
on
FreeDOS
·
· Score: 1
I wouldn't wet my pants over this yet.
Last time I checked, FreeDOS cloned the DOS I/O,
infact, the device drivers have the same "interrupt/Strategy" layout,
but it is not the RealThing(TM)
Driving a device requires a hardware interrupt,
and DOS had so many things going on behind the
scenes (MS whoring for some HW vendors, and installing
specialized services for them at secret address.
Take a look at the toshiba CD-ROMs, those things
ran with more than MSCDEX!)
I suggest you stick to MS-DOS for controlling devices,
if it is an specialized piece of hardware.
Use FreeDOS for all your software interrupt handling:-)
Oh yeah baby.
on
FreeDOS
·
· Score: 5, Interesting
Finally, and slashdot story I know everything about:-)
I found the project ~2 years ago, while attempting to
write a DOS extender, and I have been playing with
it ever since.
FreeDOS is only a DOS in that it implements the DOS API,
and does not provide "hardcoded offsets" like commercial DOSes
(for the sane minds, back in DOS, major application
developers disassembled the undocumented kernel
and found what effects of reading/writing/jumping-to
a particular address has on the system. Usually,
those "effects" were interesting features, which
cutting-edge apps made use of.)
FreeDOS does not do that, but it has everything
else DOS had; Think of it like this, it runs SoftIce without a patch or recompilation!
and SICE is a system debugger, that knows way too
much about the kernel.
I tried to hack the kernel by just reading the author's
website -he had an overview of how everything went- but there were no contributing developers.
So dump me (or was it the combination of coffee and teen age?)
I poured on the sources for weeks, without ever
scratching the surface. Then I found "The FreeDOS kernel"
in a second hand store!
Here is where things get interesting. If you ever
hacked DOS, you know what the PSP, UMB, FAT, and
all the other acronyms, which are the hallmarks of poor design and implementation
exposure, are.
Everything is there!
I know Pat is a creative man (I saw his model trains.)
and I know he was targeting the heaps of text
and wetware out there for DOS, but the reimplementation of
everything good and bad about DOS is painfully
ugly.
The chapter on memory management is an example of
this. The memory allocation algorithm is too
complicated for a single tasking OS (sic) just for
the terminology, if not for anything (arenas, banks, segments, overlaying, extending, etc.)
Wait before you point the finger of blame on the
intel architecture. DOS only sees a perfect 16bit
machine, only authors of multi-tasking OSes and
DOS extenders need to worry about memory management
services implemented in the 32-bit part of the
machine.
So all the complexity, is for 16-bits only!
TO spare you the thrill, FreeDOS is an interesting
hackable piece, only if you come from a DOS background.
It could serve as an eye opener for luckier developers
(Java guys I am looking at you.)
Also, for the casual DOS user, it is an excellent
alternative to the realthing (I kid you not, single
tasking is not fun, use sparingly.)
It runs all the important apps, 4DOS, turboC, SoftIce,
several editors, and a host of other well behaving
apps. It even has its own GUI desktop and a web
browser.
The so called "other" OSes, are purely *desktop*
OSes, and require responsive GUIs.
Linux runs on more hardware than Mac, Windows and
all commercial Unices combined, and what is a "must have"
for one linux user is a "nono" for another.
This must be a bottle-neck in the GTK signal
routing code; I beleive it could be eliminated with
some manual optimization (i.e. loop unrolling, and
inline assembler.)
file it as a bug, and let the developers take a look
at it. I am using a GHz machine, so I don't notice
the 2D math calculations. Or maybe, my monitor/gfx card
have higher refresh rates.
The kernel is GPLed, so anything that makes into
it is free as in speech.
Do you know why we hate Katz articles?
on
Heart of the Net
·
· Score: 0, Flamebait
Because they are filled with emotions!
The majority of/. readers are male, and technically
adept at that.
It takes effort to sit down and see the world from
someone else's point of view, specially when that
PoV is not an argubale fact, but an emotion.
mark me down to -1 for being off topic, and next
time you see a Katz article, pass it to a female
friend, a non technical (immaginative male.)
or anyone with human blood running through their
veins, as opposed to a lethal mixture of caffeine
and testestrone, and you will see them enjoy it.
Slashdot Mirror
Be lacked developers?
Be was going to be the source of income of herds
of open source developers, me included.
It was "get paid for be, and for linux on evenings".
I can't speak for everyone else, but I have always
been concious about it during coding, and made
sure I never tied myself too much to a Linux or
Win32, thinking I will have to port it to Be someday.
--
I just visited his website, and this guy really
got it.
Well done Mike, and to the moderators, shouldn't
this be insightful?
--
BeOS booted from within Windows, to encourage
new commers to try it.
It, of course, had its own partition and file
system, but the trial version (don't hold me to this,
I couldn't boot the BeOS CD that came with the
developer's guide.) the trial version needed windows.
--
Read this site /. post, a while ago, but but googled turned up the
It was mentioned first in an
link, and not the post itself.
This is just how capitalism works; if they rejected
to take the contract, they could have been sued
by their share holders.
But now, the guilt (if any) is spread, and every
one shares the profit.
--
> they call can fit into an array, and
...
they ALL can fit
abuse, root, postmaster, 127.0.0.1, localhost, etc.
How many "tricky" emails can you form out of those?
chances are, they call can fit into an array, and
looked up against. any name that sounds tricky,
is dropped on the spot.
--
This device will let us single out particular bad guys who need killing, without all the collateral damage. I'm entirely supportive of this effort.
1) The Chinesse embassy in Yoguslavia
2) The recent death of 60 Afghani tribes leaders.
Those are just two modern examples of well planed
attacks which have singled out the "bad guys".
All sarcasm aside, there is no "perfect" attack
from space/distance, without a solid intelligence
to guide the missiles to the inded target.
America needs intelligence, and intelligence requires
diplomacy and making aliances. But then, with a
solid intelligence, our conventional weapons would
have sufficed.
Either way, this "new" weapon is simply uncalled
for. I think of it as an over-clocked wet-dream,
for irresponsible weapon geeks in th military.
--
when the m-16 was first introduced, there was some controversy over the design. a bullet, when fired from an m-16, would tend to wobble as it flew, making it more messy when it hit a target. when it entered the body, it would tumble, rather than simply spin right through. i think there were some questions of geneva convention-compatibility early in vietnam, but i don't recall the outcome. they might have redesigned the ballistics, but i don't recall.
:-(
;-)
Oh yes,
I am now an American, but once upon a time, I have
been under the attack of American soldiers, and
an oppressing 3rd world regime, with US weapons
Please excuse my terminology (I don't know the
proper names, and I am not a gun expert, an ex-refugee yes, but not a gun expert.)
First, there are different kinds of bullets for
every gun. There are bullets which give an orange
color at night, some that drill concrete, some
that sound louder, etc.
The M-16 has all three kinds of bullets. Infact,
there are some M-16 that launch garnades.
The russian Klashnikov is not as versatile as the
american assault refiles (the M-16, the SAR-80, etc.)
But the AK-47 comes in tens of flavors, and is
enhanced by every military (the Libyan AK-47 is
closer to the M-16 in terms of bullet variaty, and
is much smaller. but it has a plastic coat -as opposed to the traditional wood-
and heats too quickly.)
So back to the topic. The M-16 might be more "humane"(sic)
than eastern weapons, but you can get "rogue" bullets
from any military establishment, that is compatible
with the M-16, and doesn't adhere to the standards.
(e.g. the Israeli M-16s launch plastic, and the
Pakistani ones can launch just about anything,
even compressed AOL coasters
--
well said.
--
> no braces {} for blocks,
> no ";" to end the statement.
> Whitespace mandatory.
>
> Yukk,
> Puke.
>
> I'd rather program in C, C++, Java, or Perl.
With that attitude, I guess you are only half jokingly
serious about the first three languages.
But Perl, oooh, perl is sooo your type.
Where were you all my life?!!
Don't touch me, I don't need your instantiation,
I am a big object now, full of features and attributes,
and YOU are the one who needs me, you crippled
abstract class.
Sorry parent object, you were just an interface
donor. Thanks to my decorator patterns and multiple
inheritance, I made it through instantiation,
and I don't need you now.
Live alone til garbage collection.
You know, Guido is the root object, and we all have
the Award attirbute, inherited from out based class.
No thanks,
I am staying here on earth, and you capitalists
fly to the stars and mine them for gold, wood,
and soil, and give my backyard a rest.
Just because Jane Soccer mom wants her SUV well
fueled, and just because corporate funded "research"
is promising me a better future, doesn't mean I am
gonna give up protesting their exploitation of
everything and everyone on earth.
We are not going to conquer the galaxay folks, we
will be dying here of polution, hunger, and nuclear accidents.
Burn your own
I failed to do this in my teens, let's see if some
kid can revenge me.
Write a tiny 32-bit microkernel that runs 2 or more FreeDOS kernels,
each in their own virtual 86 mode, and
each accessible through an Fn (function) key.
I personally figured it too late (after I was
forced to modify a Linux kernel for work.)
But it would be cool to have some kid, still at
mom's basement full of energy do this for me, and
tell me I wasn't the only 17 year old who missed
way too many parties, hacking.
No!
If we ignore the fixed system variables in MS-DOS,
and speak of FreeDOS as a configurable system,
the your statement wouldn't be as correct as otherwise.
Assuming that the server runs in extended memory,
and the kernel stays in its own real memorys. then the following can happen:
1) the overhead of context switch, from protected
to real mode. That envolves the saving of system
descriptor registors (some "megabytes" there.)
and making a far long jump.
2) each resources allocated by the serves, takes
some "marking" bytes off of the kernel memory, and
in the even of slashdoting, the available memory
will be exhausted and the pointers will wrap around
to low memory (this made intel hackers from the
early eighties weep like girls -- very nasty.)
I wouldn't wet my pants over this yet.
:-)
Last time I checked, FreeDOS cloned the DOS I/O,
infact, the device drivers have the same "interrupt/Strategy" layout,
but it is not the RealThing(TM)
Driving a device requires a hardware interrupt,
and DOS had so many things going on behind the
scenes (MS whoring for some HW vendors, and installing
specialized services for them at secret address.
Take a look at the toshiba CD-ROMs, those things
ran with more than MSCDEX!)
I suggest you stick to MS-DOS for controlling devices,
if it is an specialized piece of hardware.
Use FreeDOS for all your software interrupt handling
Finally, and slashdot story I know everything about :-)
I found the project ~2 years ago, while attempting to
write a DOS extender, and I have been playing with
it ever since.
FreeDOS is only a DOS in that it implements the DOS API,
and does not provide "hardcoded offsets" like commercial DOSes
(for the sane minds, back in DOS, major application
developers disassembled the undocumented kernel
and found what effects of reading/writing/jumping-to
a particular address has on the system. Usually,
those "effects" were interesting features, which
cutting-edge apps made use of.)
FreeDOS does not do that, but it has everything
else DOS had; Think of it like this, it runs SoftIce without a patch or recompilation!
and SICE is a system debugger, that knows way too
much about the kernel.
I tried to hack the kernel by just reading the author's
website -he had an overview of how everything went- but there were no contributing developers.
So dump me (or was it the combination of coffee and teen age?)
I poured on the sources for weeks, without ever
scratching the surface. Then I found "The FreeDOS kernel"
in a second hand store!
Here is where things get interesting. If you ever
hacked DOS, you know what the PSP, UMB, FAT, and
all the other acronyms, which are the hallmarks of poor design and implementation
exposure, are.
Everything is there!
I know Pat is a creative man (I saw his model trains.)
and I know he was targeting the heaps of text
and wetware out there for DOS, but the reimplementation of
everything good and bad about DOS is painfully
ugly.
The chapter on memory management is an example of
this. The memory allocation algorithm is too
complicated for a single tasking OS (sic) just for
the terminology, if not for anything (arenas, banks, segments, overlaying, extending, etc.)
Wait before you point the finger of blame on the
intel architecture. DOS only sees a perfect 16bit
machine, only authors of multi-tasking OSes and
DOS extenders need to worry about memory management
services implemented in the 32-bit part of the
machine.
So all the complexity, is for 16-bits only!
TO spare you the thrill, FreeDOS is an interesting
hackable piece, only if you come from a DOS background.
It could serve as an eye opener for luckier developers
(Java guys I am looking at you.)
Also, for the casual DOS user, it is an excellent
alternative to the realthing (I kid you not, single
tasking is not fun, use sparingly.)
It runs all the important apps, 4DOS, turboC, SoftIce,
several editors, and a host of other well behaving
apps. It even has its own GUI desktop and a web
browser.
It would be nice to have a "google.com" user in
/.
I bet it would be the greatest karma whore of all
time.
This is late -busy with work- but hey man, I wish
you a happy exciting life.
The so called "other" OSes, are purely *desktop*
OSes, and require responsive GUIs.
Linux runs on more hardware than Mac, Windows and
all commercial Unices combined, and what is a "must have"
for one linux user is a "nono" for another.
This must be a bottle-neck in the GTK signal
routing code; I beleive it could be eliminated with
some manual optimization (i.e. loop unrolling, and
inline assembler.)
file it as a bug, and let the developers take a look
at it. I am using a GHz machine, so I don't notice
the 2D math calculations. Or maybe, my monitor/gfx card
have higher refresh rates.
I would mod you down :'D
The kernel is GPLed, so anything that makes into
it is free as in speech.
Because they are filled with emotions!
/. readers are male, and technically
The majority of
adept at that.
It takes effort to sit down and see the world from
someone else's point of view, specially when that
PoV is not an argubale fact, but an emotion.
mark me down to -1 for being off topic, and next
time you see a Katz article, pass it to a female
friend, a non technical (immaginative male.)
or anyone with human blood running through their
veins, as opposed to a lethal mixture of caffeine
and testestrone, and you will see them enjoy it.
Actually, that is not as offensive as it looks.
FreeBSD has already been in bed with half of dozen
corporations, and that makes Daemon quite a gigolo.