Which is the best when I throw in my need for text mode support. Right now, NVIDIA plus Nouveau accomplishes the requirement well (in a frame buffer way). I get direct kernel console output (can see the last kernel traceback before it died... instead of having it hidden behind X Windows which can't show it if the kernel died). It also makes the mode correctly match the monitor and supports a wide range of fonts and font sizes. Until I know an alternative that works just as well, I need to stick with NVIDIA plus Nouveau.
It was a nice idea when it came out. But we have better things these days. So we should stop trying to use JTAG directly or even indirectly, and just use better things. This is supposed to be an OPEN machine, so it should have a simple "boot from anywhere" system. So a minimal hard burned boot loader that does nothing more than find the first SD card (an external one before an internal one) with a regular bootloader on it, and loads and runs that, should be sufficient to let the owner have complete control and avoid any chance of bricking the device.
I would favor a hardware stage 0 loader, but corporates tend to not want that (because it defeats their ability to control user experience... they'd rather the device be bricked on any attempt at owner control). But the above software method would be sufficient.
This is why the "free version" should always come with logos and other trademarks removed. I think Redhat has all their logos in a separate package which can be installed or, presumably, uninstalled.
I still blame the city... just because it is too low and too near the sea. I'd have things inland more. Geographic diversity is still a good thing, too. But lower Manhattan is not a candidate for such things.
... based on random source address in UDP datagrams. The payload is still fully encrypted, and the receiving app that decodes it with its own private key can discover the context of the datagram (e.g. which network session it belongs to, and which aspect of that session it means... like which file and offset in the file). This way the party receiving the content can't see what exit node is involved.
ISPs could block forged source addresses. It's expensive. But if they do, then maybe DDoS attacks would go down.
I don't block ads. I block OFFSITE ads. This has an important LEGAL aspect. I do not want third parties to see my browsing habits. Offsite ads let them do that. But any legal action against the site I visited is weak because of the subtle difference between whether my browser is providing that info to the third party (even if under the direction of the web site I visited) or the web site itself is. If a web site inserts ads (or doesn't) and they provide information to their advertisers about what I visit, then it is that web site that is violating my privacy (unless they disclosed this practice in an obvious way and I continued on their site knowing this).
This is one reason why I say that web browsers should have a simple to use configuration setting that can allow the user to decide what action to take for various classes of offsite media. Embedded media is one class. Javascript loading is another. Following links is another. Action choices would at least include ignore, ask, proceed. The settings can be per web site with a default for TLDs and all. A list of hostname components to ignore when matching site names would start with just "www" in it (so "www.slashdot.org" is considered the same as "slashdot.org" so "adserver.slashdot.org" would be consider as onsite for "www.slashdot.org").
At least with ONSITE ads, web sites become more responsible for the abusiveness of ads shown when you visit their site. And they become more responsible when private browsing info is released to those advertisers (aside from actually clicking on the ads). FYI, I also think browsers should give users the option to suppress referring the URL when jumping to another site (or even all the time for that matter).
Ad supported web sites then get as much opportunity to be supported by ads. They just have to play responsibly to do so, and not just give away to others the easy opportunity to abuse.
This simple logic that when any SECURE page is requested then EVERYTHING must be accessed in secure mode (valid certificate required of every part if the main requested page has a valid certificate) should have been in there right from the beginning. So many of our security problems exists because people just DON'T THINK right at the beginning AND it takes so damn fscking long for the process to fix their stupidity.
They spread out. There must have been a lot of them if there are enough to kick a few electrons out of a sensor approximately 125827309434295338201372614 m away. Maybe I should get out my two slit box and see if I can figure out if it goes through both slits at the same time.
and that's before figuring out what the "people" on the smart planet of the smart solar system in that galaxy can see in all directions. Or are they only seeing stuff on one side and wondering "WTF is it all over that way?".
... 13.3 billion light years away when it emitted the light we see today, then how far away is it now based on expansion of the universe? If someone says it was closer back then, then why isn't what we see today representing a younger galaxy?
Why not hire a veteran in IT development? At my previous job where we have about 7 developers, one was a veteran. OK, he had both arms and legs. But I don't think that having them was how he was able to do development. Of course had he been severely wounded, it might take him a few seconds longer to get to the meetings.
Mailing lists are worse. The mail keeps coming in whether you want to go idle for a while or not. It floods your mailbox (need to get a separate one just for this). And for those with a need to answer support questions, it inundates new users with all the other traffic. I don't use mailing lists anymore except for closed groups such as developers of a project.
Web forums can be great if they are managed well. But it is a near full time job, 7 or 8 days a week, 33 to 36 days a month, 400 days a year.
After reading more of the site, I guess I need to take ASUS off my list of authorized manufacturers.
Manufacturers (or more specifically, their executives, which overall do tend to be stupid people) need to learn that having service manuals available is a feature that enhances their products.
And for good reason, too. Those things are VERY DANGEROUS to attempt to do any repairs on. I'll stick with the SAFE brands like ASUS, Lenovo, Panasonic, and such.
Slashdot Mirror
If the only thing it accomplishes is to piss off Republicans, then it's well worth it.
Which is the best when I throw in my need for text mode support. Right now, NVIDIA plus Nouveau accomplishes the requirement well (in a frame buffer way). I get direct kernel console output (can see the last kernel traceback before it died ... instead of having it hidden behind X Windows which can't show it if the kernel died). It also makes the mode correctly match the monitor and supports a wide range of fonts and font sizes. Until I know an alternative that works just as well, I need to stick with NVIDIA plus Nouveau.
... is so hard to do. With this machine, we don't have to, anymore.
It was a nice idea when it came out. But we have better things these days. So we should stop trying to use JTAG directly or even indirectly, and just use better things. This is supposed to be an OPEN machine, so it should have a simple "boot from anywhere" system. So a minimal hard burned boot loader that does nothing more than find the first SD card (an external one before an internal one) with a regular bootloader on it, and loads and runs that, should be sufficient to let the owner have complete control and avoid any chance of bricking the device.
I would favor a hardware stage 0 loader, but corporates tend to not want that (because it defeats their ability to control user experience ... they'd rather the device be bricked on any attempt at owner control). But the above software method would be sufficient.
How about the shim running a real bootloader ... instead of some software stack that's trying to be an OS ... ?
... for use in global warming summers to get cool air. -140C sounds terrific.
This is why the "free version" should always come with logos and other trademarks removed. I think Redhat has all their logos in a separate package which can be installed or, presumably, uninstalled.
The problem with that is that now that they have actually PAID for it, support must be provided.
... under maximum possible unimaginable storm+tidal sea level ... there, fixed it for ya.
Put data centers inland at 100 meters (or more) up to protect against even tsunami level damage (that's what's coming next for NYC).
I still blame the city ... just because it is too low and too near the sea. I'd have things inland more. Geographic diversity is still a good thing, too. But lower Manhattan is not a candidate for such things.
... based on random source address in UDP datagrams. The payload is still fully encrypted, and the receiving app that decodes it with its own private key can discover the context of the datagram (e.g. which network session it belongs to, and which aspect of that session it means ... like which file and offset in the file). This way the party receiving the content can't see what exit node is involved.
ISPs could block forged source addresses. It's expensive. But if they do, then maybe DDoS attacks would go down.
You must be new here. Anonymous Coward never reveals anything.
I don't block ads. I block OFFSITE ads. This has an important LEGAL aspect. I do not want third parties to see my browsing habits. Offsite ads let them do that. But any legal action against the site I visited is weak because of the subtle difference between whether my browser is providing that info to the third party (even if under the direction of the web site I visited) or the web site itself is. If a web site inserts ads (or doesn't) and they provide information to their advertisers about what I visit, then it is that web site that is violating my privacy (unless they disclosed this practice in an obvious way and I continued on their site knowing this).
This is one reason why I say that web browsers should have a simple to use configuration setting that can allow the user to decide what action to take for various classes of offsite media. Embedded media is one class. Javascript loading is another. Following links is another. Action choices would at least include ignore, ask, proceed. The settings can be per web site with a default for TLDs and all. A list of hostname components to ignore when matching site names would start with just "www" in it (so "www.slashdot.org" is considered the same as "slashdot.org" so "adserver.slashdot.org" would be consider as onsite for "www.slashdot.org").
At least with ONSITE ads, web sites become more responsible for the abusiveness of ads shown when you visit their site. And they become more responsible when private browsing info is released to those advertisers (aside from actually clicking on the ads). FYI, I also think browsers should give users the option to suppress referring the URL when jumping to another site (or even all the time for that matter).
Ad supported web sites then get as much opportunity to be supported by ads. They just have to play responsibly to do so, and not just give away to others the easy opportunity to abuse.
This simple logic that when any SECURE page is requested then EVERYTHING must be accessed in secure mode (valid certificate required of every part if the main requested page has a valid certificate) should have been in there right from the beginning. So many of our security problems exists because people just DON'T THINK right at the beginning AND it takes so damn fscking long for the process to fix their stupidity.
They spread out. There must have been a lot of them if there are enough to kick a few electrons out of a sensor approximately 125827309434295338201372614 m away. Maybe I should get out my two slit box and see if I can figure out if it goes through both slits at the same time.
and that's before figuring out what the "people" on the smart planet of the smart solar system in that galaxy can see in all directions. Or are they only seeing stuff on one side and wondering "WTF is it all over that way?".
... 13.3 billion light years away when it emitted the light we see today, then how far away is it now based on expansion of the universe? If someone says it was closer back then, then why isn't what we see today representing a younger galaxy?
They need to define this in the laws and stop letting people that wear funny wigs decide.
... by those funny curly white wigs they wear.
Why not hire a veteran in IT development? At my previous job where we have about 7 developers, one was a veteran. OK, he had both arms and legs. But I don't think that having them was how he was able to do development. Of course had he been severely wounded, it might take him a few seconds longer to get to the meetings.
It's less effort to just let Slashdotters decide.
Mailing lists are worse. The mail keeps coming in whether you want to go idle for a while or not. It floods your mailbox (need to get a separate one just for this). And for those with a need to answer support questions, it inundates new users with all the other traffic. I don't use mailing lists anymore except for closed groups such as developers of a project.
Web forums can be great if they are managed well. But it is a near full time job, 7 or 8 days a week, 33 to 36 days a month, 400 days a year.
After reading more of the site, I guess I need to take ASUS off my list of authorized manufacturers.
Manufacturers (or more specifically, their executives, which overall do tend to be stupid people) need to learn that having service manuals available is a feature that enhances their products.
And for good reason, too. Those things are VERY DANGEROUS to attempt to do any repairs on. I'll stick with the SAFE brands like ASUS, Lenovo, Panasonic, and such.
Don't let cars like these anywhere near the ocean or at low elevations. Problem solved.