You can also use the Network Settings tools to manage the wireless connection. A thread at Ubunt Forums, http://www.ubuntuforums.org/showthread.php?t=142727 was a good source of information.
I came upon the need to attempt data recovery on a broken Raid5 array. Long story short, my client had a server with no backup at a data center. At the DC, an electrician was working on the breakers, to which our clients rack is connected, and took down power multiple times, probably a slew of surges too! :-@ That’s another story. I did not have any commercial tools that would reconstruct a set of RAID5 images, so off I went a Googling. What I found was an interesting solution created by Edmundo Carmona and can be found at Free Software Magazine. I’m not going to go into details here, but it worked pretty well, although we could not get any data recovered, as the drives seemed to have been totally hosed by the power issues. We eventually did try commercial tools, which yielded the same results. Anyway, some may find tool useful, but I hope you don’t have a need for this.
Edit /etc/krb5.conf to work with the 2003 AD server. It should look similar to below. The line in bold are what needs to be chanaged and entries are CASE sensitive!
[logging]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log
[libdefaults]
default_realm = ADS.LOCAL
dns_lookup_realm = false
dns_lookup_kdc = false
[realms]
ADS.LOCAL = {
kdc = ads.local
admin_server = 192.168.0.1:749
default_domain = ads.local
}
[domain_realm]
.ads.local = ADS.LOCAL
ads.local = ADS.LOCAL
[kdc]
profile = /var/kerberos/krb5kdc/kdc.conf
[appdefaults]
pam = {
debug = false
ticket_lifetime = 36000
renew_lifetime = 36000
forwardable = true
krb4_convert = false
}
Configure Samba. The basic config should look like below. Bold items are important.
Check the permissions. getfacl /home/BACKUPS You should see something like the following:
getfacl /home/BACKUPS
getfacl: Removing leading ‘/’ from absolute path names
# file: home/BACKUPS
# owner: foo
# group: foo
user::rwx
user:administrator:rwx
group::rwx
mask::rwx
other::rwx
In the event of DNS failure, you may want to edit /etc/hosts and add a line for the 2003 Server so the samba server always knows the IP of the 2003 server.
Because these two servers depend highly on time synchronization, ntpd must be setup to sync to the AD server. Do this by editing /etc/ntp.conf and /etc/ntp/step-tickers. Examples of which are as follows:
Enter your AD server’s FQDN after the first server entry in ntp.conf
### Begin /etc/ntp.conf ###
restrict default nomodify notrap noquery
restrict 127.0.0.1
server 2003server.ads.local
server 1.pool.ntp.org
server 2.pool.ntp.org
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
driftfile /var/lib/ntp/drift
broadcastdelay 0.008
keys /etc/ntp/keys
### END /etc/ntp.conf
—
List the three servers in /etc/ntp/step-tickers that are in /etc/ntp.conf.
### BEGIN /etc/ntp/step-tickers
2003server.ads.local
1.pool.ntp.org
2.pool.ntp.org
This will enable the Samba server to sync it’s time to the the AD server.
I maintain four different windows/samba domains at a university and two different hospitals. The domain member machines are spread across multiple subnets at all three locations and have dynamic addressing. I wanted to periodically scan my machines for open ports to see if anything funny was happening. To do this I needed the IPs of the systems that were connected at any given time. Using smbclient and nmblookup together could give me this information. findsmb would not work because it is limited to your current subnet. Therfore, I wrote a script to gather the IPs of domain members, so that I can scan them w/ nmap or just list them. I must thank rcsu in #samba at Freenode for his help to tweak the code. Thanks rcsu!
The following is a mini-Howto on installing and setting up the mailman,
http://www.list.org mailing list server.
It’s benefits include a web based interface to list member accounts and to archives either for the public or private for list members only.
A - INSTALLATION
1 - Download the source located at one of the available locations found at
http://www.list.org/download.html and save to your favorite dumping ground and unpack.
2 - Create a user and group w/ the name mailman.
3 - If you are sticking w/ defaults, create the directory /usr/local/mailman and give it the appropriate permissions.
4 - Change to the mailman source directory and check out the configure script help info, ./configure --help and also the README.* files that apply to you. In my case, I ran to the following:
This tells mailman what group the mail application is run as, what group the cgi scripts are run as, the hostname added to mailing list names and the hostname part of the URL for the mailman web based tools.
5 - Assuming configure has completed successfully, proceed with compiling the source.
# make && make install
B - CONFIGURATION
1 - Configure Apache to allow mailman’s web based interface to work.
Your Apache config must be edited to allow web based access. To allow this, the following should be added to the appropriate Apache config file:
ScriptAlias /mailman /usr/local/mailman/cgi-bin/
<directory /usr/local/mailman/cgi-bin>>
Order Deny,Allow
Allow from all
Options ExecCGI +FollowSymLinks
</directory>
Alias /pipermail/ /usr/local/mailman/archives/private/
<directory /usr/local/mailman/archives>
Options +FollowSymLinks
Order Deny,Allow
Allow from all
</directory>
After this has been done, restart your Apache daemon, e.g. # service httpd restart
2 - Setup the cron file for mailman to perform scheduled tasks, such as
- Managing archives
- retrying failed messages
- mail password reminders to list members
This can be done by issuing the two following commands,
# cd /var/mailman/cron
# crontab -u mailman crontab.in
3 - Edit the default files, mm_cfg.py and Defaults.py
1 - Point your browser of choice to http://host.local.domain/mailman/admin/mailman/ to see the administrative pages for your new list. From here you can make many configuration changes, which is outside the scope of this mini-howto.
2 - Point your mailing list members to http://host.local.domain/mailman/listinfo/mailman for them to see their available options.
3 - You can check various logs at /usr/local/mailman/logs. If you have any problems, some valuable info may be found here.
4 - More specific documentation can be found at http://www.list.org/docs.html.
Well, this is somewhat terse and is also a first draft, so an error or two may exist, but hopefully it may help someone.
with a slight twist. In preperation for CTCon5 WTF, I decided to setup a windows install on my Linux only laptop.
I installed windows to a spare drive in a spare laptop. I then transfered that the drive to a modular bay caddy and put it in my laptop. The typical dual boot setup is to have the Windows install be on /dev/hda or /dev/sda, but in my case it will be /dev/hdc.
I use LILO, version 22.5.9, as my boot loader. I have used GRUB but LILO has always worked so I stick with it. To get this particular setup working, the system needs to be ‘faked out’ to think that /dev/hdc is the primary boot device, /dev/hda. This can be done using the boot-as option in /etc/lilo.conf. This results in a section for the Windows installs as follows:
other = /dev/hdc1
table = /dev/hdc
label = windows
boot-as=0×80
In my case the LILO boot loader is installed on /dev/hda, which is typical, therefore, the boot-as option must specify the BIOS device code for that hard drive, in my case 0×80.
With that entry in /etc/lilo.conf you run the /sbin/lilo command to commit the changes. From now on you can now boot the Windows install that is on the removeable hard drive. Bada bing, bada bang.
