one extra chip, ten extra Watts, that's another twenty square inches of PV panel that needs to be facing the Sun.
Are we building a shoebox satellite or another Intelsat?
The difference between engineering for getting shit done AND having multiple failovers because FAILURE IS NOT AN OPTION and simply getting something up there in as small a package as possible thus not leaving ANY room for failovers, sophisticated power subsystems, orientation control, etc., is something like eight thousand pounds of mass.
space is not the issue, it's the way the kernel and/or apps handle memory.
Think of it like running win32 on a 64-bit chip with 8GB of RAM. It's nice having 8GB of RAM but Windws can't actually address it - it's a 32-bit kernel which means it can only address 4GB.
Some logging processes particularly those configured to write to volatile memory are constrained by default configurations (in eg. php) which *allocate* memory space for scripting in 32MB segments. This can also include the scripts themselves and the actual log file, but it can also *allocate* one segment for the script and another 32MB for the log. You could have 4GB of total usable memory, all that means to the user/developer is that there is potential for 125 discrete pre-allocated memory segments.
Fill that 32MB *allocation* and you run the risk of causing a page out of range error. If this happens in kernel space, well, that's a showstopper. If it happens in userspace, it can be anything from a minor annoyance (nice or kill the process then restart the system, all of which is doable remotely) or a complete showstopper (three fingered salute or in extreme cases, the hard power cycle. Which you ain't doing from low Earth orbit).
it's not so much the capacity of local storage, plus you have to consider that this is a system which is unlikely to be touched by a human being ever again so whatever goes up has to be physically resilient - super-compact flash storage such as micro/SD would be out, I'd go a couple generations back and use Compact Flash with slightly lower capacity to take advantage of larger dies - this is why NASA went on a shopping trip very recently for Pentium I and Pentium Pro chips for space systems, they're by virtue of their architecture, fairly hard against the environment. Back to topic, a cursory search around and it apepars that it's an issue with the kernel, sysvinit and/or php, all of which at some point or another default shared and allocated memory spaces for various purposes (including scripting and logging) to 32MB.
no, you don't. You can place something in the public domain with a restrictive licence, such as a book licence ("No photocopying"), or a limited distribution such as that attached to an NDA (as Microsoft did with the NT code it sent to China) or you can compile the code and distribute the binary with a clause in a licence agreement that says "No reverse engineering" (as Microsoft does in just about every commercial licence it's ever distributed under).
Just asking, because it seems to me as if someone wants this matter to be declared settled as is and for no good reason other than to guarantee a payout.
FYI, public family law matters are held to Chatham House rules (no discussion outside the Chamber) in Star Chambers (secret courts illegal since 1640 yet Kennth Clarke has claimed that right thinking people should accept their return - sensibly, as justice must be SEEN to be done, this has not come to pass for criminal courts YET). The public are not generally given access to the hearings nor to judgements in non-anonymised (read: nonadulterated) form.
In addition to the Chatham House Rule, there is also a clause in the Children Act 1989 (section 97) that prohibits discussion of live cases in public.
Upper House peers are appointed by the Government, hereditary peers were abolished in 1999, which was the last chance the Monarch had to veto anything. The Monarchy hasn't had a veto since 1911, and the last time the veto was actually USED was 1705.
that would have been Rose, having been bodyswapped by a skin entity (Lady Cassandra AKA the last human being in the universe) during a hospital chase in New New New New New New... New New New New New New... New New New York, New Earth.
TIA doesn't mean what I think you think it means. It's not personal knowledge of what information about you is going where, it's about the fact that every single little facet of your life, right down to how runny your shit is, is/will be being recorded and made money on for somebody else. That somebody else controls YOUR information. You don't even KNOW what and how much information about you is being gathered every second of every day and where it is going. Even trying to opt out of the system is information that someone can use. Simply not interacting with the system is probably the only way to minimise the amount of information you put out, but that might involve a sendep tank in a super secret facility that not even God knows about.
I've dealt with POS systems myself, as recently as 2007. From the ground up, and using hardware supplied by the client, I ended up with a custom NT4 build (needed for the barcode scanner, I wasn't about to drop a DOS based system on it), connected to a SuSE backend and airgapped from the Internet. The NT system ran on 16MB of RAM, and last time I looked (2013) it was still running on the same system build, same hardware and same backend. With eight simple rules the client has never had a problem with the system - he's had to replace one barcode scanner.
1. There is one USB port, and that is on the backend machine. 2. That port is for one data drive that is supplied with the system. 3. When you plug that data drive in, the system copies the data you need itself. When the red light goes out, unplug the drive. 4. When you've done with the data on the drive (ie when you've emailed it from another machine), format the drive*. 5. Nothing else ever gets plugged into that USB port. 6. No other data ever gets written onto that USB drive. 7. There is no network port on the NT box. Don't ever install one. 8. There is no network port on the backend system. Don't ever install one.
*The backend box formatted the drive on insertion anyway prior to the data write, this just gave the client some sense of interaction.
Slashdot Mirror
So much this!
csv is next to plain text as it gets. Why would you want to be complicating shit?
one extra chip, ten extra Watts, that's another twenty square inches of PV panel that needs to be facing the Sun.
Are we building a shoebox satellite or another Intelsat?
The difference between engineering for getting shit done AND having multiple failovers because FAILURE IS NOT AN OPTION and simply getting something up there in as small a package as possible thus not leaving ANY room for failovers, sophisticated power subsystems, orientation control, etc., is something like eight thousand pounds of mass.
guess what happens when you fill an NT system drive which has a dynamic swap file on it?
Genius.
CSV predates *Microsoft* by at least twelve years.
yep, this I pointed out elsewhere. I donated a LOT (actually 40) of P1/PPro boards with processors to NASA several years ago.
physical labour is always valuable, even to the noncorporeal.
space is not the issue, it's the way the kernel and/or apps handle memory.
Think of it like running win32 on a 64-bit chip with 8GB of RAM. It's nice having 8GB of RAM but Windws can't actually address it - it's a 32-bit kernel which means it can only address 4GB.
Some logging processes particularly those configured to write to volatile memory are constrained by default configurations (in eg. php) which *allocate* memory space for scripting in 32MB segments. This can also include the scripts themselves and the actual log file, but it can also *allocate* one segment for the script and another 32MB for the log. You could have 4GB of total usable memory, all that means to the user/developer is that there is potential for 125 discrete pre-allocated memory segments.
Fill that 32MB *allocation* and you run the risk of causing a page out of range error. If this happens in kernel space, well, that's a showstopper. If it happens in userspace, it can be anything from a minor annoyance (nice or kill the process then restart the system, all of which is doable remotely) or a complete showstopper (three fingered salute or in extreme cases, the hard power cycle. Which you ain't doing from low Earth orbit).
me too. This is highly confusing.
21,000 pages of plain text (assuming "average" page of 80col, 20 row), going by my head math.
yeah but the track width on a 32GB SD card would last about 3 seconds in space before a charged particle zaps across it and blows the whole deal.
it's not so much the capacity of local storage, plus you have to consider that this is a system which is unlikely to be touched by a human being ever again so whatever goes up has to be physically resilient - super-compact flash storage such as micro/SD would be out, I'd go a couple generations back and use Compact Flash with slightly lower capacity to take advantage of larger dies - this is why NASA went on a shopping trip very recently for Pentium I and Pentium Pro chips for space systems, they're by virtue of their architecture, fairly hard against the environment. Back to topic, a cursory search around and it apepars that it's an issue with the kernel, sysvinit and/or php, all of which at some point or another default shared and allocated memory spaces for various purposes (including scripting and logging) to 32MB.
no, you don't. You can place something in the public domain with a restrictive licence, such as a book licence ("No photocopying"), or a limited distribution such as that attached to an NDA (as Microsoft did with the NT code it sent to China) or you can compile the code and distribute the binary with a clause in a licence agreement that says "No reverse engineering" (as Microsoft does in just about every commercial licence it's ever distributed under).
Just asking, because it seems to me as if someone wants this matter to be declared settled as is and for no good reason other than to guarantee a payout.
if I'm streaming on my PC it's through Winamp or Windows Media Center. Otherwise, I go through my TiVO.
Thank Dolby Labs for no-hiss DACs, noise-cancelling headphone cans, ADC floor filters, echo and feedback cancellation, cellular handsfree...
I could but as is the nature of superinjunctions you won't find it on BAILII.
There are, however, news articles on the couple and their children, such as this one: http://www.dailymail.co.uk/new... and there is mention of them by name on Hansard: http://www.publications.parlia... (John Hemming at Col. 243) and by Tim Yeo at: https://www.youtube.com/watch?... (25 November 2009 Adjournment Debate, 2-part video)
FYI, public family law matters are held to Chatham House rules (no discussion outside the Chamber) in Star Chambers (secret courts illegal since 1640 yet Kennth Clarke has claimed that right thinking people should accept their return - sensibly, as justice must be SEEN to be done, this has not come to pass for criminal courts YET). The public are not generally given access to the hearings nor to judgements in non-anonymised (read: nonadulterated) form.
In addition to the Chatham House Rule, there is also a clause in the Children Act 1989 (section 97) that prohibits discussion of live cases in public.
pornography: the graphic depiction of consenting adults engaged in sexual activity.
Good enough?
uh, just no.
Upper House peers are appointed by the Government, hereditary peers were abolished in 1999, which was the last chance the Monarch had to veto anything. The Monarchy hasn't had a veto since 1911, and the last time the veto was actually USED was 1705.
feral youth underclass that lives beyond its means and assumes an air of total entitlement.
that would have been Rose, having been bodyswapped by a skin entity (Lady Cassandra AKA the last human being in the universe) during a hospital chase in New New New New New New... New New New New New New... New New New York, New Earth.
well your source desn't agree with Ital Design, or Wikipedia, or the DeLorean Museum, or Petrolicious, or Studio 434... Nice try, though.
TIA doesn't mean what I think you think it means. It's not personal knowledge of what information about you is going where, it's about the fact that every single little facet of your life, right down to how runny your shit is, is/will be being recorded and made money on for somebody else. That somebody else controls YOUR information. You don't even KNOW what and how much information about you is being gathered every second of every day and where it is going. Even trying to opt out of the system is information that someone can use. Simply not interacting with the system is probably the only way to minimise the amount of information you put out, but that might involve a sendep tank in a super secret facility that not even God knows about.
there is a perpetual injunction on it. Ask why, go on I double dog dare you.
that wasn't the question, but OK :)
I've dealt with POS systems myself, as recently as 2007. From the ground up, and using hardware supplied by the client, I ended up with a custom NT4 build (needed for the barcode scanner, I wasn't about to drop a DOS based system on it), connected to a SuSE backend and airgapped from the Internet. The NT system ran on 16MB of RAM, and last time I looked (2013) it was still running on the same system build, same hardware and same backend. With eight simple rules the client has never had a problem with the system - he's had to replace one barcode scanner.
1. There is one USB port, and that is on the backend machine.
2. That port is for one data drive that is supplied with the system.
3. When you plug that data drive in, the system copies the data you need itself. When the red light goes out, unplug the drive.
4. When you've done with the data on the drive (ie when you've emailed it from another machine), format the drive*.
5. Nothing else ever gets plugged into that USB port.
6. No other data ever gets written onto that USB drive.
7. There is no network port on the NT box. Don't ever install one.
8. There is no network port on the backend system. Don't ever install one.
*The backend box formatted the drive on insertion anyway prior to the data write, this just gave the client some sense of interaction.