$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda1': Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:

Choice 1: If you have Windows then disconnect the external devices by
          clicking on the 'Safely Remove Hardware' icon in the Windows
          taskbar then shutdown Windows cleanly.

Choice 2: If you don't have Windows then you can use the 'force' option for
          your own responsibility. For example type on the command line:

            mount -t ntfs-3g /dev/sda1 /mnt/hdd -o force

    Or add the option to the relevant row in the /etc/fstab file:

            /dev/sda1 /mnt/hdd ntfs-3g defaults,force 0 0

[/os/unix/commands/mount] permanent link

If you want to verify that a NTP server is available and responding to NTP queries, you can go to Query NTP server and enter the Fully Qualified Domain Name (FQDN) or IP address of the system to be queried to submit an NTP query to the system from that site. If the queried system is responding to NTP requests, you will see something similar to the following:

Output of NTP server at 68.87.96.5

ntpdate

30 Nov 16:12:42 ntpdate[23942]: ntpdate 4.1.1@1.786 Tue Sep 23 17:37:40 UTC 2003 (1)
server 68.87.96.5, stratum 2, offset 0.001361, delay 0.10997
30 Nov 16:12:42 ntpdate[23942]: adjust time server 68.87.96.5 offset 0.001361 sec

If you see "stratum 0" displayed on the results page, the system is not responding to NTP queries. The offset and delay values will be zero as well in that case.

You can find a list of publicly accessible NTP servers at NTP.Servers Web .

[/network/ntp] permanent link

1. Create an entry in /etc/hosts for the second hostname. In this particular case I added a myhost2 entry, so that I had the following entries in the file.

   127.0.0.1    localhost       
   10.0.74.214  myhost1.example.com myhost1   loghost
   10.0.74.193  myhost2.example.com myhost2
   192.168.1.1  janus

   Myhost1 and myhost2 will apply to the same network interface, whereas janus is for the second network interface card in the system. The myhost2 entry is the only new entry.
2. Create /etc/hostname.hme:n files, or /etc/hostname.le0:n files depending on your system configuration, that contain the hostname for the virtual host n. You don't need to create hostname.hme0:0 as it is the same as hostname.hme0.

The above changes will cause the virtual hosts to be configured at boot time. If you don't want to reboot the system, you can use the ifconfig command to have the system start responding on the second IP address without rebooting.

# ifconfig hme0:1 up
# ifconfig hme0:1 128.183.72.193 netmask 255.255.255.0

References:

1. FAQs document :How to setup multiple ip for Solaris
   Date: March 30, 1998
   Freelab
2. Configuring Networking
   By: Keith Parkansky
   Date: May 1, 2002
   Solaris x86

[/os/unix/solaris] permanent link

References:

1. System Won't Resume from Hibernation
   MoonPoint Support

[ More Info ]

[/os/unix/linux/ubuntu] permanent link

1. Open the BlackBerry Desktop Manager.
2. Double-click on Email Settings.

   

3. Click on the Filters tab.

   

4. Click on the New button.
5. At the Add Filter window type whatever name you wish to use for the filter in the Filter Name field.

   

6. You can filter on the "from", "sent to", "subject", and "body" fields.
   
   If you did not want to forward messages from a particular email address, you would check the From checkbox. If you didn't want to forward messages from multiple senders, you could put all of their email addresses in the From field, separating the addresses by semicolons. You can also use an asterisk as a wildcard to block multiple sending addresses. For instance if you wanted to block all email from xyzcorp.com senders, you could put *@xyzcorp.com in the From field.
7. Check the "Don't forward message to the device" checkbox.
8. Click on OK.
9. Click on OK again at the Email Settings window.

[/network/email/blackberry] permanent link

You also have the option, after you've looked up the MX information for a domain, to perform a blacklist check. That test will check a mail server IP address against 147 DNS based email blacklists. (Commonly called Realtime blacklist, DNSBL or RBL ). If your mail server has been blacklisted, some email you send may not be delivered. Email blacklists are a common method employed by email server administrators to reduce spam.

[/network/email/info] permanent link

[/hardware/storage/iomega] permanent link

The problem is apparently due to the other distributions of Linux not recognizing the Serial ATA chipset on the motherboard of the system, at least for the versions that I was using. The system has a PCChips A31G V:1.0 motherboard According to Serial ATA (SATA) chipsets ? Linux support status, "Some SATA chipsets have been supported since practically forever, as their programming interfaces are unchanged from PATA predecessors. Others are brand-new and require new drivers from scratch.

Refererences:

1. LiveCD
   Wikipedia - the free encyclopedia
   
2. Serial ATA (SATA) chipsets ? Linux support status
   Revised: February 27, 2007
   Linuxmafia

[/os/unix/linux/knoppix] permanent link

[ More Info ]

[/os/windows/xp] permanent link

The .msf file is a Mail Summary File. It does not contain the messages for a mailbox, only an index of those messages to make sorting and locating messages quicker. If you delete an msf file, which you should only do without Netscape being open, the mailbox messages themselves remain and the index will be rebuilt the next time you open Netscape and access the mailbox.

However, even after deleting the inbox.msf file twice and having Netscape rebuild it, the user reported the problem recurring. I sent a few test messages to his address. When I checked his inbox they were highlighted as unread. I marked the entire folder as read to reset the counter. He said that sometime later he was having the same problem. For instance he might see 145 listed as the number of unread messages, but only a couple would be bolded indicating they were unread. And when I sorted messages by their read status, I would only see a couple.

I finally traced the issue to Netscape's "view" options. Netscape offers different "views" for your mailboxes. You can chose to view all mail or restrict the display of messages in various ways, e.g. perhaps you only want to see unread mail, or messages marked as important, or messages with attachments, or just email from the last 5 days. Another option is to display only mail from "People I Know", which I believe is email from addresses in your address book, though I'm not sure if in Netscape 7.2 it inclues email addresses from the Collected Address Book as well.

When I clicked on "View" then "Messages", I saw that Netscape was set to display messages from "People I Know" rather than "All". I changed the setting to "All".

[/network/email/clients/netscape] permanent link

[ More Info ]

[/languages/vbs] permanent link

I edited /etc/mail/access and added the line below:

someuser@frostdragon.com                  550 Mailbox disabled for this recipient

The 550 is a standard error code for an email server to return to an email client when email is rejected. You can specify whatever message you wish after it. In this case I chose "Mailbox disabled for this recipient". I could have just used the following line instead, if I didn't want to specify my own specific error message.

someuser@frostdragon.com                  REJECT

After executing the command makemap hash /etc/mail/access </etc/mail/access to rebuild the access database file, you can test the block by establishing a telnet connection to port 25 on the server, issuing an helo or ehlo command, then a mail from command with any address as the "from" address, and then a rcpt to command with the relevant recipient address.

mail from: someone@example.com
250 2.1.0 someone@example.com... Sender ok
rcpt to: someuser@frostdragon.com
550 5.0.0 someuser@frostdragon.com... Mailbox disabled for this recipient
rcpt to: someuser@moonpoint.com
250 2.1.5 someuser@moonpoint.com... Recipient ok
quit
221 2.0.0 frostdragon.com closing connection

From the above, I can see that email to the address I wanted marked as invalid is rejected immediately, but email to the same username at a different domain name gets through. Mail with a "from" address of someuser@frostdragon.com would still be accepted, even though it is now rejected as a "to" address.

Since I don't want the server to accept email if that address appears as a "from" address either, I added the line below to /etc/mail/access as well and rebuilt the access database with makemap hash /etc/mail/access </etc/mail/access.

From:someuser@frostdragon.com             550 We don't accept mail from spammers

If you try sending using a "from" address of someuser@frostdragon.com now, the message will be rejected. However, if you test the block by the telnet e.g. telnet frostdragon.com 25 and then issuing an ehlo or helo command followed by mail from and rcpt to commands, you won't see the rejection message until you've entered the rcpt to command, i.e. it doesn't occur when the mail from command is issued.

mail from:<someuser@frostdragon.com>
250 2.1.0 <someuser@frostdragon.com>... Sender ok
rcpt to:<myself@moonpoint.com>
550 5.0.0 <myself@moonpoint.com>... We don't accept mail from spammers

References:

1. FEATUREs for check_* in sendmail 8.9
   Sendmail.Org
2. Configuring sendmail to Reject Unsolicited Mail
   HP Technical Documentation
3. Anti-Spam Configuration Control
   Sendmail.Org
4. SMTP Service Extension for Returning Enhanced Error Codes
   The Internet Engineering Task Force (IETF)
5. 22.6. The /etc/mail/access and access.db files
   Securing and Optimizing Linux
   RedHat Edition - A Hands on Guide

[/network/email/sendmail] permanent link

By Disc
Alphabetical listing

Additional packages in RPM format can be found at Dag Wieër's Apt/Yum RPM package overview.

[/os/unix/linux/redhat] permanent link

# dig

; <<>> DiG 9.2.1 <<>>
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60704
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;.                              IN      NS

;; ANSWER SECTION:
.                       517448  IN      NS      G.ROOT-SERVERS.NET.
.                       517448  IN      NS      H.ROOT-SERVERS.NET.
.                       517448  IN      NS      I.ROOT-SERVERS.NET.
.                       517448  IN      NS      J.ROOT-SERVERS.NET.
.                       517448  IN      NS      K.ROOT-SERVERS.NET.
.                       517448  IN      NS      L.ROOT-SERVERS.NET.
.                       517448  IN      NS      M.ROOT-SERVERS.NET.
.                       517448  IN      NS      A.ROOT-SERVERS.NET.
.                       517448  IN      NS      B.ROOT-SERVERS.NET.
.                       517448  IN      NS      C.ROOT-SERVERS.NET.
.                       517448  IN      NS      D.ROOT-SERVERS.NET.
.                       517448  IN      NS      E.ROOT-SERVERS.NET.
.                       517448  IN      NS      F.ROOT-SERVERS.NET.

;; ADDITIONAL SECTION:
F.ROOT-SERVERS.NET.     172107  IN      A       192.5.5.241
J.ROOT-SERVERS.NET.     172107  IN      A       192.58.128.30

;; Query time: 169 msec
;; SERVER: 207.233.128.10#53(207.233.128.10)
;; WHEN: Thu Nov  8 16:15:46 2007
;; MSG SIZE  rcvd: 260

I only saw the addresses for two of the thirteen root servers listed. The servers are named A.ROOT-SERVERS.NET. through M.ROOT-SERVERS.NET. as shown by the output of a dig command below.

# dig . NS @f.root-servers.net

; <<>> DiG 9.2.1 <<>> . NS @f.root-servers.net
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19934
;; flags: qr aa rd; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 13

;; QUESTION SECTION:
;.                              IN      NS

;; ANSWER SECTION:
.                       518400  IN      NS      H.ROOT-SERVERS.NET.
.                       518400  IN      NS      I.ROOT-SERVERS.NET.
.                       518400  IN      NS      J.ROOT-SERVERS.NET.
.                       518400  IN      NS      K.ROOT-SERVERS.NET.
.                       518400  IN      NS      L.ROOT-SERVERS.NET.
.                       518400  IN      NS      M.ROOT-SERVERS.NET.
.                       518400  IN      NS      A.ROOT-SERVERS.NET.
.                       518400  IN      NS      B.ROOT-SERVERS.NET.
.                       518400  IN      NS      C.ROOT-SERVERS.NET.
.                       518400  IN      NS      D.ROOT-SERVERS.NET.
.                       518400  IN      NS      E.ROOT-SERVERS.NET.
.                       518400  IN      NS      F.ROOT-SERVERS.NET.
.                       518400  IN      NS      G.ROOT-SERVERS.NET.

;; ADDITIONAL SECTION:
A.ROOT-SERVERS.NET.     3600000 IN      A       198.41.0.4
B.ROOT-SERVERS.NET.     3600000 IN      A       192.228.79.201
C.ROOT-SERVERS.NET.     3600000 IN      A       192.33.4.12
D.ROOT-SERVERS.NET.     3600000 IN      A       128.8.10.90
E.ROOT-SERVERS.NET.     3600000 IN      A       192.203.230.10
F.ROOT-SERVERS.NET.     3600000 IN      A       192.5.5.241
G.ROOT-SERVERS.NET.     3600000 IN      A       192.112.36.4
H.ROOT-SERVERS.NET.     3600000 IN      A       128.63.2.53
I.ROOT-SERVERS.NET.     3600000 IN      A       192.36.148.17
J.ROOT-SERVERS.NET.     3600000 IN      A       192.58.128.30
K.ROOT-SERVERS.NET.     3600000 IN      A       193.0.14.129
L.ROOT-SERVERS.NET.     3600000 IN      A       199.7.83.42
M.ROOT-SERVERS.NET.     3600000 IN      A       202.12.27.33

;; Query time: 235 msec
;; SERVER: 192.5.5.241#53(f.root-servers.net)
;; WHEN: Thu Nov  8 16:22:59 2007
;; MSG SIZE  rcvd: 436

I also checked the status of the DNS service on the system with the rndc status command and saw the following:

# rndc status
number of zones: 6
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
server is up and running

When I checked the /var/named/named.ca file on the system, I found it was dated January 24, 2003, so was almost 5 years old, since the current date is November 8, 2007. I backed up the current named.ca file and then overwrote the file with the latest information.

# dig . NS @f.root-servers.net >/var/named/named.ca

I then restarted the DNS server with /etc/init.d/named restart.

Note: if you see the following when you check the DNS server status, try issuing the /etc/init.d/restart command again.

# rndc status
rndc: connect failed: connection refused

The root hints file, /var/named/named.ca should be updated periodically, which I hadn't been doing on the server. A script to do so can be found at Keeping it working. The script will have to be customized for your particular system though, e.g. I would need to use named.ca instead of root.hints for the filename. And you also need to substitute the name of a system or an IP address of a system that should normally be reachable over your Internet connection for some.machine.net

References:

1. Configuring DNS > Configuring named
   O'Reilly - Safari Books Online
2. LOCAL AREA NETWORK DOMAIN NAME SYSTEM (DNS)
   Small Enterprise Networking and Computing Primer
3. Keeping it working
   Linux.com

[/network/dns] permanent link

[ More Info ]

[/security/spyware] permanent link

[ More Info ]

[/hardware/network/nic/sis] permanent link

[ More Info ]

[/hardware/network/nic/sis] permanent link