GentooThis forum is for the discussion of Gentoo Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi!
I'm dualbooting my gentoo install with Windows xp. If i boot windows and pop a disk in my dvd drive it all works, but if I do the same thing in gentoo nothing happens. I have installed HAL and it automounts usb-sticks and so on. Please help.
Please also post the contents of /etc/fstab. What desktop environment or file manager are you using? Does the device show up but can't be mounted, or does it not show up in your file manager at all?
You might want to confirm that you have correctly configured the cdrom in the kernel or initrd, as there are sometimes problems if e.g., the ide controller is loaded prior to the cdrom controller.
Never put users in the disk group. That gives them raw hdd access, so they can bypass all the filesystem security.
e.g. they can steal your /etc/shadow or change anything they like.
Never put users in the disk group. That gives them raw hdd access, so they can bypass all the filesystem security.
e.g. they can steal your /etc/shadow or change anything they like.
not really they just can go there it is still set by permission per-file I can look at a root folder on any drive but that does not mean you can access the folder.
If you feel real strong about it then ok your right. But my stuff is read and write protected. my /etc/shadow is write protected. good luck Been doing this a long time.
Linux is a server and that is what it's about letting user go places but not be able to read or change things you do not want changed.
Look at admin we have to allow people to access areas of the system for certain data.
ssh does not even allow root to see it. but root can change it. only that user can go to the disk but he or she can't see it or access it. Why even have read and write protection if you do not uses it.
So go to /etc/shadow as a user and try to open the file with an editor trust me if your not root it is not going to happen. unless you gave the user root permission.
for the sake of not arguing your write if you want to be.
Disk is a device and the new kernel and hal do permission by device then by access then by reed then by write.
gives me read and write access to all of sda if I am in the disk group. Similar commands work for partitions. True, filesystem permissions still work, if I elect to use the filesystem but my point was that any low level command that does not use the filesystem is open to abuse.
Consider too
Code:
dd if=/dev/urandom of=/dev/sda count=1 bs=446
that wipes out grub stage1 but leaves your partition table intact.
While it might not be necessary to have an entry in your fstab for optical drives, I have this line in mine:
Code:
/dev/cdrom /mnt/cdrom auto noauto,user,ro 0 0
Try adding something like that to yours, and see if that helps out. Also, I don't think you mentioned what DE or file manager you are using to access the optical drive. That information will further help us assist you with the problem.
/dev/cdrom /media/cdrom auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0
this makes it load and point to file /media/cdrom
Quote:
NeddySeagoon
Like I said you really should not use root I will. and your right ok lets help this man see his cdrom. Hexedit is a program only used by root on my systems. Your right do not worry.
I could care less about grub with the same dd comand I put it right back on.
Quote:
# here '/boot/grub/mbr.sda.3345'. You can restore it like this.
# dd if=mbr.sda.3345 of=/dev/sda bs=512 count=1
if you allow your user to run admin programs that is up to you.
Do you have the file /dev/sr0 ?
That will be your CDROM. udev should correctly make the /dev/cdrom symlinks no matter what your CDROM device file is called.
Do you have /dev/cdrom in cyan and what does ls -l /dev/cdrom point to.
If you have changed drivers from the old PATA to the new SCSI cdrom driver, your CD may be renumbered, do your have any devices shown by the
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.