My university in the 1990's used MIT's Project Athena setup with AFS for file sharing, Zephyr instant messaging, etc.
There was a command named "attach" to mount a really long path like /afs/university/department/servers/students/servername/j/jsmith as /university/jsmith
There was also a command named "add" that would source the .environment file within this dir. This was used to set your PATH variable etc so if you wanted to use specific commercial software the .environment would attach the dir and set some variables.
People were explicitly told not to add a user dir as the .environment in that user's dir would get sourced.
So of course I made a script that kept track of what machine I was logged into. If someone added my account the script would run xhost + opening their machine to remote X11 connections and send me a zephyr message saying "I just xhosted you"
If they were in my actual computer lab I would run xmelt or flip their screen and they would freak out. Then I'd go over and laugh and remind them not to add my account.
I will use xv to the day I die.
Great for remotely viewing / editing images (e.g. headless EC2 instances).
Has features I can't even find in a modern image editor.
http://www.trilon.com/xv/
> It's unfortunate that modified copies "may not be distributed without prior consent of the author", killing any possibility of a "neoxv" fork.
Well, just look at what happened to xsnow.
I installed Slackware 15.0 and my config automatically starts xsnow. I wanted to see why it hasn't started, only to discover a configuration window under my xterm, without borders or titlebar.
My next reaction was: removepkg xsnow, fetch xsnow-1.42, xmkmf, make, make install.
You can also try feh (https://feh.finalrewind.org/) feh is an X11 image viewer aimed mostly at console users. And sxiv (https://github.com/muennich/sxiv) Simple X Image Viewer (but this one was archived on github since Nov. 9th, 2022) and now replaced with nsxiv (https://github.com/nsxiv/nsxiv) Neo (or New or Not) Simple (or Small or Suckless) X Image Viewer.
I still use xv to print maps and various screenshots. I take a screenshot then xv filename then right click, print, greyscale, Max, Ok
It changes the colors to greyscale for my non-color laser printer, scales it perfectly to fit the 8.5x11" paper, and prints.
I remember in 1997 during the first Mars Pathfinder rover mission that NASA was basically doing a live screen sharing session from someone's desktop and they used "xv" to load the image. I was 27 but I grew up obsessed with space exploration. Well I still love it, but at the bottom it said "UNREGISTERED COPY" and people on Usenet were talking about how NASA didn't register their copy. I think they did later but I was just so excited to see xv on national television.
Funny. I did register my copy. I sent the author some money and then, as directed, I changed the source code that says "UNREGISTERED COPY" to "REGISTERED." The folks at NASA might have not bothered editing the string.
Sorry, the point of my post was supposed to be "it's a new project and they're probably busy, hence one project conserved." Wasn't trying to disparage you at all.
What's really on the brink of being lost are the commercial X environments that aren't preserved as open source. Things like the brown Motif theme on Ultrix workstations and early B&W OpenLook are effectively gone.
Freshman year in 1993 and my school had a thousand DEC pmax Ultrix workstations. It migrated over mostly to Suns and HP's but I run OpenLook olvwm at my internship but I mainly ran vtwm which my school had compiled for everything. Ultrix / SunOS / Solaris / IRIX / AIX / HP-UX
Uhh, X11 applications work in a Wayland environment. It's no different than how X11 applications work on Quartz, DWM, or any other non-X11 environment.
So it's not like these things are going to break anytime soon...
Which is to say it doesn't work. Not as an accessibility tool anyway. When something which is meant to work all the time only works some of the time, it's broken.
I like using it as a quick diagnostic to figure out if a given window is running natively or under Xwayland. If the eyes follow your mouse when you hover over the window, it’s still using Xwayland, if they don’t move, it’s a native Wayland application.
2) X apps work on Wayland, Quartz, etc. because there are X servers foe those environments, Xwayland is currently the only maintained X server; it too will eventually go away (especially when the toolkit maintainers drop X support altogether).
I don't think anyone expects Xwayland or XQuartz to go away anytime soon. The only way that would happen is if someone pulled a Haiku and reimplemented xlib and other APIs on top of a Wayland-enabled toolkit.
> Xwayland is currently the only maintained X server;
Just googling to check that claim. As a random example: xorg-server in Arch was last updated on 12/19/22. Six days ago.
Wayland proponents are so aggressive like this. You want to deny that anyone is still interested in X. Maybe it won't have dramatic changes. But people will be patching it for years.
Xwayland is built out of the same tree as the main Xorg server. Same for XQuartz. But the infrastructure for the X server running as the graphics host is rotting and not getting much love.
Because not everyone can afford and/or use latest and greatest hardware, Xserver and X software in general will never go away. Even when Wayland is mainstream. There will always be a need for older software. This is my prediction for the future. Just wait and see ^_^
I remember xantfarm, xfishtank, and xmelt / xflip very fondly.
http://www.ibiblio.org/pub/historic-linux/ftp-archives/sunsi...
My university in the 1990's used MIT's Project Athena setup with AFS for file sharing, Zephyr instant messaging, etc.
There was a command named "attach" to mount a really long path like /afs/university/department/servers/students/servername/j/jsmith as /university/jsmith
There was also a command named "add" that would source the .environment file within this dir. This was used to set your PATH variable etc so if you wanted to use specific commercial software the .environment would attach the dir and set some variables.
People were explicitly told not to add a user dir as the .environment in that user's dir would get sourced.
So of course I made a script that kept track of what machine I was logged into. If someone added my account the script would run xhost + opening their machine to remote X11 connections and send me a zephyr message saying "I just xhosted you"
If they were in my actual computer lab I would run xmelt or flip their screen and they would freak out. Then I'd go over and laugh and remind them not to add my account.