07-25-2016
Well, my ISO is 2.2GB and is based off of 13.2 32-bit. I think I'll try wiping the HD again but only use one partition and one of the default install options.
Push The Outer Linux
@Twitter, @Github, & @Tumblr: TheOuterLinux
or, @RollResearch.com
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
i'm following the, "How to setup and secure Snort, MySQL and Acid on FreeBSD 4.6 Release" off of the snort.org website.
in the documentation it says snort should be installed through the following:
-----
make -DWITH_MYSQL -DWITH_FLEXRESP ; make install
-----
later it says to do the... (13 Replies)
Discussion started by: xyyz
13 Replies
2. SCO
Hi All,
While installing a Service Pack on my Unix Solaris machine, i got the following error:
UX:acomp: ERROR: "space.c", line 16: undefined symbol: CHROOT_SECURITY
UX:acomp: ERROR: "space.c", line 16: non-constant initializer: op "NAME"
UX:idmkunix: ERROR: Compile/link of 'Driver_atup.o... (9 Replies)
Discussion started by: am_yadav
9 Replies
3. Solaris
Hi all,
Previously I had both opensuse 11.3 and Windows XP SP2 on my PC, there was no problem at all.I was able to access all documents in Windows from opensuse.
Now when I wanted to install solaris 10 on the same machine there were 2 problems ...
1. Windows is not accessible from solaris... (3 Replies)
Discussion started by: M.Choudhury
3 Replies
4. HP-UX
I am trying to build a software on HP-UX (HP-UX 11.00). It links against Xerces and Xalan libraries (amongst others).
I am getting the following errors during the final linking phase.
Can somebody help me understand the problem?
I compiled Xerces and Xalan using aCC (
as recommended) while... (1 Reply)
Discussion started by: slash_blog
1 Replies
5. SuSE
Hello,
I have a project that I have compiled on a number of linux systems including CentOS, Ubuntu, and Windows Cygwin. I am trying to build the project under SUSE 12.1. The make file runs allot of the way through, but then throws an error that an included file can't be opened.
This is the... (4 Replies)
Discussion started by: LMHmedchem
4 Replies
6. Red Hat
I am installing RHEL6 on a Cisco UCS blade and the GUI isn't showing up. Curious!!!!! I have installed it on 5 of the other blades and the GUI is there. However, there are many issues that I am having and I am going crazy with this thing. I have issues where the network adapters are not showing... (1 Reply)
Discussion started by: styehimba
1 Replies
7. UNIX for Dummies Questions & Answers
hi guys
right now I have 6 Virtual Machines (VMs) running on Vmware ESXi 5.1 and attached to Storage SAN.
All these run Suse Linux 11 SP1 x64.
All of a sudden 1 of these VMs is running very slow making high CPU usage and I see al wait % kinda high 40-50%. Apparently since I don't own this... (5 Replies)
Discussion started by: karlochacon
5 Replies
8. SuSE
hello All,
good day to you.
could you tell me is there any way I can download SUSE lunux enterprise server trail version ?
I want to install sap application over it.
thanks in advance. (1 Reply)
Discussion started by: Leaner_963
1 Replies
LEARN ABOUT DEBIAN
stg-push
STG-PUSH(1) StGit Manual STG-PUSH(1)
NAME
stg-push - Push one or more patches onto the stack
SYNOPSIS
stg push [options] [<patch1>] [<patch2>] [<patch3>..<patch4>]
DESCRIPTION
Push one or more patches (defaulting to the first unapplied one) onto the stack. The push operation allows patch reordering by commuting
them with the three-way merge algorithm. If there are conflicts while pushing a patch, those conflicts are written to the work tree, and
the command halts. Conflicts raised during the push operation have to be fixed and the git add --update command run (alternatively, you may
undo the conflicting push with stg undo).
The command also notifies when the patch becomes empty (fully merged upstream) or is modified (three-way merged) by the push operation.
OPTIONS
-a, --all
Push all the unapplied patches.
-n NUMBER, --number NUMBER
Push the specified number of patches.
--reverse
Push the patches in reverse order.
--set-tree
Push the patches, but don't perform a merge. Instead, the resulting tree will be identical to the tree that the patch previously
created.
This can be useful when splitting a patch by first popping the patch and creating a new patch with some of the changes. Pushing the
original patch with --set-tree will avoid conflicts and only the remaining changes will be in the patch.
-k, --keep
Keep the local changes.
-m, --merged
Check for patches merged upstream.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-PUSH(1)