Linked by Razvan T. Coloja on Mon 3rd Jan 2011 23:30 UTC
BeOS & Derivatives To understand what the BeOS and Haiku operating systems are, we first must remember that BeOS was developed with the multimedia user in mind. BeOS wanted to be what OS X has become today: an easy to use, attractive operating system. However, BeOS was a niche OS, destined for the media-hungry user. The percentage of audio and video applications available for Haiku is greater than the one in Linux, OS X or Windows, and the inner workings of the operating system were created in such a way, that the same multimedia passionate would find it easy to work with the user interface and files. Each application can interfere with other applications of its kind. A WAVE file selection can be dragged from a sound editor and onto the desktop, to create an audio file. Audio applications can interfere with each other via the Haiku Media Kit -- the corespondent of a Linux sound server. Applications like Cortex are a perfect example of how BeOS and Haiku deal with multimedia files: you can have more than one soundcard and use each one of those soundcards independently or separately. You can link one soundcard to the Audio Mixer, start a drum machine application and link that software to the Audio Mixer. If you want to output whatever you create with the audio application, all you have to do is drag the microphone and link it to the application's icon in Cortex.
Thread beginning with comment 455854
To view parent comment, click here.
To read all comments associated with this story, please click here.
Bully
Member since:
2006-04-07

There are other ways to protect system files then to think in root/user.

Reply Parent Score: 3

nt_jerkface Member since:
2009-08-26

If you have multiple users accessing the same computer then you need file separation. Do user files need to be separated and encrypted? If so then why not have a multi-user system?

Reply Parent Score: 2

Thom_Holwerda Member since:
2005-06-29

If you have multiple users accessing the same computer then you need file separation.


And how many home computers are accessed by multiple users?

Hint: few.

I can't find the damn link, but I believe the results from Microsoft's Customer Experience Improvement Program showed like 90% of machines having only one user (the owner). There is no need whatsoever to DEMAND multiuser OR ELSE. There ARE other ways to make machines secure. Why focus on a fringe use case (i.e., home computers with multiple users), when you're such a small effort?

Reply Parent Score: 2

izomiac Member since:
2006-07-26

If multiple humans use a computer, then do some home folder redirection at boot and you're done. Letting multiple users log in simultaneously is much harder, and it's a mainframe carry-over that's been rehashed into a security measure.

IMHO, it's not even a particularly good security model as you need things like UAC and sudo, your home directory isn't protected, and the prevalence of privilege escalation exploits suggest it's difficult to properly implement.

Reply Parent Score: 1