It is better to reject it at SMTP level and let the sender know about the fact immediately, instead of scoring the message low and lost in the spam folder, and the sender has no idea if it reached the recipient.
Use port 587. It is the standard smtp submitter port. All mail clients don't use this port by default, but I expect them to use 587 shortly in the future.
They don't allow 3rd party battle.net server (think bnetd). It is useless to use the official battle.net server since they are too laggy from here. So, no matter how much I spend, I still can't use battle.net. I think this applies to every place where no decent Internet connection available.
- You can turn off the phone if you don't want to be distubed, the caller will get voice mailbox instead - On newer phones you can set only a few people that actually ring the phone if they call, others can be silently ignored or dropped. - GSM supports two phone numbers on one SIM card (but I don't know any service providers who offer this service), then you can give the first number to all of your friends but give the second number to only a few important people - Use SMS, treat them like email, check them whenever you have the time.
I recently sold my old T68i and bought this P800. I think it is the best PDA+phone combo available now. The others are too big, clumsy and will make people around stare at you with funny look. OK, maybe the new Kyocera is OK too, but it is not GSM.
Now the sad parts. There are a few things that I miss a lot from the old phone: - decent battery life. the old t68i can run for more than 2 days with a single charge with both irda and bluetooth always on! this thing can't survive half a day with those on. (but maybe this is because I only have it for 2 days, the battery is not at full potential yet, according to the manual. I hope so) - SMS delivery status report. P800 doesn't have this yet:(
They are: - small - getting cheaper - fast enough - already being used on PDAs, digital cameras and other gadgets
The only downside is there are at least 5 types of them! (SD, MMC, MS, CF, SM). However there are already plenty of card readers in the market that accept all of them. Some of these devices can be installed into the 3.5" enclosures that are being used for floppy drives for now. So I think it is a reasonable replacement for floppy drives. I've even seen floppy drive + 6in1 card reader combo.
Perl safe mode? What the hell is that? The only things in mind that have something to do with 'safe mode' are PHP and Windows. Maybe you meant "PHP safe mode", but that's not Perl. AFAIK, Perl doesn't have something that resembles PHP safe mode.
>Besides, I hate the greedy matches when doing >regexps in perl, and I know most people coming >from a C/C++ background will have the same >dislike.
Um, I thought almost all regexp implementations use greedy matches, including ereg_* functions in php. And maybe the first implementation that allows non greedy matches as well as greedy matches is perl. CMIIW.
1. Namespace pollution, and they are growing on each new version of PHP, fast. Example: the function str_repeat didn't exist under PHP 3, now suppose somebody created a function using that name, now when upgrading to PHP 4 his scripts no longer works, he needs to do some searching and replacing to rename his function.
2. Config file (php.ini), so that one installation of PHP could be different than another, leading to case that a PHP script works on one PHP installation but don't work on another. This is really a debugging nightmare, especially if you need to debug somebody else's scripts:)
3. Bloated. There are too many built in functions that shouldn't have been put in the core, for example functions like str_rot13 and md5_file are not useful in almost all application, yet they still consume resources. They should have been relegated to a part of PEAR or something.
4. Adding an extension to PHP is a mess. You need to recompile the whole thing if you want to add a module to PHP. You can only use either compiled C language (PHP API) or PHP language (PEAR), but not both. And of course PHP need something like perl -MCPAN -e 'install Foo':). Yes, I know about phpize and php.ini, but some module can only be installed staticly without some heavy patching.
5. PHP is not secure by default under shared hosting environment where a user doesn't trust another. Yes, I know about safe_mode, but that will get you some security at the expense of flexibility. A better approach is to use CGI mode, but this requires different treatment to PHP scripts than when using regular Apache module installation.
With almost any binary based distributions (except debian maybe), you have to wait for the next release to get updated software. For example, to update gnome under redhat 7.0 to the latest version you need to compile the thing yourself, breaking several other software in the process. Not to mention breaking your package management, forcing you to use --nodeps and/or --force almost every time using RPM. Later, after it is done, you upgrade to redhat 8.0, suddenly everything is not working, forcing you to reinstall from scratch.
On the contrary, under gentoo you can have the latest and greatest software without waiting for the next version. Everything just works and handled by package management. The only time you need to compile things without emerge is when the software you want is not yet available in gentoo portage.
I'm talking about Mandrake installer here, it has a lot more to offer than legacy windows installer.
- Ability to resize existing FAT partition - Choice between normal mode for casual users or expert mode for advanced users - Network installs, installation without CDROM drive - Installation on existing FAT partition (loopback). Can windows install itself on existing ext3 partition?
It is not a problem with RPM
on
Is RPM Doomed?
·
· Score: 4, Insightful
If you take a look at comparison of various package management (http://www.kitenet.net/~joey/pkg-comp/), it is clearly shown that RPM and DEB have almost the same set of features.
So, why installing an RPM is a more hassle that installing a DEB?
Because there are more distributions using RPM, while DEB is used almost exclusively on Debian. Yeah I know there are Progeny and Storm, but they are not very popular and are using a sizable part of Debian itself anyway. When somebody decides to make a DEB package, he will make sure his package will work with Debian (and Debian only), and he can be sure that everyone that downloads his deb will be installing it on a Debian system. But when another person decides to make an RPM package, with current situation it is a very hard job to make sure his package are compatible with various version and various distribution.
This problem will be gone if every RPM based distro are following the LSB. Even if they are all following the LSB very religiously, it is still possible to encounter this sort of problem. Say a person is using a LSB 1.0 compliant distro, but he downloads an RPM package compiled for LSB 2.0, it still won't install on his system. But still LSB is a lot better than forcing a distribution monoculture to all Linux user.
Slashdot Mirror
It is better to reject it at SMTP level and let the sender know about the fact immediately, instead of scoring the message low and lost in the spam folder, and the sender has no idea if it reached the recipient.
Tivo is not available outside US.
Use port 587. It is the standard smtp submitter port. All mail clients don't use this port by default, but I expect them to use 587 shortly in the future.
No FPS games is secure from cheating, not before the Internet's bandwidth and latency is comparable to AGP's.
I'm a Linux user attending your forum, however I haven't done any payment to SCO.
What you gonna do about that?
P800 version is here. Just finished Monkey Island 2 with it. However I wonder why it is not an official scummvm release.
They don't allow 3rd party battle.net server (think bnetd). It is useless to use the official battle.net server since they are too laggy from here. So, no matter how much I spend, I still can't use battle.net. I think this applies to every place where no decent Internet connection available.
- You can turn off the phone if you don't want to be distubed, the caller will get voice mailbox instead
- On newer phones you can set only a few people that actually ring the phone if they call, others can be silently ignored or dropped.
- GSM supports two phone numbers on one SIM card (but I don't know any service providers who offer this service), then you can give the first number to all of your friends but give the second number to only a few important people
- Use SMS, treat them like email, check them whenever you have the time.
You can't upgrade yourself. Take your phone to nearest SonyEricsson service center.
I recently sold my old T68i and bought this P800. I think it is the best PDA+phone combo available now. The others are too big, clumsy and will make people around stare at you with funny look. OK, maybe the new Kyocera is OK too, but it is not GSM.
:(
Now the sad parts. There are a few things that I miss a lot from the old phone:
- decent battery life. the old t68i can run for more than 2 days with a single charge with both irda and bluetooth always on! this thing can't survive half a day with those on. (but maybe this is because I only have it for 2 days, the battery is not at full potential yet, according to the manual. I hope so)
- SMS delivery status report. P800 doesn't have this yet
Address book is slow? Try upgrading the firmware. It solved all the speed issues for me here.
They are:
- small
- getting cheaper
- fast enough
- already being used on PDAs, digital cameras and other gadgets
The only downside is there are at least 5 types of them! (SD, MMC, MS, CF, SM). However there are already plenty of card readers in the market that accept all of them. Some of these devices can be installed into the 3.5" enclosures that are being used for floppy drives for now. So I think it is a reasonable replacement for floppy drives. I've even seen floppy drive + 6in1 card reader combo.
Perl safe mode? What the hell is that? The only things in mind that have something to do with 'safe mode' are PHP and Windows. Maybe you meant "PHP safe mode", but that's not Perl. AFAIK, Perl doesn't have something that resembles PHP safe mode.
slashdot that doesn't post too much dupes
>Besides, I hate the greedy matches when doing >regexps in perl, and I know most people coming >from a C/C++ background will have the same >dislike.
Um, I thought almost all regexp implementations use greedy matches, including ereg_* functions in php. And maybe the first implementation that allows non greedy matches as well as greedy matches is perl. CMIIW.
... there are several shortcomings:
:)
:). Yes, I know about phpize and php.ini, but some module can only be installed staticly without some heavy patching.
1. Namespace pollution, and they are growing on each new version of PHP, fast. Example: the function str_repeat didn't exist under PHP 3, now suppose somebody created a function using that name, now when upgrading to PHP 4 his scripts no longer works, he needs to do some searching and replacing to rename his function.
2. Config file (php.ini), so that one installation of PHP could be different than another, leading to case that a PHP script works on one PHP installation but don't work on another. This is really a debugging nightmare, especially if you need to debug somebody else's scripts
3. Bloated. There are too many built in functions that shouldn't have been put in the core, for example functions like str_rot13 and md5_file are not useful in almost all application, yet they still consume resources. They should have been relegated to a part of PEAR or something.
4. Adding an extension to PHP is a mess. You need to recompile the whole thing if you want to add a module to PHP. You can only use either compiled C language (PHP API) or PHP language (PEAR), but not both. And of course PHP need something like perl -MCPAN -e 'install Foo'
5. PHP is not secure by default under shared hosting environment where a user doesn't trust another. Yes, I know about safe_mode, but that will get you some security at the expense of flexibility. A better approach is to use CGI mode, but this requires different treatment to PHP scripts than when using regular Apache module installation.
OK, that's what I can think right now.
... we receive so many spam from them
With almost any binary based distributions (except debian maybe), you have to wait for the next release to get updated software. For example, to update gnome under redhat 7.0 to the latest version you need to compile the thing yourself, breaking several other software in the process. Not to mention breaking your package management, forcing you to use --nodeps and/or --force almost every time using RPM. Later, after it is done, you upgrade to redhat 8.0, suddenly everything is not working, forcing you to reinstall from scratch.
On the contrary, under gentoo you can have the latest and greatest software without waiting for the next version. Everything just works and handled by package management. The only time you need to compile things without emerge is when the software you want is not yet available in gentoo portage.
... and call it GNU/Linux when you are talking to Stallman, and call it Linux when you are talking to anybody else.
I'm talking about Mandrake installer here, it has a lot more to offer than legacy windows installer.
- Ability to resize existing FAT partition
- Choice between normal mode for casual users or expert mode for advanced users
- Network installs, installation without CDROM drive
- Installation on existing FAT partition (loopback). Can windows install itself on existing ext3 partition?
If you take a look at comparison of various package management (http://www.kitenet.net/~joey/pkg-comp/), it is clearly shown that RPM and DEB have almost the same set of features.
So, why installing an RPM is a more hassle that installing a DEB?
Because there are more distributions using RPM, while DEB is used almost exclusively on Debian. Yeah I know there are Progeny and Storm, but they are not very popular and are using a sizable part of Debian itself anyway. When somebody decides to make a DEB package, he will make sure his package will work with Debian (and Debian only), and he can be sure that everyone that downloads his deb will be installing it on a Debian system. But when another person decides to make an RPM package, with current situation it is a very hard job to make sure his package are compatible with various version and various distribution.
This problem will be gone if every RPM based distro are following the LSB. Even if they are all following the LSB very religiously, it is still possible to encounter this sort of problem. Say a person is using a LSB 1.0 compliant distro, but he downloads an RPM package compiled for LSB 2.0, it still won't install on his system. But still LSB is a lot better than forcing a distribution monoculture to all Linux user.