Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.hardware > #1566

Re: suggestions for my web server

Show all headers | View raw

On 12/1/2012 6:02 AM, Pol's Team on Technlogy wrote:
> On Saturday, December 1, 2012 2:01:19 PM UTC+1, Henrik Carlqvist wrote:
>
>>
>> Why do you want SSD for a home web mserver? Those are rather expensive and
>> might not live as long as a spinning drive.
>
> i thought solid state 'disks' would use less power than rotating disks, but i am not sure.
>
>>
>> It would be easier to suggest hardware if you told us some more about
>> your plans. All we know now is that you are building a server that will>
>> provide data using the http protocol. We do not know you the data is
>
> Right, some clarification are in order.
> To tell the true, my idea is to set up a vnc server, to access my kde session through the internet.
> I am not an expert, so i would also appreciate a few hours work from some people, if not too expensive.,
>
>
> Thank you
>
> Paolo
The devil is in the details.
I'm no expert, but I'll describe some of my newbie experiences based on
my interpretation of your need.

If you just want your desktop to show up on a remote display device, you 
don't
need different hardware.  It's software that runs on your existing machine.

But therein lies the rub...which software.
Linux is a multi-user OS and stuff is defined for that.
Most ordinary newbies, like you and me, use it as a single
user system and expect it to behave like other single user
systems.  Well, it don't.

Depending on which version of which operating system running which desktop
manager, you may or may not have software installed which may or may
not be running by default.

Some distros call it desktop sharing.  Some call it VNC.  Some don't
give you a clue.

And if you go searching the running processes for "vnc", you may see
nothing, even tho it's running.  Linux distributions seem to be seriously
infected with "LetsRenameItJustCauseWeCan" disease.

Then, there's the whole issue of which desktop.
A common class of vnc server software lets you open a new session.
That won't let you see your currently running local desktop.

x0vncserver is one that remotes the current desktop session.
That works for me.
But I had several issues with it.
I had to write a script to start it at login.
I can't access it by computer hostname, but the numeric IP address works.
It requires a password file, but no way to enter the password into the file.
Google found the solution.  You use the vnc password file generation 
mechanism
from ordinary vnc then point x0vncserver at that password file from
the command line that starts it.  In my case, the location of the password
file was not accessible by my user credentials, so I had to copy
it somewhere my script could read it.

You need to forward ports in your router to the correct machine.
If you have DHCP assigned internal ip addresses, that can be a problem.
For remote access, your external IP address can change too.
And the client on the other end also needs ports forwarded thru his 
router.  This can be an issue if your remote access point is a wifi
hot spot.

Teamviewer gets around that, but I've never tried it with a linux 
machine.  Might be worth a shot.

Of course, you have to set it up to accept your connection automagically.
Doesn't help much if your computer sits there asking for
you to accept the incoming connection manually.

It's hard to debug. You really need someone on the other end of the
web and a voice connection while you do it.  You can't just access
your external IP address from the same machine.  The router doesn't
know where to send the packets.  You really need a buddy to help.

Then you need a vnc viewer on the remote machine.  I like tightvnc
on a windows machine.  All VNC versions and flavors are fully
compatible...except when they aren't.  I've been tripped up by that
more than once.

Help from a guru in a newsgroup with your distro in the name will
probably get you a better answer.

As for SSD, for newbies it's the wrong choice.
Yes, it's easy to come up with a situation where it's better.
But, for most of us newbies, we just don't have that situation
or the improvement gets lost in the noise.

Are we having fun yet?

Back to comp.os.linux.hardware | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

suggestions for my web server "Pol's Team on Technlogy" <xtekhne@gmail.com> - 2012-12-01 01:54 -0800
  Re: suggestions for my web server Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2012-12-01 13:01 +0000
    Re: suggestions for my web server "Pol's Team on Technlogy" <xtekhne@gmail.com> - 2012-12-01 06:02 -0800
      Re: suggestions for my web server mike <ham789@netzero.net> - 2012-12-01 12:30 -0800
      Re: suggestions for my web server Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2012-12-01 20:39 +0000

csiph-web