>> >- What about RBAC (Role-Based Access Control, Solaris 2.8/Trusted
>> >Solaris) support ?
>> Sorry, I did not yet have any access to Trusted Solaris.
>> I have no idea.
>The feature was added to Solaris in 2.8
>See rbac(5) or
Thank you for the hint, it seems tha I missed this....
>> >- Is there a way to gurantee network bandwidth (I'm still little bit
>> >afraid that the data stream to the cd recorder may be interrupted by
>> >another network application) for the SCSI device ?
>> 1) I got 9900 KB/s between two U-10 Running S8
>Which kind of network (10baseT, 100baseT) ?
10BaseT ??? Are you joking? Of course 100MB
>> 2) There is BURN-Proof
>Uhm... what is BURN-Proof !?
Buffer UnderRuN Proof A Sanyo Patent that allows a CD-writer to stop
recording and resume it without creating a broken media.
I currently own 3 drives which support BURN-Proof:
- Sanyo BP-2
- Plextor PX-W121032
- Sanyo CRD-BP1300P
>> >- What about a kernel module for rscsi ?
>> It is just modelled after 'rmt'
>> In fact, rscsi.c is based on rmt.c which I created for star-1.3
>> The rmt.c project was started 1994 and retired about a month ago,
>> I finished it with the following features:
>> - 100 % compatible with Sun rmt
>> - 20-40% faster than Sun rmt
>> Based on this new code, I created rscsi.
>After visiting rmt(1M)... this means that rexec must be enabled in
>/etc/inet/inetd.conf ? What about using a better/stronger
So rmt(1M) is wrong? ... no, you just missunderstood it.
You may call it via rcmd but I would not recommend to to it.
rmt and rscsi work with rsh
rmt from the star package allow much better security checks than the rmt
implementation foun on Solaris (and will get additional checks via /etc/default/rmt
rscsi already implements special security checks defined in /etc/default/rscsi
Just read the Announcement file for cdrecord-1.10a04 to see
how the security features work.
URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix