On Fri, 30 Jun 2000,  [EMAIL PROTECTED] wrote about,  system map, swapon:
> I have recently updated my kernel from 2.2.5 to 2.2.16. I had to recompile a few 
>times to
> get things (like sound) working properly. I am running RedHat 6.0, and (what seems 
>to me
> a strange side-effect) it now calls itself 6.2. Anyway, on boot, there are a couple
> of messages that bother me, and I would appreciate any advice anyone can give...:
> 
> localhost swapon: swapon: warning: /dev/hda8 has insecure permissions 0660, 0600 
>suggested
> 
> how does one change the permissions for swap space?

chmod 0600 /dev/hda8

> 
> also..., while I can't find the log for this message, I don't think it will be 
> necessary to quote it verbatim, I get the message to the effect of not finding the 
>correct
> system map, which would explain why whenever I run ppp I get the message that I 
>don't have 
> kernel support for it compiled in, and perhaps might explain why esound is unable to 
>bind
> port 5001 (?). So the other question is, you guessed it, how do I get (lilo?, 
>something else?) 
> to recognize the system map that is associated with my latest kernel recompile?

Redhat creates a symlink at boottime in the /boot directory via one of the
init scripts.
It sounds to me like you have not copied Sytem.map to /boot
I belive you would be well advised to rename it to System.map-'uname -r'
where uname -r is the kernel version and extraversion number.

Then upon the next reboot a symbolic link should be created in /boot
pointing towards the proper System.map.

Possably someone else who uses Redhat can explain how they do it, as i dont
use Redhat all to much theesdays.

As to the sound problem, i cant answer that, 1) i dont use that sound
driver 2) there is not enough info on the problem.

> 
> takcq.
> dns.

-- 
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs

Reply via email to