[nflug] Question about a process accessing my cdrom

[JJ Neff]

You know I didn't even notice I was running 2.4 until I looked right here.  I
rebooted and must have still had 2.4 set as the default.

I'll relook tonight and see if I accidentally removed the 2.6 kernel.  I was
running 2.6 compiled with gcc4 and that's when I ran into all the trouble with
the VMWare installer failing.  I got that to work and I did not test VMware
after rebooting.  That would explain why I had to get sound kernel mods and
redo so much stuff.  Hmm guess I should pay more attention to what kernel I'm
running :-)

However I was running 2.6 when I had the error.  I'll reboot and try to get
back to the 2.6 I had running.

JJN

PS I have read and heard many things about Ubuntu, but a reinstall is not in my
immediate future.  Heck maybe when I buy a new PC (parts ) in the next 3-5
years maybe....

--- Cyber Source <peter at thecybersource.com> wrote:

> 2.4??!! Might be time for an upgrade there John. You being a Debian guy, 
> you would probably love Ubuntu. Jesse could give you a heads up on that 
> distro, he's been using it and he fell in love.
> 
> JJ Neff wrote:
> 
> >2.4.27-2-686 Yes Debian etch
> >
> >Linux version 2.4.27-2-686 (horms at tabatha.lab.ultramonkey.org) (gcc version
> >3.3.6 (Debian 1:3.3.6-8)) #1 Tue Aug 16 16:31:22 JST 2005
> >
> >
> >--- Cyber Source <peter at thecybersource.com> wrote:
> >
> >  
> >
> >>What kernel are you using? And your using Debian right?
> >>
> >>JJ Neff wrote:
> >>
> >>    
> >>
> >>>/dev/hdc        /media/cdrom0   iso9660 ro,user,noauto,users,exec  0      
> 0
> >>>#/dev/hdc       /media/cdrom0   auto   
> >>>umask=0,user,codepage=850,iocharset=iso8859-1,users,noauto,ro,exec      0 
>  
> >>>      
> >>>
> >>  
> >>    
> >>
> >>>0
> >>>/dev/hdd        /media/cdrom1   iso9660 ro,user,noauto,users,exec  0      
> 0
> >>>#/dev/hdd       /media/cdrom1   auto   
> >>>umask=0,user,codepage=850,iocharset=iso8859-1,users,noauto,ro,exec      0 
>  
> >>>      
> >>>
> >>  
> >>    
> >>
> >>>0
> >>>/dev/fd0        /media/floppy0  auto    rw,user,users,noauto,exec  0      
> 0
> >>>
> >>>
> >>>
> >>>The commented lines are those that were in during setup - the non-comment
> >>>      
> >>>
> >>are
> >>    
> >>
> >>>those I put in myself.  Yes I have no-auto in there.  Please let me know
> if
> >>>anything looks crazy...
> >>>
> >>>JJN
> >>>--- Cyber Source <peter at thecybersource.com> wrote:
> >>>
> >>> 
> >>>
> >>>      
> >>>
> >>>>That would make perfect sense if you don't have the noauto option.
> >>>>
> >>>>JJ Neff wrote:
> >>>>
> >>>>   
> >>>>
> >>>>        
> >>>>
> >>>>>I will have to check that out tonight when I am back at PC, I did have
> to
> >>>>>reboot for an unrelated event this AM.  (Needed to boot into newest
> kernel
> >>>>>     
> >>>>>
> >>>>>          
> >>>>>
> >>>>and
> >>>>   
> >>>>
> >>>>        
> >>>>
> >>>>>update Nvidia kernel mods) Error stopped upon reboot -- one thing I
> >>>>>          
> >>>>>
> >>noticed
> >>    
> >>
> >>>>>     
> >>>>>
> >>>>>          
> >>>>>
> >>>>was
> >>>>   
> >>>>
> >>>>        
> >>>>
> >>>>>that the cdrom:open failed was on every console whether I logged in or
> >>>>>          
> >>>>>
> >>not! 
> >>    
> >>
> >>>>>     
> >>>>>
> >>>>>JJN
> >>>>>
> >>>>>--- Cyber Source <peter at thecybersource.com> wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>     
> >>>>>
> >>>>>          
> >>>>>
> >>>>>>just an offshoot but do you have the "noauto" option in your fstab?
> >>>>>>
> >>>>>>JJ Neff wrote:
> >>>>>>
> >>>>>>  
> >>>>>>
> >>>>>>       
> >>>>>>
> >>>>>>            
> >>>>>>
> >>>>>>>I know I asked this before but I can't seem to find any of my previosu
> >>>>>>>postings.
> >>>>>>>
> >>>>>>>My dvdburner is /dev/hdc and it seems that when I use it (not sure if
> >>>>>>>         
> >>>>>>>
> >>>>>>>              
> >>>>>>>
> >>>>using
> >>>>   
> >>>>
> >>>>        
> >>>>
> >>>>>>>    
> >>>>>>>
> >>>>>>>         
> >>>>>>>
> >>>>>>>              
> >>>>>>>
> >>>>>>it
> >>>>>>  
> >>>>>>
> >>>>>>       
> >>>>>>
> >>>>>>            
> >>>>>>
> >>>>>>>to burn or mounting it to read data is the culprit) it decided to keep
> >>>>>>>    
> >>>>>>>
> >>>>>>>         
> >>>>>>>
> >>>>>>>              
> >>>>>>>
> >>>>>>getting
> >>>>>>  
> >>>>>>
> >>>>>>       
> >>>>>>
> >>>>>>            
> >>>>>>
> >>>>>>>accessed.  The drive works in all ways in my apps, but when I open it
> or
> >>>>>>>    
> >>>>>>>
> >>>>>>>         
> >>>>>>>
> >>>>>>>              
> >>>>>>>
> >>>>>>type
> >>>>>>  
> >>>>>>
> >>>>>>       
> >>>>>>
> >>>>>>            
> >>>>>>
> >>>>>>>"eject cdrom" the tray opens and immediately slides closed.  I have to
> >>>>>>>              
> >>>>>>>
> >>be
> >>    
> >>
> >>>>>>>    
> >>>>>>>
> >>>>>>>         
> >>>>>>>
> >>>>>>>              
> >>>>>>>
> >>>>>>quick
> >>>>>>  
> >>>>>>
> >>>>>>       
> 
=== message truncated ===



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com
_______________________________________________
nflug mailing list
nflug at nflug.org
http://www.nflug.org/mailman/listinfo/nflug