On Jan 2,  7:48pm, Sergio Monesi wrote:
> Subject: Re: Some general questions (xdm)
> In message <9701021554.ZM23857@picasso.me> you wrote:
>
> > > Another thing about xdm, when I do a reboot if it is running, the machine
> > > will not reboot, but will either put me into debuging mode, or completely
> > > lock the machine.
> > Odd.
>
> I recently tried to use xdm too, and if I do a 'shutdown' when xdm is running
> the system goes down correctly but the 'reboot countdown' stops at '1' and I
> have to use the reset button.

What kernel? StrongARM?

> > a) Run setdisplay -c 16 (other options to taste) on /dev/vidcvideo0 before
> > starting X. Note that due to a bug in the console the mode reverts to 8 bpp
> > if X ever reinitialises :-(
>
> This is probably related to the same bug: I'd like to run X in 1280x1024
> instead of 1024x768 as the other consoles so I use setdisplay to set this
> resolution before starting xdm. This works OK, I login using xdm but when I
> exit Xarm reinitialises in 1280x1024 (I can see the 'server booting' image)
> but then it crashes and restart once agin in 1024x768. Sometimes it also
> seems to think that the resolution is still 1280x1024 so all the display is
> corrupted. This is the syslog output:
>
> Jan  2 11:47:17 riscbsd /netbsd: Data abort: 'Permission error (page)' status
= 00f address = 00000026 PC = 000529b8
> Jan  2 11:47:18 riscbsd /netbsd: Process = f150f100 pid = 254 comm = Xarm-27
> Jan  2 11:47:18 riscbsd /netbsd: CPSR=60000013 Traceback info
(frame=f2776fb8)
> Jan  2 11:47:18 riscbsd /netbsd: fp->lr=f010144c fp->pc=f011007c
> Jan  2 11:47:18 riscbsd /netbsd: Trapframe PC = 000529b8
> Jan  2 11:47:18 riscbsd /netbsd: Trapframe SPSR = 20000010
> Jan  2 11:47:18 riscbsd /netbsd: Multiple open of/dev/vidcvideo0 by proc 443
> Jan  2 11:47:21 riscbsd /netbsd: qms: setting mode with non empty buffer (20)

Okay, this is a known console bug.

> About the use of setdisplay, why can't I create a setuid root shell script? I
> wanted to change to 1280x1024 from a common user and so I made a shell script
> containing the setdisplay command and made it setuid root but it still report
> 'permission denied' (or whatever). I had to make setdisplay itself setuid
> root and now it does work.

IMPORTANT: SUID SHELL SCRIPT ARE A SECURITY HOLE. This is why you can't have
them. Making setdisplay seuid root probably at worst allows some denial of
service attacks by allowing remote users to crash the display. The current
console code really doesn't allow for good security models.

> Finally, I tried to compile xsysstats but rpc.rstat doesn't seem to work
> anymore (it used to run with the 1.1-release, I think) and in fact also rup
> doesn't work:
>
> Dec 30 15:44:30 riscbsd inetd[78]: /usr/libexec/rpc.rstatd: exit status 0x1
> Dec 30 15:45:01 riscbsd rpc.rstatd[415]: can't get namelist
> Dec 30 15:45:12 riscbsd rpc.rstatd[422]: can't get namelist
> Dec 30 15:50:00 riscbsd inetd[78]: pmap_unset(100001, 1)
> Dec 30 15:50:00 riscbsd inetd[78]: pmap_unset(100001, 2)
> Dec 30 15:50:00 riscbsd inetd[78]: pmap_unset(100001, 3)
> Dec 30 15:50:02 riscbsd rpc.rstatd[444]: can't get namelist
> Dec 30 15:50:02 riscbsd inetd[78]: /usr/libexec/rpc.rstatd: exit status 0x1
>
> Can anybody tell me what's wrong with it?

I suspect you don't have your kernel image in /netbsd. Either that or you don't
have the patch sets installed.

Cheers

Rob