Personal computing discussed
Moderators: renee, SecretSquirrel, notfred
flip-mode wrote:I don't know about PuTTY, but you might want to look into GNU screen. It's a very useful terminal multiplexer with a surprisingly flexible feature set. You'd just fire up screen from within a PuTTY session and then you can create multiple virtual terminals within the screen session. You can also detach from a running screen session, terminate your PuTTY connection and then later re-connect and re-attach to your running screen session with all of your stuff the way you left it (editors still running, etc.).So, does PuTTY support multiple terminals in the same session, or do I have to fire up multiple sessions of PuTTY to use multiple terminals?
flip-mode wrote:Running "shutdown -h now" is one way (you need to run with root privileges, so run using sudo or su or logged in as root).Is there a way to shut down the computer through the PuTTY terminal? Usually I just hit the power button on the machine. I don't actually know the Unix command to shut down the computer.
flip-mode wrote:POSIX is a set of standards, one of which refers to the shell/command environment, but a lot of times people are operating out of that safe portable subset. In Linux, many of the common POSIX-required tools are the GNU implementations and have extra (and typically quite useful)features that you may be using, and a lot of the system administrative commands are distro or Linux-specific. I guess it's a matter of taste, but I'd be specific unless you have a reason otherwise and know you're using a POSIX-approved subset of commands.Also, is is proper to refer to generic things as Unix, or is Posix a more accurate term? For example, should I say Unix command or Posix command? Or should I always be system specific and say FreeBSD command or Linux command?
bitvector wrote:It sounds like that is something I have to install on the FreeBSD machine? I haven't gotten as far as installing anything yet - maybe that should be one of my next pursuits.flip-mode wrote:I don't know about PuTTY, but you might want to look into GNU screen. It's a very useful terminal multiplexer with a surprisingly flexible feature set. You'd just fire up screen from within a PuTTY session and then you can create multiple virtual terminals within the screen session. You can also detach from a running screen session, terminate your PuTTY connection and then later re-connect and re-attach to your running screen session with all of your stuff the way you left it (editors still running, etc.).So, does PuTTY support multiple terminals in the same session, or do I have to fire up multiple sessions of PuTTY to use multiple terminals?
bitvector wrote:Sweet, thanks.Running "shutdown -h now" is one way (you need to run with root privileges, so run using sudo or su or logged in as root).
flip-mode wrote:Good enough.I guess it's a matter of taste, but I'd be specific.
flip-mode wrote:It sounds like that is something I have to install on the FreeBSD machine? I haven't gotten as far as installing anything yet - maybe that should be one of my next pursuits.
bitvector wrote:Running "shutdown -h now" is one way (you need to run with root privileges, so run using sudo or su or logged in as root).
just brew it! wrote:I'd be all about that, but I have yet to figure out how to get X working on the local machine. X seems to be completely unconfigured.If you want, you should even be able to get a full remote desktop going.
flip-mode wrote:The main goal of all of this is to get familiar with the system and then implement a BSD firewall at work. Any advice / guidance towards that end is hugely appreciated.
axeman wrote:Cygwin always seemed like a lot of work to me... The Xming X server for Windows is pretty easy to setup: http://sourceforge.net/projects/xming
bitvector wrote:If I were implementing a firewall for something important, I'd do (at least) two boxes with pfsync and CARP. You don't want a dead firewall to kill your connectivity.
flip-mode wrote:all of which are obviously wrong. someone throw me a rope, please.
axeman wrote:lollers, I suspect you are right. But first I have to get myself some permission to use su. Apparently, in Linux, anyone can su, and this is due to Richard Stallman's love for the masses (I just found out). But in BSD and other *nixes that don't use the GNU su, users must be a member of the wheel group. Right now I'm in the process of figuring out how to make myself a member, but if someone feels like posting instructions here, I certainly won't mind!I believe you would need to edit /etc/ssh/sshd_config to allow root logon through SSH. However, you should be able to ssh as a regular user, then use su to elevate privileges.
flip-mode wrote:Edit: By the way, I love the easy editor! Has anyone else used it? It's just so friggin simple. In time I am sure I'll have to learn Vi or Emacs or whatev, but for now I'm loving using ee!
Forge wrote:I'm a NANO person. It reminds me of edit in the good ol DOS days. Never bothered learning vi or emacs. An emac is an Apple product, and vi is just 6. Nano at least means small, and 'minimal' as a cognate isn't a horrible stretch.
bthylafh wrote:I agree. I don't even like logging on as root myself, because, to begin with, every nix guide advises against it.For security reasons, I would suggest not editing your sshd configuration to allow direct root logins. Two reasons: attackers will definitely try that username, and picking the correct username is half of what they need to get in, and root, if it's compromised, has god privileges over the system.
flip-mode wrote:axeman wrote:lollers, I suspect you are right. But first I have to get myself some permission to use su. Apparently, in Linux, anyone can su, and this is due to Richard Stallman's love for the masses (I just found out). But in BSD and other *nixes that don't use the GNU su, users must be a member of the wheel group. Right now I'm in the process of figuring out how to make myself a member, but if someone feels like posting instructions here, I certainly won't mind!I believe you would need to edit /etc/ssh/sshd_config to allow root logon through SSH. However, you should be able to ssh as a regular user, then use su to elevate privileges.
Buub wrote:Well, now that I've made myself a member of the wheel group, there is nothing hard about it at allWhat's so hard about just logging in as yourself, then doing an su?
Buub wrote:Not having "." in your path and not allowing remote root login are two of the important ones that come immediately to mind.
bitvector wrote:Buub wrote:Not having "." in your path and not allowing remote root login are two of the important ones that come immediately to mind.
Which distros put "." in your PATH by default? Obviously I can't speak for all distros, but I can't think of one I use regularly that does that.