I knew someone would be a jackass and bring that *newer* technology up. But it will be years before its practical to use that. Its actually not that important because by the time SNI is practical, the world will be switched to IPv6 (which is a more pressing issue) and IPs will cost nothing. The only setback would be having to have lots of interfaces on a machine.
But then there are SSL customers want to have unique reverse DNS anyways, which would require seperate IPs.
Maybe its because they want more control over what clients are doing? Using SSL consumes more CPU you know, on both the client and the server side.
As a sysadmin for a web hosting provider, I see lots of these types of extensions that are written with no consideration of the server side of the equation. The people writing them seem to think that the server side has infinite CPU, RAM and bandwidth, which is just not true.
The new version has some strange behavior though. I was trying to open gqview on a remote folder (through sshfs) and found that it took forever to start up. When I did an strace of it, I found that when it starts, it does a stat on the image files with every possible image filename extension combination, which takes a lot longer over a remote link. Apparently it gathers information for the sidecar. Hopefully they will make that an optional thing.
Kids, don't you know that unsecured wifi is just a gateway. Pretty soon you'll be cracking into stuff with stronger encryption. Then where will be? Sitting on the side of the road in some bad neighborhood looking asking to borrow a power jack.
(remember the good old days when large numbers of sites would shriek for IE; but render just fine if FF was set to IE's UA string?)
The good old days? Oh, I see, you mean 5 years ago. I thought you were talking about the ancientweb when Netscape roamed the net and sites held out signs like "Explorers only, we don't serve nomads here".
> Ironically all this time I've been avoiding the preg functions because I figured they were the more likely candidates to go away.
Sorry this is short, but are you *that* dumb?
I must be.
Anyway, I remember seeing (in official docs) the note that ereg functions will occasionally be dropped like 5 years ago when I first started with PHP. And the fact that PCRE functions are *much, much* more powerful is very obvious.
Well good for you. Like I said, I've been using PHP since '97 and I don't usually have to go back to ereg page of the manual much. I know PCRE is more powerful (I do lots of Perl programming too so maybe I am dumb), but there are lots of functions like that in PHP where someone thought it would be cool to add it in, so it got included, but not all of them last and I wouldn't want to write code based on something that would get deprecated. Since ereg has been around since the beginning, I figured that it would be less likely to get deprecated.
As I brought up on the mailing list months ago when I was trying to make my case, of the books in the top 10 search results for PHP on Amazon, 5 or 6 of them, including the book by Rasmus himself (wrote PHP originally), use the ereg functions in their examples. So you can imagine that there are lots of people out there learning basic search functions out there that will be going away in the next major version. This is not good.
Sorry this is long, I could probably write a whole dissertation on my thoughts on PHP though.
I've been developing in PHP since version 2 way back in '97 and I've always felt that one of PHP's biggest downfalls is that it has a configuration file. I understand that it has more to do with its origins as an Apache module, but I can't think of many modules or programming languages that are so customizable as PHP is. Over the years this has led to different schools of programmers choosing one setting or another and chastising people who use a different setting.
Another big problem is that the core developers don't seem to get just how large the PHP community is. I found out some months ago that they were deprecating the ereg/POSIX regex set of functions in 5.3 and will be removing them in 6. I bought up on the mailing list that I think this is too quick of a time table for it being removed and that they should have it marked deprecated for at least 1 major version before removing it. Their excuse was that they really wanted to get UTF-8 support in PHP (a commendable goal) and the ereg functions weren't compatible and are also too slow. So now they are pushing the preg functions which are based on PCRE. Ironically all this time I've been avoiding the preg functions because I figured they were the more likely candidates to go away.
And I'm not alone. Many many people out there have been using ereg in lots of code over the past decade and its going to be a huge shock for them when it comes time to switch suddenly. When 50%+ of the dynamic web uses PHP, this is going to cause lots of problems over the next 5-10 years.
Yes yes, I know that there is work on a PEAR module to substitute the functionality of ereg, but my point is that the core developers seem to be in their own world and aren't thinking about the overall affects of their decisions and how far reaching they are.
I can tell you know that it really doesn't matter what you choose. It will eventually be replaced by something shinier and more popular/modern. Such is the way of computers and especially in the open source world. IMHO, KVM became popular because a bunch of people who weren't really using Xen decided that they liked it better and didn't give consideration to the real issues at hand. And now that they've started using KVM for real work, they are running into those issues and regret the whole thing. I've had a heavy investment in Xen since 2005 and its worked well for me and will continue to work well. But I don't really care about all that GUI management stuff, I just wrote my own. What it really comes down to is what can you live with? Do you have servers that are handling thousands/millions of transactions per day? Or are you just running a departmental webserver with just a few users? If you're doing something intense, then its worth your time to test the technologies out for yourself and see which one works better. You can test Xen vs. KVM for free.
Having used both rpm and apt for a long time now in a sysadmin setting, I can say that both have their pluses and minuses. rpm to me has a much more professional feel to it IMHO. I really wish that dpkg had the -V flag like rpm does, I've used that more times than you probably could imagine. rpm always seems faster at finding a package name given a file path and at listing out the files in a package. On the flip side, rpm historically hasn't had good depenencies and I never liked how they always wanted to compile in support for everything in rpm, which is one reason I liked being able to configure all that in emerge on Gentoo. Plus rpm used to have all kinds of problems with the database getting locked or corrupt. I switched to Gentoo as a workstation a while back when I tried to uninstall kernel-source and it said I couldn't because some audio library depended on it. That just shouldn't ever happen. But then I switched to Ubuntu because Gentoo development goes so fast that if you don't emerge -pv system practically every night, you end up not being able to upgrade at all.
So the point is that there are always reasons for the various package management systems being the way they are and because most people are unique, there are always going to be people who like those different features. You shouldn't poke fun of their choices until you understand them better. Hence the phrase, don't judge a man until you've walked a mile in his shoes.
Dialup networking off by default finally
on
Fedora 13 Is Out
·
· Score: 4, Insightful
While looking through the packages I noticed that Dialup Networking was NOT selected by default. Is this the first version to be that way? Kinda significant as in the end of an era.
Despite history (and having really good access to historical information), will people keep making stupid choices, voting for someone that screws them in the end and buying products that they think will make them happy but end up at the next garage sale for 90% off.
Glad he felt the desire to give time back. I think that one thing that can help out open source is to let the developer know that you liked their software. Bug reports are good but when they all pile up, it kinda makes development feel more like work. The next program I'm releasing soon (http://suso.suso.org/xulu/clide) is going to have a --warmfuzzy option that will allow the user to send a ping like feedback back to the author to let them know that they enjoy using the software. Kinda like a ring the bell if you liked the service thing. All too often open source tools are used and the developer doesn't have any feedback as to whether their software is being used successfully or not. I'd like to help change that.
Um, the generally accepted start of the Internet is by activities surrounding the start of ARPANET in the late 1960s. ARPA in its name still lives on as part of reverse DNS entries. Some people say it started in 1967, some say 1969, either way, it was much earlier than 1981 and there are a lot more protocols that are part of what we call "the Internet" than just TCP/IP, although of course not all of it is routed globally. Check your/etc/protocols file sometime, the first line says Internet (IP) protocols.
since gopher came AFTER the birth of the internet (1981) but before the widespread usage of the web (circa 1993).
I hope you don't mean the birth of the Internet was in 1981. Or maybe you typoed 1991 (when Wikipedia says gopher was released)? I thought gopher was actually a bit older than that.
I just wish people would stop holding onto FTP like they were Charlton Heston.
There are probably old procedures at companies that still are written to call for using them as backups or storage of application software and the politics at such companies are that they don't easily allow those procedures to be updated.
Slashdot Mirror
My older brother and I were both born on Tuesdays.
I knew someone would be a jackass and bring that *newer* technology up. But it will be years before its practical to use that. Its actually not that important because by the time SNI is practical, the world will be switched to IPv6 (which is a more pressing issue) and IPs will cost nothing. The only setback would be having to have lots of interfaces on a machine.
But then there are SSL customers want to have unique reverse DNS anyways, which would require seperate IPs.
Maybe its because they want more control over what clients are doing? Using SSL consumes more CPU you know, on both the client and the server side.
As a sysadmin for a web hosting provider, I see lots of these types of extensions that are written with no consideration of the server side of the equation. The people writing them seem to think that the server side has infinite CPU, RAM and bandwidth, which is just not true.
The new version has some strange behavior though. I was trying to open gqview on a remote folder (through sshfs) and found that it took forever to start up. When I did an strace of it, I found that when it starts, it does a stat on the image files with every possible image filename extension combination, which takes a lot longer over a remote link. Apparently it gathers information for the sidecar. Hopefully they will make that an optional thing.
Nevermind, I was the one that was confused. You currently have ext3 fs that are NOT on LVM. In the future, choose LVM.
Hey, IRC called, they want their asshole back.
I tried Linux LVM snapshots, but most of the servers I manage run regular partitions with ext3 file systems, so LVM snapshots will not work.
Last time I checked they worked fine. I think you mean something else by "snapshots".
Alright, I'm really really serious now. This is the last time. For sure.
This is your dialup
This is AOL
This is your dialup on AOL
*sizzle*
Any questions?
Finland To Legalize Use of Unsecured Wi-Fi
Kids, don't you know that unsecured wifi is just a gateway. Pretty soon you'll be cracking into stuff with stronger encryption. Then where will be? Sitting on the side of the road in some bad neighborhood looking asking to borrow a power jack.
What bugs me is when a company uses a name for something that doesn't make sense.
When I hear "retina display" I think what you are talking about is a system that projects an image into my retina.
and hundreds of terabytes per day. Any word on what they're using for a database back-end?
Something that you don't need to worry about using. And neither does anyone else who is "thinking about switching to whatever it is".
Apple, that acronym is already taken for an operating system.
I'm really hoping Cisco is going to sue you over that. But I won't hold my breath.
(remember the good old days when large numbers of sites would shriek for IE; but render just fine if FF was set to IE's UA string?)
The good old days? Oh, I see, you mean 5 years ago. I thought you were talking about the ancientweb when Netscape roamed the net and sites held out signs like "Explorers only, we don't serve nomads here".
> Ironically all this time I've been avoiding the preg functions because I figured they were the more likely candidates to go away.
Sorry this is short, but are you *that* dumb?
I must be.
Anyway, I remember seeing (in official docs) the note that ereg functions will occasionally be dropped like 5 years ago when I first started with PHP. And the fact that PCRE functions are *much, much* more powerful is very obvious.
Well good for you. Like I said, I've been using PHP since '97 and I don't usually have to go back to ereg page of the manual much. I know PCRE is more powerful (I do lots of Perl programming too so maybe I am dumb), but there are lots of functions like that in PHP where someone thought it would be cool to add it in, so it got included, but not all of them last and I wouldn't want to write code based on something that would get deprecated. Since ereg has been around since the beginning, I figured that it would be less likely to get deprecated.
As I brought up on the mailing list months ago when I was trying to make my case, of the books in the top 10 search results for PHP on Amazon, 5 or 6 of them, including the book by Rasmus himself (wrote PHP originally), use the ereg functions in their examples. So you can imagine that there are lots of people out there learning basic search functions out there that will be going away in the next major version. This is not good.
Sorry this is long, I could probably write a whole dissertation on my thoughts on PHP though.
I've been developing in PHP since version 2 way back in '97 and I've always felt that one of PHP's biggest downfalls is that it has a configuration file. I understand that it has more to do with its origins as an Apache module, but I can't think of many modules or programming languages that are so customizable as PHP is. Over the years this has led to different schools of programmers choosing one setting or another and chastising people who use a different setting.
Another big problem is that the core developers don't seem to get just how large the PHP community is. I found out some months ago that they were deprecating the ereg/POSIX regex set of functions in 5.3 and will be removing them in 6. I bought up on the mailing list that I think this is too quick of a time table for it being removed and that they should have it marked deprecated for at least 1 major version before removing it. Their excuse was that they really wanted to get UTF-8 support in PHP (a commendable goal) and the ereg functions weren't compatible and are also too slow. So now they are pushing the preg functions which are based on PCRE. Ironically all this time I've been avoiding the preg functions because I figured they were the more likely candidates to go away.
And I'm not alone. Many many people out there have been using ereg in lots of code over the past decade and its going to be a huge shock for them when it comes time to switch suddenly. When 50%+ of the dynamic web uses PHP, this is going to cause lots of problems over the next 5-10 years.
Yes yes, I know that there is work on a PEAR module to substitute the functionality of ereg, but my point is that the core developers seem to be in their own world and aren't thinking about the overall affects of their decisions and how far reaching they are.
I thought that was what multicast was for. Ouch! Too early.
I can tell you know that it really doesn't matter what you choose. It will eventually be replaced by something shinier and more popular/modern. Such is the way of computers and especially in the open source world. IMHO, KVM became popular because a bunch of people who weren't really using Xen decided that they liked it better and didn't give consideration to the real issues at hand. And now that they've started using KVM for real work, they are running into those issues and regret the whole thing. I've had a heavy investment in Xen since 2005 and its worked well for me and will continue to work well. But I don't really care about all that GUI management stuff, I just wrote my own. What it really comes down to is what can you live with? Do you have servers that are handling thousands/millions of transactions per day? Or are you just running a departmental webserver with just a few users? If you're doing something intense, then its worth your time to test the technologies out for yourself and see which one works better. You can test Xen vs. KVM for free.
You are joking I hope.
Having used both rpm and apt for a long time now in a sysadmin setting, I can say that both have their pluses and minuses. rpm to me has a much more professional feel to it IMHO. I really wish that dpkg had the -V flag like rpm does, I've used that more times than you probably could imagine. rpm always seems faster at finding a package name given a file path and at listing out the files in a package. On the flip side, rpm historically hasn't had good depenencies and I never liked how they always wanted to compile in support for everything in rpm, which is one reason I liked being able to configure all that in emerge on Gentoo. Plus rpm used to have all kinds of problems with the database getting locked or corrupt. I switched to Gentoo as a workstation a while back when I tried to uninstall kernel-source and it said I couldn't because some audio library depended on it. That just shouldn't ever happen. But then I switched to Ubuntu because Gentoo development goes so fast that if you don't emerge -pv system practically every night, you end up not being able to upgrade at all.
So the point is that there are always reasons for the various package management systems being the way they are and because most people are unique, there are always going to be people who like those different features. You shouldn't poke fun of their choices until you understand them better. Hence the phrase, don't judge a man until you've walked a mile in his shoes.
While looking through the packages I noticed that Dialup Networking was NOT selected by default. Is this the first version to be that way? Kinda significant as in the end of an era.
Despite history (and having really good access to historical information), will people keep making stupid choices, voting for someone that screws them in the end and buying products that they think will make them happy but end up at the next garage sale for 90% off.
Yes
Glad he felt the desire to give time back. I think that one thing that can help out open source is to let the developer know that you liked their software. Bug reports are good but when they all pile up, it kinda makes development feel more like work. The next program I'm releasing soon (http://suso.suso.org/xulu/clide) is going to have a --warmfuzzy option that will allow the user to send a ping like feedback back to the author to let them know that they enjoy using the software. Kinda like a ring the bell if you liked the service thing. All too often open source tools are used and the developer doesn't have any feedback as to whether their software is being used successfully or not. I'd like to help change that.
Um, the generally accepted start of the Internet is by activities surrounding the start of ARPANET in the late 1960s. ARPA in its name still lives on as part of reverse DNS entries. Some people say it started in 1967, some say 1969, either way, it was much earlier than 1981 and there are a lot more protocols that are part of what we call "the Internet" than just TCP/IP, although of course not all of it is routed globally. Check your /etc/protocols file sometime, the first line says Internet (IP) protocols.
since gopher came AFTER the birth of the internet (1981) but before the widespread usage of the web (circa 1993).
I hope you don't mean the birth of the Internet was in 1981. Or maybe you typoed 1991 (when Wikipedia says gopher was released)? I thought gopher was actually a bit older than that.
I just wish people would stop holding onto FTP like they were Charlton Heston.
Here's your chance!' Get yourself a piece of pre-Internet history
I think Jon Postel is rolling in his grave right now.
There are probably old procedures at companies that still are written to call for using them as backups or storage of application software and the politics at such companies are that they don't easily allow those procedures to be updated.