It's what micros~1 has repeatedly called themselves. In fact, one day after another crash and subsequent disk trashing by "scandisk" they called themselves micros~1, micros~2, micros~3, micros~4, micros~5 and micros~6! They all sat in a folder called progra~1.
I don't know why no one has mentioned this but printing from most devices is pretty easy, all you need is a printer with either built-in bluetooth or a host USB port (usually used for mass storage devices). Just plug in a Bluetooth dongle and it'll become visible, send it a file and it'll print. I had an HP which did this 5 years ago and I sent it files from a Symbian phone. Thanks to intents, any application which wants to send a file can queue a print job.
GitHub provides a friendly interface to view the source without having to use the repo tool and downloading the whole thing, so I'm eagerly waiting for this to get pushed there as well. Shouldn't take long.
Simply using the list of installed files to search against is not a hack, is well documented and works exactly as expected. Also, if a file wasn't installed through the package manager, dpkg will tell you as well:
$ dpkg -S weeblefrob
dpkg-query: no path found matching pattern *weeblefrob*.
$ dpkg -S/usr/bin/weeblefrob
dpkg-query: no path found matching pattern/usr/bin/weeblefrob.
Only one version of any given package may be installed at any time and to see which version is installed you can use either dpkg -l $package or apt-cache policy $package (this tells you which version would get installed, too). If you want to search for files in all packages (even those not installed), you can use apt-file.
Why would anyone drive around in their laptops? Anyone who has one of those know how quickly they die. Sure, electric cars don't produce CO2 but those batteries aren't exactly environmentally friendly on the inside, they need replacements after a certain amount of cycles and the power for the charger still needs to come from somewhere. Could be coal plants for all we know. Investments in these type of cars are useless, no one will be driving around in these kind of cars for long.
You see, petrol has been used quite successfully for the past 100 years and we need something which will last for at least another 100 years. Perhaps something like, you know, hydrogen.
I don't see how dpkg -S can't do this, why would a filename search against all packages be inadequate? Perhaps an example would be useful:
$ dpkg -S `which git`
git:/usr/bin/git
Here, `which git` returns/usr/bin/git and since packages must not overlap in the filesystem dpkg will always return one package name when given a full path. Even for example with ls, when there's also lsmod, lsof, lsusb, etc.
Zfs, no. But you can use clang and llvm just fine. For jails, there's a plethora of solutions like LXC, VZ and the more elaborate virtualisation solutions like Xen and KVM.
At best, it can register a "charm" (basically an action for the app-wide context menu) for a certain protocol, and another app can register itself as handling that protocol - then, whenever user activates that charm in app #1, app #2 is activated and parameters are passed to it.
This sounds awfully familiar... Anyway, thanks a lot for taking the time to explain win8/Metro. There's a lot of interesting stuff to learn about! A terrific day to you and whoever's with you.
Quite some time, actually. And it's awesome because replacements are FREE nowadays. No one wants them so I actually have a small surplus now of old tellies that people didn't want to keep any longer. The analogue ones are best, just flick the next or previous channel button and it instantly switches channel! That's so awesome, I laugh in the face of anyone trying to sell one of those set-top boxes with their awfully slow menus and "interactive content" which are in reality mandatory loading screens whenever you come across one of those channels.
Good one. Maybe it's better to reverse the attack, kill the controller until it power cycles. The obvious downside is that the attack would still run and could still perform other steps to take over the boot process. But then, dealing with malware has always been a game of cat-and-mouse. You take the _least_ effort measure against today's malware, and then pass on the ball. A "perfect" solution would be absolutely devastating, because 30 years into the game the malware authors continue to remain one step ahead. Supposedly TPM would solve this, but it's a very complex hardware solution. If -- or rather when -- a weakness is found, then what do we do? Longer keys? Back to the old cat-and-mouse but in hardware, no thanks.
It's what micros~1 has repeatedly called themselves. In fact, one day after another crash and subsequent disk trashing by "scandisk" they called themselves micros~1, micros~2, micros~3, micros~4, micros~5 and micros~6! They all sat in a folder called progra~1.
I don't know why no one has mentioned this but printing from most devices is pretty easy, all you need is a printer with either built-in bluetooth or a host USB port (usually used for mass storage devices). Just plug in a Bluetooth dongle and it'll become visible, send it a file and it'll print. I had an HP which did this 5 years ago and I sent it files from a Symbian phone. Thanks to intents, any application which wants to send a file can queue a print job.
I'm sure he'd manage to make an iTunes visualisation of the missile trajectories and allow the UAVs to reload using in-app purchases.
Because it's SO HARD to install joe, nano, ne or just edit files over a mounted sftp. Oh wait, you can't mount sftp in Windows.
Something to run slashdots unoptimised JavaScript at an acceptable frame rate!
GitHub provides a friendly interface to view the source without having to use the repo tool and downloading the whole thing, so I'm eagerly waiting for this to get pushed there as well. Shouldn't take long.
https://github.com/android/
Simply using the list of installed files to search against is not a hack, is well documented and works exactly as expected. Also, if a file wasn't installed through the package manager, dpkg will tell you as well:
$ dpkg -S weeblefrob /usr/bin/weeblefrob /usr/bin/weeblefrob.
dpkg-query: no path found matching pattern *weeblefrob*.
$ dpkg -S
dpkg-query: no path found matching pattern
Only one version of any given package may be installed at any time and to see which version is installed you can use either dpkg -l $package or apt-cache policy $package (this tells you which version would get installed, too). If you want to search for files in all packages (even those not installed), you can use apt-file.
Why would anyone drive around in their laptops? Anyone who has one of those know how quickly they die. Sure, electric cars don't produce CO2 but those batteries aren't exactly environmentally friendly on the inside, they need replacements after a certain amount of cycles and the power for the charger still needs to come from somewhere. Could be coal plants for all we know. Investments in these type of cars are useless, no one will be driving around in these kind of cars for long.
You see, petrol has been used quite successfully for the past 100 years and we need something which will last for at least another 100 years. Perhaps something like, you know, hydrogen.
I don't see how dpkg -S can't do this, why would a filename search against all packages be inadequate? Perhaps an example would be useful:
$ dpkg -S `which git` /usr/bin/git
git:
Here, `which git` returns /usr/bin/git and since packages must not overlap in the filesystem dpkg will always return one package name when given a full path. Even for example with ls, when there's also lsmod, lsof, lsusb, etc.
Zfs, no. But you can use clang and llvm just fine. For jails, there's a plethora of solutions like LXC, VZ and the more elaborate virtualisation solutions like Xen and KVM.
Definately no reason to switch to GNU, though.
apt has never fubar'ed any of my systems without my explicit consent. You get a warning and have to type in 'Yes, do as I say!' before shit happens.
apt is analogous to yum and dpkg is analogous to rpm. With that out of the way:
Lists files in package package and
searches for file in all packages (may list multiple packages).
It happens (I've even done so myself when I was younger), but they're just using "Anonymous" to grab attention. Not to hide their tracks.
Fins hack Finland. Nothing to see here, move along.
It lives on in the form of Android, more specifically the java. parts of the Dalvik core library.
Page shows me a bunch of irrelevant news pages. Guess what the top story is?. Hmm.
So you want to compress and decompress inside the kernel? Really?
And not a single fuck was given.
That's not how woosh works, you don't woosh your own reply.
Sure, go spend some more. When the credit card refuses, just get another one. Hell, Greece does it all the time so why can't we?
Energy could be a lot cheaper if they spent less on office furniture and sponsorships. Everyone has to tighten their belt these days, no exceptions.
At best, it can register a "charm" (basically an action for the app-wide context menu) for a certain protocol, and another app can register itself as handling that protocol - then, whenever user activates that charm in app #1, app #2 is activated and parameters are passed to it.
This sounds awfully familiar... Anyway, thanks a lot for taking the time to explain win8/Metro. There's a lot of interesting stuff to learn about!
A terrific day to you and whoever's with you.
Quite some time, actually. And it's awesome because replacements are FREE nowadays. No one wants them so I actually have a small surplus now of old tellies that people didn't want to keep any longer. The analogue ones are best, just flick the next or previous channel button and it instantly switches channel! That's so awesome, I laugh in the face of anyone trying to sell one of those set-top boxes with their awfully slow menus and "interactive content" which are in reality mandatory loading screens whenever you come across one of those channels.
Even after his death, he's going to say ONE MORE THING.
Good one. Maybe it's better to reverse the attack, kill the controller until it power cycles. The obvious downside is that the attack would still run and could still perform other steps to take over the boot process. But then, dealing with malware has always been a game of cat-and-mouse. You take the _least_ effort measure against today's malware, and then pass on the ball. A "perfect" solution would be absolutely devastating, because 30 years into the game the malware authors continue to remain one step ahead. Supposedly TPM would solve this, but it's a very complex hardware solution. If -- or rather when -- a weakness is found, then what do we do? Longer keys? Back to the old cat-and-mouse but in hardware, no thanks.