I get the impression that 90% of the world's operating systems (including Windows and commerical versions of Unix) use some code from the BSD TCP/IP stack. Of course, the BSD license is more forgiving than the GPL regarding source code, this isn't a license violation.
Of course, having everything derive code from the same source is a risk; isn't this part of the reason the ping of death was so much of an issue?
Yup, I agree. Having worked in two situations, one without a raised floor and one with, I can say that the site with raised flooring is much, much better organised in terms of cabling.
However, you do want to make sure that you don't cram too many cables under the floor; you run the risk of blocking airflow if your airconditioning is trying to dissipate heat using that gap as an airflow path. However, that's probably not an issue in a smaller room.
Aside from that, make sure you have enough power points in place and there is enough juice to power them all.
Finally, for wire ties, try to get some of the ones IBM use (at least for their Unix systems); they are basically strips of velcro which you can easily attach/detach.
Interesting; certainly the move here has been for ever-larger cinemas, usually by Virgin (now UGC). Your idea is a sound one, except that the overheads for showing on one screen are probably less than for 5 smaller ones; e.g. you only need one projectionist, you can probably get by with fewer ticket collectors etc.
I don't have any more information to hand about screen sizes over time, so I can only say what I think is happening. Perhaps its a UK phenomenon *shrug*
larger screens = more people per screen = more money. The days of the smaller cinemas seems to be numbered, with larger cinemas taking over (certainly that seems to be the case here in the UK). If we see a move from many small screens to fewer large screens, there can still be more moviegoers.
If the fewer screens have a higher fill rate (i.e. less empty seats) revenue will rise with costs staying almost the same.
Ask Citrix to give you a list of other sites where they have implemented their software successfully and visit them. Ask the local administrators (and users!) how they find it.
However, make sure that it's a site similar to the one you are on; no point getting a business as a reference site for a uni.
Finally, if things don't go as planned post-implementation, point out to Citrix that you are educating the future decision makers of the world; if they perceive that Citrix is crap, they won't buy it in years to come. That should get them to help fix your problems!
About time. The main issue people had wasn't the extension to Kerberos (which is in the Kerberos spec anyway, as I understand it), it was the fact they didn't tell anyone what it was or what it did. Then, when they did, they basically said "you can read this, but you can't use it to write anything or talk about it to anyone else". Now they've finally (it appears) opened up and said "this is how we do it; go forth and use it, but only to talk to Win2k".
Hopefully, this will help products such as Samba and pam_smb to interoperate with win2k better.
Hell, I'd be happy just to get rid of the porn spam... Pop-up ads are less of a problem now I use Konqueror and click on no for 90% of the Javashit popups (some are actually valid, e.g. where I clicked on a link to pop up an info window).
Hrm; if they really did that, it would break 99% of all mailing lists which almost never have the user's email address in the To: field. As for preventing SPAM, I'd disagree; the spam filter on hotmail does a reasonable job of clearing out most of the rubbish which gets sent to it; it isn't 100%, but it helps.
Hehe, I remember when we eventually got our AV installations done when I worked at a university. 90% of the machines were infected (mostly with Ethan), some with 2 viruses!
Of course, we were running in a fairly unregulated environment with internet access and floppies/zip drives/CD-Rs being rampant. Once we got the virus scanners in place, we managed to get a handle on it, but it shows how much you need anti-virus software in almost any organisation.
Well, one only has to go to Microsoft's web site to see Microsoft's marketing machine at work. Remember they've been selling operating systems that are allegedly more and more secure than the last, yet their latest effort still has gaps you could drive the pacific fleet through. Anything MS says, I take with a pinch, nay, a truckload of salt.
However, there have been cases where e.g. cover disks for magazines have been infected with virii, as well as some other disks. Even if you only open 'trusted' attachments, you can still get hit. Also, some viruses have been able to launch themselves despite not being explicitly opened in some cases.
SunPC accelerator???? It's only a 486 in there. Oh, and it was only supported in Solaris up to 2.5.1 with shaky support in 2.6. Anything later than that and it won't work. Also, it wasn't too hot at running anything other than DOS/Win3.x, with shaky support for Win95. It might run linux, but I'd doubt it.
On a serious note (yes, that is possible!), Pocket PC 2000 fits happily within a 16MB Flash and runs OK on my iPAQ. The memory in these phones is getting smaller; hell, Samsung had a model out that had 32MB you could store MP3s on; putting PocketPC on one of these isn't out of the question. Put in a Compact flash reader, and you can have many MB of storage (I have a 256MB Compact flash card, and they're getting bigger).
In short, there isn't a memory limitation on these. In fact, you can almost certainly save some memory by not having the text recognition; just use the number keys like you do for SMS.
This is something I think would help linux become more widely accepted, but there's more to it.
I was thinking this morning how I hadn't udpated my Apache server in a while, and wondering whether I should apt-get the latest version (Apache is kind of important for security, as it's the only open port on my system from the internet). However, I've done various tweaks to config files which would get overwritten if I accepted the Debian standard file, but I don't want to miss out on any new settings that could be important. I know I can do a diff, but that's effort I'd rather not have to go through.
This kind of situation is where a registry-like interface is useful; the install program just has to do a quick 'if-not-exist then add' to any new settings and leave the rest alone (or ask if you want an overwrite of all settings, with appropriate disclaimers).
This kind of thing is difficult to do in a flat file split into different sections (if there isn't a concept of sections, you can just tag the setting on), but trivial in a registry structure, especially when the tool (dpkg-upgrade/apt/rpm) has to handle all the different file formats. However, linux/Unix users would rebel en masse if the registry got inflicted on them (with damn good reason! I like being able to fix problems from single user mode using vi!), but some form of layer between the text file and settings may provide the best of both worlds (programmatic ease and editability). apt/dpkg/rpm could use the interface to add/modify settings without splatting your custom tweaks while still adding the new required settings.
Unfortunately, we're starting from a difficult point, with thousands of applications with many different requirements for their settings. Hopefully we can get some covergence over time.
One system running all the data over one PCI bus to some SCSI burners or
Several systems each having one burner and one server pushing all the data over one PCI bus to a NIC
In short, the data is still going over one PCI bus (on the NFS server), so PCI bus is still a bottleneck and you've just wasted time/money/simplicity on this solution.
The only way round this is to have a server class system as the NFS server; assuming you have one of these, it's probably already working as an NFS server and will probably not be available to be dedicated to working as a server for your burner-cluster. If it's not dedicated, you have contention for scarce resources (the PCI bus, CPU, memory, network bandwidth) which will likely result in coasters.
Re:The kicker's in the tail
on
SuSE 7.3 vs XP
·
· Score: 2
My pet peeve is the bit that keeps asking me to set up auto-update; you actually have to "set it up" to tell it to sod off and not bother you again.
Added to this was the hassle I had getting it to play nice with my iPAQ which ended up with me having to use a serial connection, otherwise it would corrupt the filesystem requiring a reinstall. I still have no idea why an application using USB manages to screw up a computer so easily.
Certainly I'd see value as a user of a huge corporate internet. Several times I've wanted to find information on some of our internal pages which, of course, I can't use google.com for because of the firewall. While there is an internal search engine, it's results can be less than stellar and I've missed Google.
Aside from anything else, it gives Google a revenue stream so they can continue to provide their services (web, image and usenet searches) for free; they need to find a valid business model, and hopefully this can contribute.
I personally think the best time to learn computers was the 70s; there seems to be so much folklore based on that era from things like Seymour Cray, PDPs, IBM et al. These days, we have (generally) anonymous beige boxes with commodity parts which doesn't leave much room for the folklore engendered in those days.
Despite missing these things, I'm like you in some ways that my first computing experiences predated the WWW, I've done some assembly (on a speccy, though). I worked in the computing department of a university, and some of the things I saw was worrying, not least the fact that the only language many of them was taught was Java. I'm waiting for a new era of buffer overruns and memory leaks to happen, simply because they've never been taught how. Hell, I learned C/C++ at Uni, and despite my tending to be fairly determined at letting them through, one of my programs had a small (5 bytes every second or so, IIRC, but it adds up) memory leak that went unnoticed for several months.
The US export regime is, as you say, very limiting. I work at a large company and we had to go to a US export control presentation, even though we're based in the UK. Reason being, anything which begins its life in the US is subject to US export restrictions. For example, if I took a Windows laptop I purchased in the UK to e.g. Iraq, I'd be in trouble because Windows originated in the US. Yup, it's really that bad.
Luckily, there are only a few countries in the black list (and fewer in the last 6 months; India and Pakistan were bribed for their support against Afghanistan by removal from the list, and Afghanistan is now largely off the list too). Unfortunately, we do have bases in some of those countries, mainly in the Middle East (which should be a good hint as to what type of company it is...).
Back on topic; even if you're not based in the US, PGP may become a liability if you do business in a restricted country.
The problem with basic X is that it expects to drive one X client (display) at a time. While X can run dual headed, each monitor is expected to display a different image; driving the same image to two monitors should be possible, I'm just not sure if X-windows is designed for it.
Slashdot Mirror
Of course, having everything derive code from the same source is a risk; isn't this part of the reason the ping of death was so much of an issue?
However, you do want to make sure that you don't cram too many cables under the floor; you run the risk of blocking airflow if your airconditioning is trying to dissipate heat using that gap as an airflow path. However, that's probably not an issue in a smaller room.
Aside from that, make sure you have enough power points in place and there is enough juice to power them all.
Finally, for wire ties, try to get some of the ones IBM use (at least for their Unix systems); they are basically strips of velcro which you can easily attach/detach.
I don't have any more information to hand about screen sizes over time, so I can only say what I think is happening. Perhaps its a UK phenomenon *shrug*
Will someone tell me I wasn't going mad and that really did happen?
The page you were looking for has apparently been eaten.
Sorry. I was hungry.
It been slashdotted already?
However, make sure that it's a site similar to the one you are on; no point getting a business as a reference site for a uni.
Finally, if things don't go as planned post-implementation, point out to Citrix that you are educating the future decision makers of the world; if they perceive that Citrix is crap, they won't buy it in years to come. That should get them to help fix your problems!
Hopefully, this will help products such as Samba and pam_smb to interoperate with win2k better.
The first thing I noticed about the web page was that the banner ad was for Windows XP...
- Allow all
- deny all
- ask on each
Mozilla's option of unrequested windows is what I actually want, as it's a pain to have to keep clicking on no.Hell, I'd be happy just to get rid of the porn spam... Pop-up ads are less of a problem now I use Konqueror and click on no for 90% of the Javashit popups (some are actually valid, e.g. where I clicked on a link to pop up an info window).
Hrm; if they really did that, it would break 99% of all mailing lists which almost never have the user's email address in the To: field. As for preventing SPAM, I'd disagree; the spam filter on hotmail does a reasonable job of clearing out most of the rubbish which gets sent to it; it isn't 100%, but it helps.
Of course, we were running in a fairly unregulated environment with internet access and floppies/zip drives/CD-Rs being rampant. Once we got the virus scanners in place, we managed to get a handle on it, but it shows how much you need anti-virus software in almost any organisation.
Well, one only has to go to Microsoft's web site to see Microsoft's marketing machine at work. Remember they've been selling operating systems that are allegedly more and more secure than the last, yet their latest effort still has gaps you could drive the pacific fleet through. Anything MS says, I take with a pinch, nay, a truckload of salt.
However, there have been cases where e.g. cover disks for magazines have been infected with virii, as well as some other disks. Even if you only open 'trusted' attachments, you can still get hit. Also, some viruses have been able to launch themselves despite not being explicitly opened in some cases.
SunPC accelerator???? It's only a 486 in there. Oh, and it was only supported in Solaris up to 2.5.1 with shaky support in 2.6. Anything later than that and it won't work. Also, it wasn't too hot at running anything other than DOS/Win3.x, with shaky support for Win95. It might run linux, but I'd doubt it.
In short, there isn't a memory limitation on these. In fact, you can almost certainly save some memory by not having the text recognition; just use the number keys like you do for SMS.
I was thinking this morning how I hadn't udpated my Apache server in a while, and wondering whether I should apt-get the latest version (Apache is kind of important for security, as it's the only open port on my system from the internet). However, I've done various tweaks to config files which would get overwritten if I accepted the Debian standard file, but I don't want to miss out on any new settings that could be important. I know I can do a diff, but that's effort I'd rather not have to go through.
This kind of situation is where a registry-like interface is useful; the install program just has to do a quick 'if-not-exist then add' to any new settings and leave the rest alone (or ask if you want an overwrite of all settings, with appropriate disclaimers).
This kind of thing is difficult to do in a flat file split into different sections (if there isn't a concept of sections, you can just tag the setting on), but trivial in a registry structure, especially when the tool (dpkg-upgrade/apt/rpm) has to handle all the different file formats. However, linux/Unix users would rebel en masse if the registry got inflicted on them (with damn good reason! I like being able to fix problems from single user mode using vi!), but some form of layer between the text file and settings may provide the best of both worlds (programmatic ease and editability). apt/dpkg/rpm could use the interface to add/modify settings without splatting your custom tweaks while still adding the new required settings.
Unfortunately, we're starting from a difficult point, with thousands of applications with many different requirements for their settings. Hopefully we can get some covergence over time.
- One system running all the data over one PCI bus to some SCSI burners or
- Several systems each having one burner and one server pushing all the data over one PCI bus to a NIC
In short, the data is still going over one PCI bus (on the NFS server), so PCI bus is still a bottleneck and you've just wasted time/money/simplicity on this solution.The only way round this is to have a server class system as the NFS server; assuming you have one of these, it's probably already working as an NFS server and will probably not be available to be dedicated to working as a server for your burner-cluster. If it's not dedicated, you have contention for scarce resources (the PCI bus, CPU, memory, network bandwidth) which will likely result in coasters.
Added to this was the hassle I had getting it to play nice with my iPAQ which ended up with me having to use a serial connection, otherwise it would corrupt the filesystem requiring a reinstall. I still have no idea why an application using USB manages to screw up a computer so easily.
Aside from anything else, it gives Google a revenue stream so they can continue to provide their services (web, image and usenet searches) for free; they need to find a valid business model, and hopefully this can contribute.
Despite missing these things, I'm like you in some ways that my first computing experiences predated the WWW, I've done some assembly (on a speccy, though). I worked in the computing department of a university, and some of the things I saw was worrying, not least the fact that the only language many of them was taught was Java. I'm waiting for a new era of buffer overruns and memory leaks to happen, simply because they've never been taught how. Hell, I learned C/C++ at Uni, and despite my tending to be fairly determined at letting them through, one of my programs had a small (5 bytes every second or so, IIRC, but it adds up) memory leak that went unnoticed for several months.
Luckily, there are only a few countries in the black list (and fewer in the last 6 months; India and Pakistan were bribed for their support against Afghanistan by removal from the list, and Afghanistan is now largely off the list too). Unfortunately, we do have bases in some of those countries, mainly in the Middle East (which should be a good hint as to what type of company it is...).
Back on topic; even if you're not based in the US, PGP may become a liability if you do business in a restricted country.
Remember that being on the bleeding edge is a risk, especially if it might put your data at risk.
The problem with basic X is that it expects to drive one X client (display) at a time. While X can run dual headed, each monitor is expected to display a different image; driving the same image to two monitors should be possible, I'm just not sure if X-windows is designed for it.