Mauriat Miranda     mjmwired

Automated FTP Script

I’ve been doing some development for some embedded Linux devices which only support ftp and telnet. In order to automate transfer of binaries from my Fedora development host to the target embedded device I’m using this handy ftp script: #!/bin/bash # arg1 = dest hostname # arg2 = local file # arg3 = dest dir HOST=$1 SRCFILE=$2 USER=root PASSWD=password #DESTDIR=/usr/local/data DESTDIR=$3 ftp -inv $HOST<<ENDFTP user $USER $PASSWD cd $DESTDIR bin put $SRCFILE chmod 755 $SRCFILE bye ENDFTP Then I added something like this to my Makefile after cross-compiling:

Default Xorg Resolution

Recent versions of Linux and the Xorg X-Windows system have been engineered to require very little configuration settings to properly detect graphics options and display resolutions. In most cases graphics should “just work”. The Xorg system stores all its configuration options in the file: xorg.conf. Many distributions including Fedora and CentOS keep this file in the /etc/X11/ directory. In the past this file would contain a great deal of information that was not easy to setup.

SSH Client Configuration

I have a VPS which is host to many websites. Some of those sites are permitted ssh access for their admins. However I am the admin to several sites myself. Each site has a different username (login/password) for administration. Additionally I have changed the ssh port to a different number (instead of the default 22) to avoid some script/bot attacks. All of this makes for very inconvenient ssh usage and plenty of typing errors.

Command Line DVD Burning

When I built my server, I only used a CD-RW/DVD-ROM combination drive. Whenever I remotely downloaded a ISO using wget or bittorrent, I would have to copy the 2-4GB file(s) from my server to either my desktop or laptop. I finally caved, and bought a DVD-RW drive for my server (even though it will get minimal usage). (This was all on my CentOS 5 server, I executed these commands entirely remotely.

NetworkManager and YUM Update Issue

As been noted, the NetworkManager update in Fedora 9 and Fedora 10 prevents YUM from performing a regular update. Apparently due to a bug in the Fedora Update system. The following error may be seen: Public key for NetworkManager- is not installed The solution is coming soon, but for a temporary workaround YUM supports an exclude option: yum --exclude=NetworkManager\* update This should ignore NetworkManager related packages and continue on in the update process.