Re: [gentoo-user] Noah's ArK

2019-11-17 Thread Andrew Udvare


> On 2019-11-17, at 06:19, Helmut Jarausch  wrote:
> 
> I'd like to "preserve" some packages which do require components I don't like 
> to have "regularly" installed any more like some depending on Python2 or are 
> 32bit.

For Python (any version), use wheels:

https://pypi.org/project/wheel/

You would have to clone/download the packages yourself, and then run `python 
setup.py bdist_wheel` for them. This also ensures that you preserve compiled 
versions of the packages. As time goes on, these older packages will not 
compile against newer GCC/Clang versions without patches. Most popular packages 
already have wheels, although they might not have every combination built.

For anything else, if it doesn't need stuff like hardware 3D acceleration, use 
a VM that retains the packages you want. This also leads into...

If it does need native hardware access, use chroot and/or disk images (that you 
would boot into separately). I prefer to try and create barriers between 
'production' (what I use everyday) and one-off things like some old game that 
only supports 32-bit.

You probably want to retain old versions of toolchains (GCC, binutils, Clang, 
LLVM, etc) in case you need to build anything (built with -mtune not -march). 
Use Gentoo's binpkg format for this with the `qpkg` command. These packages can 
also be deployed on non-Gentoo systems but YMMV as you look for dependencies.

I tend to keep old hardware around for running old software. You might want to 
do the same.

A lot of older (much older) x86 support is being added to MAME everyday. This 
may come in handy in the future to preserve older versions of Linux distros and 
apps/games.

https://www.mamedev.org/releases/whatsnew_0215.txt (search 386)

Andrew


[gentoo-user] app-emulation/libguestfs-1.38.6 fails to build

2019-11-17 Thread Hartmut Figge
Greetings,

attempting to build libguestfs-1.38.6  failed. build.log showed a
complaint about not able to find libcrypt.so.2. So I looked for that
one. It was in /lib/xcrypt and /lib64/xcrypt, but not in /lib or /lib64.

It was defined so: libcrypt.so.2 -> libcrypt.so.2.0.0

So I copied the so.2.0.0 to the missing places and created symlinks for
so.2. Then the emerge of libguestfs succeeded.

Seems to be a bug. Is it one?

Hartmut




Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread Dale
Håkon Alstadheim wrote:
>
> Den 17.11.2019 12:22, skrev Dale:
>> Neil Bothwick wrote:
>>> On Sun, 17 Nov 2019 10:50:08 +, Mick wrote:
>>>
> Magic SysReq would probably have helped in those situations. ext3/4
> only journal metadata by default, you can specify a mount option to
> also journal data but it impacts performance.
 When X hangs and I lose the keyboard to the extent where neither
 Ctrl+Alt+F1, or Ctrl+Alt+Del would work, I will use ssh to connect
 remotely and stop the hanging process or restat the X server.  If ssh
 is also not working, I use the magic SysReq sequence to stop
 processes,
 sync the disks and reboot, or shutdown.  I don't recall losing data in
 such cases, although when I have time I run fsck with Live media just
 in case.
>>> I do the same, but configuring the power button to do a clean shutdown
>>> may like life simpler.
>>>
>>>
>>
>> I don't have a second system to ssh in with but if I did, that's what
>> I'd do as well, or try at least.
>
> You can get ssh clients for Android or Apple iOS. Just remember to set
> up with public keys before you need them, and also give them a static
> address if the box in question is router/dhcp-server.
>
>
>
>


I guess I could do that from my cell phone then.  It's a Samsung android
thingy.  Hey, I can talk with it and text.  Everything else is gravy. 
Good but not really necessary.  lol  Thing is, if it is slow, it will
likely be slow when I ssh in as well.  Most of the time, it will move,
just very, very slowly. 

Dale

:-)  :-) 



Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread n952162

On 11/17/19 16:06, Mick wrote:

You keep top-posting and inverting the logical Q/A flow of this thread ...

On Sunday, 17 November 2019 12:53:51 GMT n952162 wrote:

Ah, now I see.  Yes, in that respect, that is, if you don't have a
chance to get /forcefsck written.

Running fsck manually with various options and then trying to recover various
superblock locations could get you farther than simply running fsck in an
accepting fashion.


Have you had any experience with this?  I spent days search for that
superblock once, even writing a pgm to search for the magic number,
after working with dump2fs, and never got anywhere.  I'd sure like to
hear that somebody had success with it.



Needless to say, you would not try this on the original partition, but a
backup image you can create with ddrescue and friends. In any case, running
fsck.ext4 -n (or -E nodiscard) should not cause any fs losses, unless the
disk/hardware is faulty.  Hence working on a backup image is the safest
option.



Thanks for the tip about ddrescue.




Re: [gentoo-user] Noah's ArK

2019-11-17 Thread Mickaël Bucas
Hi

If it's only for Python 2 packages, it's easy with "virtualenv", I've
done it for multiple independent Trac installations, each with a
different set of plugins. You still have to keep the Python 2 base
packages on the system.

If it's for 32 bits packages, you can isolate them in a chroot,
following the Gentoo guide [1]. I remember having used this to install
binary packages like Adobe Acrobat when multilib was supported only
with 32bits binary packages (I don't remember what made it necessary).
If the chroot is mounted at system start, you can define menu actions
in your desktop environment to launch commands inside of the chroot.
You may need to bind mount your home directory or other data
directories inside of the chroot to make them visible to these
programs.

The chroot solution can also work for Python 2, and it's not limited
to 32 bits : you can create the chroot with a 64 bits stage 3 tarball.

Best regards

Mickaël Bucas
[1] https://wiki.gentoo.org/wiki/Project:AMD64/32-bit_Chroot_Guide

Le dim. 17 nov. 2019 à 12:20, Helmut Jarausch  a écrit :
>
> Hi,
>
> I'd like to "preserve" some packages which do require components I
> don't like to have "regularly" installed any more like some depending
> on Python2 or are 32bit.
>
> Is there a means to build a "mini binary system" where I can put these?
>
> Many thanks for a hint,
> Helmut



[gentoo-user] Re: problem with named restarting

2019-11-17 Thread Ian Zimmerman
On 2019-11-17 06:00, John Covici wrote:

> On Sat, 16 Nov 2019 16:12:53 -0500,
> Ian Zimmerman wrote:
> > 
> > It looks like a bug.  Can you build with -g and without stripping?
> 
> Hmmm,  I have split-debug on and I thought I had -g in my flags, but I
> will check.  Does it go in CFLAGS .etc?

-g has to be on in both CFLAGS and LDFLAGS, I think.  Stripping is
disabled with FEATURES=" ... nostrip ..." in make.conf, I hope it also
works as an environment variable but I am not positive.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.



[gentoo-user] Re: daemon fox?

2019-11-17 Thread Ian Zimmerman
On 2019-11-17 10:28, Mick wrote:

> On Saturday, 16 November 2019 17:24:34 GMT Ian Zimmerman wrote:

> > Is it possible to start firefox as a daemon, ie. without opening any
> > windows, and later connect to it as needed to display URLs?  I have
> > in mind something similar to "emacs --daemon".
> 
> Wouldn't such a behaviour have security implications?  Can you have a
> daemon spawning new window instances, but each one sandboxed
> separately?

I don't see how it would be different, security-wise, from opening a new
window in a fully-fledged graphical fox when I run "firefox $URL" from
the command line, and that's what happens now.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.



Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread Håkon Alstadheim



Den 17.11.2019 12:22, skrev Dale:

Neil Bothwick wrote:

On Sun, 17 Nov 2019 10:50:08 +, Mick wrote:


Magic SysReq would probably have helped in those situations. ext3/4
only journal metadata by default, you can specify a mount option to
also journal data but it impacts performance.

When X hangs and I lose the keyboard to the extent where neither
Ctrl+Alt+F1, or Ctrl+Alt+Del would work, I will use ssh to connect
remotely and stop the hanging process or restat the X server.  If ssh
is also not working, I use the magic SysReq sequence to stop processes,
sync the disks and reboot, or shutdown.  I don't recall losing data in
such cases, although when I have time I run fsck with Live media just
in case.

I do the same, but configuring the power button to do a clean shutdown
may like life simpler.




I don't have a second system to ssh in with but if I did, that's what
I'd do as well, or try at least.


You can get ssh clients for Android or Apple iOS. Just remember to set 
up with public keys before you need them, and also give them a static 
address if the box in question is router/dhcp-server.






Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread Mick
You keep top-posting and inverting the logical Q/A flow of this thread ...

On Sunday, 17 November 2019 12:53:51 GMT n952162 wrote:
> Ah, now I see.  Yes, in that respect, that is, if you don't have a
> chance to get /forcefsck written.

Running fsck manually with various options and then trying to recover various 
superblock locations could get you farther than simply running fsck in an 
accepting fashion.

If fsck.ext4 shows up "bad magic number", you can run dumpe2fs on the 
partition and grep for "superblock" to find the location of both primary and 
backup superblocks of the corrupted fs.  Then you can 'e2fsck -b  /
dev/sdaX' for each '' superblock location and and try mount it 
thereafter to see if you can access your files.  With a bit of luck at least 
one of the supeblocks will work recovering most of the data previously saved 
on this fs.

Needless to say, you would not try this on the original partition, but a 
backup image you can create with ddrescue and friends. In any case, running 
fsck.ext4 -n (or -E nodiscard) should not cause any fs losses, unless the 
disk/hardware is faulty.  Hence working on a backup image is the safest 
option.

-- 
Regards,

Mick

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread n952162

Ah, now I see.  Yes, in that respect, that is, if you don't have a
chance to get /forcefsck written.


On 11/17/19 13:23, Dale wrote:

n952162 wrote:

How do you fix a broken filesystem, other than letting fsck have its way
with it?

The point is, don't touch it until you do.  If you boot a system from
the hard drive, it has to be touched and you don't know what condition
it is in when your system has crashed in some way.  If you boot some
other way and run fsck on it, then it is just like it was when your
system went down.  It hasn't even been mounted read only at that point.
If you have data that can be replaced, it isn't a big deal.  You can
restore from backups, fetch data again that was lost or whatever.
However, if you want to minimize that risk, don't touch the drive(s)
until fsck has done its job.

Dale

:-)  :-)






Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread Dale
n952162 wrote:
> How do you fix a broken filesystem, other than letting fsck have its way
> with it?

The point is, don't touch it until you do.  If you boot a system from
the hard drive, it has to be touched and you don't know what condition
it is in when your system has crashed in some way.  If you boot some
other way and run fsck on it, then it is just like it was when your
system went down.  It hasn't even been mounted read only at that point. 
If you have data that can be replaced, it isn't a big deal.  You can
restore from backups, fetch data again that was lost or whatever. 
However, if you want to minimize that risk, don't touch the drive(s)
until fsck has done its job. 

Dale

:-)  :-) 



Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread n952162

How do you fix a broken filesystem, other than letting fsck have its way
with it?


On 11/17/19 12:39, Dale wrote:

n952162 wrote:

I'm not seeing how doing an fsck from a live cd helps.


Generally speaking, something ends up being mounted rw and if it isn't
clean, that can cause issues that may have been fixable before to become
issues that are no longer fixable.  This is why a lot of people put a
rescue system in /boot and add it to their boot loader menu.  Sadly, my
/boot partition isn't large enough or I'd do that as well.  If you have
data you don't want to lose and no backups or only older backups, you
don't want to do anything that involves risk.  Booting something else
and fixing file system errors is the safest way.








Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread Dale
n952162 wrote:
> I'm not seeing how doing an fsck from a live cd helps.
>

Generally speaking, something ends up being mounted rw and if it isn't
clean, that can cause issues that may have been fixable before to become
issues that are no longer fixable.  This is why a lot of people put a
rescue system in /boot and add it to their boot loader menu.  Sadly, my
/boot partition isn't large enough or I'd do that as well.  If you have
data you don't want to lose and no backups or only older backups, you
don't want to do anything that involves risk.  Booting something else
and fixing file system errors is the safest way. 

The bad thing about this, you won't know how serious it is until you do
something the wrong way.  It's like me the other day.  I'm susceptible
to catching infections.  My neighbor has the sniffles and is prone to
sinus infections.  I went for a visit without realizing it could be
contagious.  He ended up going to the Doctor and finding out he has
strep.  Now I'm sitting here watching for symptoms and at the ready to
go to the Doctor at the first sign.  Looking back, I should have waited
until he was no longer sick.  The other thing is, I can't turn the clock
back.  I've been exposed to something I can catch now.  I need to
remember that when he has the sniffles, treat it as a worst case
scenario until I know it isn't.  If you do the wrong thing with a file
system, you will learn about it after it is irreparable if not careful. 
Treat it as bad and you are less likely to do damage.  Treat it as if it
isn't and you could lose data if it ends up having a problem that must
be fixed first.  It's about trying to limit the risk. 

Dale

:-)  :-) 



Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread n952162

On 11/17/19 10:51, Neil Bothwick wrote:

On Sun, 17 Nov 2019 10:27:48 +0100, n952162 wrote:


There's a million ways a system can hang.  Acpi is a mechanism for
shipping kernel events to user space.  If user space isn't working, acpi
won't work.   I think.

But if it's just X that is locked, then ACPI could be used to rescue the
system in a less aggressive way than Magic SysReq.




Right.  That's the point.  X runs in user-space.



Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread n952162






On 11/17/19 11:30, Neil Bothwick wrote:

Please don't top-post on this list.

Magic SysReq would probably have helped in those situations. ext3/4 only
journal metadata by default, you can specify a mount option to also
journal data but it impacts performance.




I wonder how often NTFS loses data.



Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread n952162

I'm not seeing how doing an fsck from a live cd helps.


On 11/17/19 11:50, Mick wrote:

On Sunday, 17 November 2019 10:30:49 GMT Neil Bothwick wrote:

On Sun, 17 Nov 2019 11:21:18 +0100, n952162 wrote:

(in fact, that's exactly the situation that I've been confronted with
and have turned to this mailing list to help me with: X locked up, my
power-button was unresponsive so I had to force it down (holding the
power key down for 30 seconds), and on reboot TWO filesystems had to be
rebuilt by fsck, with substantial loss of organization and of data
(despite both being ext3/4 journaling filesystems - I just don't
understand that!) )

As has been mentioned before holding the power button down until the system
powers off is equal to a hard shutdown.  No write caches are flushed, no data
is synced to disk and any writes could be left in mid air resulting in a
messed up fs.  I always boot with a LiveUSB/CD and perform a fsck without
mounting any drives, before I will try to boot the system normally again.

If you lose power while the system is idle and no write operations are in
process/waiting, then you may well have no loss of data as a result.



Please don't top-post on this list.

Magic SysReq would probably have helped in those situations. ext3/4 only
journal metadata by default, you can specify a mount option to also
journal data but it impacts performance.

When X hangs and I lose the keyboard to the extent where neither Ctrl+Alt+F1,
or Ctrl+Alt+Del would work, I will use ssh to connect remotely and stop the
hanging process or restat the X server.  If ssh is also not working, I use the
magic SysReq sequence to stop processes, sync the disks and reboot, or
shutdown.  I don't recall losing data in such cases, although when I have time
I run fsck with Live media just in case.





Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread Dale
Neil Bothwick wrote:
> On Sun, 17 Nov 2019 10:50:08 +, Mick wrote:
>
>>> Magic SysReq would probably have helped in those situations. ext3/4
>>> only journal metadata by default, you can specify a mount option to
>>> also journal data but it impacts performance.  
>> When X hangs and I lose the keyboard to the extent where neither
>> Ctrl+Alt+F1, or Ctrl+Alt+Del would work, I will use ssh to connect
>> remotely and stop the hanging process or restat the X server.  If ssh
>> is also not working, I use the magic SysReq sequence to stop processes,
>> sync the disks and reboot, or shutdown.  I don't recall losing data in
>> such cases, although when I have time I run fsck with Live media just
>> in case.
> I do the same, but configuring the power button to do a clean shutdown
> may like life simpler.
>
>


I don't have a second system to ssh in with but if I did, that's what
I'd do as well, or try at least.  Recently, I only run into trouble when
a tab on Firefox goes memory hungry.  Most of the time it grows slowly
and I'm able to catch it.  I just close Firefox or just kill that one
process, which kills Tree Style Tab add-on.  Once it consumes my memory
and most of my swap, it gets pretty unresponsive.  o_O  I think I did a
thread on this a while back.  I'm not sure which to blame, the add-on or
Firefox or even both. 

It's rare that I have a hard lock up that is the kernel itself.  Usually
I can get something to work given enough time.  Still, given the amount
of data I have stored here, some irreplaceable, options are nice.  Good
clean options are really nice. 

Dale

:-)  :-) 



[gentoo-user] Noah's ArK

2019-11-17 Thread Helmut Jarausch

Hi,

I'd like to "preserve" some packages which do require components I  
don't like to have "regularly" installed any more like some depending  
on Python2 or are 32bit.


Is there a means to build a "mini binary system" where I can put these?

Many thanks for a hint,
Helmut


Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread Neil Bothwick
On Sun, 17 Nov 2019 10:50:08 +, Mick wrote:

> > Magic SysReq would probably have helped in those situations. ext3/4
> > only journal metadata by default, you can specify a mount option to
> > also journal data but it impacts performance.  
> 
> When X hangs and I lose the keyboard to the extent where neither
> Ctrl+Alt+F1, or Ctrl+Alt+Del would work, I will use ssh to connect
> remotely and stop the hanging process or restat the X server.  If ssh
> is also not working, I use the magic SysReq sequence to stop processes,
> sync the disks and reboot, or shutdown.  I don't recall losing data in
> such cases, although when I have time I run fsck with Live media just
> in case.

I do the same, but configuring the power button to do a clean shutdown
may like life simpler.


-- 
Neil Bothwick

Top Oxymorons Number 21: "Now, then ..."


pgpdKYhFL0ZiW.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] Re: problem with named restarting

2019-11-17 Thread John Covici
On Sat, 16 Nov 2019 16:12:53 -0500,
Ian Zimmerman wrote:
> 
> On 2019-09-19 14:23, John Covici wrote:
> 
> > Sep 18 22:25:45 ccs.covici.com named[4207]: resolver.c:4917: 
> > INSIST(dns_name_issubdomain(>name, >domain)) failed, back trace
> > Sep 18 22:25:45 ccs.covici.com named[4207]: #0 0x5645afbc0610 in ??
> > Sep 18 22:25:45 ccs.covici.com named[4207]: #1 0x7f64def5037a in ??
> > Sep 18 22:25:45 ccs.covici.com named[4207]: #2 0x7f64df10168b in ??
> > Sep 18 22:25:45 ccs.covici.com named[4207]: #3 0x7f64df1030cc in ??
> > Sep 18 22:25:45 ccs.covici.com named[4207]: #4 0x7f64df108025 in ??
> > Sep 18 22:25:45 ccs.covici.com named[4207]: #5 0x7f64df109a44 in ??
> > Sep 18 22:25:45 ccs.covici.com named[4207]: #6 0x7f64def6e329 in ??
> > Sep 18 22:25:45 ccs.covici.com named[4207]: #7 0x7f64de8aa448 in ??
> > Sep 18 22:25:45 ccs.covici.com named[4207]: #8 0x7f64de5ff62f in ??
> > Sep 18 22:25:45 ccs.covici.com named[4207]: exiting (due to assertion 
> > failure)
> > 
> 
> It looks like a bug.  Can you build with -g and without stripping?

Hmmm,  I have split-debug on and I thought I had -g in my flags, but I
will check.  Does it go in CFLAGS .etc?


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com



Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread Mick
On Sunday, 17 November 2019 10:30:49 GMT Neil Bothwick wrote:
> On Sun, 17 Nov 2019 11:21:18 +0100, n952162 wrote:
> > (in fact, that's exactly the situation that I've been confronted with
> > and have turned to this mailing list to help me with: X locked up, my
> > power-button was unresponsive so I had to force it down (holding the
> > power key down for 30 seconds), and on reboot TWO filesystems had to be
> > rebuilt by fsck, with substantial loss of organization and of data
> > (despite both being ext3/4 journaling filesystems - I just don't
> > understand that!) )

As has been mentioned before holding the power button down until the system 
powers off is equal to a hard shutdown.  No write caches are flushed, no data 
is synced to disk and any writes could be left in mid air resulting in a 
messed up fs.  I always boot with a LiveUSB/CD and perform a fsck without 
mounting any drives, before I will try to boot the system normally again.

If you lose power while the system is idle and no write operations are in 
process/waiting, then you may well have no loss of data as a result.


> Please don't top-post on this list.
> 
> Magic SysReq would probably have helped in those situations. ext3/4 only
> journal metadata by default, you can specify a mount option to also
> journal data but it impacts performance.

When X hangs and I lose the keyboard to the extent where neither Ctrl+Alt+F1, 
or Ctrl+Alt+Del would work, I will use ssh to connect remotely and stop the 
hanging process or restat the X server.  If ssh is also not working, I use the 
magic SysReq sequence to stop processes, sync the disks and reboot, or 
shutdown.  I don't recall losing data in such cases, although when I have time 
I run fsck with Live media just in case.
-- 
Regards,

Mick

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread Dale
Neil Bothwick wrote:
> On Sun, 17 Nov 2019 10:27:48 +0100, n952162 wrote:
>
>> There's a million ways a system can hang.  Acpi is a mechanism for
>> shipping kernel events to user space.  If user space isn't working, acpi
>> won't work.   I think.
> But if it's just X that is locked, then ACPI could be used to rescue the
> system in a less aggressive way than Magic SysReq.
>
>

That's why I was asking.  I've had to use Magic SysPeq a few times but
thought this would/might be a better option in most cases but maybe not
all.  I will say this, the magic works in every case I can recall so
far.  On occasion when I reboot, it does the fsck and all but nothing
appears to be lost.  Most of the time, it shuts down pretty clean.  I've
got to where when I do the sync part, I give it a minute or so to
finish.  That seems to give it time to sync and unmount cleanly.

As is the usual tho, this depends on the type of lockup I guess. 

Dale

:-)  :-) 



Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread Neil Bothwick
On Sun, 17 Nov 2019 11:21:18 +0100, n952162 wrote:

> (in fact, that's exactly the situation that I've been confronted with
> and have turned to this mailing list to help me with: X locked up, my
> power-button was unresponsive so I had to force it down (holding the
> power key down for 30 seconds), and on reboot TWO filesystems had to be
> rebuilt by fsck, with substantial loss of organization and of data
> (despite both being ext3/4 journaling filesystems - I just don't
> understand that!) )

Please don't top-post on this list.

Magic SysReq would probably have helped in those situations. ext3/4 only
journal metadata by default, you can specify a mount option to also
journal data but it impacts performance.


-- 
Neil Bothwick

Documentation: (n.) a novel sold with software, designed to entertain the
   operator during episodes of bugs or glitches.


pgp9kZqzpAHy_.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] daemon fox?

2019-11-17 Thread Mick
On Saturday, 16 November 2019 17:24:34 GMT Ian Zimmerman wrote:
> Is it possible to start firefox as a daemon, ie. without opening any
> windows, and later connect to it as needed to display URLs?  I have in
> mind something similar to "emacs --daemon".

Wouldn't such a behaviour have security implications?  Can you have a daemon 
spawning new window instances, but each one sandboxed separately?


> I had some hopes for "firefox --headless" but that doesn't do what I
> want: later "firefox $URL" will not connect to the running one but will
> start a new instance.

I think this is by design, but I am not well versed in the innards of FF.

-- 
Regards,

Mick

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread n952162

(in fact, that's exactly the situation that I've been confronted with
and have turned to this mailing list to help me with: X locked up, my
power-button was unresponsive so I had to force it down (holding the
power key down for 30 seconds), and on reboot TWO filesystems had to be
rebuilt by fsck, with substantial loss of organization and of data
(despite both being ext3/4 journaling filesystems - I just don't
understand that!) )


On 11/17/19 10:35, n952162 wrote:


And - although hitting the power button will clear up some situations,
if your hard disk is having trouble closing, shutdown() probably won't
be able to get around that and the shutdown will be like a power-loss
shutdown.


On 11/17/19 10:27, n952162 wrote:


There's a million ways a system can hang.  Acpi is a mechanism for
shipping kernel events to user space.  If user space isn't working,
acpi won't work.   I think.


On 11/17/19 09:44, Dale wrote:

n952162 wrote:


okay, I've got ...

acpid is, by default, not in the default openrc run list   [:blush:]

Solution:

    sudo rc-update add acpid


On 11/13/19 07:48, n952162 wrote:


I've reinstalled gentoo from the gentoo repository and now my
power button doesn't do a shutdown anymore.  What do I have to do
to have it issue a shutdown?  This is an openrc system.

I have this, but it doesn't work:

$ cat  /etc/acpi/events/powerbtn
event=button[ /]power.*
action=/sbin/poweroff

On a different gentoo system I have, I have just the one line, the
action line, in that file and the power-button works fine (whether
there's causation there or not, I have no idea :-) )

I generally do /not/ press the power button while in my window
manager, but first when I've logged off. Since that wasn't
working, I tried inside my window manager ... I got a just a
couple of lines that looked like they came from shutdown(), but
too few (couldn't read them).

Then, on startup, the filesystems needed fscking!!!






I have a related question.  If for some reason my system is locked
up, keyboard isn't working or something like that.  If I have acpi
in working order, would hitting the power button be seen or would
that be the same as the keyboard and not be recognized?  Anyone have
experience on this or read about someone who has ran into this?

Just curious but if the answer is yes, I may work on setting this up
and working.

Thanks.

Dale

:-)  :-)








Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread n952162

And - although hitting the power button will clear up some situations,
if your hard disk is having trouble closing, shutdown() probably won't
be able to get around that and the shutdown will be like a power-loss
shutdown.


On 11/17/19 10:27, n952162 wrote:


There's a million ways a system can hang.  Acpi is a mechanism for
shipping kernel events to user space.  If user space isn't working,
acpi won't work.   I think.


On 11/17/19 09:44, Dale wrote:

n952162 wrote:


okay, I've got ...

acpid is, by default, not in the default openrc run list [:blush:]

Solution:

    sudo rc-update add acpid


On 11/13/19 07:48, n952162 wrote:


I've reinstalled gentoo from the gentoo repository and now my power
button doesn't do a shutdown anymore.  What do I have to do to have
it issue a shutdown?  This is an openrc system.

I have this, but it doesn't work:

$ cat  /etc/acpi/events/powerbtn
event=button[ /]power.*
action=/sbin/poweroff

On a different gentoo system I have, I have just the one line, the
action line, in that file and the power-button works fine (whether
there's causation there or not, I have no idea :-) )

I generally do /not/ press the power button while in my window
manager, but first when I've logged off. Since that wasn't working,
I tried inside my window manager ... I got a just a couple of lines
that looked like they came from shutdown(), but too few (couldn't
read them).

Then, on startup, the filesystems needed fscking!!!






I have a related question.  If for some reason my system is locked
up, keyboard isn't working or something like that.  If I have acpi in
working order, would hitting the power button be seen or would that
be the same as the keyboard and not be recognized?  Anyone have
experience on this or read about someone who has ran into this?

Just curious but if the answer is yes, I may work on setting this up
and working.

Thanks.

Dale

:-)  :-)






Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread Neil Bothwick
On Sun, 17 Nov 2019 10:27:48 +0100, n952162 wrote:

> There's a million ways a system can hang.  Acpi is a mechanism for
> shipping kernel events to user space.  If user space isn't working, acpi
> won't work.   I think.

But if it's just X that is locked, then ACPI could be used to rescue the
system in a less aggressive way than Magic SysReq.

> On 11/17/19 09:44, Dale wrote:
> > n952162 wrote:  
> >>
> >> okay, I've got ...
> >>
> >> acpid is, by default, not in the default openrc run list [:blush:]
> >>
> >> Solution:
> >>
> >>     sudo rc-update add acpid
> >>
> >>
> >> On 11/13/19 07:48, n952162 wrote:  
> >>>
> >>> I've reinstalled gentoo from the gentoo repository and now my power
> >>> button doesn't do a shutdown anymore.  What do I have to do to have
> >>> it issue a shutdown?  This is an openrc system.
> >>>
> >>> I have this, but it doesn't work:
> >>>
> >>> $ cat  /etc/acpi/events/powerbtn
> >>> event=button[ /]power.*
> >>> action=/sbin/poweroff
> >>>
> >>> On a different gentoo system I have, I have just the one line, the
> >>> action line, in that file and the power-button works fine (whether
> >>> there's causation there or not, I have no idea :-) )
> >>>
> >>> I generally do /not/ press the power button while in my window
> >>> manager, but first when I've logged off.  Since that wasn't working,
> >>> I tried inside my window manager ... I got a just a couple of lines
> >>> that looked like they came from shutdown(), but too few (couldn't
> >>> read them).
> >>>
> >>> Then, on startup, the filesystems needed fscking!!!
> >>>  
> >>  
> >
> >
> > I have a related question.  If for some reason my system is locked up,
> > keyboard isn't working or something like that.  If I have acpi in
> > working order, would hitting the power button be seen or would that be
> > the same as the keyboard and not be recognized?  Anyone have
> > experience on this or read about someone who has ran into this?
> >
> > Just curious but if the answer is yes, I may work on setting this up
> > and working.
> >
> > Thanks.
> >
> > Dale
> >
> > :-)  :-)  
> 




-- 
Neil Bothwick

Windows Error #56: Operator fell asleep while waiting.


pgpLktp0NrWy6.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread n952162

There's a million ways a system can hang.  Acpi is a mechanism for
shipping kernel events to user space.  If user space isn't working, acpi
won't work.   I think.


On 11/17/19 09:44, Dale wrote:

n952162 wrote:


okay, I've got ...

acpid is, by default, not in the default openrc run list [:blush:]

Solution:

    sudo rc-update add acpid


On 11/13/19 07:48, n952162 wrote:


I've reinstalled gentoo from the gentoo repository and now my power
button doesn't do a shutdown anymore.  What do I have to do to have
it issue a shutdown?  This is an openrc system.

I have this, but it doesn't work:

$ cat  /etc/acpi/events/powerbtn
event=button[ /]power.*
action=/sbin/poweroff

On a different gentoo system I have, I have just the one line, the
action line, in that file and the power-button works fine (whether
there's causation there or not, I have no idea :-) )

I generally do /not/ press the power button while in my window
manager, but first when I've logged off.  Since that wasn't working,
I tried inside my window manager ... I got a just a couple of lines
that looked like they came from shutdown(), but too few (couldn't
read them).

Then, on startup, the filesystems needed fscking!!!






I have a related question.  If for some reason my system is locked up,
keyboard isn't working or something like that.  If I have acpi in
working order, would hitting the power button be seen or would that be
the same as the keyboard and not be recognized?  Anyone have
experience on this or read about someone who has ran into this?

Just curious but if the answer is yes, I may work on setting this up
and working.

Thanks.

Dale

:-)  :-)




Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]

2019-11-17 Thread Dale
n952162 wrote:
>
> okay, I've got ...
>
> acpid is, by default, not in the default openrc run list   [:blush:]
>
> Solution:
>
>     sudo rc-update add acpid
>
>
> On 11/13/19 07:48, n952162 wrote:
>>
>> I've reinstalled gentoo from the gentoo repository and now my power
>> button doesn't do a shutdown anymore.  What do I have to do to have
>> it issue a shutdown?  This is an openrc system.
>>
>> I have this, but it doesn't work:
>>
>> $ cat  /etc/acpi/events/powerbtn
>> event=button[ /]power.*
>> action=/sbin/poweroff
>>
>> On a different gentoo system I have, I have just the one line, the
>> action line, in that file and the power-button works fine (whether
>> there's causation there or not, I have no idea :-) )
>>
>> I generally do /not/ press the power button while in my window
>> manager, but first when I've logged off.  Since that wasn't working,
>> I tried inside my window manager ... I got a just a couple of lines
>> that looked like they came from shutdown(), but too few (couldn't
>> read them). 
>>
>> Then, on startup, the filesystems needed fscking!!!
>>
>


I have a related question.  If for some reason my system is locked up,
keyboard isn't working or something like that.  If I have acpi in
working order, would hitting the power button be seen or would that be
the same as the keyboard and not be recognized?  Anyone have experience
on this or read about someone who has ran into this? 

Just curious but if the answer is yes, I may work on setting this up and
working. 

Thanks.

Dale

:-)  :-)