05-24-2011
Several have pointed out that we seem to be ignoring the matter of cost. In fact, TCO is one of our main motivations.
We have been a strictly Linux shop. Over the years, we have gathered the impression from colleagues using commercial Unixen that we were spending much more time on maintenance and recovery than they were.
Since workstation use has fallen dramatically over the past decade, you can find some really good deals on second-hand IA64/POWER workstations. As for licenses, Solaris is free for noncommercial use, and HP-UX and AIX licenses are tied to the machine.
8 More Discussions You Might Find Interesting
1. Programming
I'm kinda fed up with all the theoretical side of the programming. now i'd love to participate in some project dealing with C network programming under Unix. My question is: is there any online programs or projects where i can really participate? Any other suggestions how to build up practical... (1 Reply)
Discussion started by: solvman
1 Replies
2. UNIX for Advanced & Expert Users
Hi everybody,
I'm kinda fed up with all the theoritical part of programming. I wonder if there is any online project or something where i can participate to practice my skills? Any other suggestions how to build up practical side of Unix C programming?
Thank you all. (1 Reply)
Discussion started by: solvman
1 Replies
3. UNIX for Dummies Questions & Answers
Is Solaris still very hardware dependent? As in it is used mostly on SUN workstations and servers?
What about IBM's AIX? Does it only work on IBM machines?
Which is more popular and are there performance or usage differences? (1 Reply)
Discussion started by: CapsuleCorpJX
1 Replies
4. Solaris
hello
has anyone built a script that compares 2 Solaris servers? CPU, memory, swap, memory variables in /etc/system, Solaris version
Could you please advise on how to make such a comparaison?
thanks (9 Replies)
Discussion started by: melanie_pfefer
9 Replies
5. AIX
I have been in IT for around 7 years now and have benefited greatly from Open Source as well as free commercial offerings like Vmware Server that allow me to setup virtual environments and get some hands on time with different OS's and software.
I am starting a new job in a few weeks which has... (5 Replies)
Discussion started by: supercrazy1
5 Replies
6. AIX
Hello,
I have a directory which suddenly got filled up 100% from 70% ; (this is an oracle directory which has application and database in it ORACLE EBS)
I do make cold backups, last month when I made cold backup of the directory /oratec the tar zip file was 31GB and this month when i made the... (5 Replies)
Discussion started by: filosophizer
5 Replies
7. Solaris
I'd like to share some experiences and what I found for NIS migration from Solaris 8 NIS to Linux platform.
I'm not an expert for both platforms, it's just when I tested both systems and found something really tricky. That might takes a lot of time for you to find the root cause. So, I think I can... (11 Replies)
Discussion started by: bestard
11 Replies
8. UNIX for Beginners Questions & Answers
Good day to all.
I'm relatively new in using the Sun Solaris OS. I would like to request your expertise in helping to solve a problem that I have at work. Not sure if this has been asked before but I have tried searching through the internet to no avail.
Basically I have 2 sun solaris... (8 Replies)
Discussion started by: Fossil_84
8 Replies
lc(Mono 2.6) lc(Mono 2.6)
NAME
lc - Mono License Compiler
SYNOPSIS
lc -c filename -t targetassembly [-i reference...] [-v] [-o outputpath] [-nologo]
DESCRIPTION
lc tool is a license compiler for Mono. It's used to convert a licenses.licx file to a resource that can be embedded into an executable.
When using commercial components for .NET they often require a license resource at runtime to make sure the developer was licensed to use
this control. The most common way of making sure the component was properly licensed is by using license resources. At compile time the
developer uses the lc tool to convert a licenses.licx file to a programname.exe.licenses file and embed that as a managed resource during
compilation.
RUNTIME OPTIONS
The following options are available:
--complist=filename, -c filename
This option is used to specify the input file, the licenses.licx file to create a license reesource for. This option is required.
The license compiler will read each line in this file and try to load the types specified on that line.
--target=assemblyname, -t targetassembly
full assembly name with file extension for the target assembly. The license compiler uses this as a key when compiling the licenses.
It has to match the assembly the resource will be embedded in. This option is required.
--load=reference, -i reference
Assembly reference to load before trying to compile a license. This option is needed for assemblies where the references are not in
the gac. Compilers should pass all references to the license compiler.
--verbose,, -v
Gives more verbose output about the license compiling process.
--help, -h
Displays usage instructions.
--outdir=path, -o path
Target path file the licenses resource. By default the license compiler emits the resource in the current directory. The filename
will always match the target assembly passed to --target with .licenses added.
--nologo
Do not emit the "Mono License Compiler" logo on stdout while compilng.
LICENSE FILES
The format for the license files (licenses.licx) is the following:
# comment
namespace.type, assemblyname
namespace.type, full-assemblyname
All lines starting with a # are ignored. the first form requires that the assembly was loaded through the --load,-i option but does not
require the full assembly name, only the first part.
The second form requires the full assembly name including locale, version and publickeytoken.
MAILING LISTS
Mailing lists are listed at the http://www.mono-project.com/Mailing_Lists
WEB SITE
http://www.mono-project.com
SEE ALSO
mono(1), mcs(1)
lc(Mono 2.6)