Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Which UNIX OS is going to give me the most versatility? I Want Total Control Post 302974317 by metacogitans on Friday 27th of May 2016 10:54:31 PM
Old 05-27-2016
Which UNIX OS is going to give me the most versatility? I Want Total Control

I am going to be switching to something Unix for my primary OS, and I really need to know right now, which one is going to be able handle getting tweaked up entirely, and be able to stay fluent doing all the stuff I plan on doing using Unix?

I need to be able to have grass roots control sometimes, and get as close to hardware and their instructions as practical . Then the rest of the time, I also would like it to be fluent on its own, for efficiency and convenience, and wouldn't mind it packaged with the essentials, like having codecs; also handling basic drivers on its own would be a big plus.

That being said, I still want to be able to get at anything/everything (all the nooks and crannies) without it being an obstacle to get at, but it's also nice to have the OS accommodating me while doing that as much as practical.

Just a few examples of the things I'm envisioning doing (some demanding, some convenient, and some stuff just insanity and recklessness, and antics that you would maybe say aren't possible if they didn't sound like they could work):

- Put a second OS on the machine, completely gut it, like, straight up filleting the stuff I don't want out of the hard-drive and leaving only the bare bones, restricting it from taking up CPU usage, and letting it run in the background as just a command line.

- Rigging up ports on my motherboard to hook up devices that aren't meant for computers, or in some cases never intended to be hooked up to anything period.

- Keeping a surrogate PC solely as a first line 'dummy' so disruptive garbage getting dumped off by the internet for no reason gets sent there instead, that way I can look at the endless piles of crap and headaches and get to just stare at in awe without having it already being on my computer first. Then periodically do fresh installs on the dummy, and make it so the installer sets it back up for being a surrogate again automatically.

- Logging anything and everything that ever takes place on my computer, as one big unmanageable volume of raw data stored in the form of random characters and symbols that can't even be translated back into anything .

- Logging instructions from my actual processor by mining it out of my RAM, yielding mounds of gibberish to be read through by me later for no reason.

 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix System Total Replication

Is there any way to totally replicate a unix system from one hardisk to another? And be able to swap the hardisk and restart the system without any error? TQ (4 Replies)
Discussion started by: nuraman
4 Replies

2. HP-UX

How should I know the total RAM available on UNIX

Hi How Should I know the Total RAM available on HP-UX box? (7 Replies)
Discussion started by: skull123
7 Replies

3. UNIX for Dummies Questions & Answers

grep running total/ final total across multiple files

Ok, another fun hiccup in my UNIX learning curve. I am trying to count the number of occurrences of an IP address across multiple files named example.hits. I can extract the number of occurrences from the files individually but when you use grep -c with multiple files you get the output similar to... (5 Replies)
Discussion started by: MrAd
5 Replies

4. UNIX for Advanced & Expert Users

can some one give me some link about process and job control commands

can some one give me some link about process and job control commands (2 Replies)
Discussion started by: alokjyotibal
2 Replies

5. Shell Programming and Scripting

Calculate total space, total used space and total free space in filesystem names matching keyword

Good afternoon! Im new at scripting and Im trying to write a script to calculate total space, total used space and total free space in filesystem names matching a keyword (in this one we will use keyword virginia). Please dont be mean or harsh, like I said Im new and trying my best. Scripting... (4 Replies)
Discussion started by: bigben1220
4 Replies

6. Programming

Please give me some advise to program for unix/linux using c/c++?

I have a good foundation of c++.I want to learn to program for linux/unix,can you give me some advises,for example classic books ,which operating system is used better(freebsd,solaris,federal linux.etc),and which aspects uses mostly in job.Can you give me clear direction for working or learning. (1 Reply)
Discussion started by: fengshuiyue
1 Replies

7. UNIX for Dummies Questions & Answers

For SFTP connection - How to give password in UNIX Script (ksh)

Hi, I am not able to give the password in Unix script for SFTP connection. When I am trying to manully SFTP command for accessing the server , it asking for pwd and I could provide the pwd but I am not getting how to provide the pwd inside the Unix script. sftp -v user@xyz.com. ... (4 Replies)
Discussion started by: Vineeta Nigam
4 Replies
Server(3pm)						User Contributed Perl Documentation					       Server(3pm)

NAME
Net::SMTP::Server - A native Perl SMTP Server implementation for Perl. SYNOPSIS
use Carp; use Net::SMTP::Server; use Net::SMTP::Server::Client; use Net::SMTP::Server::Relay; $server = new Net::SMTP::Server('localhost', 25) || croak("Unable to handle client connection: $! "); while($conn = $server->accept()) { # We can perform all sorts of checks here for spammers, ACLs, # and other useful stuff to check on a connection. # Handle the client's connection and spawn off a new parser. # This can/should be a fork() or a new thread, # but for simplicity... my $client = new Net::SMTP::Server::Client($conn) || croak("Unable to handle client connection: $! "); # Process the client. This command will block until # the connecting client completes the SMTP transaction. $client->process || next; # In this simple server, we're just relaying everything # to a server. If a real server were implemented, you # could save email to a file, or perform various other # actions on it here. my $relay = new Net::SMTP::Server::Relay($client->{FROM}, $client->{TO}, $client->{MSG}); } DESCRIPTION
The Net::SMTP::Server module implements an RFC 821 compliant SMTP server, completely in Perl. It's extremely extensible, so adding in things like spam filtering, or more advanced routing and handling features can be easily handled. An additional module, Net::SMTP::Server::Relay has also been implemented as an example of just one application of this extensibility. See the pod for more details on that module. This extension has been tested on both Unix and Win32 platforms. Creating a new server is as trivial as: $server = new Net::SMTP::Server($host, $port); This creates a new SMTP::Server. Both $host and $port are optional, and default to the current hostname and the standard SMTP port(25). However, if you run on a multi-homed machine, you may want to explicitly specify which interface to bind to. The server loop should look something like this: while($conn = $server->accept()) { my $client = new Net::SMTP::Server::Client($conn) || croak("Unable to handle client connection: $! "); $client->process; } The server will continue to accept connections forever. Once we have a connection, we create a new Net::SMTP::Server::Client. This is a new client connection that will now be handled. The reason why processing doesn't begin here is to allow for any extensibility or hooks a user may want to add in after we've accepted the client connection, but before we give the initial welcome message to the client. Once we're ready to process an SMTP session, we call $client->process. This may HANG while the SMTP transaction takes place, as the client and server are communicating back and forth (and if there's a lot of data to transmit, well...). Once $client->process returns, various fields have been filled in. Those are: $client->{TO} -- This is an array containing the intended recipients for this message. There may be multiple recipients for any given message. $client->{FROM} -- This is the sender of the given message. $client->{MSG} -- The actual message data. :) The SMTP::Server module performs no other processing for the user. It's meant to give you the building blocks of an extensible SMTP server implementation. For example, using the MIME modules, you can easily process $client->{MSG} to handle MIME attachments, etc. Or you could implement ACLs to control who can connect to the server, or what actions are taken. Finally, a suggested use that the author himself uses, is as an SMTP relay. There are lots of times I need access to an SMTP server just to send a message, but don't have access to one for whatever reason (firewalls, permissions, etc). You can run your own SMTP server whether under Unix or Win32 environments, and simply point your favorite mail client to it when sending messages. See the Net::SMTP::Server::Relay modules for details on that use. AUTHOR AND COPYRIGHT Net::SMTP::Server / SMTP::Server is Copyright(C) 1999, MacGyver (aka Habeeb J. Dihu) <macgyver@tos.net>. ALL RIGHTS RESERVED. You may distribute this package under the terms of either the GNU General Public License or the Artistic License, as specified in the Perl README file. SEE ALSO
Net::SMTP::Server::Client, Net::SMTP::Server::Relay perl v5.10.1 1999-12-28 Server(3pm)
All times are GMT -4. The time now is 10:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy