02-11-2019
To make this clear, UNIX/Linux are not FreeWindowsWithLessBugs(tm). If you look at the ways they differ from Windows and think, "I can use that feature to solve problems," then maybe Linux is for you.
The difference is as much in philosophy as anything. Windows provides the bare minimum of features and expects you to buy upgrades and proprietary programs to make up the difference. Linux has most features available by default, more robustly and with more options, with a less polished interface,
Creating disk images in Windows: Feature removed in 199x when it stopped being DOS, so dish out the moolah for a proprietary implementation.
Creating disk images in UNIX: Disks are literally files, so any command-line utility capable of reading files can deal with disks. Nonetheless there's a variety of tools. It's a bad idea to use them while the partition's being written to, but we can't stop you.
Burning CDROM images in Windows: We added this feature 20 years too late and nobody cares any more.
Burning CDROM images in UNIX: A flagship feature since 1996.
etc.
GUI-wise, Linux/Unix seem to be trying hard to imitate Windows these days. But the GUI is only skin-deep, not deeply integrated.
Last edited by Corona688; 02-11-2019 at 12:06 PM..
7 More Discussions You Might Find Interesting
1. Programming
At time of installation I have to open the resource. and i have to insert a string serial number in the exe.
please provide me code to edit the exe (in solaris) to insert a serial number which can be used by exe at run time. (6 Replies)
Discussion started by: ssahu
6 Replies
2. Programming
I'm very new to c++ & unix programming. I have a c++ exe that runs on the unix box, but I am trying to write a c++ windows app that executes the program on unix. I have tried execv(), but it doesn't seem to work or I'm doing something wrong. Would really like to see examples if at all possible. ... (5 Replies)
Discussion started by: ch5082
5 Replies
3. UNIX for Advanced & Expert Users
Hi,
I have a requirement to run multiple instances of an .exe file present in windows server from unix machine. The number of threads to be invoked is determined dynamically based on a variable field. We will be passing some parameters to windows .exe file for each instance.
I am a unix... (2 Replies)
Discussion started by: sam99
2 Replies
4. Linux
What are the differences, advantages, and disadvantages? (1 Reply)
Discussion started by: Advice Pro
1 Replies
5. Programming
I am writing java application on windows.
There are more than 100 threads run within java.exe.
I want to know what threads run within process java.exe so that I can find out if there are abnormal java threads. (4 Replies)
Discussion started by: mika
4 Replies
6. Shell Programming and Scripting
Hi,
I am triggering a windows exe file using the below command.
ssh user@remoteserver command.exe -option1:xx /option2:yy
This command is working fine from windows command prompt. When I am triggering the same command from ssh I get the error message cant load
Any ideas to deal with... (2 Replies)
Discussion started by: ahmedwaseem2000
2 Replies
7. Windows & DOS: Issues & Discussions
I ssh from Windows to Linux server and execute a few commands. I have ssh keys setup between them and works fine.
The commands get executed on the Linux server however I wish to stay on the Linux terminal that was opened by putty.exe. However, the terminal simply does the job and closes.
... (10 Replies)
Discussion started by: mohtashims
10 Replies
LEARN ABOUT DEBIAN
wincommand
WinCommand(1x) AfterStep X11 window manager WinCommand(1x)
NAME
WinCommand - AfterStep module for choosing and manipulating windows based on patterns
CONFIGURATION OPTIONS
DESCRIPTION
WinCommand is a command line tool which allows you to select windows based on their name and to then manipulate them in various ways.
Actions currently supported are: "center", "center jump", "iconify", "jump", "kill", "move", "resize" and "sendtodesk".
DEFAULTS
The default pattern is "", meaning all windows will be selected.
All other default-values depend on the action you would like WinCommand to take. If more than one action is specified, default-values are
set depending on the last action specified.
ACTIONS
center
Place matching windows into the center of the screen.
center jump:
Places first window that matches into the center of the screen and jumps to it.
iconify:
Iconifies matching windows.
jump:
Jumps to the first window which matches.
kill:
Kills all matching windows.
move:
Moves all matching windows to x/y. x and y are specified using the -x and -y flags.
resize:
Resize all matching windows. The two parameters width and height are specified using the -width and -height flags.
send_to_desk:
Send all matching windows to desk specified with the -new_desk flag.
OPTIONS
-all
Operate on all windows which match the given pattern. This is set by default unless the action is either "jump" or "center jump".
-alldesks
Windows on all desks will be taken into account. This is set by default if action is either "jump" or "center jump".
-desk
Windows on the whole desk will be taken into account.
-x/-y
These are required when issuing the move-command.
-width/-height
These are required whenever you want to resize windows.
Examples WinCommand -pattern term iconify
This command will iconify all terminals. Since the specified pattern is a regular expression, something like this also works:
WinCommand -pattern "(term)|(moz)" iconify
This will iconify all terminals and mozilla-browser windows.
WinCommand -pattern xmm jump
will jump to your xmms. In this situation, it's far more advisable to use GWCommand though.
It is probably not a good idea to delete windows while windows are being arranged.
3rd Berkeley Distribution AfterStep v.2.2.11 WinCommand(1x)