FedoraThis forum is for the discussion of the Fedora Project.
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.
Someone is currently polluting my hardware by preventing me from reading my cd with my external device on my netbook : the problem occured this morning.
Which system are you running there? Could you give error messages so we can analyze it. How do you know it is a attack to your machine? We need more information about the problem otherwise there is no way to guess what is going on.
*If this is related to the members other thread (http://www.linuxquestions.org/questi...ok-4175454305/ ASUS netbook, Fedora 18) then he should at least be able to show 'dmesg' and /var/log/messages output right after attaching the external device and after trying to read a CD.
Eject the disk and then unplug the device.
Open a terminal window and run 'sudo tail -f ~/.xession-errors* /var/log/messages' (w/o quotes).
Now attach the device and check messages scrolling by for anything related.
Now insert a CDROM or DVD and check messages scrolling by for anything related.
Now (unless the CDROM or DVD gets mounted automagically) mount the disk and check messages scrolling by for anything related.
By now you should have a list of lines to post.
[root@maman ~]# sudo tail -f ~/.xession-errors*/var/log/messages
tail: impossible d'ouvrir «*/root/.xession-errors*/var/log/messages*» en lecture: Aucun fichier ou dossier de ce type
[root@maman ~]#
when the cd device is plugged:
[root@maman ~]# sudo tail -f ~/.xession-error*/var/log/messages
tail: impossible d'ouvrir «*/root/.xession-error*/var/log/messages*» en lecture: Aucun fichier ou dossier de ce type
[root@maman ~]#
Sacre! 0) you should not need to run anything as root, 1) "*/root/.xession-errors*/var/log/messages*" isn't one string but two locations, 3) adding glob chars w/o knowing what you're doing can be a recipe for disaster. So log out and log in as unprivileged user and try again. If ~/.xsession-errors* then doesn't exist it's no problem, just 'sudo tail -f /var/log/messages'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.