As for VB, I'm not sure. I think there are a lot of hardware subtleties at work. I have to create iso file images of any CD I want to read in VB, let alone write. If device privileges are indeed the problem, I would try setting the file privileges for /dev/dsk/cXtYdZs2 (find X, Y, Z with "cdrecord -scanbus").
The problem with su was indeed caused by trying to add the media manager capability. Here's the explanation: http://defect.opensolaris.org/bz/show_bug.cgi?id=264 You should be able to add a few profiles without causing the bug, but I'm not sure how many. I don't know if the parser would recognize the "roles=..." clause if it were placed before the "profiles=..." clause, but that seems like a possible way to avoid the problem. Tom Kostas Oikonomou wrote: > Tom, > > Thanks. I will do that. > One more question, if you happen to know the answer: this whole > problem was caused by my adding the "media manager" capability (or > role, I'm not too clear) to myself. The reason > for that was that I run Virtual Box, and it would not see my DVD drive > as a writer, only as a reader. I therefore needed write access to that > device, and I thought that this "media manager" capability would > accomplish that. Instead, it caused a few hours of trouble! Do you > know how to do this correctly? > > Kostas > > Tom Vacek wrote: >> You won't be able to su unless you have given yourself a root role in >> user_attr. Here is what mine looks like: >> >> my_username::::profiles=Primary Administrator;roles=root >> >> Kostas Oikonomou wrote: >>> I successfully booted single-user, and edited the /etc/user_attr >>> file to completely remove myself. >>> But when I booted multi-user, I still can't su, I still get "Roles >>> can only be assumed by authorized users". On my Solaris 10 system >>> /etc/user_attr has no entry at all for me, and su has always worked >>> fine. >>> >>> Kostas >>> _______________________________________________ >>> desktop-discuss mailing list >>> desktop-discuss at opensolaris.org >>> >> >
