Hi!
I was researching about old binary formats and did some tests.
Meantime, I was able to run sucessfully only the QMAGIC format.
Nonetheless, the OMAGIC, NMAGIC and ZMAGIC didn't work anymore.
Some time ago, I ran into similar problem, and turning off userspace
randomization was
On Sat 2014-04-19 13:37:27, Geyslan Gregório Bem wrote:
Pavel,
Thank you.
Maintainers, is there some chance to fix it or a.out is really
doomed?
There should be chance to fix it.
Do you have some idea when it stopped working?
Hi!
> Are there some potentially serious problems that I should be aware of
> if I totally disable the CONFIG_ACPI option on the X86_64 platform?
>
> Would it do harm to the hardware?
>
> Thank you for your attention to this matter.
These machines are still mostly IBM-PC compatible, so it is
On Sat 2020-07-04 21:34:36, 孙世龙 sunshilong wrote:
> Thank you for taking the time to respond to me.
>
> >These machines are still mostly IBM-PC compatible, so it is likely to
> >somehow work. You'll likely get worse power and thermal
> >management. Try it.
> It's an industrial personal computer
Hi!
> This patch series adds configurable (i.e. user-defined) block device LED
> triggers.
>
> * Triggers can be created, listed, and deleted via sysfs block class
> attributes (led_trigger_{new,list,del}).
>
> * Once created, block device LED triggers are associated with LEDs just
> like
Hi!
> +++ b/Documentation/ABI/testing/sysfs-block
> @@ -316,3 +316,19 @@ Description:
> does not complete in this time then the block driver timeout
> handler is invoked. That timeout handler can decide to retry
> the request, to fail it or to start a
On Thu 2021-07-29 12:03:04, Ian Pilcher wrote:
> On 7/29/21 3:54 AM, Pavel Machek wrote:
> > We normally have a trigger ("block device activity") which can then
> > expose parameters ("I watch for read" and "I monitor sda1").
> >
&g
