similar to: Install via VNC

I am working on the Centos wiki instructions for doing an install via vnc: http://wiki.centos.org/TipsAndTricks/VncHeadlessInstall CD is all burned and ready to go. I then thought about the viewer settings particularly the port number and firewall rules. When I connect vncviewer to a vncserver it uses port(s) 590n where n is the display number. OK, is that what happens when a server connects

My OQO boxes have the AR5413 wifi chipset, so for the first time in quite a while, I again need to run madwifi. So I went looking for the dkms madwifi rpms, but could not find them. They use to be on rpmforge, as I recall. dkms is there. So have I lost some memory cells or have these rpms taken a hike?

With my OQO, I get the following message when I try to suspend: cpufreq: suspend failed to assert current frequency is what timing core thinks it is. I see in /var/log/messages: kernel: acpi-cpufreq: CPU0 - ACPI performance management activated There are a number of apps and such dedicated to 'cpufreq' on the system. I have done a bit of searching and have not figured out what to do

Dear all, On the "TipsAndTricks/VncHeadlessInstall" wiki page, the first sentence under "Download ISO" section should be changed from: The first thing you will need is once if the ISO's from the CentOS mirrors. to: The first thing you will need is one of the ISO's from the CentOS mirrors. Regards, Timothy Lee

I just read the http://wiki.centos.org/TipsAndTricks/VncHeadlessInstall, and it was easy to follow and worked like a charm, I wasn't aware of the anaconda stuff... And a suggestion: could the fact that the netboot iso is just 9 megs big be emphasise... and maybee link to http://wiki.centos.org/HowTos/CreateLocalRepos as a tips to save bandwith net installs? /Mats

(Apologies for the potential duplicate post. My initial post had a smashed subject line. This post only adds the subject and this note.) I would like permission to edit this page. The changes I have in mind are: 1) It is not necessary to burn a CD/DVD to do a "headless" install in cases where the installed system has a monitor, but for some reason cannot support a graphical

I have a test system: Centos 5.2 on an OQO, that has been hanging hard. I have to unplug it and pull the battery so I can then cold start it. This last time all I did was open a terminal window and SU to root, then start the lastest build of SIP Communicator (which uses JRE 1.6.0_10). I was not even making a test phone call at the time. Oh, and the system only runs IPv6, no v4 addressing.

the man page for vncviewer presents the -via gateway option to use ssh through a gateway. I understand if I want a secure vnc connection to server.foo.com I can use the command: vncviewer localhost -via server.foo.com But I have moved my SSHD services from port 22 to port n. So according to the man pages, I need an environment variable of VNC_VIA_CMD and override the default command with:

My OQO has a VIA chipset. From the hwconf: class: VIDEO bus: PCI detached: 0 desc: "VIA Technologies, Inc. CX700M2 UniChrome PRO II Graphics" vendorId: 1106 deviceId: 3157 subVendorId: 1106 subDeviceId: 3157 pciType: 1 pcidom: 0 pcibus: 1 pcidev: 0 pcifn: 0 When I install Centos, I default to the vesa driver, and it operates at the monitor's native 800x480. Of course I

Thanks a lot. 2015-08-19 1:39 GMT+06:00 Akemi Yagi <amyagi at gmail.com>: > On Tue, Aug 18, 2015 at 10:16 AM, Ilyas Arinov <arinov.ilyas at gmail.com> > wrote: > > Username changed to standards. > > > > I have 2 days in week to pedantically rewrite whole content until I can. > > > > Those (first 8-10 weeks): > > > > FrontPage > >

Hi all, the patch "qemu-vnc-wmvi.patch" adds support for the WMVi pseudoencoding in qemu vnc server. If the client implements it, it is supposed to be able to change colour depth when receiving a WMVi message. Since I didn''t know any client that supports it and I wanted to test the implementation before submitting any patch I also modified vncviewer to support WMVi. The

So I took the anaconda cfg, commented out the partition/disk pieces and ran it off my repo server and it almost worked. Little things like not including things I had done on network setup. No first boot.... :) So now I am reading up on building a kickstart cfg http://wiki.centos.org/TipsAndTricks/KickStart http://www.centos.org/docs/5/html/5.2/Installation_Guide/s1-kickstart2-howuse.html

Hello. All these pages translated except Events. It will be done 10-12 hours later, now I cant finish it. We should add Russian wiki link on the English front page. After that I want to start Tips and Tricks translation for every item under the section. For example those pages first: - How to create an installation DVD from the install CDs

I have successfully built an install CD following the instructions at: http://wiki.centos.org/TipsAndTricks/VncHeadlessInstall Now I am trying to do the same with FC10 and I am failing in two ways. I have tried to find a similar howto for even FC9, but have not found the right google magic. The first problem should be small. When I set isolinux.cfg to start with: prompt 1 timeout 0 I

- How to edit the CentOS Wiki <https://wiki.centos.org/HowTos/Wiki/Editing> - How to contribute your RPMs to the CentOS Project <https://wiki.centos.org/HowTos/Packages/ContributeYourRPMs> - How to create public mirrors for CentOS <https://wiki.centos.org/HowTos/CreatePublicMirrors> There are several pages automatically use /ru/ in their links from HowTo

I am going over: ftp://ftp.oqo.com/unsupported/linux/OQOLinux.html This is for the 'older' model 1, I have the model 2. The files are 18 mo old, and relate to kernel 2.6.10. Of course I want to avoid a custom kernel, but please help me understand what is being covered here: "2. Enable crusoe processor in kernel .config CONFIG_MCRUSOE=y" What is the crusoe processor? 3.

I may be getting a couple of these for traveling servers (smaller than a PICO-ITX system!). Info is available for putting Ubuntu on it (see http://en.wikipedia.org/wiki/OQO), but what about Centos? Any help out there?

http://www.realvnc.com/products/enterprise/4.1/ipv6.html IPv6 support in VNC Server E4.1.7/P4.1.2 VNC Server E4.1.7 & P4.1.2 are fully IPv6-aware, but is shipped with IPv6 support disabled by default, for security reasons. IPv6 can be enabled by setting "InTransports=IPv6,IPv4" (the default being IPv4 only), either on the command-line when starting vncserver under Unix Ok.

HI all, i am configuring VNC server in CentOS 5.1. i have enables this two lines in /etc/sysconfig/vncserver file VNCSERVERS="2:vnc" VNCSERVERARGS[2]="-geometry 1024x768 -depth 24" here i have created a user vnc and set the password using vncpasswd cmd. then i started the vncserver # vncserver New 'localhost.localdomain:1 (gopinath)' desktop is

I was looking at vnc.c to see what would be involved in making a reverse VNC connection (vnc server connects to the client), and it looks possible but I also wondered if there was any reason why libvncserver couldn''t be used instead? Both qemu-dm and libvncserver appear to be licensed under GPL although I haven''t checked what version. I''ve never figured out whether