A New Zealand computer hacker has accessed the private bank accounts of dozens of unsuspecting Kiwis, showing how easy it is to break into our internet banking system.
The hacker installed software in a Wellington internet cafe that allowed him to gather the user names and passwords of people banking online at the cafe.
Police e-crime national manager Maarten Kleintjes says he has been urging banks "for years" to introduce systems that ensure internet banking is safe, but most have been slow to respond.
Kleintjes says the problem is that internet banking access relies on a simple password "which can easily be stolen". Other countries use "two-factor identification" where, in addition to a password, the customer is given a new security password for each internet banking session.
Only two local banks, ASB and BankDirect, have a two-part identification system, where the customer is sent a text with a security password to use before transferring money.
Online bankers can follow the advice on bank websites about using anti-virus software to detect and avoid key-logging programmes on home computers, but the software provides no guarantees. Kleintjes says it is "unreasonable and unrealistic" to expect all customers to know how to do this. He said the banks should introduce safe systems that have been available overseas for years.
Apache's Ant may be worth a look. It handles dependancies very well. It may not be so great with timing of jobs (cron + ant?) or handling jobs running in parallel (ant plus a custom 'run task in the background'?).
Web _servers_ have been ussing SSL certs since day one. They are commonplace for web users verifying the identity of a web server.
But they can also be used for identifying the identify of the web _user_.
If client certs were more widely used by users, and more widely supported by web sites (a catch-22 situation I guess) then we can bypass usernames/passwords completely if we wish. And rely on the client certificate for identification purposes.
Then I won't have to keep coming up with unique passwords for the billion and one web sites I am a member at.
Speaking of which:
echo "example.com:mypassword" | md5sum | cut -c1-6
That will generate a unique password per site. And you still let you easily recall what password you used. s/example.com/whateverdomainyouaresigningonat/ig
None of the topics mentioned in the review really seem to be Linux specific. Why not just call it "Java Application Development" (period, no "on Linux")?
There are some things that I think would be worth covering though, in a book about Java/Linux. Particularly for someone coming from a development of an app in a Windows Environment to deploying an app in a production Linux environment. Since often they will know all they need about Java. But won't be very familiar with Linux. And may not know the best way to do things in a 'Linux' way.
Some examples...
Init Scripts: Setting up init scripts to stop/start your Java services (e.g. getting tomcat to run on boot up). That differs a lot from how you'd do it with services on Windows.
Permissions I: Often on windows things will be run as root/Administrator. On Linux the better way is to have Java services run as a non-root user. e.g. run Tomcat as tomcat not root. There are some implications to this. e.g. you an unprivileged user cannot listen on addresses with sub-1000 port numbers. The solution is something like iptables or mod_jk2.
Permissions II: Another permissions issue (that I see crop up a lot with people moving from the Windows dev machine to one of our Linux servers for productions) is file permissions. Users being not being able to read/write config/data files that they had been able to see/use well enough on Windows. i.e. a paragraph on the almighty chown -R would be handy.
Command Lines: A page or two on running things from the command line would be a great thing. Often people working on Linux servers are doing so remotely. And won't have a GUI. And often they are only familiar with launching their app from the ide. So knowing about 'java' and 'javac' would be handy. And mention the need for colons between dir names not semi-colons. e.g. java -cp/myclasses:/3rdparty.jar mainclass.
Automating Tasks Users moving from a windows/dev environment to a Linux/production environment would also be well served by a page or two on automation tools. e.g. using ant to automate the process of getting code out of CVS and deploying it. e.g. cron for automating the process of running Java jobs on a regular basis.
As has been pointed out, the fee RedHat charge is for their services. If you can forgo the services and the brand there are freely (beer/speech) available alternatives.
Whitebox Enterprise Linux 3 has taken the RedHat Enterprise Linux 3 source RPMs, removed trademarks and RedHat artwork and produced their own binary distro of those source RPMs. The resulting server is RHEL3 RPM compatible (which is useful if you are using 3rd party repositories.
WhiteBox Linux release erratta fixes following on from any that RH release. So the distro is kept up to date (using up2date or yum, or if you're like me, apt)
There are other projects with RHEL3 based distros as well.
I don't get this. It will just lead to a general slowing down of the services running on the Internet.
Where do people think that email is being sent from? A dedicated server that the user has somewhere dedicated solely to sending email?
Most people will be sending email through their ISP. And ISP that was coping with x,xxxx,xxxx pieces of email a day will suddenly now have to redo their email architecture to cope with the extra computational cost involved.
Other people send email using their webhost. The extra computational overhead will now mean that other users on the server will not have as much CPU to utilise and their sites will work more slowly.
What needs to happen is for more emails to be signed with people's digital identities. Then someone needs to create a network/service where people can 'vouch' for certain identities. Thus you can build up an associative trust network. And you spam filter can may a more informed judgement call on the validatily of the email it processes.
UML runs insidethe host OS and thus is a security risk.
Correction: It runs in user space (hence the name). It can run as any user (i.e. doesn't have to be root). So that makes it as much (or less) of a security risk as any other program: perl, apache, postfix, etc.
I manage a lot of servers remotely. I started out using the hardware RAID support on my server's mobos. But there were issues with that.
First, it was hard getting Linux driver support (I think drivers were available, but it was a matter of downloading them. And I don't beleive they worked on the 2.6 kernel's I used).
Then the RAID setup required BIOS settings. When you only have remote access to a server (and no KVM-o-IP) that means you need to work through a tech at the DC. Not, umm, ideal.
And finally, there was the issue of 'what if I need to move these disks to a different server'. One that doesn't have the same raid controller. Well, it wouldn't work.
Anyway, I ended up using software raid. I've used it now on a few dozen servers. And I'm really happy with it. Performance seems fine, albeit I'm not using it in really IO critical environments like a dedicated database server. In in 99% of cases I'd now use software raid in preference to hardware raid.
What follows are a few tips I'd like to pass along that may be a help with getting a software raid setup...
If you get the chance setup RAID on / and/boot via your OS installer (on a new system). Doing it afterwards is a real pain.
Build RAID support and RAID1,and RAID5 into the kernel (not as modules). You'll need that if you boot from a raid1 boot partition. Note: if you are using RAID5 you'll need RAID1 built in (since I beleive in the event of a failed disk the raid personaility swaps from RAID5 to RAID1).
With a 2.6 kernel build I've been getting "no raid1 module" errors at the make install phase when building with a RAID-ed / or/boot. The 'fix' is to compile the RAID support you need into the kernel (not as modules) then run:/sbin/mkinitrd -f/boot/initrd-2.6.8.1.img 2.6.8.1 --omit-raid-modules (substituting your kernel image name/version).
Every now and then I've had the kernel spit a drive out a raid array. I've found that sometimes the kernel may be being overly cautious. You can often raidhotremove then raidhotadd it back again. And you may never see a problem again. If you do, it probably really is time to replace the disk.
Rebuilding a RAID array goes smoothly. It happens in the background when the Linux machine is in multi user mode. The md code rebuild guarantees a minimum rebuild rate. From memory it takes about an hour or two to do a 200GB RAID1 array.
You can see the RAID rebuild status in/proc/mdstat. I run a very simple script to check the RAID status each day and send out an email if it is broken.
If you are using a RAID-ed/boot, grab the latest lilo since IIRC it has better RAID support than what is in the distros I use.
Hard drive-wise I've been happy with Seagate Barracudas. I've had to replace a few failed Western Digital drives. (Just my recommendation from experience, it could just have been good/bad luck on my part).
One neat trick with Software raid is that your drives don't have to be the same size. You do RAID on partitions. And your raid array sizes itself according to the smallest common denominator in the array.
Tip: always create a bit of spare space on any device you are RAID-ing. e.g. a 4GB swap partition. Then if you have a drive fail and it needs to be replaced, and your replacement varies in size slightly you'll still be able to use it. Not all 40/120/200GB drives are created with equal sizes:).
In summary: Software RAID=good. Decent performance. I've had no real kernel bugs with it. No need for BIOS access. Easy to move drives between servers. Easy to monitor failures. Non-intrusive/minimal downtime when recovering a failed devi
[IPMI] will allow for remote monitoring, management and recovery capabilities, regardless of the status or health of the server. New features such as enhanced security using leading authentication and encryption mechanisms in combination with remote console viewing will help reduce operational risk by securing remote operations. Moreover, with IPMI being implemented at the silicon level, it deals with monitoring basic server parts such as power supplies, fans, voltage and temperature irrespective of the type or health of the CPU or operating system.
Supermicro have a sub $60 daughter card (for their motherboards only) that seems to offer console access over LAN using 'out of band' bandwidth, whatever that is. There are othervendors offering 'IPMI-enabled' mobos as well.
Has anyone used one of these? I'm considering getting a few cards for the SuperMicros I colocate. And wonder how the seial console access works over a WAN, getting it setup, securing it, etc. And what support, server-side, there is for IPMI based monitoring.
UML support was added to the 2.6 kernel a while back (2.5.34 in Sep 2002).
Since then the mainline kernel has lagged behind the latest UML releases on user-mode-linux.sf.net.
Over the 2.6.8 to 2.6.9 timeframe BlaisorBlade (aka Paolo Giarrusso) has worked with Andrew Morton and Jeff Dike to bring the mainline kernel up to date with the latest UML changes. (To the point where the 2.6.9 kernel is more current than the latest 'official' UML release). I would guess this was the biggest, in terms of lines of code, change in 2.6.9. Most of the changes just touched the 'um' architecture though. So changes are pretty isolated from other arch-es.
This may be of interest to you if you run chrooted systems anywhere (UML may be more secure). Or if you are a kernel hacker (so much easier to debug things that run in a user process).
There are over 30 subversion related packages in the install, including updated to db4, apr, httpd and mod_ssl. Moreover, it seems that (at least the last install I tried) these other packages must be updated as a pre-requisite for installing svn.
I want to use svn+ssh. I don't need any of the apache/webdav integration. And having to move to a custom version of apache is going to be a show-stopper for a lot of people.
And does anyone know why vanilla berkely db is not good enough for svn?
svn developers: please release a client/server that can be installed without requiring updates to other packages (unless you need that specific, extra, functionality). Do this and you'll increase the svn adoption rate.
By having an open proxy anyone can send/receive data via your proxy server (duh). There are implications: e.g. I've seen someone's server bandwidth being used to serve images in a spam (pr0n) email.
If you don't want people hiving off your bandwidth and potentially using your server's bandwidth for puposes you wouldn't normally approve of, then consider controlling your proxy access.
Why is the poster doing this as a JSR? They are requests for Java specifications. Things that go into the core of the Java platform.
The problem domain for this proposed JSR is primarily in the business world, not the technical one. I can't see any one proposal getting sufficient backing from a wide enough user group. Certainly not enough for everyone to agree on a useful technical implementation of this.
There are better ways to handle this...
I suggest that the poster goes and sets up his own web service to do this (banks and investment firms offer such services already). And work out an open API.
It's good you've found a problem that interests you. But please don't feel you need to go and clutter up my platform of choice to go solving it.
Each athlete signs an agreement to abide by the Olympic committee's code of conduct. That code includes these clauses:
Under no circumstances, throughout the duration of the Olympic Games, may any athlete, coach, official, press attaché or any other accredited participant be accredited or act as a journalist or in any other media capacity.
will not use or authorize the use of the following items for the purpose of trade, without the prior written consent of the USOC (which consent shall not be unreasonably withheld) (1) photographs, films or videos of myself in the apparel or equipment provided by the USOC for the Games; (2) any Games medals; and (3) photographs, films or videos of myself with any Games medals;
Reading that I would argue that posting on a blog is not acting in the capacity of a journalist. Nor in a 'media capacity'
I would also argue that that posting photos of myself or my medals is not for the 'purpose of trade'.
Then I'd ensure that those photos were taken by friends and family, and not me.
And then the USOC will not 'reasonably withhold' permission for me using those images.
Anyway, it'd be fun to see one of the athletes test this. 'Course, it's not my medal on the line;)
He has 3000 people using the service. It would have taken them some time to sign up. He would have had ample info about the cost of running the service and providing support for it.
I can only deduce that Mr. Winer's personal circumstances have changed dramatically, and that is what is causing the problem.
And I agree with the grandfather post. There should have been warning about the service change. He should have let people know they had a week or a month to move things off the server. There would have been an increase in server load. But it would have been manageable.
In addition to the NX work, Intel this year released prototype wireless network support--albeit nearly a year after full-fledged support was available in Windows.
Don't they mean that Linux had new wireless network support this year? Or was Intel the wireless support contributor for Linux? Either way I think the sentence is in error. Though I'm probably just being pendantic for raising it.
Of course even one hour's root access is enough to enable the user to add their own back doors (e.g. other user accounts). So you'd also need to monitor things like/etc/passwd and shadow file changes carefully. And tools like Chkrootkit can help.
But definitely, ssh public/private key authentication is the way to go.
[quote]when they "feel there is a market need."[/quote]
Um, the market would be me. The time would be now.
Bring it on!
I see that the new dual core opterons are supposed to be pin compatible with existing boards. So that makes it possible to get an AMD server today, and in xx months time pop in a new chip and turn it from a single proc to a dual proc (dual -> quad?) server. Nice. Now if only memory prices would come down some more. So I can enjoy a 16GB quad proc server for under $3K.
Why are we still using passwords for everything? I must sign up for 2 or 3 new websites a week. I've been using the Internet for 32 years now. So that means I've signed up for just over 8388640 passwords.
Would someone please write a browser plugin that will enable public/private key authentication using my ssh agent
Because they were the first to support subqueries
on
Why MySQL Grew So Fast
·
· Score: 5, Insightful
Not.
MySQL has always been fast. That is probably why most people use it.
MySQL has also been easy to manage (e.g. move database files from one subdirectory to another and the tables have also moved). That kind of simplicity brings tears to the eyes of an Oracle admin. There are a few options you can tune and teak, but by and large it just works out of the box (er, RPMs).
And of course the reason it has been so popular is that it has been so popular. If you get my circular drift. People use it because there is a lot of documentation about it. Perl and PHP pretty much always have the MySQL libraries so it can be used on web sites, etc.
Speacking of those subqueries, what's up with the delay getting 4.1 out from alpha to beta/gamma/production. I want to start using it. And 4.1 has been out in alpha for over a year now. Not to mention new development is already proceeding with the 5.0 release.
Instead of VMWare consider User Mode Linux. It is free. And it permits you to run many virtual servers per host server. e.g. you should be able to run 16-30 virtual servers per 3Ghz Intel proc. Just make sure you have enough memory (4GB is handy).
With Copy on Write file systems you can prep up your testing environment. Snapshot it. Run your tests. Then nuke the resulting file systems and start again. Being able to start a test run with the whole file system in the state it was in when you started (without having to roll back individual files and databases) is very convenient.
That's right. People can sue Debian for problems with Sun's software. People can also sue Debian if there is a bug in the Linux kernel. Or a problem with any other software package.
Debian distribute their distro. They are responsible for it.
No doubt they 'pass the buck' with their own clause indemnifying themselves in the event of any problem.
Slashdot Mirror
And in a not unrelated story: Hacker takes 3 minutes to get your cash
--
Linux VPS Hosting you can Bank On
Apache's Ant may be worth a look. It handles dependancies very well. It may not be so great with timing of jobs (cron + ant?) or handling jobs running in parallel (ant plus a custom 'run task in the background'?).
--
Linux Server + Persistence => Solution
Web _servers_ have been ussing SSL certs since day one. They are commonplace for web users verifying the identity of a web server.
But they can also be used for identifying the identify of the web _user_.
If client certs were more widely used by users, and more widely supported by web sites (a catch-22 situation I guess) then we can bypass usernames/passwords completely if we wish. And rely on the client certificate for identification purposes.
Then I won't have to keep coming up with unique passwords for the billion and one web sites I am a member at.
Speaking of which:
echo "example.com:mypassword" | md5sum | cut -c1-6
That will generate a unique password per site. And you still let you easily recall what password you used. s/example.com/whateverdomainyouaresigningonat/ig
--
Linux VPS Hosting for geeks
None of the topics mentioned in the review really seem to be Linux specific. Why not just call it "Java Application Development" (period, no "on Linux")?
There are some things that I think would be worth covering though, in a book about Java/Linux. Particularly for someone coming from a development of an app in a Windows Environment to deploying an app in a production Linux environment. Since often they will know all they need about Java. But won't be very familiar with Linux. And may not know the best way to do things in a 'Linux' way.
Some examples...
Init Scripts: Setting up init scripts to stop/start your Java services (e.g. getting tomcat to run on boot up). That differs a lot from how you'd do it with services on Windows.
Permissions I: Often on windows things will be run as root/Administrator. On Linux the better way is to have Java services run as a non-root user. e.g. run Tomcat as tomcat not root. There are some implications to this. e.g. you an unprivileged user cannot listen on addresses with sub-1000 port numbers. The solution is something like iptables or mod_jk2.
Permissions II: Another permissions issue (that I see crop up a lot with people moving from the Windows dev machine to one of our Linux servers for productions) is file permissions. Users being not being able to read/write config/data files that they had been able to see/use well enough on Windows. i.e. a paragraph on the almighty chown -R would be handy.
Command Lines: A page or two on running things from the command line would be a great thing. Often people working on Linux servers are doing so remotely. And won't have a GUI. And often they are only familiar with launching their app from the ide. So knowing about 'java' and 'javac' would be handy. And mention the need for colons between dir names not semi-colons. e.g. java -cp /myclasses:/3rdparty.jar mainclass.
Automating Tasks Users moving from a windows/dev environment to a Linux/production environment would also be well served by a page or two on automation tools. e.g. using ant to automate the process of getting code out of CVS and deploying it. e.g. cron for automating the process of running Java jobs on a regular basis.
--
Java Hosting on Linux, Simple Enough Even For Windows Users
You have to feel sorry for Declan. The duty team roster has him doing a 24 hour shift today.
--
Linux VPS Hosting with 24x7 support, so we know how he feels.
If you need to figure out where in the sky those planets are, try kstars. It is one of the better planetarium-type apps out there.
Now if only the 'summer' skies over New Zealand would clear for a night, I can actually make use of my shiny new telescope.
--
Stellar Linux VPS Hosting
As has been pointed out, the fee RedHat charge is for their services. If you can forgo the services and the brand there are freely (beer/speech) available alternatives.
Whitebox Enterprise Linux 3 has taken the RedHat Enterprise Linux 3 source RPMs, removed trademarks and RedHat artwork and produced their own binary distro of those source RPMs. The resulting server is RHEL3 RPM compatible (which is useful if you are using 3rd party repositories.
WhiteBox Linux release erratta fixes following on from any that RH release. So the distro is kept up to date (using up2date or yum, or if you're like me, apt)
There are other projects with RHEL3 based distros as well.
Don't you just love the GPL?
--
WBEL3 Based Linux VPSs
I don't get this. It will just lead to a general slowing down of the services running on the Internet.
Where do people think that email is being sent from? A dedicated server that the user has somewhere dedicated solely to sending email?
Most people will be sending email through their ISP. And ISP that was coping with x,xxxx,xxxx pieces of email a day will suddenly now have to redo their email architecture to cope with the extra computational cost involved.
Other people send email using their webhost. The extra computational overhead will now mean that other users on the server will not have as much CPU to utilise and their sites will work more slowly.
What needs to happen is for more emails to be signed with people's digital identities. Then someone needs to create a network/service where people can 'vouch' for certain identities. Thus you can build up an associative trust network. And you spam filter can may a more informed judgement call on the validatily of the email it processes.
--
Fast Linux Virtual Private Servers
Correction: It runs in user space (hence the name). It can run as any user (i.e. doesn't have to be root). So that makes it as much (or less) of a security risk as any other program: perl, apache, postfix, etc.
I manage a lot of servers remotely. I started out using the hardware RAID support on my server's mobos. But there were issues with that.
First, it was hard getting Linux driver support (I think drivers were available, but it was a matter of downloading them. And I don't beleive they worked on the 2.6 kernel's I used).
Then the RAID setup required BIOS settings. When you only have remote access to a server (and no KVM-o-IP) that means you need to work through a tech at the DC. Not, umm, ideal.
And finally, there was the issue of 'what if I need to move these disks to a different server'. One that doesn't have the same raid controller. Well, it wouldn't work.
Anyway, I ended up using software raid. I've used it now on a few dozen servers. And I'm really happy with it. Performance seems fine, albeit I'm not using it in really IO critical environments like a dedicated database server. In in 99% of cases I'd now use software raid in preference to hardware raid.
What follows are a few tips I'd like to pass along that may be a help with getting a software raid setup...
If you get the chance setup RAID on / and /boot via your OS installer (on a new system). Doing it afterwards is a real pain.
Build RAID support and RAID1,and RAID5 into the kernel (not as modules). You'll need that if you boot from a raid1 boot partition. Note: if you are using RAID5 you'll need RAID1 built in (since I beleive in the event of a failed disk the raid personaility swaps from RAID5 to RAID1).
With a 2.6 kernel build I've been getting "no raid1 module" errors at the make install phase when building with a RAID-ed / or /boot. The 'fix' is to compile the RAID support you need into the kernel (not as modules) then run: /sbin/mkinitrd -f /boot/initrd-2.6.8.1.img 2.6.8.1 --omit-raid-modules (substituting your kernel image name/version).
Every now and then I've had the kernel spit a drive out a raid array. I've found that sometimes the kernel may be being overly cautious. You can often raidhotremove then raidhotadd it back again. And you may never see a problem again. If you do, it probably really is time to replace the disk.
Rebuilding a RAID array goes smoothly. It happens in the background when the Linux machine is in multi user mode. The md code rebuild guarantees a minimum rebuild rate. From memory it takes about an hour or two to do a 200GB RAID1 array.
You can see the RAID rebuild status in /proc/mdstat. I run a very simple script to check the RAID status each day and send out an email if it is broken.
If you are using a RAID-ed /boot, grab the latest lilo since IIRC it has better RAID support than what is in the distros I use.
Hard drive-wise I've been happy with Seagate Barracudas. I've had to replace a few failed Western Digital drives. (Just my recommendation from experience, it could just have been good/bad luck on my part).
One neat trick with Software raid is that your drives don't have to be the same size. You do RAID on partitions. And your raid array sizes itself according to the smallest common denominator in the array.
Tip: always create a bit of spare space on any device you are RAID-ing. e.g. a 4GB swap partition. Then if you have a drive fail and it needs to be replaced, and your replacement varies in size slightly you'll still be able to use it. Not all 40/120/200GB drives are created with equal sizes :).
In summary: Software RAID=good. Decent performance. I've had no real kernel bugs with it. No need for BIOS access. Easy to move drives between servers. Easy to monitor failures. Non-intrusive/minimal downtime when recovering a failed devi
How about IPMI?
The marketing blurb goes something like this:
Supermicro have a sub $60 daughter card (for their motherboards only) that seems to offer console access over LAN using 'out of band' bandwidth, whatever that is. There are other vendors offering 'IPMI-enabled' mobos as well.
Has anyone used one of these? I'm considering getting a few cards for the SuperMicros I colocate. And wonder how the seial console access works over a WAN, getting it setup, securing it, etc. And what support, server-side, there is for IPMI based monitoring.
--
Hosting VPS servers with SSH console access
UML support was added to the 2.6 kernel a while back (2.5.34 in Sep 2002).
Since then the mainline kernel has lagged behind the latest UML releases on user-mode-linux.sf.net.
Over the 2.6.8 to 2.6.9 timeframe BlaisorBlade (aka Paolo Giarrusso) has worked with Andrew Morton and Jeff Dike to bring the mainline kernel up to date with the latest UML changes. (To the point where the 2.6.9 kernel is more current than the latest 'official' UML release). I would guess this was the biggest, in terms of lines of code, change in 2.6.9. Most of the changes just touched the 'um' architecture though. So changes are pretty isolated from other arch-es.
This may be of interest to you if you run chrooted systems anywhere (UML may be more secure). Or if you are a kernel hacker (so much easier to debug things that run in a user process).
--
(UML-based) VPS Hosting
There are over 30 subversion related packages in the install, including updated to db4, apr, httpd and mod_ssl. Moreover, it seems that (at least the last install I tried) these other packages must be updated as a pre-requisite for installing svn.
I want to use svn+ssh. I don't need any of the apache/webdav integration. And having to move to a custom version of apache is going to be a show-stopper for a lot of people.
And does anyone know why vanilla berkely db is not good enough for svn?
svn developers: please release a client/server that can be installed without requiring updates to other packages (unless you need that specific, extra, functionality). Do this and you'll increase the svn adoption rate.
--
CVS & SVN Hosting
By having an open proxy anyone can send/receive data via your proxy server (duh). There are implications: e.g. I've seen someone's server bandwidth being used to serve images in a spam (pr0n) email.
If you don't want people hiving off your bandwidth and potentially using your server's bandwidth for puposes you wouldn't normally approve of, then consider controlling your proxy access.
--
Use your VPS proxy powers for the powers of good
Why is the poster doing this as a JSR? They are requests for Java specifications. Things that go into the core of the Java platform.
The problem domain for this proposed JSR is primarily in the business world, not the technical one. I can't see any one proposal getting sufficient backing from a wide enough user group. Certainly not enough for everyone to agree on a useful technical implementation of this.
There are better ways to handle this...
I suggest that the poster goes and sets up his own web service to do this (banks and investment firms offer such services already). And work out an open API.
It's good you've found a problem that interests you. But please don't feel you need to go and clutter up my platform of choice to go solving it.
--
Java Hosting on Linux VPSs
Each athlete signs an agreement to abide by the Olympic committee's code of conduct. That code includes these clauses:
Reading that I would argue that posting on a blog is not acting in the capacity of a journalist. Nor in a 'media capacity'
I would also argue that that posting photos of myself or my medals is not for the 'purpose of trade'.
Then I'd ensure that those photos were taken by friends and family, and not me.
And then the USOC will not 'reasonably withhold' permission for me using those images.
Anyway, it'd be fun to see one of the athletes test this. 'Course, it's not my medal on the line ;)
--
Gold Medal Winning Linux VPS Hosting
He has 3000 people using the service. It would have taken them some time to sign up. He would have had ample info about the cost of running the service and providing support for it.
I can only deduce that Mr. Winer's personal circumstances have changed dramatically, and that is what is causing the problem.
And I agree with the grandfather post. There should have been warning about the service change. He should have let people know they had a week or a month to move things off the server. There would have been an increase in server load. But it would have been manageable.
---
Yep, we host blogs
http://zdnet.com.com/2100-1104-5227102.html:
Don't they mean that Linux had new wireless network support this year? Or was Intel the wireless support contributor for Linux? Either way I think the sentence is in error. Though I'm probably just being pendantic for raising it.
---
VPS Hosting
Of course even one hour's root access is enough to enable the user to add their own back doors (e.g. other user accounts). So you'd also need to monitor things like /etc/passwd and shadow file changes carefully. And tools like Chkrootkit can help.
But definitely, ssh public/private key authentication is the way to go.
- Linux VPS Hosting
[quote]when they "feel there is a market need."[/quote]
Um, the market would be me. The time would be now.
Bring it on!
I see that the new dual core opterons are supposed to be pin compatible with existing boards. So that makes it possible to get an AMD server today, and in xx months time pop in a new chip and turn it from a single proc to a dual proc (dual -> quad?) server. Nice. Now if only memory prices would come down some more. So I can enjoy a 16GB quad proc server for under $3K.
ADV: VPS Hosting on the fastest chips we can findWhy are we still using passwords for everything? I must sign up for 2 or 3 new websites a week. I've been using the Internet for 32 years now. So that means I've signed up for just over 8388640 passwords.
Would someone please write a browser plugin that will enable public/private key authentication using my ssh agent
. Then I just need to tell them my public key.ADV: Get your own 'no password required' virtual private server
Not.
MySQL has always been fast. That is probably why most people use it.
MySQL has also been easy to manage (e.g. move database files from one subdirectory to another and the tables have also moved). That kind of simplicity brings tears to the eyes of an Oracle admin. There are a few options you can tune and teak, but by and large it just works out of the box (er, RPMs).
And of course the reason it has been so popular is that it has been so popular. If you get my circular drift. People use it because there is a lot of documentation about it. Perl and PHP pretty much always have the MySQL libraries so it can be used on web sites, etc.
Speacking of those subqueries, what's up with the delay getting 4.1 out from alpha to beta/gamma/production. I want to start using it. And 4.1 has been out in alpha for over a year now. Not to mention new development is already proceeding with the 5.0 release.
- Run the latest and greatest alpha MySQL database on your own VPS
For those who don't like 1000 line changelogs, here are the changes that Marcello specifically mentioned on his -pre and -rc lkml postings:
- Run Your own Linux Server on The Latest and Greatest 2.4 or 2.6 Kernel
Instead of VMWare consider User Mode Linux. It is free. And it permits you to run many virtual servers per host server. e.g. you should be able to run 16-30 virtual servers per 3Ghz Intel proc. Just make sure you have enough memory (4GB is handy).
With Copy on Write file systems you can prep up your testing environment. Snapshot it. Run your tests. Then nuke the resulting file systems and start again. Being able to start a test run with the whole file system in the state it was in when you started (without having to roll back individual files and databases) is very convenient.
- UML-based VPS Hosting
That's right. People can sue Debian for problems with Sun's software. People can also sue Debian if there is a bug in the Linux kernel. Or a problem with any other software package.
Debian distribute their distro. They are responsible for it.
No doubt they 'pass the buck' with their own clause indemnifying themselves in the event of any problem.