XLiveCD: Cygwin and X For Windows On A Live CD
mallumax writes "OSnews is running a story
on XliveCD which runs an X server (from X.org) from the CD using Cygwin. Also included are awk, sed, perl, vim, bash, grep, other text utilities, and most importantly an OpenSSH client. XliveCD is being developed by University Technology Services of Indiana University. Now you can carry Cygwin with you! I have been looking for something like this for a long time. Torrent link."
I was going to ask what the point was, given the number of Live CDs such as Knoppix, etc. Then I actually RTFA and they suggest it's for use in public access Windows boxes, where a reboot may not be available but running stuff from the CD is.
I still suspect VNC on a USB key or CD might be easier, and the difference between forwarding X and using VNC isn't that much in my experience.
- Take a CD to work and use X on any machine with a CD drive
- Use this as a framework to add more applications like dev tools, auditing tools or desktop apps (probably forking the project, but interesting)
- Use it to prove to the ill tempered that *Nix is not all bad and quite usable
- Find a way to port it to Flash drives and such
- Another valid use of BitTorrent
:D (the download of this iso that is)
Remember that this is an early version. The best uses are to come probably.US Democracy:The best person for the job (among These pre-selected choices...)
The reality is a little less exciting - just a program you can run from a CD. (yawn).
I'm sorry if I appear to be to be knit-picking but...
You have the client-server relationship wrong, a common mistake when talking about X windows.
The application running on Unix is the client to the X-server running, in this case, off a Windows machines.
Client examples: xterm, konqueror, Kmail, Evolution running on *nix
Server: X.org running on _Windows_ via Cygwin
--Aaron Greenberg
> What is the point?3 438 of it's ease of use.
The point is easy interoperability between *nix and Windows OSs. See my post at OSNews.com http://www.osnews.com/comment.php?news_id=9163#31
You can also find more info from from a paper published for the SIGUCCS of the ACM titled: Easy access to remote graphical UNIX applications for windows users Listed below is the publicly available abstract:
ABSTRACT
A barrier deters Windows users from evaluating graphical scientific software that runs only on remote UNIX systems. Graphical UNIX applications are based on X Windows. To make use of X applications, Windows users must install an X server, install communications software for connecting to remote UNIX systems, and configure their systems to display graphics from remote systems. This barrier can be removed by making use of an X server and communications software that run live from CD-ROM. This poster presents such a CD-ROM known as XLiveCD.
XLiveCD appears to users as an application that provides a command-prompt that allows them to log in to remote computers. Windows XP/NT/ 2000 users insert the CD into a drive and click twice in response to a wizard. A terminal window appears on the screen and provides a command prompt. From the command prompt users run the secure shell (ssh) to connect to a remote computer and launch applications. X graphics windows are forwarded automatically.
XLiveCD is based entirely on open source software and is available free for download. It is a Cygwin environment (from Red Hat, Inc.), including the X.org X server and openssh installed and modified to be run from CD-ROM. The home page is http://xlivecd.indiana.edu/.
I really, really wish the X guys hadn't used this terminology. But they did, so we need to keep it straight.
Just think of it this way:
A file server provides files to its clients. A print server provides printing to its clients. An X Window server provides graphical windows to its clients.
Thus, when you run any X application, it is a client to the X Window server. It asks the server for a window to display stuff in.
So, if you buy an expensive rack-mount server machine, and you hook up a thin client that lets you use a GUI, that thin client has an X server on it, and the X server talks to X clients that run on the server.
The neat thing is that in the other universe (the one where Spock has a beard), they call "clients" "servers" and "servers" "clients", but the X guys still did it backwards there so this confusion still applies.
Hope this helps.
steveha
lf(1): it's like ls(1) but sorts filenames by extension, tersely
I use cygwin in a few different places. One our file server is running NT, put cygwin on there and it like a real server ;)
Also, Since I'm booted into XP most of the time, cygwin fills the nitch of having sshd to copy files back too, perl for running some reports, X for those server admin applications, even vi when I need to do some text work. (Ya, I said vi)
I was running Linux with VMware for XP, but the resources wasted, and no VPN software that worked with our nortel vpn connection, decided to just use cygwin, perfect choice.
Couple things, You can have real RXVT term's without X they run stand alone, and you can customize with normal black backgrounds, right side bars, etc. It also supports Rootless for seemless looking with windows. (Like OSX.) Comes with links, super quick to read heavy text sites, no popup banners, and color/frame support. I use it to read slashdot, and if someone looks over my shoulder, they just see text.
KDE under cygwin runs ok, few bugs, but since I just needed a manager, I went with windowmaker (Or rootless). Save the resources. (Old habits..) Konsole is nice, with tab's, I just with there was a tabbed RXVT then life would be truly sweet. (No tabbed putty yet, come on!)
Cygwin is the first software I install on a new windows system, just makes the whole thing usable. I recommend it to anyone doing work. I dont know how it compares to ActivePerl or others, since I've been using cygwin's for years, havn't had a need to switch.
BTW, a native port of nethack would be nice in the default install... And since I'm making requests, (hint to any Cygwin developers) how about real native selectable for download, icewm, screen and irssi(with ssl). Maybe VNC also. So I can remotely run X software off a Windows box over an ssh tunnel. (Production networks, security, makes an admin work harder..)
-
Halliburton, they get no bid contracts, they hire columbian mercs to watch the oil pipelines, and have more armored vechicals than the US Army in IRAQ. Don't join the Army, Join Halliburton!
I see the point for portables computers with WiFi or GPRS Internet access, which can be a pain (or simply impossible) to setup under Linux. Imagine that you can borrow a laptop from time to time at work to go on the road, and cannot afford to take hours to install cygwin, but with this solution instead you can in seconds connect to your remote Unix server.
Google passes Turing test : see my journal
The point is that you can sit at any windows machine, which may not necessarily be your own, and have a decent set of utilities to use.
I personaly work on many machines on any given day. The majority of which I do not own. I'm not "allowed" by my customer to go and just start throwing applications onto their system willy-nilly.
With this, I can work on any machine, using a shell I know, (bash), have a functional Xserver available, and access to a bajillion other GNU utilities without ever installing a single app.
Ever needed to tail a file in windows? It's there. Yes, there is a tail app for windows, and it's free. The point here is that this doesn't need to be installed. Grep? same thing.
Just boot to a LiveCD distro, you say? But I need to see what's happening on this Virii / Spyware ridden hunk o' junk while it's running windows.
Could I build my own suite? Yeah... but why would I? This has what I need.
Kudos and my thanks to the Cygwin team.
US Democracy:The best person for the job (among These pre-selected choices...)
Just downloaded it. This CD is great! The "insert and go" character of the CD makes it very useful.
.ssh directory should not be placed on the desktop! :)
Only one comment: the
.sig: No such file or directory
The terminology makes sense, but is it sensible?
When you run the server on your thin client, and the clients all run on your rackmount server, and the newbies are all confused, and we need to write posts explaining why the seemingly backwards terminology is in fact correct... in some sense, it's sensible, but if you take a poll of a bunch of newbies, the consensus would be that it's confusing. (I'll stop now before someone beats me senseless.)
If some terminology makes arguable sense but confuses everyone but hard-core computer geeks, is it really the best terminology? I say no.
steveha
lf(1): it's like ls(1) but sorts filenames by extension, tersely
I currently work for an organization that has very strict (and government controlled) policies in place for the installation and use of software packages. It's called bureaucracy. To install PuTTy on my XP workstation I must submit a ticket via our Management System interface. That ticket must then be assigned to my manager for an approval for the request of the software. Once my manager approves (could be a week or more) the ticket is then assigned to a senior manager for approval. Once that senior manager approves the installation of the software the ticket is assigned to an auditor to evaluate the financial impact on the company, the auditor must then write up a RFP (Request for Purchase) and submit approval to the ticket. The ticket is then assigned to the final approver (who is usually the CIO or another officer just below) who evaluates the ticket, verifies the approvals, verifies the finanical impact, approves the ticket, then assigns it to the Desktop Admin. The Desktop Admin then assigns the ticket to a Support Technician to be implemented. (ie. installed) (Oh, and I'm a member of IT and a Support Analyst, by the way.)
At any point in that process, if there is a denial. The whole thing must be reviewed, reentered, and start all over again.
This, I drop it in the CD-ROM, install nothing, run the X apps I need to run on the UNIX gear I monitor. Remove the CD, reboot, and no impact to the installed system that requires red tape.
Does that help?
"Genius may shine aloof and alone, like a star, but goodness is social, and it takes two men and God to make a Brother."
DSL, Damn Small Linux embedded will let you run Linux in a window with X Server, SSH, VNC, Mozilla Firefox, Dillo, a texteditor, vi.....you name it. It all fits nicely on a 128 MB USB key. Oh and it's based on everyone's favorite live CD, Knoppix.
Gorkman
I made just such a CD for myself nearly 3 years ago so that I could have cygwin (particularly SSH), emacs, CVS, Java, and Mozilla with me wherever I happened to be, such as in the classroom. The fun part was getting the autorun feature to properly set up the paths. I also made use of the TMP variable as the directory where I could write to the local disk when needed. I suppose what I really should do is establish a RAM disk.
I have recently even been considering migrating to a DVD so I can install the full cygwin installation along with Firefox and plugins; music and video players and rippers; some USB device drivers for my camera, MP3 players, voice recorder, and smart media scanner; and if I can figure it out also the synchronization software for my phone and PDA so I am not tied to a single machine!
I suppose you could add games, too., as if I had time for such things. Hm... the CD emulator with the CD images... I could perhaps include a few of my favorite classics!
@HbFyo0$k8 tH!$
Yes, but use X to do WHAT exactly? Click on pretty buttons over and over again? If I can't have cygwin on disk, able to manipulate files, save scripts, etc, what's the use, really? The few Unix apps that are worth the trouble of running in an X11 window on a Windows box, already have native ports.
The debugger that came with our version HP/UX server did not have a console interface; it was GUI only. That means we had to have X to log in an do any debugging work on our apps.
I could have used something like this.