Actually, if I remember correctly, national airspaces stop at some particular height up - otherwise, orbit would be a massive legal headache. And it is, of course, perfectly reasonable for a given country to impose restrictions on companies while on their turf - for instance, pre-launch - and while in their airspace - like most of the launch. I can see international law having a say, I can also see there being no particular jurisdiction in space. But in any case, regulation on who can go is applicable on the ground and during launch, and so is perfectly reasonable.
This actually really doesn't need much modification, I do believe the API calls are there for setting nice levels like this - it just requires people to be using a window manager that supports it. In fact, just having checked, this would not be difficult at all for a window manager to implement given GNU C priority handling.
it's just that the people who write window managers haven't, and it's rather not the kernel's job past handling the scheduling.
Also, from this article's description of "Swap" and "paging", linux uses paging. I've seen the code for it. It even lets you define a particular file to occupy a particular region in memory via paging.
Now, I'm not entirely sure which direction you mean (for Mac or for Linux) but I'd like to note that I could essentially copy my current OS to a 64-bit machine, tweak one variable in a config file, run one command, and have a system compiled and reasonably optomized for a 64-bit machine:)
Gentoo Linux is nice. effectively a pile of automated howtos (ebuild scripts) for building your own Linux system.
It seems worthwhile to note that if I recall, one of the reasons for the old, bigger-component hardware has to do with size being related to radiation resistance; take, say, a P4 and throw it into a nice radiation bath - say, outside of the atmosphere - and I'd not be surprised if it wouldn't run a thing, and I certainly wouldn't trust it with my life. That said, it certainly doesn't preclude newer, better technology for the shuttles, it just means that they have significantly different design requirements physically, in addition to the strict software requirements. And I'd certainly like to have the multiply-redundant systems to keep a stray gamma ray from killing me by flipping a bit in the wrong place.
So basically, old hardware is, and new hardware must be, more radiation resistant than our fast land-based new systems - and this leaves everyone with much less incentive to make new technology for the purpose, especially with the old stuff functioning for the most part just fine.
Actually, if I remember correctly, national airspaces stop at some particular height up - otherwise, orbit would be a massive legal headache.
And it is, of course, perfectly reasonable for a given country to impose restrictions on companies while on their turf - for instance, pre-launch - and while in their airspace - like most of the launch.
I can see international law having a say, I can also see there being no particular jurisdiction in space. But in any case, regulation on who can go is applicable on the ground and during launch, and so is perfectly reasonable.
This actually really doesn't need much modification, I do believe the API calls are there for setting nice levels like this - it just requires people to be using a window manager that supports it. In fact, just having checked, this would not be difficult at all for a window manager to implement given GNU C priority handling.
it's just that the people who write window managers haven't, and it's rather not the kernel's job past handling the scheduling.
Also, from this article's description of "Swap" and "paging", linux uses paging. I've seen the code for it. It even lets you define a particular file to occupy a particular region in memory via paging.
Now, I'm not entirely sure which direction you mean (for Mac or for Linux) but I'd like to note that I could essentially copy my current OS to a 64-bit machine, tweak one variable in a config file, run one command, and have a system compiled and reasonably optomized for a 64-bit machine :)
Gentoo Linux is nice. effectively a pile of automated howtos (ebuild scripts) for building your own Linux system.
It seems worthwhile to note that if I recall, one of the reasons for the old, bigger-component hardware has to do with size being related to radiation resistance; take, say, a P4 and throw it into a nice radiation bath - say, outside of the atmosphere - and I'd not be surprised if it wouldn't run a thing, and I certainly wouldn't trust it with my life.
That said, it certainly doesn't preclude newer, better technology for the shuttles, it just means that they have significantly different design requirements physically, in addition to the strict software requirements. And I'd certainly like to have the multiply-redundant systems to keep a stray gamma ray from killing me by flipping a bit in the wrong place.
So basically, old hardware is, and new hardware must be, more radiation resistant than our fast land-based new systems - and this leaves everyone with much less incentive to make new technology for the purpose, especially with the old stuff functioning for the most part just fine.