Most corporate sites are supposed to be oriented for those who don't know their products. Some promote them blindly; some flaunt their "magnificent" specs; some just post a picture. But the objective is the same
Users who need to go to those sites usually aren't the kind of customers that uses google (or any other engine) to search for a product; They read an article in a magazine, or saw an advertisement, and them go check the URL supplied in the article (or ad). If none was found, they almost probably will try typing the company name at the URL (which will send them to MSN's crappy search engine)
Besides, at it was already pointed out, strage URLs aren't marketeable enough. You can't paint "http://www.cornershop-cosmetics-from-chicago-inc. net/ " in a van:-) You'll want www.cornershop.com. Better yet, www.cosmetics.com (_We_ are _the_ cosmetics shop).
Domain names aren't just a resource. They're part of a marketing strategy and image. No search engine can replace that.
I've finished the process of migrating a fairly large ISP/Telco (1.5M users) to LDAP a couple of months ago. I've been at it for over a year, and
from my own experience I can tell you that:
1 - The best available tools are definitely the command-line that come with most servers.
2 - OpenLDAP sucks big time in large scale environments. It's replication is anything but reliable
3 - GQ is a very, very nice browser for LDAP. But I wouldn't use it for administration.
4 - You can assemble a whole range of ISP services (mail, ftp, http, whatever) based on an LDAP tree. Even if you can't find a _insert favorite daemon here_ supporting LDAP, you can always use...
5 - PAM/NSS LDAP. It just rocks. If you configure it properly, anything using PAM/NSS will use/update your tree accordingly. This includes unix tools like "passwd", "useradd", or "finger", or services like QPopper and OpenSSH.
6 - The best way to automate some processes is to create our own tools. Net::LDAP is very easy to use, and does anything you can think of (in terms of LDAP ops)
Slashdot Mirror
Most corporate sites are supposed to be oriented for those who don't know their products. Some promote them blindly; some flaunt their "magnificent" specs; some just post a picture. But the objective is the same
. net/ " in a van :-) You'll want www.cornershop.com. Better yet, www.cosmetics.com (_We_ are _the_ cosmetics shop).
Users who need to go to those sites usually aren't the kind of customers that uses google (or any other engine) to search for a product; They read an article in a magazine, or saw an advertisement, and them go check the URL supplied in the article (or ad). If none was found, they almost probably will try typing the company name at the URL (which will send them to MSN's crappy search engine)
Besides, at it was already pointed out, strage URLs aren't marketeable enough. You can't paint "http://www.cornershop-cosmetics-from-chicago-inc
Domain names aren't just a resource. They're part of a marketing strategy and image. No search engine can replace that.
I've finished the process of migrating a fairly large ISP/Telco (1.5M users) to LDAP a couple of months ago. I've been at it for over a year, and
from my own experience I can tell you that:
1 - The best available tools are definitely the command-line that come with most servers.
2 - OpenLDAP sucks big time in large scale environments. It's replication is anything but reliable
3 - GQ is a very, very nice browser for LDAP. But I wouldn't use it for administration.
4 - You can assemble a whole range of ISP services (mail, ftp, http, whatever) based on an LDAP tree. Even if you can't find a _insert favorite daemon here_ supporting LDAP, you can always use...
5 - PAM/NSS LDAP. It just rocks. If you configure it properly, anything using PAM/NSS will use/update your tree accordingly. This includes unix tools like "passwd", "useradd", or "finger", or services like QPopper and OpenSSH.
6 - The best way to automate some processes is to create our own tools. Net::LDAP is very easy to use, and does anything you can think of (in terms of LDAP ops)
Gconftool is your friend:
/apps/galeon/Advanced/Network/user_agent --type=string "Mozilla/4.0 (compatible; MSIE 5.5; oops, wrong! it's:) Mozilla/5.0 Galeon/0.12.5 (Linux i686; U;) Gecko/20011012"
Try: gconftool -s