Sponsored Content
Full Discussion: Linux GUI
Special Forums UNIX Desktop Questions & Answers Linux GUI Post 63327 by locustfurnace on Thursday 24th of February 2005 06:53:26 AM
Old 02-24-2005
What is "Linux 9" exactly? Slackware 9? RedHat Linux 9.0, SuSE 9?
Did you update any packages prior to your problem?
Have you tried startx to load your desktop?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

GUI for Redhat Linux

I just installed Redhat Linux 8.0 and I do not know how to get to my GUI Desktop. Right now I'm just in the shell please help. (2 Replies)
Discussion started by: savagebeast
2 Replies

2. UNIX Desktop Questions & Answers

Need a gui for linux.

I want one that won't run too slugish on a slower system (p 200Mhz for example). I know kde is out, anybody think gnome will run ok (I got 128 megs ram on it btw...don't ask :))? (5 Replies)
Discussion started by: pudad
5 Replies

3. Red Hat

Linux not logging into GUI

hi, Can someone help in trouble shooting why my RedHat linux 8.0 in not logging into the KDE screen. Thanks (1 Reply)
Discussion started by: kayode
1 Replies

4. SuSE

GUI problem with Suse Linux

hi Guys,, Am very new to Linux OS.. This is my first experience with Linux. I have installed linux suse 10 in my laptop.it was working fine.. suddenly after 3 days,(i was changing some options of the already installed linux) when i login, i am getting only command interface and GUI is not... (2 Replies)
Discussion started by: mac4rfree
2 Replies

5. Linux

Which Linux distribution has a GUI like MS Windows ?

Hello experts, I have windows on my PC and now I want to continue java programming in Linux. Can anyone please suggest which distribution I can use which will give me better environment for programming and also good interface like windows... (4 Replies)
Discussion started by: gentleDean
4 Replies

6. Linux

CD Burning in Linux, GUI Software

Hi.. I just brought a CD writer. It has nero for windows bundled with it. I found nero very easy to use as well as usefull.. I then see that wht we have in linux.. I found that in my Redhat 9 i have two CD writers software but both are no where nare nero... So is there any GUI based cd... (5 Replies)
Discussion started by: billcrosby
5 Replies

7. UNIX for Dummies Questions & Answers

Small linux no gui

I want to execute from a grub a very small linux that only has commands, so at startup it executes this shell script I wrote and after that the user has an option to go back to the grub. I've heard of busybox but that doesn't seem to be helpful? Can anyone recommend a non gui distro, that can... (1 Reply)
Discussion started by: jcnewton13
1 Replies

8. Programming

creating an application with gui in linux

hi, so I am familiar with visual studio for windows, I was wondering if there's that kind of IDE for linux that I can use to make an application... thanks! (2 Replies)
Discussion started by: h0ujun
2 Replies

9. Red Hat

RedHat Linux GUI Issues

hi all i have installed Windows 7 first. then i installed linux on dual partations... i am booting both of them through dual boot... but when i start linux its only working well with CUI, when i used commands like startx or changed the initd to 5 then its loading the GUI interface of RedHat... (9 Replies)
Discussion started by: Nikhil Dethe
9 Replies

10. SuSE

Linux SLES Gui Not coming up

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
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)
All times are GMT -4. The time now is 10:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy