06-25-2012
HELP for Newbie: Unable to run GUI installer (Ubuntu client connected to SLES server)
Hello All,
I'm using my Ubuntu 10.04 client connected via SSH to a SuSE Linux server (SuSE Linux Enterprise Server 11 (x86_64) version 11 patchlevel=1).
I'm trying to run an install of WebSphere Portal but can't seem to be able to run the GUI installer.
Running xclock as root returns this error:
Error: Can't open display:
Running xhost returns this:
xhost: unable to open display ""
As far as my very limited knowledge of Linux goes, I don't have to export display while connecting from an Ubuntu client (never had to do that connecting to AIX and some others). So I think it's something on the server side that needs to be configured or run... Your help would be very appreciated!
Thanks in advance!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello all,
1) I want to have a GUI application that will call Unix shell scripts,
2) that GUI application should be able to reside on windows ( if possible) and then call Unix shell script either directly or through a server residing on unix.
That is for example.
If a is windows gui (... (1 Reply)
Discussion started by: hchivukula
1 Replies
2. Virtualization and Cloud Computing
Hi
I have downloaded vmware server 1.0.10 and ubuntu 9.10. Installed
vmware server on my windows xp and created the disk space for Ubuntu.
Now when i am running the virtual machine using the above downloaded
iso image, I get the installation window. I selected 'Install Ubuntu'
option and... (2 Replies)
Discussion started by: kushal154
2 Replies
3. UNIX for Dummies Questions & Answers
I'm trying to run these commands (keylset,keylget) but i keep getting a error message "invalid command name "keylset"". I've tried running it on both ubuntu's terminal and also Evolane Tcl Engine. Any idea what could be the problem? (1 Reply)
Discussion started by: abe171
1 Replies
4. Shell Programming and Scripting
Hey guys,
I just can't seem to find any hints on this topic (or maybe I just don't find the correct search terms to use :rolleyes: ).
My company developed an application which requires harsh configuration to run it on a server. So I wrote a LOT of shell scripts which take care of the... (2 Replies)
Discussion started by: fatfingerjoe
2 Replies
5. AIX
Hey
I'm getting the below error when trying to launch the GUI installer.
I contacted the application owner and they asked me to remove JAVA_HOME env variable, I removed it but still get this error.
As the error message said, tried with -console and it didnt work too. nothing happened, it... (3 Replies)
Discussion started by: rocker_me2002
3 Replies
6. Red Hat
Hi,
I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server.
On the NFS Server, in /etc/dfs/, I added following line to dfstab file.
share -F nfs -o rw /var/share
& then ran the following
svcadm -v enable -r... (3 Replies)
Discussion started by: SunilB2011
3 Replies
7. Shell Programming and Scripting
Dear all,
I am using solaris 10 OS.
I configured NIS server and i also configured NIS client server but when i use the command ypinit -s sunserv1 in NIS client it is showing me the below error.
Enumerates maps from sunserv1. please check that it is running. (2 Replies)
Discussion started by: bhargav90
2 Replies
8. SuSE
I had sles 11 sp2 installed on my system some days back and it was running fine.
Today after I restarted my system the gui is not coming up and system starts in command terminal.
sax2 command returns error:
sax: gui is missing, starting command line interface
sax: no x-server... (4 Replies)
Discussion started by: rupeshkp728
4 Replies
9. IP Networking
I'm trying to setup a small home network environment as a pet project. These are physical machines nothing virtual. Any help or ideas is greatly appreciated.
I can ping between both machines and I have Samba established and can read/write different shares. When I try to SSH from Windows 8.1... (10 Replies)
Discussion started by: lombardi4851
10 Replies
10. Ubuntu
Hi;
I had Windows Server 2003 and performed a fresh Ubuntu Server 15 installation.
After installation, Ubuntu server not booting
I guess there is boot problem conflicting with my old Windows Server.
This is my pastebin:
http://paste.ubuntu.com/13851828/
Any help to start my new... (1 Reply)
Discussion started by: gc_sw
1 Replies
build(1) General Commands Manual build(1)
NAME
build - build SuSE Linux RPMs in a chroot environment
SYNOPSIS
build [--clean|--no-init] [--rpms path1:path2:...] [--arch arch1:arch2:...] [--root buildroot] [specfile|srcrpm]
build --help
build --verify
DESCRIPTION
build is a tool to build SuSE Linux RPMs in a safe and clean way. build will install a minimal SuSE Linux as build system into some direc-
tory and will chroot to this system to compile the package. This way you don't risk to corrupt your working system (due to a broken spec
file for example), even if the package does not use BuildRoot.
build searches the spec file for a BuildRequires: line; if such a line is found, all the specified rpms are installed. Otherwise a selec-
tion of default packages are used. Note that build doesn't automatically resolve missing dependencies, so the specified rpms have to be
sufficient for the build.
If a spec file is specified on the command line, build will use this file and all other files in the directory for building the package. If
a srcrpm is specified, build automatically unpacks it for the build. If neither is given, build will use all the specfiles in the current
directory.
OPTIONS
--clean
remove the build system and reinitialize it from scratch.
--no-init
skip the build system initialization and start with build immediately.
--list-state
list rpms that would be used to create a fresh build root. Does not create the build root or perform a build.
--rpms path1:path2:path3...
Where build can find the SuSE Linux RPMs needed to create the build system. This option overrides the BUILD_RPMS environment vari-
able.
--arch arch1:arch2:arch3...
What architectures to select from the RPMs. build automatically sets this to a sensible value for your host if you don't specify
this option.
--root buildroot
Specifies where the build system is set up. Overrides the BUILD_ROOT enviroment variable.
--useusedforbuild
Tell build not to do dependency expansion, but to extract the list of packages to install from "# usedforbuild" lines or, if none
are found, from all "BuildRequires" lines. This option is useful if you want to re-build a package from a srcrpm with exactly the
same packages used for the srcrpm build.
--norootforbuild
--help Print a short help text.
--verify
verify the files in an existing build system.
.spec FILE OPTIONS
The build command interprets some special control comments in the specfile:
# norootforbuild
# needsrootforbuild
build uses either user root or user abuild in the build system to do the build. For non-SUSE distros as well as since SUSE 10.2,
the default build user is abuild. For 10.2 and before, the default build user is root. These two flags in the spec file allow to
deviate from the defaults and force-set the build user to abuild and root (for # norootforbuild and # needsrootforbuild respec-
tively.
# needsbinariesforbuild
provide the binary rpms that have been used to set up the build root in /.build.binaries within the build root.
ENVIRONMENT
BUILD_ROOT
The directory where build should install the chrooted build system. "/var/tmp/build-root" is used by default.
BUILD_RPMS
Where build can find the SuSE Linux RPMs. build needs them to create the build system. "/media/dvd/suse" is the default value
which will do the trick if you have the SuSE Linux DVD mounted.
BUILD_RPM_BUILD_STAGE
The rpm build stage (-ba, -bb, ...). This is just passed through to rpm, check the rpm manpage for a complete list and descrip-
tions. "-ba" is the default. You can use this to add more options to RPM.
SEE ALSO
rpm(1),
Maximum RPM:
http://www.rpm.org/max-rpm/
cross distribution packaging:
http://en.opensuse.org/Build_Service/cross_distribution_package_how_to
SUSE packaging standards and guidelines:
http://en.opensuse.org/Packaging
(c) 1997-2008 SuSE Linux AG Nuernberg, Germany build(1)