I have a Raspberry Pi with Raspbian Wheezy installed. I'm using TightVNC server on the Raspberry Pi and RealVNC on my MAC to connect to it. However, when I log in with RealVNC, I'm given a new session, with my own desktop, applications etc.
I want to login to the SAME session as the already running Raspberry, so I can refresh the browser etc (We're using this to display a company desktop application).
How can I achieve this?
I don't believe this is supported by TightVNC (which I think only does "Virtual" sessions). But I may be wrong...
The answer here: https://serverfault.com/questions/27044/how-to-vnc-into-an-existing-x-session suggests a few alternatives (at least ones which work on Fedora based Unix distros)
I know RealVNC can do it (it's known as "User Mode" or "Service Mode" as opposed to "Virtual Desktop" mode), but depending on your users, you may have to license it, or the free mode may suffice.
Related
I have a short Question related to Raspberrys but in applies in general to Linux systems.
Can I prevent someone from reading out the SD-Card of the Raspberry?
What do I mean: I can simply disable all login-posibilitys to prevent anyone from logging into the system. But if you unplug the SD-Card and mount it in another linux system, you still have full access to all files.
Is there any possibility besides glueing the SD-Card to the Pi?
I would be already greatfull for some keywords to google with ;)
some Linux distributions (e.g. Ubuntu) support full disk encryption, which you can activate during setup.
Since you have an Raspberry PI, I assume that you have already installed raspbian. Therefore you can search for raspbian home folder encryption for example.
You can also set access rights so only the Pi user can open them.
I want to run Visual Studio Code Remote Development using SSH to my Raspberry Pi 3 Model B+ running Raspbian GNU/Linux 9 (stretch).
I have tried to follow the "Getting started" instructions. I run the command Remote-SSH: Connect to Host..., but I get the message Can't connect to admin#pihole.local: unreachable or not Linux x86_64 (Linux armv7l )
As far as I know, Raspbian is 32 bit. So, does this mean that what I want to achieve is impossible?
I can connect to the Raspberry Pi using ssh on the command line without problems (not password based).
I'm running VS Code insiders on macOS Mojave 10.14.4.
Update 2: As of the 10th of February, x86_64, ARMv7l (AArch32) and ARMv8l (AArch64) are the supported Linux architectures for Remote SSH. It it appears that a glibc based Linux distribution is needed to meet certain prerequisites/dependencies. There is also experimental support for Windows 10/Windows Server 2016/2019 in the Insiders builds. More information can be found on the prerequisites information page.
Update: As of the 12th of June, approximately one month after my answer to this, support was added for the Raspberry Pi 3. There is no support for other ARM architectures yet, and this does not work with the Raspberry Pi Zero W yet, but I'm not sure about the Raspberry Pi 1 or 2. One point to note at present is that you need to setup public key authentication so you have passwordless login, otherwise you'll need to enter your Raspberry Pi's password multiple times, and it will ultimately fail. Also, as mentioned in a comment, if you've tried the 'stable' Remote Development extensions and found out they didn't work... you need to make sure you remove them from both VSCode AND your Raspberry Pi... else it really won't work. This is also mentioned in the Github issue.
Because of how the Remote SSH function actually work, when you connect to your SSH host, the Remote SSH extension provisions the so-called VS Code Server to that host, so the VS Code Server has to be able to run in your remote environment. Consequently, at present, each architecture may need different implementations or tweaks, before it will be considered 'supported'. At the time of writing, there are no armv7l builds, but this recently changed. We're still early days for this useful looking functionality... but things are changing quickly... There is no Windows or MacOS SSH host support at present... but this may not be the case in another months time.
There is an issue open on GitHub on this topic, so it may be worth keeping an eye on it or subscribing to it to see if/when support is added.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
Spent a couple hours this evening on the #openbsd irc channel troubleshooting a display issue. Couldn't figure this one out though we had fun trying!
Specs:
USB Stick and Openbsd 6.2 Image
Known good,
Openbsd image installed successfully from this USB, to a virtual env on a separate device, using these instructions
Desktop computer
Motherboard, 64bit Intel processor
On-board graphics only
Currently running Ubuntu 16.04.03 Server
BIOS (legacy enabled) set to boot USB first
Monitor
40" Toshiba LCD TV Model 40UX600U
Symptoms
Start computer on Ubuntu server, displays just fine, no issues
Boot to Openbsd USB stick, bios screen runs, self check passes then monitor displays "Unsupported Video Signal". This is not an Openbsd message, but rather from the monitor itself.
Done so far
Cleanly formatted USB (under supervision)
Installed from USB to virtual env on separate device, no issues, loads Openbsd just fine.
Boot computer to Ubuntu, display works perfect
Boot computer to Openbsd USB, display shows error message above.
Unplug and replug VGA cable
Power off, power on monitor
Suspicions
- Pg. 88 of the Toshiba monitor manual shows a table of Acceptable Signal Formats for PC IN. My hunch is the graphics driver is incompatible with this monitor.
Questions
Is there anything I can do to make this monitor work with a new Openbsd 6.2 install?
How can I check Openbsd monitor compatibility before embarking next time?
Ubuntu has KMS support for the nVidia graphics card but OpenBSD only has support for the old UMS driver. The OpenBSD kernel (probably, I'm not sure) is using 640x480 as resolution and the Linux kernel is using the highest resolution supported by your monitor.
You have two options to "fix" the problem. Install OpenBSD on another computer or with a different monitor (you can also use a laptop with a USB<->HDD adapter), when the installer ask if you want graphics support (or something like that, I don't remember), reply yes. Finish the installation and reboot. Then move the HDD to the original computer and power on the machine. You will see the same message but at some point the system will run xenodm (a graphical launcher for X11 sessions, like xdm), then the monitor will work fine. Unfortunately, you can't see the console messages.
Don't change xorg.conf, your problem is not only related to the monitor. Another option (quite better, imho) is to buy a cheap used ATI graphics card and just install OpenBSD. The ATI graphics cards are fully supported (except the newest ones) and have KMS support. You will only see the message during two or three seconds and after of that, you will see the console. Maybe you will need run the installer on a different computer or with a different monitor, but everything will work fine after of that.
Anyway, OpenBSD uses only a standard mode for the basic console. It doesn't make weird unsupported things. So, probably your monitor has some kind of problem with the lowest VGA resolution/frequency. The problem is that the OpenBSD kernel can't change to a higher resolution during the boot process because it doesn't support the nVidia cards at the kernel level. It uses a userland driver for the nVidia cards, like the Linux/BSD/Unix traditionally used to use.
If you have an old (like 10 years or so) Linux LiveCD/installer, try to run it on your computer. You will see the same problem.
I'm considering getting a collection of Dell PowerEdge servers. Dell documentation is pretty poor (no surprise there) and I have trouble figuring out if I can go with iDRAC Basic or if I need iDRAC Express or Enterprise.
My need is to install Ubuntu Server (minimal install with SSH is enough). After install all I need is SSH and possibly a remote "reset" button. I can install the OS before taking the system to server room so I don't really need remote OS deployment tools. However, the server does not have a graphics adapter. Is it possible to install Ubuntu with just iDRAC Basic or do I need additional hardware?
#iwork4dell Remote OS deployment implies Virtual Console (like VNC) and Virtual Media (using a remote ISO like a local DVD). These are Enterprise license features. OS deployment tools are are the driver pack that is stored in flash on the server and made available during OS installation to support new hardware on older OSes.
The iDRAC is an integrated VGA adapter so all the Power Edge servers do have a video adapter in them unless you disable it in BIOS. If your willing to attach a keyboard and monitor to the server basic is all you need. You can also upgrade the iDRAC with a license key after purchase.
See http://en.community.dell.com/techcenter/extras/m/white_papers/20440743
and http://i.dell.com/sites/doccontent/shared-content/data-sheets/en/Documents/idrac-spec-sheet.pdf
IDRAC is possible, just you can open gui of idrac and then launch on the online server. You can add the iso file on virtual server.
When I start up my Linux VM (Xubuntu 14.04 aka Trusty) on VMWare Player (v6.0.3), my Windows host (Windows 7 pro x64) makes an IRQL_NOT_LESS_OR_EQUAL blue screen of death.
The fact is that BSOD occurs juste after selecting an entry in my guest's GRUB screen.
How to avoid that?
The problem occurs because somewhere in VMWare drivers, an Interruption Request is made to satisfy guest shared hardware (USB, NAT, ...). The workaround is to uncheck "Connect at power on" checkbox on every device listed in "Virtual Machine Settings > Hardware" menu. You will then be able to boot.
Once the guest is started you can individually connect the pieces of hardware you want.
With my HP laptop, if I add the CD/DVD drive to my Ubuntu VM then this happens every time. So like the doctor says, "Does it hurt when you do that? then don't do it." ;) It'd be nice if VMware Player didn't bomb out for something straightforward like that, but such is life. You can always turn off that hardware before you run the VM.
My general experience as well is that it's better to add/remove hardware to the VM with the VM off. Remember that these are things which you usually wouldn't be able to change with a PC running, so it's not unreasonable for driver authors to assume that what they have on startup will not change.
BTW, don't forget that you'll need to manually delete all the lock files in the VM directory as well. VMware Player does a less-than-perfect job of cleaning up after crashes.