They also tend to be fierce Mac supporters, and getting them to move to even a Windows platform is hard enough, no matter how many times you tell them it's cheaper and faster.
Too bad their configuration interface and network support sucks as much as it did eight years ago if you aren't running windows. Do yourself a favor and get a QMS if you're looking for a new printer.
If it needs root access to devices, which it almost certainly does to ifconfig an interface up, it should be installed suid root (if safe). Also, sudo is a great utility for doing things as root, does it come installed by default?
The crux is that they're not necessarily changing things to make them *better*, just to make them *different* (i.e. not inter-operable). They can do this because they are in a monopoly position and this strengthens their position my making others need their software to interact with users that are already using it.
This is a terrible example. You are trying to describe a scenario that requires a many to many relationship. The intermediary "joiner" or cross-reference table is only necessary if you have a need to keep both joined tables normalized, i.e. you want each distinct telephone number, as well as each person object, to be stored in the database only once.
You've already given up the possibility of normalizing your phone numbers in the heirarchical model (my roomates home phone is the same as mine and it shows up in LDAP twice, once for me and once for him), so a simple many to one join to the telephone number table will allow you to list a home phone twice, once for each of us.
Now, if the data you are modeling truely requires a many to many relationship (your model needs to handle the real world, you can't change the world to fit the limitations of your tools), you have no way of representing that information in a normalized fashion in a heirarchical model. The so called "kludge" of an x-ref table from the relational world is not even an option.
The heirarchical model is so limited and simplistic that it can be implemented in a single, self-referential table in a relational database, and can even be queried in a recursive manner (oracle has had 'connect by prior' for dealing with these models since I started with the product 10 years ago).
From my view as a mathematician, and not a computer programmer, the relational model is so much more robust and powerful than a heirarchical model it hardly warrants discussion.
They typical router solution is to have the dual hosted box participate in a routing protocol like OSPF using gated or something similar. Configure your routing daemon to have each physical interface advertise a zero cost route to a loopback address configured on the unix box then always use that loopback address to connect to it. If an iterface fails, the routing protocol converges and you maintain your connection.
Depending on the routing daemon and the OS you can even get load balancing between the equal cost routes when both interfaces are up.
Re:I Hope You Keep Bail Money Near Your Gun
on
Fight Virus With Virus?
·
· Score: 2, Informative
Colorado (for positive) and many other states have a "make my day" law. If someone breaks into your home you can automatically assume you are in danger of grevious bodily harm or death and can shoot dead on the spot.
This guy patented toast, I think I'm going to patent fire, or maybe the wheel.
ABSTRACT: A method of refreshing a bread product by heating the bread product to a temperature between 2500 degree(s) F. and 4500 degree(s) F. The breadproducts are maintained at this temperature range for a period of 3 to 90 seconds."
CLAIM:
1. A method of refreshing bread products, comprising: a) placing a bread product in an oven having at least one heating element, b)
setting the temperature of the heating elements between 2500 F. and 4500 F., and c) ceasing exposure of the bread product to the at
least one heating element after a period of 3 sec. to 90 sec.
2. The method of claim 1 including the step of exposing the bread product to electromagnetic radiation in the wavelength range
between 1.2 and 3.4 microns.
3. The method of claim 1 including the step of selecting said bread products from rolls, muffin, buns and bagels."
You seem to start at the premise that a stackless implementation is better than a stack based one and that Python *wants* to move in that direction. Stackless implementations are usually faster, but you lose ease of recursion and reentrancy. This is the first I've heard of Python going stackless, have I missed something?
When governments fear the people there is liberty.
First, let me say I am a huge Python fan and advocate. It is my language of choice and I use it to develop applications both at home and professionally.
That said, I see two major weaknesses in Python. First, the lack of function overloading based on parameter signature is, in my opinion, a missing piece of functionality that would be a huge boon to Python's OOedness. Secondly, Python's thread support is almost worthless without a multi-threaded interpreter.
Can you speak to when and if these two major shortfalls will be addressed?
Oh, and just for the counters: Perl Sucks, Python Rules.:-)
When governments fear the people there is liberty.
Slashdot Mirror
Hmmmm...
Googling for "redhat mirror iso" yields this as the first result:
http://www.redhat.com/download/mirror.html
But then, why bother looking for yourself when you can post drivel on slashdot and someone else will do it for you?
You know you're a real sysadmin when you can edit your /etc/fstab with ed in single user mode.
Lemme hear an "Amen!" from my brothers who have been there, done that.
Inability to use the preview button aside:
Most emacs users know how to use vi.
Few vi users know how to use emacs.
Form your own conclusions.
:wq
s/to/too/
Vi(m) is for people are to dumb to use Emacs.
They also tend to be fierce Mac supporters, and getting them to move to even a Windows platform is hard enough, no matter how many times you tell them it's cheaper and faster.
Good, cheap, fast... pick any two.
Too bad their configuration interface and network support sucks as much as it did eight years ago if you aren't running windows. Do yourself a favor and get a QMS if you're looking for a new printer.
No, it's The Lord of the Rings: The Two Towers.
I bet you John the Ripper would crack your password in a matter of hours. They've built rules into it to do those letter to number conversions.
But what if I don't want a big flat TV, Jerry?
It's still standard journalistic practice to define any acronym the first time it's used in an article.
If it needs root access to devices, which it almost certainly does to ifconfig an interface up, it should be installed suid root (if safe). Also, sudo is a great utility for doing things as root, does it come installed by default?
The crux is that they're not necessarily changing things to make them *better*, just to make them *different* (i.e. not inter-operable). They can do this because they are in a monopoly position and this strengthens their position my making others need their software to interact with users that are already using it.
This is a terrible example. You are trying to describe a scenario that requires a many to many relationship. The intermediary "joiner" or cross-reference table is only necessary if you have a need to keep both joined tables normalized, i.e. you want each distinct telephone number, as well as each person object, to be stored in the database only once.
You've already given up the possibility of normalizing your phone numbers in the heirarchical model (my roomates home phone is the same as mine and it shows up in LDAP twice, once for me and once for him), so a simple many to one join to the telephone number table will allow you to list a home phone twice, once for each of us.
Now, if the data you are modeling truely requires a many to many relationship (your model needs to handle the real world, you can't change the world to fit the limitations of your tools), you have no way of representing that information in a normalized fashion in a heirarchical model. The so called "kludge" of an x-ref table from the relational world is not even an option.
The heirarchical model is so limited and simplistic that it can be implemented in a single, self-referential table in a relational database, and can even be queried in a recursive manner (oracle has had 'connect by prior' for dealing with these models since I started with the product 10 years ago).
From my view as a mathematician, and not a computer programmer, the relational model is so much more robust and powerful than a heirarchical model it hardly warrants discussion.
They typical router solution is to have the dual hosted box participate in a routing protocol like OSPF using gated or something similar. Configure your routing daemon to have each physical interface advertise a zero cost route to a loopback address configured on the unix box then always use that loopback address to connect to it. If an iterface fails, the routing protocol converges and you maintain your connection.
Depending on the routing daemon and the OS you can even get load balancing between the equal cost routes when both interfaces are up.
Colorado (for positive) and many other states have a "make my day" law. If someone breaks into your home you can automatically assume you are in danger of grevious bodily harm or death and can shoot dead on the spot.
ABSTRACT: A method of refreshing a bread product by heating the bread product to a temperature between 2500 degree(s) F. and 4500 degree(s) F. The breadproducts are maintained at this temperature range for a period of 3 to 90 seconds."
CLAIM:
1. A method of refreshing bread products, comprising: a) placing a bread product in an oven having at least one heating element, b) setting the temperature of the heating elements between 2500 F. and 4500 F., and c) ceasing exposure of the bread product to the at least one heating element after a period of 3 sec. to 90 sec.
2. The method of claim 1 including the step of exposing the bread product to electromagnetic radiation in the wavelength range between 1.2 and 3.4 microns.
3. The method of claim 1 including the step of selecting said bread products from rolls, muffin, buns and bagels."
When governments fear the people there is liberty.
When governments fear the people there is liberty.
When governments fear the people there is liberty.
When governments fear the people there is liberty.