Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!ee.und.ac.za!shrike.und.ac.za!shrike.und.ac.za!maltby From: maltby@shrike.und.ac.za (Gavin Maltby) Newsgroups: comp.os.386bsd.bugs Subject: Progs with priveleged mem access reboot NetBSD 0.9? Date: 22 Oct 1993 06:56:45 GMT Organization: University of Natal (Durban), South Africa Lines: 32 Message-ID: <2a807e$m81@shrike.und.ac.za> NNTP-Posting-Host: shrike.und.ac.za X-Newsreader: TIN [version 1.2 PL0] Hi, Since upgrading to NetBSD 0.9, and later doing a complete reinstall, there've been a couple of recurring problems. The first was recompiling the kernel---dependencies on Makefile weren't resolved correctly. But that could be hacked by taking away those dependencies and being careful to do nothing between the config, make depend, and make. This is not a problem that everyone has had, but appeared after the upgrade and some time after the re-install (the first kernel recompile after the reinstall was trouble free) Now we've been getting 'random' reboots whenprograms with priveleged access to memory are executed. These include w and ps and various others! I had the setup, eg for w, something like this: -rw-r----- root kmem /dev/mem, /dev/kmem, /dev/drum -r-xr-sr-x bin kmem /bin/w which grants those running w read access to memory. I had a feeling that I once set some of these permission from setuid root to setgid kmem. So I tried making things like w run setuid root, to no avail. No messages are logged when the system reboots---no panics, nothing. Would appreciate any pointers. Thanks in advance Gavin