That's a bad troll since they all use the same ports
Re:FreeBSD 5 works fine in production, here
on
FreeBSD 5.2 Released
·
· Score: 1
If you run cutting edge then expect getting cut once in a while. I just love looking at people's system that complain about stability and they have every alpha/beta/tweak etc. known to man. You can't have it both ways.
Current is for shaking out the bug and making new features. Try a release if you want to be more stable.
That's true if you want to talk about the speed at which they hit. You neglected inertia which tells us that the heavier object will have much more energy.
Hold a 2x4 in front of you and I'll shoot a 22 pistol and a 45 auto at the board. I bet the board will stop the 22 but do you want to find out if it can stop the 45 at roughly the same velocity?
That feature has been available for a long, long time on pre-winamp3 via plugins.
Personally, I wouldn't put up with the slower load times and the other annoyances I find with winamp3 but if you are happy with it, great. All the great plugins have given winamp a lot of flexibility and winamp3 just seemed to be a let down after I already had all the cool features I needed/wanted without the speed penalty, etc..
Stop spreading FUD here. NetBSD shows 17 cpu types. Yes, Linux still supports more with ia64, ppc64, s390, etc. so at least your counting is somewhat off on both sides.
Your counts totally ignore edian issues. A playstation 2 and an SGI machine can't run the same binaries even though they are both MIPS because one is big endian and the other is little endian. ARMv2 is completely different architecturally than later versions. There are many other examples.
x86-64 is still a work in progress on both platforms and so is ppc64 (it's only a couple weeks old:)) but both are in heavy development and will quickly improve on all OSes. Obscure embedded platforms like v850, cris, h8300, etc. would make me nervous to use in a large production. They are not widely developed for and what info you can dig up suggests that they could be quirky with all the compiler weirdness, etc. that hasn't been shaken out yet. I'd much rather go with a more matured platform like ARM, MIPS, M68k, etc. regardless of the OS being chosen for the application.
There are times when a platform is more mature/complete/etc. (PA-RISC on linux is better supported) but NetBSD is generally very consistent and complete across all of the 40 platforms it currently supports.
The bottom line is use the right tool for the job. If I have a PA-RISC or s390 or wanted to build a PVR then I'd probably choose Linux and I would choose a BSD for most of the rest of my needs. You might choose a little different but both are good tools and very capable.
To get back ontopic. I use pkgsrc on several platforms ( BSD, Linux, OS X, Irix) and these fixes helped out on all platforms. I love the work that everyone has put into pkgsrc and can't wait to see it grow and develop more. Someone else needs to test it on Solaris Sparc/x86 since I don't have a box currently running it.:)
It doesn't matter how fast technology is progressing. In a large environment, it takes time to get everything deployed, tested, etc. Many large companies complain about having to switch versions every 3 years let alone every year. How productive are you going to be if you just got everything regression tested on your apps, patched and basically through the deployment if you have to start all over. Many places still run DOS/Win95/Solaris2.6/etc. because of all the time and money they have into custom solutions that would take enormous resources to convert safely without bring the business to a halt.
Yes, technology should move forward but it is a tool that should conform to the users and not the other way around. I don't think this is an excuse to run unpatched software but you should be given the time to properly migrate to the next platform.
I can see why centrally managed solutions are becoming more popular with upgrades so much easier to manage at the servers. (thin clients, LSTP, citrix, terminal services, etc.)
Better be careful who you blast off the network. The more sophisticated these worms get, the harder they are to track. You could be blasting the wrong machine and now who's in the wrong?
Even if you find the right target, most blasting techniques affect routers and other users along the way.
RELENG_4 gets you the 4-Stable branch and you'll get all enhancements and security fixes. It will also get you 4.9PRE and briefly 4.9-RELEASE when it gets to that. RELENG_4_8 will get you 4.8-RELEASE plus security patches.
It sounds like you already have what you want. If you don't want uname to say 4.9PRE then hack/usr/src/sys/conf/newvers.sh to say what you want and you'll have it all.:P
Lots of things have been ported back and forth. I don't say USB is NetBSD just because the other two got it from there originally. They all share things and that is a good thing. Yes, pf is the result of the hard work of the OpenBSD developers. I used OpenBSD and pf to guard my own network but I think it's cool that Net and Free have it now too.
Now if someone could port it to OS X and Irix. heheh
Or we could go the other way. Pkgsrc is what NetBSD uses and it is available on several platforms. It is platform independant and you can check out Work In Progress before it makes it into the main tree. They have BSD, Linux, Irix, Solaris and OS X (Darwin) so far. I've been playing with it on OS X and Irix lately and it's nice to have some consistency across platforms.
Of course everyone has their own opinion but I'll stick with ports/pkgsrc for me. Perhaps there will be something I like more later but not right now.
My brother-in-law started at Dreamworks months ago and they gave him an HP with Linux pre-loaded. Search HP for Dreamworks and you will see they have been pushing it for a while now on machines other than servers.
There are several Power3 setups in the list including #4 and #5. Not bad for 375Mhz chips and you really have to wonder what the newer chips are capable of.
Mac-On-Linux uses your existing OS9/OS X partition so whatever is installed on that install will be in MOL. If you have mozilla in OS X then you will have it with MOL. It's up to you if you want to use it. Maybe you want to download something directly in your OS X evironment. It's nice to have the option
I'm not sure what your issue is but wildcards work fine on my sftp servers.
There are some shells that have worked on supporting tab completion (zsh, etc.) but that is a spotty solution at best. There are several GUI clients that support sftp and the completion issue is non-existant that way. This still only solves a small part of the issue. There was also a patch to put that functionality into OpenSSH but not much seems to have come of that (yet).
You can use the yafc ftp client since it uses sftp and has tab completion. The commands aren't exactly like ftp but it is very similar. I prefer using scp/sftp for transfering files in conjunction with the scponly shell.
I'm not saying that's what the poster is doing but it is something you could do. I probably would find a cheaper card to do this personally if I ran a video card at all in a server.
FreeBSD is no harder to install than normal debian linux, once you understand the disk terminology (rather than separate physical partitions like in the Linux world, you create one physical partition, and then create multiple slices within that on which you'll mount your filesystems).
It's true that it is pretty easy once you get the disk terminology. Unfortunately you (like so many others) have it backwards. Please check the handbook. The proper way to say it is you create a slice and then make partitions within that slice. It is similar to extended partition with logical drives inside except that a slice is seen as a primary partition to other OSes.
The 68k to PPC was 32-bit --> 32bit and made it possible with a few glitches but went relatively well for an arch change.
32bit --> 64bit isn't going to be pretty if you try to convert existing hardware. The data path(s) would be huge bottlenecks (shoving 64bit through 32bit pathways) if it could be made to work at all. It wouldn't be worth all the headaches to attmpt this but I'm sure someone will try it anyway.:)
Slashdot Mirror
That's a bad troll since they all use the same ports
If you run cutting edge then expect getting cut once in a while. I just love looking at people's system that complain about stability and they have every alpha/beta/tweak etc. known to man. You can't have it both ways.
Current is for shaking out the bug and making new features. Try a release if you want to be more stable.
That's true if you want to talk about the speed at which they hit. You neglected inertia which tells us that the heavier object will have much more energy.
Hold a 2x4 in front of you and I'll shoot a 22 pistol and a 45 auto at the board. I bet the board will stop the 22 but do you want to find out if it can stop the 45 at roughly the same velocity?
That feature has been available for a long, long time on pre-winamp3 via plugins.
Personally, I wouldn't put up with the slower load times and the other annoyances I find with winamp3 but if you are happy with it, great. All the great plugins have given winamp a lot of flexibility and winamp3 just seemed to be a let down after I already had all the cool features I needed/wanted without the speed penalty, etc..
Stop spreading FUD here. NetBSD shows 17 cpu types. Yes, Linux still supports more with ia64, ppc64, s390, etc. so at least your counting is somewhat off on both sides.
:)) but both are in heavy development and will quickly improve on all OSes. Obscure embedded platforms like v850, cris, h8300, etc. would make me nervous to use in a large production. They are not widely developed for and what info you can dig up suggests that they could be quirky with all the compiler weirdness, etc. that hasn't been shaken out yet. I'd much rather go with a more matured platform like ARM, MIPS, M68k, etc. regardless of the OS being chosen for the application.
:)
Your counts totally ignore edian issues. A playstation 2 and an SGI machine can't run the same binaries even though they are both MIPS because one is big endian and the other is little endian. ARMv2 is completely different architecturally than later versions. There are many other examples.
x86-64 is still a work in progress on both platforms and so is ppc64 (it's only a couple weeks old
There are times when a platform is more mature/complete/etc. (PA-RISC on linux is better supported) but NetBSD is generally very consistent and complete across all of the 40 platforms it currently supports.
The bottom line is use the right tool for the job. If I have a PA-RISC or s390 or wanted to build a PVR then I'd probably choose Linux and I would choose a BSD for most of the rest of my needs. You might choose a little different but both are good tools and very capable.
To get back ontopic. I use pkgsrc on several platforms ( BSD, Linux, OS X, Irix) and these fixes helped out on all platforms. I love the work that everyone has put into pkgsrc and can't wait to see it grow and develop more. Someone else needs to test it on Solaris Sparc/x86 since I don't have a box currently running it.
It doesn't matter how fast technology is progressing. In a large environment, it takes time to get everything deployed, tested, etc. Many large companies complain about having to switch versions every 3 years let alone every year. How productive are you going to be if you just got everything regression tested on your apps, patched and basically through the deployment if you have to start all over. Many places still run DOS/Win95/Solaris2.6/etc. because of all the time and money they have into custom solutions that would take enormous resources to convert safely without bring the business to a halt.
Yes, technology should move forward but it is a tool that should conform to the users and not the other way around. I don't think this is an excuse to run unpatched software but you should be given the time to properly migrate to the next platform.
I can see why centrally managed solutions are becoming more popular with upgrades so much easier to manage at the servers. (thin clients, LSTP, citrix, terminal services, etc.)
Better be careful who you blast off the network. The more sophisticated these worms get, the harder they are to track. You could be blasting the wrong machine and now who's in the wrong?
Even if you find the right target, most blasting techniques affect routers and other users along the way.
Vigilantism is just asking for trouble.
RELENG_4 gets you the 4-Stable branch and you'll get all enhancements and security fixes. It will also get you 4.9PRE and briefly 4.9-RELEASE when it gets to that. RELENG_4_8 will get you 4.8-RELEASE plus security patches.
/usr/src/sys/conf/newvers.sh to say what you want and you'll have it all. :P
It sounds like you already have what you want. If you don't want uname to say 4.9PRE then hack
Lots of things have been ported back and forth. I don't say USB is NetBSD just because the other two got it from there originally. They all share things and that is a good thing. Yes, pf is the result of the hard work of the OpenBSD developers. I used OpenBSD and pf to guard my own network but I think it's cool that Net and Free have it now too.
Now if someone could port it to OS X and Irix. heheh
Are you blocking cookies or some other thing that could be stopping this?
That would be GNU/SCO/Linux or would it be SCO/GNU/Linux?
Or we could go the other way. Pkgsrc is what NetBSD uses and it is available on several platforms. It is platform independant and you can check out Work In Progress before it makes it into the main tree. They have BSD, Linux, Irix, Solaris and OS X (Darwin) so far. I've been playing with it on OS X and Irix lately and it's nice to have some consistency across platforms.
Of course everyone has their own opinion but I'll stick with ports/pkgsrc for me. Perhaps there will be something I like more later but not right now.
My brother-in-law started at Dreamworks months ago and they gave him an HP with Linux pre-loaded. Search HP for Dreamworks and you will see they have been pushing it for a while now on machines other than servers.
You could get a 4Gb Tadpole SPARCbook but you couldn't run vmware on it.
It's kinda a bit more on the price too.
I'd have to agree that this would be the perfect upgrade for my Blue&White G3.
There are several Power3 setups in the list including #4 and #5. Not bad for 375Mhz chips and you really have to wonder what the newer chips are capable of.
I bet you quadruple your times. If you are taking a shock, I bet you don't hold the turn long enough and fly off the track.
The faster you go the more stress and vibration you should be generating.
You mean virtualized environment.
Mac-On-Linux uses your existing OS9/OS X partition so whatever is installed on that install will be in MOL. If you have mozilla in OS X then you will have it with MOL. It's up to you if you want to use it. Maybe you want to download something directly in your OS X evironment. It's nice to have the option
I'm not sure what your issue is but wildcards work fine on my sftp servers.
There are some shells that have worked on supporting tab completion (zsh, etc.) but that is a spotty solution at best. There are several GUI clients that support sftp and the completion issue is non-existant that way. This still only solves a small part of the issue. There was also a patch to put that functionality into OpenSSH but not much seems to have come of that (yet).
You can use the yafc ftp client since it uses sftp and has tab completion. The commands aren't exactly like ftp but it is very similar. I prefer using scp/sftp for transfering files in conjunction with the scponly shell.
How about ramdisk?
I'm not saying that's what the poster is doing but it is something you could do. I probably would find a cheaper card to do this personally if I ran a video card at all in a server.
I use it all the time with the BSDs but X is X so it should work for others too.
My preferred method of setting up X.
X -configure
Edit XF86Config and add monitor refresh setting, wheel mouse tweaks, default color depth
startx
This method has worked great for me. YMMV
FreeBSD is no harder to install than normal debian linux, once you understand the disk terminology (rather than separate physical partitions like in the Linux world, you create one physical partition, and then create multiple slices within that on which you'll mount your filesystems).
It's true that it is pretty easy once you get the disk terminology. Unfortunately you (like so many others) have it backwards. Please check the handbook. The proper way to say it is you create a slice and then make partitions within that slice. It is similar to extended partition with logical drives inside except that a slice is seen as a primary partition to other OSes.
It can run just fine if you are using a processor upgrade but not with the original 601 cpu.
The 68k to PPC was 32-bit --> 32bit and made it possible with a few glitches but went relatively well for an arch change.
:)
32bit --> 64bit isn't going to be pretty if you try to convert existing hardware. The data path(s) would be huge bottlenecks (shoving 64bit through 32bit pathways) if it could be made to work at all. It wouldn't be worth all the headaches to attmpt this but I'm sure someone will try it anyway.