@tiffers

are you compiling for AOS4 as host or Linux as host OS ?

@Hans

AmigaDOS processes have always been an extended for Exec Task,

@all

I personally see it this way... any "Exec Task" no matter who launched it
has its own memory space, and only "MEMF_SHARED" memory is going
to be available between them.

tasks/processes/threads/ does it really matter...
other OS may allow threads to occupy the same memory space,
but we are not those other OS, why not take the path of
every seperate thread of execution as being an own task whether
able to be an AmigaDOS extended process or not?

that means if it is shared amongst threads/tasks/process then mark it shared,
otherwise it isnt available, seems to be the simplest rule to follow

if anyone more knowing about the subject can correct me for AOS4 specifics?

@Rogue

I'll be wanting ExecSG to be the host (minimal host memory footprint),
I would be wanting to create a virtual machine tool inside AOS4

@LiveForIt

something like qemu with the "cpu-user-mode-linux" functionality,
or go the full fledged "cpu-softmmu" path for any arbitrary archspec

@Hans

possibly, will have to explore this later... I have other things to concentrate
on before this might be achieved if at all

@Atheist

I agree, be dammed anything else, lets just get this whole legal mess done,
over with and ended... let the companies who have *delivered* survive,

And I list Hyperion/ACube as having not only shown but delivered,
hell I am personally sorting out funds to buy a sam440 when it becomes
available whether AmigaOS4 is part of the package or not

@LiveForIt

with the virtual machining I was thinking of launching non-native material within a wrapping process of some kind...

anyway... I will have to leave things there until I can sort out an AOS4 machine to test some ideas out on...

donations or use of a machine to get something past "idea" into a functional
toolkit would be appreciated,

I can be found with this same username on UtilityBase for donation info

@abalaban

true enough ... I wasnt thinking about such security measures inside
I was more thinking that protection would happen "at the door"
not after entry is successful

@Rogue:

does the PPC "ExecNG" have faclities for handling Virtual Machining in
current state? just yes/no would be fine to answer this,

I see nothing wrong with defaulting the UMA to being read-write
and anything *allocated* becomes write-only by the allocator...
executable code being "write-enabled" exclusive of "executable"
seems fair also...

I hope to code something dependant on such functionality once I lay
hands on an AOS4 capable device, ...

I wish you all the best in the current mess

@Athiest:

Ive seen enough of this thread to actually get a proper grasp at how
"Memory Protection" actually needs to work... and with what I learnt
of the AOS3 and AOS2 systems I originally learned programming with
I will be looking forward to the Hyperion produced AOS4 becoming
generally available.

there is *nothing* stopping a program asking exec nicely to walk *all* virtual memory spaces as "read-only" to find strings...
being able to "write" changes over the found string is another matter...

What is the definition of "Memory Protection" ?

are you working on a concept similar to "protection bits" for files in a filesystem ? (allocated areas in the memory system...)

for me "common sense" is not common at all so I find discussions
about such things as this become convoluted and a mess

Id like to see a form of protection bits for memory areas,
as I would need such options for a "Symmetry" extension to
the exec.library

in addition to the above it would allow me to handle some
virtual machine management tasks in a simpler manner

Im still working on concept design only at this time,
until I can sort out some means of testing

anyway I'll leave the floor open to others before
I get completely sidetracked :)

@voxel

TWAIN support or SANE support?

@all

TWAIN is Windows and
SANE seems to be everything else,

Windows also has TWO variations, "STI" and "WIA"
in addition to BlueTooth and other support stack materials,

I would personally prefer the SANE solution since
reference drivers for BSD & Linux systems would then be available,
along with also *other* types of drivers

afaik someone is already working on sane-drivers and
sane-libs package support as part of the OpenOffice effort.

anyone care to correct me for the above?

@Billsey

Ive seen commercial sales of LAN over Home-Power adapters here in New Zealand under HomeLAN or some similar name,

@all-others

I agree with the above sentiments in this thread...
the amigans.net community are more "open eyed" in general as to anything that is possible and also the difficulties,

I personally hope I will be able to lay hands on an AOS4 capable PPC board myself,
all the best to everyone :)

Belxjander

@AmiKit




Me, My Cat and her three kittens...

3 bundles of cut cuddly with paws claws and the attitude to use them :P

@all

I have actively used and *read* a working NTFS Windows 2000 professional setup Harddisk using the NTFileSystem module from Aminet...

this was done on an AMIthlon setup

as for filesystem limitations... there are some quirks...

may be something to do with 32bit vs 64bit block addressing
for the filesystem...to with maximum HDD sizing and filesize limits

I think AFFS and FAT32 share the file size limit for the 32bit restricted versions...

I know I have had a larger filesize than that stored on SFS and NTFS between various setups

now I will go back to scrimping and saving for a Samantha
so I can put together some kind of development machine