Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Corné Beerse" <cbeerse@lycos.nl>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: Helge Deller <deller@gmx.de>,
	Ulrich Deiters <ukd@xenon.pc.Uni-Koeln.DE>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] B1000/C3000
Date: Fri, 16 Apr 2004 17:38:47 +0200	[thread overview]
Message-ID: <407FFE07.50000@lycos.nl> (raw)
In-Reply-To: <20040416144733.GI24370@baldric.uwo.ca>

Carlos O'Donell wrote:

> On Fri, Apr 16, 2004 at 01:00:01PM +0200, Corn? Beerse wrote:
> 
>>Be noted that the Xvnc fron DebianWoody crashes on my HP-D370...
> 
> 
> Does the viewer from sid crash you box?

Since my D370 has no graphical display, the viewer will not work, i use the 
viewer on my desktop.

> Any idea why it crashes?

Not jet, not time to investigate, so many other things to do...

The idea to use Xvnc for the X11-server for display :0 just came since I did 
just that on a RedHatLinux server (hp DL380 ;) There it runs without a problem.

I think (well that will be my first step) is that the RedHatLinuxIntel box runs 
in runlevel 5, the graphical runlevel. The D370 is in its text-console runelvel. 
I think I need to force it in its graphical runlevel and convince the Xserver is 
properly configured, even without the hardware. For that I have to dive into 
Debian and its X11 configuration which (I have already seen) differs from 
RedHat, SuSE and HP-UX.

For what its worth, Xvnc can (for a start) just replace the other X11-server 
binary. Once that works (`vncviewer palinux:0` gives a login box), the call to 
Xvnc can be extended with some configuration like colordepth, resolution and 
security, see `Xvnc --help` for a list of options and the `vncserver` script for 
some other details.


CBee

  reply	other threads:[~2004-04-16 15:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14  9:44 [parisc-linux] B1000/C3000 Ulrich Deiters
2004-04-14 10:31 ` Joel Soete
2004-04-14 19:02 ` Helge Deller
2004-04-16 11:00   ` Corné Beerse
2004-04-16 14:47     ` Carlos O'Donell
2004-04-16 15:38       ` Corné Beerse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-14 20:46 Deiters
2004-04-14 20:51 ` John David Anglin
2004-04-14 20:57   ` M. Grabert
     [not found]     ` <20040414232833.GQ31873@tausq.org>
2004-04-15  2:04       ` M. Grabert
2004-04-15  2:48         ` Randolph Chung
2004-04-15 15:48         ` Grant Grundler
2004-04-15 19:42           ` M. Grabert
2004-04-15 23:35             ` Grant Grundler
2004-04-16  2:26               ` M. Grabert
2004-04-16  6:01                 ` Grant Grundler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=407FFE07.50000@lycos.nl \
    --to=cbeerse@lycos.nl \
    --cc=carlos@baldric.uwo.ca \
    --cc=deller@gmx.de \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=ukd@xenon.pc.Uni-Koeln.DE \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox