Re: Thunderbird no longer opens links

2017-12-02 Thread solitone

On 01/12/17 22:59, Alexander V. Makartsev wrote:

On 01.12.2017 22:19, Michael Biebl wrote:


I think it might be useful to open a (wishlist) bug report against the
linux package to not add the recommends when building for stretch-backports

Isn't AppArmor required in buster and also required in stretch-backports 
linux-image? Of course AppArmor can be disabled completely or partially 
if profile for some application is broken, but it is not just 
recommended package now.


Yes, if I'm pretty sure it wasn't just recommended, but it was 
required--if I remember right I had no choice.




Re: Thunderbird no longer opens links

2017-12-02 Thread Alexander V. Makartsev
On 02.12.2017 14:11, solitone wrote:
> On 01/12/17 22:59, Alexander V. Makartsev wrote:
>> On 01.12.2017 22:19, Michael Biebl wrote:
>>>
>>> I think it might be useful to open a (wishlist) bug report against the
>>> linux package to not add the recommends when building for
>>> stretch-backports
>>>
>> Isn't AppArmor required in buster and also required in
>> stretch-backports linux-image? Of course AppArmor can be disabled
>> completely or partially if profile for some application is broken,
>> but it is not just recommended package now.
>
> Yes, if I'm pretty sure it wasn't just recommended, but it was
> required--if I remember right I had no choice.
>
Now, when I hit this buggy profile problem, I'm thinking about how to
deal with these problems in the future for other applications.
After consulting AppArmor manual I have not found any reference about
how to override AppArmor profile.
All profiles are placed in "/etc/apparmor.d/" and that is it, so the
only options are either disable misbehaving AppArmor profile or modify
it which is bad option because this is package shipped profile.
For an example, systemd unit-files could be easily overridden without
resorting to modification of package shipped unit-files.
I this possible for AppArmor?

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 



playing blurays with vlc (or other)

2017-12-02 Thread Pierre Frenkiel

hi,
I'm fighting to play a bluray (OS = Stretch - 32 bit)
None of the tips I found on Google (when not leading to a obsolete URL) 
worked for me.

Has anybody a solution, either with vlc or an other program?


best regards,
--
Pierre Frenkiel



Re: playing blurays with vlc (or other)

2017-12-02 Thread deloptes
Pierre Frenkiel wrote:

> hi,
> I'm fighting to play a bluray (OS = Stretch - 32 bit)
> None of the tips I found on Google (when not leading to a obsolete URL)
> worked for me.
> Has anybody a solution, either with vlc or an other program?
> 
> 
> best regards,

https://wiki.archlinux.org/index.php/Blu-ray

sounds interesting

never purchased blue-ray videos, but I am a fan of mplayer

regards



Re: playing blurays with vlc (or other)

2017-12-02 Thread Pierre Frenkiel

On Sat, 2 Dec 2017, deloptes wrote:


https://wiki.archlinux.org/index.php/Blu-ray


  all links in that page are dead (i.e. error 404)
  anyway, after downloading bdplus-vm0, I was able to play
  the bluray with vlc, but with a very bad video. And if I
  try to select a track other than 1, the video is completely scrambled.
  I must add that that the problem doesn't come from the disc,
  as I can see it correctly with the reader of my ADSL box.


never purchased blue-ray videos, but I am a fan of mplayer


  I also tried mplayer: mplayer  br:mnt
  I get a 2-hour presentation video, but impossible to select the film
  itself, or to open any menu. That is curiously the contrary of vlc,
  with which I'm unable to see this presentation talk...

best regards,
--
Pierre Frenkiel



Re: Upgrading from very-old Debian (and xtoolwait)

2017-12-02 Thread David Wright
On Fri 01 Dec 2017 at 21:52:33 (+0100), deloptes wrote:
> Jonathan Dowland wrote:
> 
> > Non-the-less, it's not something that many people will have attempted,
> > and there are quite likely to be things that might slip through the net.
> > Not just things within the Debian ecosystem: a machine running Lenny was
> > presumably installed in or around 2009, so there's nearly 9 years worth
> > of local sysadmin changes that might have been made.
> > 
> >> I had few problems from wheezy to lenny,
> > 
> > That would be downgrading by two releases. That's bound to be
> > troublesome.
> > 
> >>but almost no problem from lenny to stretch.
> > 
> > That's the path that OP's friend would be attempting (as lenny is
> > currently oldoldoldoldstable). I'm glad it worked for you, but I would
> > still not recommend it to anyone else.
> 
> Aah sorry, I moved from lenny to squeeze then I moved partially to wheezy
> last year before squeeze got obsolated and this year I moved to stretch in
> one day, doing wheezy -> jessie and jessie -> stretch.
> 
> So the problem was squeeze -> wheezy

My only negative recollections there are:

a) I played safe on this very old laptop and upgraded to a 486 kernel
(3.2.0-4-486 IIRC) because of the necessity for pae in 686 versions.

b) I've still found no replacement for xtoolwait which was last
available in squeeze (version 1.3-6.2). It's the only thing that
ensures all the xterms appear in their correct places when starting
X. But I have to have a workaround for a bug where it sometimes
sticks around and consumes most of the CPU cycles, typically while
starting xclock. I just put the following line early on in .xsession

( sleep 60; pgrep xtoolwait; pkill xtoolwait ) &

Cheers,
David.



Re: playing blurays with vlc (or other)

2017-12-02 Thread Thomas Amm
On Sat, 2 Dec 2017 15:38:23 +0100 (CET)
Pierre Frenkiel  wrote:

> On Sat, 2 Dec 2017, deloptes wrote:
> 
> > https://wiki.archlinux.org/index.php/Blu-ray  
> 
>all links in that page are dead (i.e. error 404)
>anyway, after downloading bdplus-vm0, I was able to play
>the bluray with vlc, but with a very bad video. And if I
>try to select a track other than 1, the video is completely
> scrambled. I must add that that the problem doesn't come from the
> disc, as I can see it correctly with the reader of my ADSL box.
> 
> > never purchased blue-ray videos, but I am a fan of mplayer  
> 
>I also tried mplayer: mplayer  br:mnt
>I get a 2-hour presentation video, but impossible to select the
> film itself, or to open any menu. That is curiously the contrary of
> vlc, with which I'm unable to see this presentation talk...
> 
> best regards,

mplayer allows to select specific chapters/titles: 
 mplayer [br]://[title][/device] [options]

I don't own a blueray player, but I found mplayers extended
options quite useful playing DVDs. The man page/documentation is quite
extensive but definitely worth a read.

-- 
Backup not found: (A)bort (R)etry (P)anic



Re: Removing old python packages installed with pip

2017-12-02 Thread David Wright
On Fri 01 Dec 2017 at 12:42:35 (-0300), Eike Lantzsch wrote:
> On Friday, December 1, 2017 3:24:47 PM -03 Urs Thuermann wrote:
> > On a machine running Debian stretch I have installed python3, which is
> > currently python3.5.  Nothing of python3.4 is present.
> > 
> > But in /usr/local/lib/python3.4/dist-packages/ a number of packages is
> > still installed.  Probably, these have been installed using pip3 when
> > python3.4 was current.
> > 
> > Now, it seems pip3 isn't able to remove packages from that old
> > directory.  Is it safe to just rm -r /usr/local/lib/python3.4?

You should preserve /usr/local/lib/python3.4/dist-packages/,
so removing just the files, and not *all* the directories, is safer.

> If those packages were installed together with the Debian system then 
> deinstall with aptitude or apt remove.

If Debian installs files (other than empty directories) under
/usr/local/, I would file a bug. That tree is for you, not Debian.

> If you mix two different package installers the consequence is that one does 
> not know about the other and they can interfere with each other.
> On Debian always install packages the "Debian way".
> Don't make a Frankendebian:
> https://wiki.debian.org/DontBreakDebian

My understanding of "Frankendebian" is a system that mixes *Debian*
versions. There have to be ways of adding other suites of software
to a Debian system and, if they're for general rather than personal
use, the /usr/local/ tree is a good way to go. Why else bother to
have /usr/local/bin in the default $PATH?

>From the reference above: "Installing software to the /usr/local will
make it available to all users, and will not interfere with the
package manager. The stow package can be useful for managing software
installed to /usr/local."

Cheers,
David.



Re: Removing old python packages installed with pip

2017-12-02 Thread tomas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, Dec 02, 2017 at 09:27:43AM -0600, David Wright wrote:
> On Fri 01 Dec 2017 at 12:42:35 (-0300), Eike Lantzsch wrote:

[...]

> > If you mix two different package installers the consequence is that one 
> > does 
> > not know about the other [...]

> My understanding of "Frankendebian" is a system that mixes *Debian*
> versions [...]

Agreed, I also think that Eike's cautionary note is based on a
misinterpretation of what a Frankendebian is. Debian packagers
go out of their way to work well with locally installed software
(if you look at the packaging guidelines for big package groups,
like Debian Perl, you'll see that).

That said, extra care *is* needed when installing software outside
the distribution's package manager. That is, I think, obvious.

Even with a classical Frankendebian, I've made good experiences
(typically stable + unstable). But you've to expect difficulties
(in my case it was aptitude's more advanced, and thus complex
dependency resolver maneuvering itself into a more and more
impenetrable thicket or downright giving up). Do plan in extra
care and be prepared to learn. But there's no reason to be
afraid of that, either.

Cheers
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAloiyOYACgkQBcgs9XrR2kZBbwCfVn4UleKMV2mScsQOkKhqTNCu
TvEAnjujPW6s2UwMpyjIt8A+6STU6ajD
=pY21
-END PGP SIGNATURE-



Re: playing blurays with vlc (or other)CtmpM 7#

2017-12-02 Thread Pierre Frenkiel

On Sat, 2 Dec 2017, Thomas Amm wrote:


mplayer allows to select specific chapters/titles:
mplayer [br]://[title][/device] [options]


  I actually tried both syntaxes, i.e.:

  mplayer br://125//dev/sr0
 or
  mplayer br://125//mnt

 (note that mplayer br://125/dev/sr0 doesn't work for me)

 but as I said, 125 is the last title found by mplayer, and it is
 the last part of the presentation talk.
 What do you suggest to get the film itself?

best regards,
--
Pierre Frenkiel



Re: playing blurays with vlc (or other)

2017-12-02 Thread Brad Rogers
On Sat, 2 Dec 2017 15:38:23 +0100 (CET)
Pierre Frenkiel  wrote:

Hello Pierre,

>> https://wiki.archlinux.org/index.php/Blu-ray  
>
>   all links in that page are dead (i.e. error 404)

Odd;  All the ones I tried from that page worked.  The only exception
being that the slysoft page is currently parked.

Of course, even if the links are dead the advice, AFAICT, is good.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Bet you thought you knew what I was about
Problem - Sex Pistols


pgpcFrra5lbiH.pgp
Description: OpenPGP digital signature


inotifywait in bash script: space

2017-12-02 Thread B.M.
Dear all,

not a Debian specific question, but I hope to get an answer here...

I try to use inotifywait in a bash script to block until a file in a directory 
gets changed. Then the script should continue. That's working well unless the 
path I hand over to inotifywait contains spaces.

I already tried to escape them like so:

  MYCOMMAND = "inotifywait  -qqr -e create \"$MYDIR\""

where MYDIR is something like "/tmp/test dir" but although echo shows the 
command correctly and putting the very same command in a shell just works, as 
part of my script it doesn't work. (I don't want to get paths back from 
inotifywait.)

Thanks for any pointers towards clarification and help.

Best,
Bernd



Re: playing blurays with vlc (or other)

2017-12-02 Thread Pierre Frenkiel

On Sat, 2 Dec 2017, Brad Rogers wrote:


On Sat, 2 Dec 2017 15:38:23 +0100 (CET)
Pierre Frenkiel  wrote:

Hello Pierre,


https://wiki.archlinux.org/index.php/Blu-ray


  all links in that page are dead (i.e. error 404)


Odd;  All the ones I tried from that page worked.  The only exception
being that the slysoft page is currently parked.



   oops, I should have say also "all the links I tried"...

   [11] ==> The requested URL /aacs/ was not found on this server.
   [12] ==> The requested URL /aacs/advanced-users.php was not found on this 
server.
   [13] ==> The requested URL /aacs/ was not found on this server.

   and among the players listed in that page, the only one
   with which I could see the film, and not the presentation,
   was vlc.

   the information about vm0 was useful for vlc,
   but as I said, the problem is not actually solved, as I'm unable
   to use vlc with any audio track other than 1.



Re: inotifywait in bash script: space

2017-12-02 Thread Thomas Schmitt
Hi,

B.M. wrote:
>   MYCOMMAND = "inotifywait  -qqr -e create \"$MYDIR\""

I assume you later execute this by

  $MYCOMMAND

(and that you have no blanks around the '=').


>  echo shows the command correctly

Not for me. I get already riddled in dialog:

  $ Y="a  b  c"
  $ X="echo \"$Y\""
  $ $X
  "a b c"

Obviously "echo" sees three arguments here:
  "a
  b
  c"

I get the expected result by

  $ eval "$X"
  a  b  c

Still being riddled, my theory is that bash variable substitution happens
after quotation mark interpretation. So the marks inserted by $X stay
as they are.
The command "eval" performs a full shell parser interpretation after "$X"
got evaluated. (This might have other undesirable effects ... ponder ...)


Have a nice day :)

Thomas



Re: playing blurays with vlc (or other)

2017-12-02 Thread Brad Rogers
On Sat, 2 Dec 2017 17:32:06 +0100 (CET)
Pierre Frenkiel  wrote:

Hello Pierre,

>oops, I should have say also "all the links I tried"...

Aaah.   :-)

>[11] ==> The requested URL /aacs/ was not found on this server.
>[12] ==> The requested URL /aacs/advanced-users.php was not found
> on this server. [13] ==> The requested URL /aacs/ was not found on
> this server.

Yep, you're right.  :-(

I did get the relevant files from that site, but all references are now
gone from the home page.  However, a quick $searchengine search lead me
to http://vlc-bluray.whoknowsmy.name/ which *does* have keydb.cfg and
recently updated, too.

No luck trying to find advanced-users.php though.  Sorry.  Not that I
ever had it installed myself, in any case.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Did you do it for fame, did you do it in a fit?
Identity - X-Ray Spex


pgpnIUJlkMy1S.pgp
Description: OpenPGP digital signature


[OT] Relavant mailing list or USENET group

2017-12-02 Thread Richard Owlett

This is part of my search for a LINUX PDA. [1] [2]

Those threads and Raspberry Pi links have been educational and have 
firmed up my goals {e.g. There is no longer a strong preference for an
x86 processor}. A Raspberry Pi has attractive features for some future 
unrelated projects {physical form factor makes it unsuitable for now}.


In previous posts I've wrote of _current_ application. That was a 
mistake as it encouraged some to ignore my specifications and suggest 
"one-off" solutions. {I've been looking for a similar device for 
approximately a decade ;}



It must:
1. be currently available from U.S. retail vendor.
2. have a physical form factor similar to a "smartphone".
   [Latest releases tend to be uncomfortably large.
Maximum viable size 8" x 5".]
3. run Linux (prefer Debian) without restriction for replacing
   delivered OS.
4. have touchscreen display.
5. be able to read/write a USB flash drive.
6. *NOT* be a "smartphone".

Any suggestions for a suitable mailing list or USENET group.
TIA

[1] Handhelds that conveniently run Debian
https://lists.debian.org/debian-user/2017/11/msg00256.html

[2] Wanted - a Debian handheld
https://lists.debian.org/debian-user/2017/11/msg00351.html




Re: [OT] Relavant mailing list or USENET group

2017-12-02 Thread rhkramer
On Saturday, December 02, 2017 12:17:39 PM Richard Owlett wrote:
> 6. *NOT* be a "smartphone".

Well, I am curious about why you don't want it to be a smartphone, and whether 
doing something like removing the SIM from a cell phone (and possibly epoxying 
the socket) would meet your needs?



Re: BIOS Can Not Find Disk

2017-12-02 Thread Dan Norton

On 12/01/2017 02:58 PM, Thomas Schmitt wrote:

Hi,

Dan Norton wrote:

# fdisk -l
...
Disklabel type: gpt
In the dim past, fdisk
could set a partition as "active", which was its euphemism for "bootable".

I guess, this applies only to MBR partition tables, not to GPT as on your
disk.

As Pascal stated, there is a bit defined in GPT to be the equivalent of
the "active" bit in MBR partitions. But it looks like "BIOS boot" in the
output of fdisk indicates a particular GPT partition type GUID.
Line 164 and 165 in
   https://github.com/karelzak/util-linux/blob/master/libfdisk/src/gpt.c
say
/* Hah!IdontneedEFI */
DEF_GUID("21686148-6449-6E6F-744E-656564454649", N_("BIOS boot")),

Probably MBR code which will look for a boot indicator is not able to
interpret GPT.

Nevertheless, afaik GRUB installs an MBR which knows from where to get
its next program. So the question is rather how to install GRUB or repair
the existing installation. (Beyond my experience, i fear.)


Pascal Hambourg wrote:

- Partition attribute bit 2 = legacy BIOS bootable.
...
I just wonder how a BIOS would use that, though.

It's not the BIOS which reacts on the "active" bit. It's the MBR program
code which may or may not look for the bit. If it does, then it runs the
program code at the start of the partition.
Package "syslinux" has "mbr.bin" which is supposed to act that way:
   http://git.zytor.com/syslinux/syslinux.git/tree/mbr/mbr.S



OK, the syslinux and syslinux-efi packages are now installed and I'm 
studying man grub-install to see how to get the right mbr installed. It 
appears to be in /usr/lib/SYSLINUX-EFI/efi64. It is called syslinux.efi. 
Not sure this will cure the "ERROR:No boot disk..." problem tho.


 - Dan



Re: [OT] Relavant mailing list or USENET group

2017-12-02 Thread Richard Owlett

On 12/02/2017 12:02 PM, rhkra...@gmail.com wrote:

On Saturday, December 02, 2017 12:17:39 PM Richard Owlett wrote:

6. *NOT* be a "smartphone".


Well, I am curious about why you don't want it to be a smartphone,
and whether doing something like removing the SIM from a cell phone
(and possibly epoxying the socket) would meet your needs?



You might say it's the 3 P's ;/
[ Philosophical Practicality Prudence ]

Philosophical - application of Linux philosophy
 > As stated by McIlroy, and generally accepted throughout the Unix 
community, Unix programs have always been expected to follow the concept 
of DOTADIW, or "Do One Thing and Do It Well."

https://en.wikipedia.org/wiki/Unix_philosophy#Do_One_Thing_and_Do_It_Well

Practicality - avoidance of Android
Most "smartphones" come only with Android which presumes someone who has 
never met the user knows best what the user needs (let alone wants) and 
then goes to great lengths to prevent the end user from installing a 
suitable OS.


Practicality - possible regulatory constraints
~50 years ago I held a commercial operators license from the FCC and 
later in RFI suppression and type acceptance (FCC & VDE). I've read 
recent posts of a so called "SOS mode" active even when sim is removed. 
I don't know how onerous compliance would be -- *NOT* interested in 
wasting time and effort to pursue.


P.S. I have been described as "PERSISTENT" 




Re: BIOS Can Not Find Disk

2017-12-02 Thread Thomas Schmitt
Hi,

Dan Norton wrote:
> OK, the syslinux and syslinux-efi packages are now installed

SYSLINUX and GRUB are competitors (with GRUB winning the race on hard disk
but lagging behind on ISO 9660 for old BIOS).
I mentioned the SYSLINUX file "mbr.bin" (source: mbr.S) only to
substantiate my statement about the boot flag, the MBR and the (old) BIOS.

So i expect that you only need GRUB packages to solve your problem.
But i also expect that the boot flag will not play any role if you
strive for a normal GRUB installation.


> I'm studying man grub-install to see how to get the right mbr installed. It
> appears to be in /usr/lib/SYSLINUX-EFI/efi64. It is called syslinux.efi. 

That's quite some mix-up.

The Master Boot Record is in the first 512-byte block of a disk. It may
contain up to 446 bytes of 16-bit x86 machine code and 4 MBR partition
table entries.
The x86 machine code is started by old BIOS as first stage of the custom
boot process. It can do what its programmers wants. Normally it locates
and starts a bigger x86 program.
The MBR partition table is of no interest for old BIOS. (But as said,
the MBR code might read the table and choose a partition if its programmer
wanted it to do so.)

As successor of old BIOS there is the (U)EFI firmware. Usually it has a
Legacy BIOS emulation mode which causes the MBR program to be started.
But in its native EFI mode it looks at the MBR partition table.

If there is only one partition entry which has type 0xee and starts at
block 1 (i.e. 1 block after the MBR block 0), then there is a GUID Partition
Table (GPT). The MBR is then called "Protective MBR" because it protects
the GPT from old unaware partition editors.
EFI will then look in this GPT for the EFI System Partition and in there
for the programs /EFI/BOOT/BOOTX64.EFI or /EFI/BOOT/BOOTIA32.EFI.
You have GPT but no EFI System Partition.

If the MBR partition table bears a partition of type 0xef, then EFI will
accept it as EFI System Partition and look for the files.
You have a Protective MBR and thus no partition of type 0xef.

If no EFI System Partition is advertised bei GPT or MBR partition table
then EFI will not consider the disk for booting.

The file "syslinux.efi" in the "efi64" directory of SYSLINUX is a
program which may serve as /EFI/BOOT/BOOTX64.EFI in the EFI System Partition.
See http://www.syslinux.org/wiki/index.php?title=Install#UEFI


Since your disk has no EFI System Partition, consider to try this:

If your machine has EFI firmware, then check whether it is set to use
"Legacy BIOS" or something with similar meaning. If not, then try to
enable this legacy emulation. Maybe the MBR code on the disk knows how to
start booting the system on the disk.


Have a nice day :)

Thomas



Re: BIOS Can Not Find Disk

2017-12-02 Thread David Christensen

On 12/01/17 20:07, Dan Norton wrote:

On 12/01/2017 08:54 PM, David Christensen wrote:

On 12/01/17 10:50, Dan Norton wrote: >>> Maybe this is the wrong forum, but 
please bear with me a little bit.
This post was sent from a desktop with jessie installed. The problem 
is it will not boot normally. Network booting has been disabled in 
the NVRAM setup. After POST there is a one-liner which says it can 
not find disk. 


Please post the *exact* contents of the console screen.


ERROR:No boot disk has been detected or the disk has failed.


It can be booted with a supergrub2 cd, however.

# fdisk -l

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A615A904-0620-459F-BF44-5E53E54FDF24

Device Start    End    Sectors   Size Type
/dev/sda1   2048 411647 409600   200M BIOS boot
/dev/sda2 411648   16783359   16371712   7.8G Linux swap
/dev/sda3   16783360  151001087  134217728    64G Linux LVM
/dev/sda4  151001088  285218815  134217728    64G Linux LVM
/dev/sda5  285218816  419436543  134217728    64G Linux LVM
/dev/sda6  419436544  553654271  134217728    64G Linux LVM
/dev/sda7  553654272 1953525134 1399870863 667.5G Linux filesystem


This post is being written with Debian 8 installed on /dev/sda3, above.


How did you create the contents of this disk?


fdisk for sda1 and sda2, then installer for sda3 through sda7. The 
installer was from Debian 8.9 netinst on cd.


Does the disk have the original GPT partition table created by HP, or 
did you overwrite it?




What are your LVM PV's, VG's, and LV's?


# lvm pvdisplay
   --- Physical volume ---
   PV Name   /dev/sda3
   VG Name   debian8-vg
   PV Size   64.00 GiB / not usable 4.00 MiB
   Allocatable   yes
   PE Size   4.00 MiB
   Total PE  16383
   Free PE   9399
   Allocated PE  6984
   PV UUID vyN3Lt-vGyw-lVZi-RDBG-NoXL-nqlH-k9eolf

   "/dev/sda4" is a new physical volume of "64.00 GiB"
   --- NEW Physical volume ---
   PV Name   /dev/sda4
   VG Name
   PV Size   64.00 GiB
   Allocatable   NO
   PE Size   0
   Total PE  0
   Free PE   0
   Allocated PE  0
   PV UUID QqDROv-x2rg-3C3z-Lkdw-U95u-86BT-Jzrc6O

   "/dev/sda5" is a new physical volume of "64.00 GiB"
   --- NEW Physical volume ---
   PV Name   /dev/sda5
   VG Name
   PV Size   64.00 GiB
   Allocatable   NO
   PE Size   0
   Total PE  0
   Free PE   0
   Allocated PE  0
   PV UUID oOQuaB-qAIu-q3DW-1h0B-rKA0-q1Z4-oznScr

   "/dev/sda6" is a new physical volume of "64.00 GiB"
   --- NEW Physical volume ---
   PV Name   /dev/sda6
   VG Name
   PV Size   64.00 GiB
   Allocatable   NO
   PE Size   0
   Total PE  0
   Free PE   0
   Allocated PE  0
   PV UUID hHiVce-cC0V-u7zz-tqjU-5Rdd-nPza-BlPMQz


# lvm vgdisplay
   --- Volume group ---
   VG Name   debian8-vg
   System ID
   Format    lvm2
   Metadata Areas    1
   Metadata Sequence No  17
   VG Access read/write
   VG Status resizable
   MAX LV    0
   Cur LV    4
   Open LV   4
   Max PV    0
   Cur PV    1
   Act PV    1
   VG Size   64.00 GiB
   PE Size   4.00 MiB
   Total PE  16383
   Alloc PE / Size   6984 / 27.28 GiB
   Free  PE / Size   9399 / 36.71 GiB
   VG UUID   lfqcVE-yP6G-IeYF-zHYt-jc60-Jzas-c1fr5p


# lvm lvdisplay
   --- Logical volume ---
   LV Path    /dev/debian8-vg/root
   LV Name    root
   VG Name    debian8-vg
   LV UUID    Eh9QwL-dTlm-s8H5-5FYN-CxBl-wnvn-om3Pbx
   LV Write Access    read/write
   LV Creation host, time debian8, 2017-11-20 12:32:12 -0500
   LV Status  available
   # open 1
   LV Size    9.31 GiB
   Current LE 2384
   Segments   1
   Allocation inherit
   Read ahead sectors auto
   - currently set to 256
   Block device   254:0

   --- Logical volume ---
   LV Path    /dev/debian8-vg/home
   LV Name    home
   VG Name    debian8-vg
   LV UUID    NugOd8-PRZM-9B1e-n0Ut-MWuB-Svso-Cfyxoe
   LV Write Access    read/write
   LV Creation host, time debian8, 2017-11-20 12:33:08 -0500
   LV Status  available
   # open 1
   LV Size    9.31 GiB
   Current LE 2384
   Segments   1
   Allocation inherit
   Read ahead sectors auto
   - currently set t

Re: [OT] Relavant mailing list or USENET group

2017-12-02 Thread David Wright
On Sat 02 Dec 2017 at 13:17:14 (-0600), Richard Owlett wrote:
> On 12/02/2017 12:02 PM, rhkra...@gmail.com wrote:
> >On Saturday, December 02, 2017 12:17:39 PM Richard Owlett wrote:
> >>6. *NOT* be a "smartphone".
> >
> >Well, I am curious about why you don't want it to be a smartphone,
> >and whether doing something like removing the SIM from a cell phone
> >(and possibly epoxying the socket) would meet your needs?
> >
> 
> You might say it's the 3 P's ;/
> [ Philosophical Practicality Prudence ]
> 
> Philosophical - application of Linux philosophy
>  > As stated by McIlroy, and generally accepted throughout the Unix
> community, Unix programs have always been expected to follow the
> concept of DOTADIW, or "Do One Thing and Do It Well."
> https://en.wikipedia.org/wiki/Unix_philosophy#Do_One_Thing_and_Do_It_Well
> 
> Practicality - avoidance of Android
> Most "smartphones" come only with Android which presumes someone who
> has never met the user knows best what the user needs (let alone
> wants) and then goes to great lengths to prevent the end user from
> installing a suitable OS.
> 
> Practicality - possible regulatory constraints
> ~50 years ago I held a commercial operators license from the FCC and
> later in RFI suppression and type acceptance (FCC & VDE). I've read
> recent posts of a so called "SOS mode" active even when sim is
> removed. I don't know how onerous compliance would be -- *NOT*
> interested in wasting time and effort to pursue.
> 
> P.S. I have been described as "PERSISTENT" 

Consideration of smartphones seems to be going round in circles:

https://lists.debian.org/debian-user/2017/11/msg00266.html
https://lists.debian.org/debian-user/2017/11/msg00271.html

So let me ask a slightly different question. Given

2. have a physical form factor similar to a "smartphone".
6. *NOT* be a "smartphone".

what would be the principal use of this device, who would
it be aimed at, and what would be the size of its market?

Cheers,
David.



Re: [OT] Relavant mailing list or USENET group

2017-12-02 Thread John Hasler
David Wright writes:
> what would be the principal use of this device, who would it be aimed
> at, and what would be the size of its market?

I'd buy one were it cheap enough (it wouldn't be).
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA



Re: [OT] Relavant mailing list or USENET group

2017-12-02 Thread Joe
On Sat, 2 Dec 2017 13:17:14 -0600
Richard Owlett  wrote:

> On 12/02/2017 12:02 PM, rhkra...@gmail.com wrote:
> > On Saturday, December 02, 2017 12:17:39 PM Richard Owlett wrote:  
> >> 6. *NOT* be a "smartphone".  
> >
> > Well, I am curious about why you don't want it to be a smartphone,
> > and whether doing something like removing the SIM from a cell phone
> > (and possibly epoxying the socket) would meet your needs?
> >  
> 
> You might say it's the 3 P's ;/
> [ Philosophical Practicality Prudence ]
> 
> Philosophical - application of Linux philosophy
>   > As stated by McIlroy, and generally accepted throughout the
>   > Unix   
> community, Unix programs have always been expected to follow the
> concept of DOTADIW, or "Do One Thing and Do It Well."
> https://en.wikipedia.org/wiki/Unix_philosophy#Do_One_Thing_and_Do_It_Well
> 

So you'll be avoiding anything containing systemd...

> Practicality - avoidance of Android
> Most "smartphones" come only with Android which presumes someone who
> has never met the user knows best what the user needs (let alone
> wants) and then goes to great lengths to prevent the end user from
> installing a suitable OS.
> 

And there, I think, you encounter the brick wall. It cannot possibly
be accidental that modern portable hardware makes it so difficult to
install Linux, or indeed any alternative OS. I think it is not desired
that people should carry around devices which are not under the complete
control of the manufacturer, particularly in terms of data collection.
In short, I think you're trying to fight the system.

I wish you luck: I have an eight-year-old Acer Aspire One, which I
bought second-hand and which must be on borrowed time. It has Ethernet
and three real USB ports, and runs straight Debian unstable without a
trace of a problem. I've been looking to replace it for a few years,
but have seen nothing promising. It's all 'runs Debian flawlessly,
although the sound, Bluetooth and wifi don't work yet...' and even that
in a chroot with the host kernel running.

-- 
Joe



Re: BIOS Can Not Find Disk

2017-12-02 Thread Michael Lange
On Fri, 1 Dec 2017 23:07:15 -0500
Dan Norton  wrote:

(...)
> > What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
> > where?
> >
> 
> 
> GRUB2 to sda1.
> 

I did not read this thread in detail, so maybe this has already been
discussed, but I have just now been thinking, shouldn't grub go
to /dev/sda instead of /dev/sda1 ?

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

It would be illogical to kill without reason.
-- Spock, "Journey to Babel", stardate 3842.4



Re: Thunderbird no longer opens links

2017-12-02 Thread Ben Caradoc-Davies

On 02/12/17 23:43, Alexander V. Makartsev wrote:

Now, when I hit this buggy profile problem, I'm thinking about how to
deal with these problems in the future for other applications.
After consulting AppArmor manual I have not found any reference about
how to override AppArmor profile.
All profiles are placed in "/etc/apparmor.d/" and that is it, so the
only options are either disable misbehaving AppArmor profile or modify
it which is bad option because this is package shipped profile.
For an example, systemd unit-files could be easily overridden without
resorting to modification of package shipped unit-files.
I this possible for AppArmor?


Yes, there is aa-complain in the apparmor-utils packages, but this was 
itself buggy when I used it for thunderbird:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882047

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand



Re: [OT] Relavant mailing list or USENET group

2017-12-02 Thread David Wright
On Sat 02 Dec 2017 at 13:52:41 (-0600), John Hasler wrote:
> David Wright writes:
> > what would be the principal use of this device, who would it be aimed
> > at, and what would be the size of its market?
> 
> I'd buy one were it cheap enough (it wouldn't be).

Well, I just might¹. But I'm afraid your reply doesn't actually
address any of those three questions.

¹ With no real keyboard, I'm not convinced. (Speaking as someone
who has never yet laid out actual dosh for a computer.)

Cheers,
David.



Re: Thunderbird no longer opens links

2017-12-02 Thread Alexander V. Makartsev
On 03.12.2017 02:57, Ben Caradoc-Davies wrote:
> On 02/12/17 23:43, Alexander V. Makartsev wrote:
>> Now, when I hit this buggy profile problem, I'm thinking about how to
>> deal with these problems in the future for other applications.
>> After consulting AppArmor manual I have not found any reference about
>> how to override AppArmor profile.
>> All profiles are placed in "/etc/apparmor.d/" and that is it, so the
>> only options are either disable misbehaving AppArmor profile or modify
>> it which is bad option because this is package shipped profile.
>> For an example, systemd unit-files could be easily overridden without
>> resorting to modification of package shipped unit-files.
>> I this possible for AppArmor?
>
> Yes, there is aa-complain in the apparmor-utils packages, but this was
> itself buggy when I used it for thunderbird:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882047
>
> Kind regards,
>
If I understood this correctly, aa-complain will only switch profile to
"complain mode"(log, but don't block). This is effectively the same as
disabling the profile, which is not a good solution.
"aa-complain" is useful for debugging and writing my own profiles, but
it won't be as useful when partially broken profile is coming from
package, because any user-modifications will be over-written after
package updates.

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 



Re: BIOS Can Not Find Disk

2017-12-02 Thread Felix Miata
Michael Lange composed on 2017-12-02 22:33 (UTC+0100):

> On Fri, 1 Dec 2017 23:07:15 -0500 Dan Norton wrote:

> (...)
>> > What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
>> > where?

>> GRUB2 to sda1.

> I did not read this thread in detail, so maybe this has already been
> discussed, but I have just now been thinking, shouldn't grub go
> to /dev/sda instead of /dev/sda1 ?

 OP made it clear his is a multiboot context. Grub on sda works for a first
installation, but guess what happens with the next and subsequent installations
if you allow same with them? Just as traditionally experienced with
re-installation of Windows, each subsequent installation tries to, and typically
does, usurp control from the former, followed by updates to the prior at least
attempting to wrest it back, often with annoying, and time consuming, and
sometimes fatal, consequences. With the complication that is multiboot, some
kind of administrative intervention is inevitably needed.

The option the OP chose is to intervene ab initio. When Grub is installed to an
MBR primary partition, and the MBR contains legacy boot code, and a boot flag is
appropriately set, and the same policy is maintained, a subsequent installation
makes no attempt to usurp control from the first. Ultimate boot control remains
with whichever partition contains the boot flag, a very simple thing to change
when desired from any kind of boot.

EFI and GPT were supposedly created in part to simplify hosting multiple
operating systems, but as OP's threads prove, the real-world post-BIOS/MBR
firmware and partitioning schemes at best seem not to make multiboot any 
simpler.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/



Re: BIOS Can Not Find Disk

2017-12-02 Thread Michael Lange
On Sat, 2 Dec 2017 18:09:56 -0500
Felix Miata  wrote:

> Michael Lange composed on 2017-12-02 22:33 (UTC+0100):
> 
> > On Fri, 1 Dec 2017 23:07:15 -0500 Dan Norton wrote:
> 
> > (...)
> >> > What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
> >> > where?
> 
> >> GRUB2 to sda1.
> 
> > I did not read this thread in detail, so maybe this has already been
> > discussed, but I have just now been thinking, shouldn't grub go
> > to /dev/sda instead of /dev/sda1 ?
> 
>  OP made it clear his is a multiboot context. Grub on sda works for a
> first installation, but guess what happens with the next and subsequent
> installations if you allow same with them?

Sure, I know that. A second linux install might override the "primary"
install's grub if you don't watch what you are doing, usually no big
issue though, it should still be possible to boot the primary OS and
reinstall this one's grub if desired. Windows is a pain in the neck of
course, still booting a Live system and reinstalling grub from a chroot
environment seems comparatively easy to me compared to the OP's
troubles ;)

But anyway, I just wanted to mention what struck me when I glanced
through the thread, I have seen similar discussions before where the sda
vs. sda1 issue was actually the problem and somehow was overlooked while
discussing more elaborate technical details.

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

There are always alternatives.
-- Spock, "The Galileo Seven", stardate 2822.3



Re: [OT] Relavant mailing list or USENET group

2017-12-02 Thread John Hasler
David Wright writes:
> what would be the principal use of this device, who would it be aimed
> at, and what would be the size of its market?

I wrote:
> I'd buy one were it cheap enough (it wouldn't be).

David Wright writes:
> Well, I just might¹. But I'm afraid your reply doesn't actually
> address any of those three questions.

It says that one group it might be aimed at is people who are like me
except for having a bit more money.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA



Re: BIOS Can Not Find Disk

2017-12-02 Thread Dan Norton

On 12/02/2017 02:35 PM, David Christensen wrote:

On 12/01/17 20:07, Dan Norton wrote:

On 12/01/2017 08:54 PM, David Christensen wrote:
On 12/01/17 10:50, Dan Norton wrote: >>> Maybe this is the wrong 
forum, but please bear with me a little bit.
This post was sent from a desktop with jessie installed. The 
problem is it will not boot normally. Network booting has been 
disabled in the NVRAM setup. After POST there is a one-liner which 
says it can not find disk. 


Please post the *exact* contents of the console screen.


ERROR:No boot disk has been detected or the disk has failed.


It can be booted with a supergrub2 cd, however.

# fdisk -l

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A615A904-0620-459F-BF44-5E53E54FDF24

Device Start    End    Sectors   Size Type
/dev/sda1   2048 411647 409600   200M BIOS boot
/dev/sda2 411648   16783359   16371712   7.8G Linux swap
/dev/sda3   16783360  151001087  134217728    64G Linux LVM
/dev/sda4  151001088  285218815  134217728    64G Linux LVM
/dev/sda5  285218816  419436543  134217728    64G Linux LVM
/dev/sda6  419436544  553654271  134217728    64G Linux LVM
/dev/sda7  553654272 1953525134 1399870863 667.5G Linux filesystem


This post is being written with Debian 8 installed on /dev/sda3, 
above.


How did you create the contents of this disk?


fdisk for sda1 and sda2, then installer for sda3 through sda7. The 
installer was from Debian 8.9 netinst on cd.


Does the disk have the original GPT partition table created by HP, or 
did you overwrite it?


It had no GPT until I put  one on it. Previous scheme was 4 primaries 
and 1 extended. The extended had logicals for /, /home, /tmp, and /var.







What are your LVM PV's, VG's, and LV's?


# lvm pvdisplay
   --- Physical volume ---
   PV Name   /dev/sda3
   VG Name   debian8-vg
   PV Size   64.00 GiB / not usable 4.00 MiB
   Allocatable   yes
   PE Size   4.00 MiB
   Total PE  16383
   Free PE   9399
   Allocated PE  6984
   PV UUID vyN3Lt-vGyw-lVZi-RDBG-NoXL-nqlH-k9eolf

   "/dev/sda4" is a new physical volume of "64.00 GiB"
   --- NEW Physical volume ---
   PV Name   /dev/sda4
   VG Name
   PV Size   64.00 GiB
   Allocatable   NO
   PE Size   0
   Total PE  0
   Free PE   0
   Allocated PE  0
   PV UUID QqDROv-x2rg-3C3z-Lkdw-U95u-86BT-Jzrc6O

   "/dev/sda5" is a new physical volume of "64.00 GiB"
   --- NEW Physical volume ---
   PV Name   /dev/sda5
   VG Name
   PV Size   64.00 GiB
   Allocatable   NO
   PE Size   0
   Total PE  0
   Free PE   0
   Allocated PE  0
   PV UUID oOQuaB-qAIu-q3DW-1h0B-rKA0-q1Z4-oznScr

   "/dev/sda6" is a new physical volume of "64.00 GiB"
   --- NEW Physical volume ---
   PV Name   /dev/sda6
   VG Name
   PV Size   64.00 GiB
   Allocatable   NO
   PE Size   0
   Total PE  0
   Free PE   0
   Allocated PE  0
   PV UUID hHiVce-cC0V-u7zz-tqjU-5Rdd-nPza-BlPMQz


# lvm vgdisplay
   --- Volume group ---
   VG Name   debian8-vg
   System ID
   Format    lvm2
   Metadata Areas    1
   Metadata Sequence No  17
   VG Access read/write
   VG Status resizable
   MAX LV    0
   Cur LV    4
   Open LV   4
   Max PV    0
   Cur PV    1
   Act PV    1
   VG Size   64.00 GiB
   PE Size   4.00 MiB
   Total PE  16383
   Alloc PE / Size   6984 / 27.28 GiB
   Free  PE / Size   9399 / 36.71 GiB
   VG UUID   lfqcVE-yP6G-IeYF-zHYt-jc60-Jzas-c1fr5p


# lvm lvdisplay
   --- Logical volume ---
   LV Path    /dev/debian8-vg/root
   LV Name    root
   VG Name    debian8-vg
   LV UUID    Eh9QwL-dTlm-s8H5-5FYN-CxBl-wnvn-om3Pbx
   LV Write Access    read/write
   LV Creation host, time debian8, 2017-11-20 12:32:12 -0500
   LV Status  available
   # open 1
   LV Size    9.31 GiB
   Current LE 2384
   Segments   1
   Allocation inherit
   Read ahead sectors auto
   - currently set to 256
   Block device   254:0

   --- Logical volume ---
   LV Path    /dev/debian8-vg/home
   LV Name    home
   VG Name    debian8-vg
   LV UUID    NugOd8-PRZM-9B1e-n0Ut-MWuB-Svso-Cfyxoe
   LV Write Access    read/write
   LV Creation host, time debian8, 2017-11-20 12:33:08 -0500
   LV Status  available
   # open

Re: BIOS Can Not Find Disk

2017-12-02 Thread deloptes
Michael Lange wrote:

> Windows is a pain in the neck of
> course, still booting a Live system and reinstalling grub from a chroot
> environment seems comparatively easy to me compared to the OP's
> troubles ;)

Agreed here and this is exactly what I do.
+ grub2 finds windows automatically and perhaps other systems




A user with two faces?

2017-12-02 Thread A_Man_Without_Clue
Hi all,

I am encountering mysterious phenomenon with Buster/LXDE.
Seems like my user account has two identities.

One day I log into my account, do some work, for instance I copy files
to one directory or I install an application software then logout,
shutdown or reboot.

I will login again with same account then I would find the files I had
copied are not there, or an application software I had installed wasn't
there...at all.

I logout, reboot or shutdown.

I login again then I would find those files are in fact in a directory
where I had copied. The software is installed.

As if there are two users with same account.

What is really going on with this?

I really have no clue.




Re: A user with two faces?

2017-12-02 Thread A_Man_Without_Clue


On 12/03/2017 03:14 PM, A_Man_Without_Clue wrote:
> Hi all,
> 
> I am encountering mysterious phenomenon with Buster/LXDE.
> Seems like my user account has two identities.
> 
> One day I log into my account, do some work, for instance I copy files
> to one directory or I install an application software then logout,
> shutdown or reboot.
> 
> I will login again with same account then I would find the files I had
> copied are not there, or an application software I had installed wasn't
> there...at all.
> 
> I logout, reboot or shutdown.
> 
> I login again then I would find those files are in fact in a directory
> where I had copied. The software is installed.
> 
> As if there are two users with same account.
> 
> What is really going on with this?
> 
> I really have no clue.
> 
> 


Ok, I now know why but I do not know what caused it and how to recover.

I have software RAID1 (mirror two disks) configured and somehow it has
created different contents in /home directory for a user. I confirmed
this by booting with one disk at the time and sure enough, they have
different contents.

cat /proc/mdstat

showed one disk had been removed, I don't know when that happened.
Anyway, I re-added the disk and now it's synchronizing.

Hope this will solve the mystery.