[Oberon] Re. ANN, Unix Oberon ports, release 2.4.3

[Guenter Feldmann]

Am Freitag 12 Mai 2006 12:49 schrieb easlab at absamail.co.za:
> Thanks for confirming that this package has the look & feel of S3,
> because it's a port of mostly the same source.
>
> Will the first tester who confirms [or otherwise] that it will
> allows the following, report his confirmation:
> 1. run normal linux inet facilities: Mozilla, lynx ... Threaded
> NewsReaders, full-featured email client ...,
> 2. copy the linux downloaded text to a file, probably by cutNpaste: gpm,
> 3. copy the '2 above text' to the Unix Oberon port file-space,

Please have a look at    http://www.oberon.ethz.ch/unixOberon.html
in the ETH download page.

Excerpt:

	Differences between Native Oberon and the Unix Oberon ports
	
	1) File System
 	  Native Oberon resides in a dedicated partition with Native's flat file
	system (AosFS). In Native Oberon, one can mount other file systems in order
	to transfer files to/from other file systems: FAT12 (diskette), FAT 16,
	FAT32, ISO. Also the network or a floppy disk (as Backup device) can be used 
	as transport media. 
	  Unix Oberon (like Mac Oberon and Win Oberon) uses the file system of the 
	guest system (Solaris, Linux, ...). Every Oberon file is a file in the 
	underlying Unix file system and every Unix file (device) is directly 
	accessible by Oberon. 
	  For reading and writing of Unix ASCII files, the commands 
	'EditTools.OpenUnix' and 'EditTools.StoreUnix' can be used. 

	  As the Unix file system is hierarchical, the Unix Oberon file system is		
	hierachical too. The directory in which Oberon is started is the current 
	directoy '.'. Filenames may contain absolute or relative paths, 
	  e.g.: EditTools.OpenUnix "/etc/X11/XF86Config-4" 
	  
	  If in Oberon, an open is performed on a file without path specification in 
	its name, the system searches the file in the directories listed in the 
	environment variable OBERON. OBERON is set in the startup script and can be 
	modified to suit the users demands. The current working directory '.' should 
	be the first element in OBERON. This guarantees that files in '.' always hide 
	files with the same name in the other directories. 

	  If Oberon has write permission for an opened file, the path appears in the 
	NamePlate and 'Store' writes it back to the original place. If Oberon has no 
	write permission for the opened file, the path is missing in the NamePlate 
	and [Store] writes it into the current working directory. 

	  Oberon may only be started in a directory for which it has write
	permissions!


I hope this helps.

-- Guenter

> 4. manipulate the '3 above text' by normal S3 facilities.
>
> Obviously 1 & 2 being linux facilities are acheivable.
> But how's the interface across to S3 text format ?
>
> Since all linux & FAT partitions will be accessible, I'm wondering
> if the N-O partitions will be too ?
>
>
> == Chris Glur.
>
>
>
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon