Linux Neophyte

I mentioned in a recent post that I had installed KDE on my lappy, when I did it, I used the recommended Ubuntu method; sudo aptitude install kubuntu-desktop. If you don’t know, that installs all of the apps and settings that you’d have if you installed from the Kubuntu CD. That’s all fine and good with me save for one thing; I don’t want the Kubuntu boot/shutdown splash screens. I really like the sexy black/orange splash that comes with stock Ubuntu (which is what I installed back in the day). I used the following method to restore the default usplash.

Get to a shell prompt, and execute the following commands:

sudo update-alternatives --config usplash-artwork.so

You’ll be prompted with the following:

There are 2 alternatives which provide `usplash-artwork.so’.
Selection Alternative
———————————————–
1 /usr/lib/usplash/usplash-theme-ubuntu.so
*2 /usr/lib/usplash/usplash-theme-kubuntu.so
Press enter to keep the default[*], or type selection number:

I entered 1 to select usplash-theme-ubuntu.so and hit Enter.

Now enter the command below:

sudo dpkg-reconfigure linux-image-$(uname -r)

You’ll receive a few status messages, and then a few moments later you’ll have your prompt back. Now go about your business, you’re done! The next time you boot, you’ll have the default Ubuntu boot splash staring back at you.

written by M@ \\ tags: CLI, Console, Desktop, Edgy, Ubuntu

A student here at work has a notebook which just up and died. The story was that the fan died about a week before, she ignored it and just kept running the machine. As many of us have learned, lappies can run hot. This wasn’t a very good idea (to say the least). As computers will do when too much heat is applied, it choked and took everything with it. My hope was to save the data she’s been collecting throughout her college career so I started poking around.

The notebook itself seems thrashed, holding the power button down will flash the power LED, then it just blinks out (kinda sad). Obviously I’m not getting at the data on the disk if I have to use this machine. I yank the disk, toss it into another lappy (same model) and insert a Knoppix 3.9 boot CD. To my chagrin, the poor little disk is hurting too. I got a horrid click/crunch noise during POST and the system couldn’t find the disk. Dismayed, I pulled the drive, tapped it ever so slightly and tried again. No joy. OK, I have another idea, I grab a ziplock bag (thanks to the ladies in AP, they ALWAYS have “stuff” around, I always find the strangest things in their area), pop the drive into it and stick the whole thing into the freezer for an hour and a half (passing the time by drinking coffee and hoping this works).

Now that it’s frozen, I take the disk, slide it back into the lappy and start it up. No hard disk noises at all, it’s just not spinning up. Well, we’re getting to the point where I won’t have the tools to save the data. So, I says to myself, “screw it” and whacked the disk off of the top of my desk a couple of times and try again. JOY! The drive spins up!

Note to self: violence is better than cold…

I boot from the CD into the Knoppix KDE desktop, mount /dev/hda2 (which is where XP lives on this machine) and use scp to transfer the contents of her “My Documents” folder to my Fedora machine here at work. The command looked like scp -r /mnt/hda2/Documents\ and\ Settings/[username]/My\ Documents/ xxx.xxx.xxx.xxx: (I removed her username and my IP from the example).

Dell will be in to replace the ever so toasted motherboard (and anything else that’s been trashed) and I can hand it all back to her with her data in place.

Just another illustration of the power of Linux, there was no way I could have added this drive to a desktop machine here at work without buying a laptop drive conversion kit. Knoppix was the PERFECT solution.

written by M@ \\ tags: Desktop, Hardware, KDE, Knoppix

I just read an announcement from Linspire (http://www.linspire.com/lindows_news_pressreleases_archives.php?id=212) stating that they’re opening up Click ‘N Run (CNR) to several popular Linux distributions. My knee-jerk reaction to this is EXCELLENT!

I’ve only heard/read wonderful things about CNR, so I can’t give any details past what’s included in the press release. It should be interesting to follow the reactions of the distros mentioned and see if/how they plan on embracing CNR.

If this is something that the better known distros will latch onto, the argument that software installation on Linux “sucks” could be a thing of the past. If played well, this could do A LOT to push Desktop Linux into the foreground.

This might be a good time to download Freespire and see just how nice CNR is.

written by M@ \\ tags: Apps, News

http://anapnea.net is offering free Linux shell accounts to those that would like to apply. I read about this on Sunday morning (yesterday) via Digg and decided to give it shot. I joined the IRC channel (#anapnea on FreeNode) and queried cyraq asking about the application. It was a simple process, he asked why I needed the account (explaining that this is a standard application question) and I told him that I’m new to Linux, and for me, it’s a learning experience. After that, I just had to provide him with my desired username.

I figure sharing a system with others can teach me a few things, I looked at it from a newb’s point of view and here are some of the reasons I came up with for checking out Anapnea.

Community: The IRC channel is full of people buzzing about the service, asking questions, and giving each other help. It seems to be a combination of newish to seasoned Linux/Unix users that are excited about the service. If you’re just getting started with Linux, this is a great way to get some help. Everyone using that service is using the exact same software as you. If you have a question, ask, you’re almost sure to get an answer.

Introduction to Console Applications: You’ll have access to several well known communication applications. IRSSI, CenterICQ and others. These are common Linux tools for communicating on IRC and IM networks. You can read about some of them on the Anapnea home page. The apps are already installed for you, all you have to do is try them out. See what you like or don’t like. I would suggest reading up on IRSSI, if you’re totally green, it’s not the easiest application to configure. That said, it’s the IRC client I’ve been using since I first gave Linux a shot. It’s terrific!.

Resource Sharing: By sharing a system with others, you get a feel for the right and wrong things to do when on a multi-user system. Poking around in other people’s home dirs would fall into the “wrong” category. That is a sure way to get your account revoked. I watched somebody lose his account today because he was doing just that. You are permitted to protect your directory from peekers, and I would do so (chmod 700 $HOME).

Introduction to SSH: SSH (Secure Shell) is the most common way to remotely log into a Linux server. If you haven’t yet made the jump to Linux, you might not even be aware of how useful SSH is (trust me, it’s amazing). Why not try it out, you can use an app like PuTTy on your Windows box to log into your account and muck about with Linux applications.

Customizing a BASH Environment: OK, this may not be for the super newbie, BASH is the shell you’ll be using to interact with the computer. There are [insert some insanely high, random number] of things you can do with BASH. Again, this comes in really handy if you haven’t got your own Linux box to play with but want to poke around. Not to worry if you really are 100% new to Linux, BASH doesn’t require customization to use it.

An account on Anapnea isn’t a replacement for your own Linux machine, you will only have 5 MB of storage and access to a limited number of applications. It is however, a great way to get your feet wet AND have some free web space out there on the Internet.

Another cool note, when asked if you’re a Gentoo user, you can proudly say Yes!

About Anapnea.net:

This morning, I spent a few minutes talking to cyraq, I wanted to know just why the hell he was offering this service, and maybe find out a little bit about him. It turns out his reason for starting Anapnea, was to help people who needed a shell account but didn’t necessarily have the means to buy one. If you’re not sure why anyone would need/want a remote shell account, I can offer an example. I have a friend who’s university won’t permit the use of IRC on their network. Being a student, he doesn’t have extra money for a shell account. This is a perfect solution for him, he can use IRC resources without violating the University’s rules.

The first two weeks of Anapnea’s life went well. News spread of its existence through word of mouth, people would sign up (who wouldn’t?) and a small community began to develop. Eventually, it was Dugg and In a period of 12 hours, cyraq went from being the sole administrator of 48 accounts, to the leader of a 3 person administration team that now had to manage 370 accounts (one of which I own). I can’t tell the story better than he, so…

(16:26) (mattds) and this was pretty much overnight?
(16:26) (cyraq) yeah, woke up at 3AM to get some water, and on the way checked my email
(16:26) (cyraq) You have 126 new emails.
(16:27) (cyraq) stayed up till 3PM
(16:27) (cyraq) went back to sleep at 6PM
(16:27) (cyraq) at one point, the emails were coming faster than i could answer them

I don’t have any info on the newest members of the team (lightdifference and Mike42), but I do know that cyraq is a young admin and by his own admission, very passionate about Linux. I think it’s great that he’s giving back to the community by offering this service. Another reason to embrace Linux and the people involved with it.

Disclaimer: I’m not a reporter, my apologies if that’s the lamest summary of an interview you’ve ever read

written by M@ \\ tags: BASH, CLI, Console, SSH

The Dropbear SSH client included on the DD-WRT firmware can make it trivial for you to access computers on your network without exposing them to the Internet. For example, let’s say I have remote SSH management enabled on my router, and I have a computer named ubuntu running an SSHd on my LAN. I want to log into ubuntu from anywhere but don’t want to forward ports from the WAN side of the router to that machine. All I need to do is SSH into my router, and from the DD-WRT shell prompt enter ssh [username]@ubuntu and provide my password. All very easy to do and keeps my machines away from the world on the ugly side of the router/firewall.

Now, ubuntu is only accessible from the LAN, so to make my life a little easier, I want to allow password-less logins, this is how it’s done.

This builds off of DD-WRT: SSH Remote Management with Public Key Authentication and DD-WRT: Samba Startup Script / Reconfigure Dropbear SSHd. Just to keep things fresh, the router only allows logins via public-key authentication, the machine ubuntu hosts the script that the router launches at startup on a Samba share (smb://ubuntu/ddwrt). The local path to that share on ubuntu is ~/ddwrt. The router will map that share to /tmp/smbshare during startup and will execute the dd-wrt-startup.sh script located there.

Configure public-key authenication on the Linux machine:

Since I used this machine to create a keypair earlier, I’m just going to recycle. Up until now, I’ve only configured this machine to make connections to other hosts using public-key authentication. Now I need to accept public-key auth connections from other hosts.

To do this, I need to create an authorized_keys file in ~/.ssh/. The command below will write my ~/.ssh/id_rsa.pub file to the bottom of a pre-existing authorized_keys file or create a new one if it doesn’t exist. This file allows me to authenticate with my private key on the computer ubuntu.

cat ~/.ssh/id_rsa.pub >>~/.ssh/authorized_keys

Copy private key to router and convert it:

Next, I need to get my private key someplace accessible to the router, I’m just copying it to the Samba share that auto-mounts when the router starts up.

cp -v ~/.ssh/id_rsa ~/ddwrt/

Now, I remove the password from the copy of the private key, this is mandatory. DD-WRT’s Dropbear client has its own format for private keys and cannot convert encrypted (password protected) OpenSSH keys. Not to mention that I actually WANT password-less logins :). Just follow the prompts provided after executing the next command.

ssh-keygen -p -f ~/ddwrt/id_rsa

Note: This key will NEVER leave my personal network so I’m not worried about it getting into the hands of anyone I don’t trust.

Next I SSH into the router.

ssh root@192.168.1.1 -i ~/.ssh/id_rsa

Using dropbearkonvert I convert the OpenSSH key to a Dropbear key.

dropbearkonvert openssh dropbear /tmp/smbshare/id_rsa /tmp/smbshare/id_dropbear

Install private key to home dir at router startup:

The last step is to have the key installed to the /tmp/root/.ssh/ directory on the router whenever the router starts up. I could opt to leave the key on the Samba mount, but I decided to put it on the router because I actually have more than one machine I want to get to. If for some reason the machine running the Samba server is off-line, I wouldn’t have access to the private key.

To automagically install the key, I need to add the lines below to the router’s startup script, this can be done from the router, vi /tmp/smbshare/dd-wrt-startup.sh or from my desktop using my editor of choice nano ~/ddwrt/dd-wrt-startup.sh.

## install dropbear private key for passwordless login to other machines
cp /tmp/smbshare/id_dropbear /tmp/root/.ssh/
chmod 600 /tmp/root/.ssh/id_dropbear

You can reboot the router to test the script or you can manually enter cp /tmp/smbshare/id_dropbear /tmp/root/.ssh/ on the router and test it by entering ssh [username]@[hostname] -i ~/.ssh/id_dropbear. This should bring up a prompt similar to the one below:

Host ‘ubuntu’ is not in the trusted hosts file.
(fingerprint md5 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx)
Do you want to continue connecting? (y/n)

Answering “y” will add the host to ~/.ssh/known_hosts and I won’t be prompted about it again until I reboot the router. If I want to permanently add all of my machines to known_hosts, I can connect to each one of them and answer “y” at the Do you want to continue connecting? Prompt. After all of my hosts are known, I copy the file from the router to my Samba share (cp ~/.ssh/known_hosts /tmp/smbshare). Lastly, I go back to my startup script and add the line below.

cp /tmp/smbshare/known_hosts /tmp/root/.ssh/

that’s all folks, the router will install the files I need whenever it reboots and I have access to all of my machines through ONE tightly locked door.

written by M@ \\ tags: CLI, Console, DD-WRT, Hardware, SSH

Well, they’ve finally done it! Fedora fixed the kernel problem that was simply driving me mad. Back in November, I posted about Fedora Core 6 - SATA & CIFS Problems which led to painfully slow boot times on my office OptiPlex system.

If you’re suffering from this garbage at startup:

ata1: port is slow to respond, please be patient
ata1: port failed to respond (30 secs)
ata1: SRST failed (status 0xFF)
ata1: SRST failed (err_mask=0x100)
ata1: softreset failed, retrying in 5 secs

Then all you need to do is perform a standard update (su -c 'yum update') and restart the machine. The 2.6.19-1.2895.fc6 kernel will fix it.

Now that the issue is resolved, Fedora doesn’t feel broken to me anymore. JOY!

written by M@ \\ tags: Apps, FC6, Fedora, Hardware, RPM

The first non-beta version of Flash 9 for Linux is out, you can download the installer from Adobe’s site. I downloaded the tar.gz installer and had no problem whatsoever installing it. The instructions are on the download page, and all you’ll need to know before hand is where your browsers are installed to. To find out, you can use the package management tools included in your distro.

Fedora:

rpm -ql firefox

This query will give you a lot of information (you might want to pipe it to less). What you want to zero in on is the directory that is referenced most, on my system it’s /usr/lib/firefox-1.5.0.9/. You’ll notice a lot of references to /usr/share/ and can pretty much ignore them. That directory holds icons, .desktop files and other shared objects.

I did the same for SeaMonkey (rpm -ql seamonkey), the install location for the current version of the monkey is /usr/lib/seamonkey-1.0.7/.

Ubuntu:

dpkg -L firefox

That’s another command that will hand you TONS of information. Again, I only care about the installation directory, I know from using Ubuntu that the standard application install location is /usr/lib/[installdir]. So to clean up the output, I used grep to filter out the data I don’t need (you could do the same on the Fedora example above).

dpkg -L firefox |grep /usr/lib

That gave me something that looked like:

/usr/lib
/usr/lib/firefox
/usr/lib/firefox/firefox
/usr/lib/firefox/libgfxpsshar.so
/usr/lib/firefox/libgkgfx.so
/usr/lib/firefox/libgtkembedmoz.so
/usr/lib/firefox/libgtkxtbin.so
/usr/lib/firefox/libjsj.so
[snip]

From that I can see that Ubuntu installs Firefox to /usr/lib/firefox.

I also use SeaMonkey on Ubuntu, but I had to manually install it. For that reason, dpkg has no clue as to where the software is. I chose to install it to /usr/local/seamonkey, which is the location that the SeaMonkey installer suggests. I just keep that in the back of my mind or I could enter a locate seamonkey. That will return a lot of hits as well and will look something like:

/usr/bin/seamonkey
/usr/local/seamonkey
/usr/local/seamonkey/install.log
/usr/local/seamonkey/registry
/usr/local/seamonkey/libplds4.so
/usr/local/seamonkey/libxpcom.so
/usr/local/seamonkey/libmozz.so
[snip]

Now that I know where my browsers are installed to, I can run the Flash installer and give it the correct path to each browser when asked.

written by M@ \\ tags: Apps, CLI, Console, DPKG, Fedora, Firefox, Flash, Mozilla, RPM, Ubuntu

Yep, still working with DD-WRT :).. I wanted to make some changes to the router config but these changes aren’t available in DD-WRT’s control panel. Since we’re working with Linux here, I figured there had to be SOME way to hack it up.. Well, I was correct! The firmware has some features that make it pretty simple to execute a script at startup. You have some options, one is to enable JFFS and physically store a script on the router. Another is to mount a Samba share on startup and keep your script there. I opted for the Samba share because it can store your script as well as allow you to upload files (via scp for instance) directly to a computer on your network through your SSHd.

The script I’m creating is only useful if you have your router configured for remote SSH management (see DD-WRT: SSH Remote Management with Public Key Authentication for my how-to). The configuration process applies to setting up any startup script on a Samba share.

The script I want to execute on startup is going to change the configuration of the Dropbear SSHd. By default, when you connect to the router via SSH, you’re presented with a pre-login prompt advertising the firmware’s version. I prefer not sharing that info with anyone (not in such a blatant fashion at any rate), so I need to kill off the dropbear process and restart it without the banner flag. You might be wondering why I don’t just edit dropbear’s config file on the router… The simple answer is that there isn’t one.

I’m going to be using a Samba share I’ve created just for DD-WRT on the machine named ubuntu (also my desktop). The local path is ~/ddwrt and the network path is smb://ubuntu/ddwrt

Create the script:

Create a script on your Samba share named dd-wrt-startup.sh. One way to create the file is to enter the commands below in a terminal.

cd ~/ddwrt
touch dd-wrt-startup.sh

Open ~/ddwrt/dd-wrt-startup.sh with your editor of choice and add the text below (each command should be on its own line):

#!/bin/sh
## kill/restart dropbear; remove pre-logon message
killall dropbear
dropbear -r /tmp/root/.ssh/ssh_host_rsa_key -d /tmp/root/.ssh/ssh_host_dss_key -p 22 -s

Be sure that when you specify the port (-p 22), you use the same port that you have configured in the DD-WRT control panel.

The difference between the command to launch dropbear that I wrote, and the command the router defaults to, is that I’ve removed the banner file flag (-b [path to loginprompt]). If you want to see what the exact command line is on your router before you make the change, SSH in and enter a ps, someplace in the process list you’ll see the dropbear command line.

Configure Samba FS Automount:

Before going on, be sure that the Samba server has a static IP or (better yet) a static DHCP address. If you don’t use static DHCP, you may want to use the machine’s IP address instead of its name when configuring the share below. Check out the DD-WRT DNSMasq wiki page for more info.

Log into the DD-WRT Control Panel, Click Administration then select the Management tab. Scroll down to the Samba FS Automount section and configure as follows:

• SMB Filesystem: Enable
• Share: //ubuntu/ddwrt
• User Name: [valid smb user]
• Password: [smb user's password]
• Startscript: dd-wrt-startup.sh

Now all you need to do is click Save Settings and Reboot Router. The next time you SSH in, you’ll notice that no information about the router is given until you’ve provided your credentials and successfully authenticated. You will also notice that entering the mount command will show you that your Samba share is mounted to /tmp/smbshare.

written by M@ \\ tags: CLI, Console, DD-WRT, Hardware, SSH

I spent some time tweaking out my (and by “my” I mean on loan from work) Dell D600 laptop tonight. I’m using KDE on this machine as I haven’t used it since giving Gnome a shot and I’m trying to diagnose a strange problem I’m having by ruling Gnome out as the cause. I’ve got this thing looking pretty sweet and I’m pretty happy with the feel of it. Thanks to my play time, I finally figured out just what the hell was annoying me so much about KDE and fixed it!

Waiting for the big revelation???

Bah, nothing major. It comes down to the fact that I detest the look of the Plastik window decorations and the useful area of the screen always felt small to me. These aren’t show stoppers, I was just lazy and didn’t get around to tweaking. Now that I have, I’m really digging on KDE. I LOVE the look and feel of Gnome, however continued KDE use might, just might, convert me.

I think on Monday I’ll switch to KDE on my work Fedora system and put it through its paces. I’ll just boot Plastik and set both my kicker and external task bar to allow other windows to cover them.

So check it out if ya like, it seems I was feeling like many shades of gray this evening…

written by M@ \\ tags: Desktop, KDE

So, I’ve been spending a fair amount of time mucking about on my DD-WRT based router and I have a few topics to cover. They’ll all sort of build on each other and I’ll ping-back when appropriate. I initially attempted to do them all in one colossal post and then realized that it just wouldn’t work. So first things first, SSH.

When I set up a personal Internet facing SSH daemon, I only allow logins via public/private key files. This greatly improves security by eliminating the potential for brute force password cracking. If you aren’t familiar with public key authentication, the quick of it goes something like this; you have a key pair that consists of a public and a private key. The public key lives on the server you want to log into, and the private key lives on your computer (the client). You can share the public key with anyone, and you should physically protect the private key with your life. You can choose to encrypt the private key with a password (you will need to enter the password each time you attempt to authenticate with the key) or leave the password blank (which allows you to log in without a password). Note: It’s strongly suggested that you password protect your private key.

So what’s the point of it? Your public key can only be used with its partner private key. As long as your private key is safe (only you have access to it), nobody can crack your account and log in (even if they have the public key, you can’t generate a private key based on the data in the public key). This is why I suggest encrypting the private key with a password, if you have it on a thumb drive and lose the drive, the dweeb who picks it up and wants to see what you have access too will still need to get past the password on the private key. This gives you time to create a new keypair and update the machines you connect to.

I hope I made that clear, it makes more sense once you start using it. If you’re confused at all after going through all of this, please let me know in the comments of this post, I’ll clear up what I can.

Creating a keypair on your Linux box

If you haven’t previously used SSH to connect to a host, you won’t have a ~/.ssh/ directory on your machine. If you aren’t sure whether or not you’ve used SSH before, open a terminal and enter ls -lad ~/.ssh. If the folder doesn’t exist, you’ll want to create it and set the proper permissions now. The command below will create the directory with a mode of 700, only you as the owner will be able to list the contents of ~/.ssh

mkdir ~/.ssh -m=u+rwx,g-rwx,o-rwx

This next command will create a keypair in ~/.ssh/ as long as you have the OpenSSH Client package installed (chances are, you do). Basically we’re creating a (standard) 2048-bit RSA keypair with a custom comment (-C [comment]. If you decide not to customize the comment, ssh-keygen will insert your [username]@[host] as the comment). If you don’t enter a password for your key when prompted, you won’t need to enter one when attempting logins with this keypair. As convenient as this sounds, I would (again) suggest using a strong password to keep this keypair safe.

ssh-keygen -C [comment] -f ~/.ssh/id_rsa

Now that we have a keypair (~/.ssh/id_rsa and ~/.ssh/id_rsa.pub), we need to log into the DD-WRT control panel, enable SSH and paste in our authorized key.

Configure SSHd

Open ~/.ssh/id_rsa.pub with your editor of choice, select all of the text and copy it.

Next, open your browser and enter the address of the router, Click on the Administration tab, and then on Services. Scroll down to the Secure Shell section and set it up as follows:

• SSHd: Enable
• Password Login: Disable
• Port: 22
• Authorized Keys: Paste in the contents of your id_rsa.pub file. The actual key (the ugly part of the file) must NOT wrap, it needs to be on one line.

Note: I ALWAYS change the port from 22 to some high number that’s easy for me to remember. It cuts down on attempted break-ins, do whatever works for you.

Now that SSHd is configured, click Save Settings and then Reboot Router. At this point, you can only use SSH to log into the router from your LAN (in other words, we haven’t opened SSH up to the world yet).

Once the DD-WRT control panel is visible again, open a terminal and enter the command below:

ssh root@192.168.1.1 -i ~/.ssh/id_rsa

If all goes well, should see a login prompt like the one below. You’ll need to enter the password for your private key. After that you should be at a shell prompt. If yes, Congrats! You’re communicating with your router via SSH.

DD-WRT v23 SP2 std (c) 2006 NewMedia-NET GmbH
Release: 09/15/06 (SVN revision: 3932)
Enter passphrase for key ‘/home/[username]/.ssh/id_rsa’

Now that it’s all tested, we can open SSH up to the Internet. This is optional of course, if you don’t want SSH access to your router from remote locations, then skip it.

Log into the DD-WRT control panel and select the Administration tab and then the Management tab. In the Remote Access section configure as follows.

• Web GUI Management: Disable
• SSH Management: Enable
• SSH Remote Port: [same port you selected in the Secure Shell configuration]

Again, click Save Settings and Reboot Router. After the reboot, you’re SSHd is available to you from anywhere

Extra bit to make life easier

Finally, if you think that’s an annoying amount of text to enter whenever you want to SSH into your router, create an SSH Config file. Use whatever editor you like, enter the text below and save the file to ~/.ssh/config

host ddwrt
hostname 192.168.1.1
port 22
user root
identityfile ~/.ssh/id_rsa

Now all you need to do is enter ssh ddwrt to connect to your router.

Finally, I should mention that allowing remote “root” logins is a really bad idea. I’ve made an exception in this case as DD-WRT is unique in that it only has one user account. There are ways of renaming the account, if I explore them, I’ll (of course) tell you about it.

written by M@ \\ tags: CLI, Console, DD-WRT, Hardware, SSH