I've got an aix-box somewhere on the network and a PC on my desk. Nothing fancy so far.
The PC is made dual-boot:
- windowsXP with putty & winSCP
or
- slackware 13 with xfce4 installed.
The aix-box runs DB2 v8.2 and I've installed db2top to monitor the database.
db2top is a character based app (like top) and can display a lot of usefull information in a nice way.
So I try to figure out how I can present this info on my screen
1) linux character based (tty1, tty2, etc): Just ssh to aix and start you app. Does not work because aix is not aquinted with "TERM=linux". So you overrule this by typing "export TERM=dtterm" and all is good: nice colors and nice line-draws.
When you start GNU-screen first and then ssh to aix, you font is suddenly not able anymore to display lines. Strange...
2) linux grahical: on your xfce desktop you start Terminal (the standard xfce4 term app) and ssh to aix.
Now you do not get your colors (TERM=xterm) so you try TERM=dtterm. Now you do not get your lines drawn (same as GNU-screen mentioned earlier)
The next option is "TERM=aixterm" That looks better:
Colors? Yes!
Lines? Yes!
Perfect? No! The lines are not aligned.... A screen-row with a line starting on a position > 1 is aligned right.
Windows+putty give the same results as xfce-terminal: not perfect.
I thought that installing linux on my desktop would give me a perfect user-interface to my aix-boxes.
Was I too optimistic?
Anyone has experience or study with Text User Interface and Curses::UI using Perl?
- What is the criteria to decide which method is better for a console based UI?
- Which DTL (dialog tag language) is supported by these?
The background is that I want to write a wrapper over some UNIX tools... (0 Replies)
I want to print only the lines that meet the criteria : "worde:" and "wordo;"
I got this far:
sed -n '/\(*\)\1e:\1o;/p;'
But it doesn't quite work.
Can someone please perfect it and tell me exactly how its a fixed version/what was wrong with mine?
Thanks heaps, (1 Reply)
Hi,
I have written a shell script that does the job of downloading a build file and upgrading a application on my test linux system.
This shell is a interactive script where the user needs to enter certain info like the remote system on which the upgrade has to be performed and the build number... (2 Replies)
Hi all
I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface?
If you have any ideas, please tell me then. Thank you (2 Replies)
I have to create a user interface in which user can easily update ,delete or insert a new record which is pointing to a file in AIX Server?
Using awk,sed ican update ,modify the file.
how to create a link to userlike GUI(without using Tomcat,IIS) (3 Replies)
BOOTCTL(1) bootctl BOOTCTL(1)NAME
bootctl - Control the firmware and boot manager settings
SYNOPSIS
bootctl [OPTIONS...] status
bootctl [OPTIONS...] list
bootctl [OPTIONS...] update
bootctl [OPTIONS...] install
bootctl [OPTIONS...] remove
DESCRIPTION
bootctl checks, updates, installs or removes the boot loader from the current system.
bootctl status checks and prints the currently installed versions of the boot loader binaries and all current EFI boot variables.
bootctl list displays all configured boot loader entries.
bootctl update updates all installed versions of systemd-boot, if the current version is newer than the version installed in the EFI system
partition. This also includes the EFI default/fallback loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is
created if there is no current entry. The created entry will be added to the end of the boot order list.
bootctl install installs systemd-boot into the EFI system partition. A copy of systemd-boot will be stored as the EFI default/fallback
loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is created and added to the top of the boot order list.
bootctl remove removes all installed versions of systemd-boot from the EFI system partition, and removes systemd-boot from the EFI boot
variables.
If no command is passed, status is implied.
OPTIONS
The following options are understood:
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
--path=
Path to the EFI System Partition (ESP). If not specified, /efi, /boot, and /boot/efi are checked in turn. It is recommended to mount
the ESP to /boot, if possible.
-p, --print-path
This option modifies the behaviour of status. Just print the path to the EFI System Partition (ESP) to standard output and exit.
--no-variables
Do not touch the EFI boot variables.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
SEE ALSO
Boot loader specification[1] systemd boot loader interface[2]
NOTES
1. Boot loader specification
https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec
2. systemd boot loader interface
https://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface
systemd 237 BOOTCTL(1)