Re: What am I missing that causes this error response from the wheezy mozilla?
On 2019-02-07, deloptes wrote: > Curt wrote: > >> I thought the $10,000 rule had to do with *cash*. >> >> Cash does not include: >> >> • Personal checks drawn on the account of the writer. >> • A cashier’s check, bank draft, traveler’s check or money order with a >> face value of more than $10,000. >> >> https://www.irs.gov/pub/irs-utl/irsform8300referenceguide.pdf >> >> Maybe I'm missing something here. > > Don't know how it is in US - here if you want to withdraw more than 5000,- > cash from the local bank office, you have to request it upfront > Not related to the price of tea in China.
Re: Install Report: Buster Weekly Build on Intel NUC (NUC8I5BEK1)
On 2019-02-07, Kenneth Parker wrote: > > On Wed, Feb 6, 2019 at 11:13 PM Carl Fink wrote: > >> My Intel NUC (Next Unit of Computing) mini-PC arrived today. Installing the >> RAM and M.2 card was super-simple. Then I tried to install Debian. >> > > Okay folks, it looks like Microsoft and Intel are playing Hardball on > people installing Linux on Laptop Computers. > I'm unsure a small-form-factor computer is a laptop or whether, in the case of the OP's NUC, an OS was pre-installed.
Setting default $PATH for all users
I'm running Debian Stretch with MATE desktop. I want the current user and all future users to include all directories in root's $PATH. I haven't found a definitive answer in my web search. The answer's seem to depend on which Linux is used and multiple parameters. TIA
Re: Setting default $PATH for all users
On Fri, Feb 08, 2019 at 07:18:39AM -0600, Richard Owlett wrote: > I'm running Debian Stretch with MATE desktop. > I want the current user and all future users to include all directories in > root's $PATH. > > I haven't found a definitive answer in my web search. The answer's seem to > depend on which Linux is used and multiple parameters. > As with most things in Linux and Unix, it depends. Some likely candidates are /etc/bash.bashrc, /etc/profile, /etc/profile.d/, and /etc/environment. Regards, -Roberto -- Roberto C. Sánchez
Re: Setting default $PATH for all users
On Fri, Feb 08, 2019 at 08:22:54AM -0500, Roberto C. Sánchez wrote: > On Fri, Feb 08, 2019 at 07:18:39AM -0600, Richard Owlett wrote: > > I'm running Debian Stretch with MATE desktop. > > I want the current user and all future users to include all directories in > > root's $PATH. > > > > I haven't found a definitive answer in my web search. The answer's seem to > > depend on which Linux is used and multiple parameters. > > > As with most things in Linux and Unix, it depends. > > Some likely candidates are /etc/bash.bashrc, /etc/profile, > /etc/profile.d/, and /etc/environment. More background: processes inherit their environment from their parent process, and so on. Since most of your (user) environment doesn't make sense for system daemons (what is Apache to do with LS_COLORS? But also arguably PATH shouldn't be there, or should, at least, be ignored), there are "checkpoints" at which the (user) environment can be set. Traditionally that happens at login (/etc/profile, ~/.profile and all their shell-specific variations -- sometimes you want slightly different environments for different shells). But X. When X came up, a similar mechanism was introduced, to let programs started directly from X also have nice environments: That is where Xsession (of which there are system-wide scripts in (Debian, at least) /etc/X11/Xsession, typically broken up in task-specific snippets in /etc/X11/Xsession.d -- and user-specific scripts in e.g. ~/.Xsession (or its older sibling ~/.Xsessionrc)). See "man Xsession" and the scripts in /etc/X11/Xsession* -- they are shell scripts and might inspire you. With the advent of desktop environments things have become a bit more complex, but I'm the wrong person for that: I just fled the DE craze ten years ago. Cheers -- tomás signature.asc Description: Digital signature
Re: Install Report: Buster Weekly Build on Intel NUC (NUC8I5BEK1)
On Fri, Feb 08, 2019 at 12:29:36PM -, Curt wrote: > I'm unsure a small-form-factor computer is a laptop or whether, in > the case of the OP's NUC, an OS was pre-installed. I didn't feel like arguing before. The NUC is a 15x15x5 cm brick, a tiny desktop, not a laptop. You can get it with or without an OS. Mine came without. -- Carl Fink nitpick...@nitpicking.com Read John Grant's book, Corrupted Science: http://a.co/9UsUoGu Dedicated to ... Carl Fink!
Re: Setting default $PATH for all users
On 02/08/2019 07:37 AM, to...@tuxteam.de wrote: On Fri, Feb 08, 2019 at 08:22:54AM -0500, Roberto C. Sánchez wrote: On Fri, Feb 08, 2019 at 07:18:39AM -0600, Richard Owlett wrote: I'm running Debian Stretch with MATE desktop. I want the current user and all future users to include all directories in root's $PATH. I haven't found a definitive answer in my web search. The answer's seem to depend on which Linux is used and multiple parameters. As with most things in Linux and Unix, it depends. Some likely candidates are /etc/bash.bashrc, /etc/profile, /etc/profile.d/, and /etc/environment. More background: processes inherit their environment from their parent process, and so on. [snip] there are "checkpoints" at which the (user) environment can be set. Traditionally that happens at login (/etc/profile, Edited that to *NO* effect. ~/.profile By my problem definition, any thing in /home/user is not relevant as I explicitly want something that affects all current and future users. and all their shell-specific variations -- sometimes you want slightly different environments for different shells). But X. When X came up, a similar mechanism was introduced, to let programs started directly from X also have nice environments: That is where Xsession (of which there are system-wide scripts in (Debian, at least) /etc/X11/Xsession, typically broken up in task-specific snippets in /etc/X11/Xsession.d -- and user-specific scripts in e.g. ~/.Xsession (or its older sibling ~/.Xsessionrc)). See "man Xsession" and the scripts in /etc/X11/Xsession* -- they are shell scripts and might inspire you. No mention of path there. With the advent of desktop environments things have become a bit more complex, but I'm the wrong person for that: I just fled the DE craze ten years ago. Cheers -- tomás
Re: Setting default $PATH for all users
Richard Owlett wrote: > By my problem definition, any thing in /home/user is not relevant as I > explicitly want something that affects all current and future users. Everybody, no matter what? pam_env can do that. PAM is the pluggable authentication module system, and controls all sorts of logins. man pam_env for instructions. -dsr-
Stretch to buster
Hi Updated from Stretch to Buster (non-free) the other day all went fine, just undertaken apt update && apt upgrade today and all seem to go fine, The process seems to be pretty painless for the most part. Paul -- Paul Sutton http://www.zleap.net https://www.linkedin.com/in/zleap/ gnupg : 7D6D B682 F351 8D08 1893 1E16 F086 5537 D066 302D
Re: Setting default $PATH for all users
On Fri, Feb 08, 2019 at 08:58:28AM -0600, Richard Owlett wrote: > On 02/08/2019 07:37 AM, to...@tuxteam.de wrote: > >More background: processes inherit their environment from their > >parent process, and so on. > > > >[snip] there are "checkpoints" at which the (user) environment > >can be set. > > > >Traditionally that happens at login (/etc/profile, > > Edited that to *NO* effect. I said "traditionally": there your primary "login" is a shell. For X and graphical environments, it's another story. > >~/.profile > > By my problem definition, any thing in /home/user is not relevant as > I explicitly want something that affects all current and future > users. Right -- I mentioned that for completeness, since this is a recurring pattern: a system-wide config which can be overridden per user. > >But X. When X came up [...] > >See "man Xsession" and the scripts in /etc/X11/Xsession* -- they > >are shell scripts and might inspire you. > > No mention of path there. No need: those are shell snippeds sourced by the X session shell, which will be the mother of all your X processes -- and PATH is part of their inherited environment. Setting PATH there will be inherited by those. But see Dan's other take -- pam will set things (among others the PATH for any authentication which goes via PAM (i.e. the display manager, where you log into X, a shell in a console, or even an ssh from another box). Cheers -- tomás signature.asc Description: Digital signature
Re: Stretch to buster
On 2/8/19 8:06 AM, Paul Sutton wrote: > Hi > > Updated from Stretch to Buster (non-free) the other day all went fine, > just undertaken > > apt update && apt upgrade > > today and all seem to go fine, The process seems to be pretty painless > for the most part. > > Paul > > That's good to hear! Keep in mind that Buster is still Testing though, and not officially released, so you will still experience non-stable packages and libraries. I too am running Buster right now with minimal issues. Cheers, -Matt
Apparmor and skype.
Hi!
Im trying to setup apparmor on my computer.
Im trying to confine firefox-esr to just the necessary staff.
Config files and Download, Desktop directory.
This is my config file and i cant understand why it doesn't work. It
allows me to save everywhere i want.
I attach my apparmor profile
Thanks in Advance!!
# Last Modified: Fri Feb 8 16:08:56 2019
#include
/usr/lib/firefox-esr/firefox-esr flags=(complain) {
#include
#include
#include
deny "/home/*/Computer Science/**" rw,
deny /home/*/Data/** rw,
deny /home/*/Data/Security/** rw,
deny /home/*/Documents/** rw,
deny /home/*/Music/** rw,
deny /home/*/Pictures/** rw,
deny /home/*/Public/** rw,
deny /home/*/Templates/** rw,
deny /home/*/Videos/** rw,
/home/*/Desktop/** rw,
/home/*/Downloads/** rw,
"/home/*/.mozilla/firefox/Crash Reports/*" r,
"/home/*/.mozilla/firefox/Pending Pings/" r,
/dev/shm/org.chromium.* rw,
/home/*/ r,
/home/*/** rwk,
/home/*/.ICEauthority r,
/home/*/.Xauthority r,
/home/*/.bash_history r,
/home/*/.bash_logout r,
/home/*/.bashrc r,
/home/*/.cache/* rwk,
/home/*/.cache/fontconfig/* r,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/ r,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/.startup-incomplete w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/activity-stream.tippytop.json
r,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/cache2/ r,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/cache2/doomed/ r,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/cache2/doomed/* w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/cache2/entries/* rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/cache2/index rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/cache2/index.log rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/cache2/index.tmp rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-backup/ rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/ rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/allow-flashallow-digest256.pset
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/allow-flashallow-digest256.sbstore
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/base-track-digest256.pset
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/base-track-digest256.sbstore
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/block-flash-digest256.pset
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/block-flash-digest256.sbstore
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/block-flashsubdoc-digest256.pset
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/block-flashsubdoc-digest256.sbstore
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/except-flash-digest256.pset
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/except-flash-digest256.sbstore
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/except-flashallow-digest256.pset
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/except-flashallow-digest256.sbstore
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/except-flashsubdoc-digest256.pset
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/except-flashsubdoc-digest256.sbstore
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/google4/
rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/mozplugin-block-digest256.pset
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/mozplugin-block-digest256.sbstore
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/mozstd-trackwhite-digest256.pset
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/mozstd-trackwhite-digest256.sbstore
w,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/test-block-simple-1.sbstore
rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/test-block-simple.pset
rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/test-block-simple.sbstore
rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/test-harmful-simple-1.sbstore
rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/test-harmful-simple.pset
rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/test-harmful-simple.sbstore
rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/test-malware-simple-1.sbstore
rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/test-malware-simple.pset
rw,
/home/*/.cache/mozilla/firefox/jjdjufjv.default/safebrowsing-updating/test-malware-simple.sbstore
rw,
/home/*/.cache/moz
Re: Apparmor and firefox!
I corrected the subject title! On 2/8/19 5:47 PM, G wrote: > Hi! > Im trying to setup apparmor on my computer. > > Im trying to confine firefox-esr to just the necessary staff. > Config files and Download, Desktop directory. > > This is my config file and i cant understand why it doesn't work. It > allows me to save everywhere i want. > > I attach my apparmor profile > > > Thanks in Advance!! >
Re: Stretch to buster
I did the same on a test install, a couple times. (mate desktop) The first try failed, I forgot to also edit the /etc/apt/sources.list.d/base.list the second worked quite well. I am a bit nervous about updating my daily drivers. On 2/8/19 7:06 AM, Paul Sutton wrote: Hi Updated from Stretch to Buster (non-free) the other day all went fine, just undertaken apt update && apt upgrade today and all seem to go fine, The process seems to be pretty painless for the most part. Paul
Re: IPv6 addresses
Le 08/02/2019 à 04:00, Richard Hector a écrit : However, it's starting to look like the router actually does advertise the ULA as well (I thought it didn't) AFAIK, a router does not advertise a prefix by itself, if it has not been configured to do so. It just appears that the idea of using one stanza per ip address (or at least per prefix) doesn't seem to work consistently. It works to configure up multiple static addresses on an interface. It may not work as expected to configure addresses using multiple methods which set interface parameter values conflicting with each other.
Re: Setting default $PATH for all users
On Fri 08 Feb 2019 at 07:18:39 (-0600), Richard Owlett wrote: > I'm running Debian Stretch with MATE desktop. > I want the current user and all future users to include all > directories in root's $PATH. If you're talking about PATH, then you're talking about logging in. So of equal importance to the DE you're using is the DM, and I'll guess that's likely lightdm. Was that amongst your search terms? > I haven't found a definitive answer in my web search. The answers > seem to depend on which Linux is used and multiple parameters. Yes, as are so many other details of configuration. If searching outwards gets you no further, then perhaps turn your attention inwards. For example, grep -r PATH /etc or, a little less noisy, grep -r PATH= /etc will reveal some candidates (plus lots of false positives, which the filenames will make obvious). Cheers, David.
Re: Stretch to buster
On Fri, 8 Feb 2019 15:06:34 + Paul Sutton wrote: > Updated from Stretch to Buster (non-free) the other day all went fine, > just undertaken Why? Buster is still alpha. A lot can still go wrong. Hope it's not your primary use distro. > apt update && apt upgrade With testing, dist-upgrade is the recommended upgrade procedure. That would be 'full-upgrade' with apt, if memory serves. Read the manual for why. > today and all seem to go fine, The process seems to be pretty painless > for the most part. Well I think that's because Debian's alphas are everybody else's betas or better. B
mariadb 10.1 for debian buster
I am trying to install MySQL-python on debian buster. It's failing to build with the error I found detailed here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918393. From reading that it appears to be fixed, but in the version of mariadb I get it's not. The version of mariadb I get is 10.3. I did not have this issue with 10.1. Is there a way to still get 10.1? I have tried many variations like mariadb-common=10.1 but none work. Alternatively, is there a way to get the fixed 10.3?
Re: Stretch to buster
On 2/8/19 11:09 AM, Patrick Bartek wrote: On Fri, 8 Feb 2019 15:06:34 + Paul Sutton wrote: Updated from Stretch to Buster (non-free) the other day all went fine, just undertaken Why? Buster is still alpha. A lot can still go wrong. Hope it's not your primary use distro. Why?: 1. migrate now, or later this year when Buster is the new Stable. 2. Newer features. Mate 1.20 is great, so is 1.16 but there have been several "new shiny things" I like. alpha? maybe so: Been using Buster on one machine for 6 months or a year, no issues... none that lasted more than the next update anyway. The last couple months zip. I have other distros available on the machines. My data is always accessible. apt update && apt upgrade With testing, dist-upgrade is the recommended upgrade procedure. That would be 'full-upgrade' with apt, if memory serves. Read the manual for why. my procedure was dead simple: using Pluma: edit both /etc/apt/sources.list and /etc/apt/sources.list.d/base.list > replace stretch with buster using Synaptic: refresh and update ... took about an hour. reboot and all was good today and all seem to go fine, The process seems to be pretty painless for the most part. Well I think that's because Debian's alphas are everybody else's betas or better. true that! packages have to be in pretty good shape to get to the Buster repo excellent vetting process B
GUIs are turning into seas of grey (gnumeric)
I can't understand why modern GUIs are composed of grey20 widgets on a grey21 background. How am I meant to know what's going to happen when I press Return on each of these dialogue boxes, 13? We used to see things more like attachment 4 only a few years ago. How can I get back something like that? help.gnome.org/users/gnumeric/stable/gnumeric.html is a huge page and it shows fancy elements being placed on graphs, but not into its own windows, as far as I can see. Cheers, David.
Re: Stretch to buster
On 09/02/2019 02:22, Peter Ehlert wrote: > > On 2/8/19 11:09 AM, Patrick Bartek wrote: >> On Fri, 8 Feb 2019 15:06:34 + >> Paul Sutton wrote: >> >>> Updated from Stretch to Buster (non-free) the other day all went fine, >>> just undertaken >> Why? Buster is still alpha. A lot can still go wrong. Hope it's not >> your primary use distro. > Why?: 1. migrate now, or later this year when Buster is the new Stable. > 2. Newer features. Mate 1.20 is great, so is 1.16 but there have been > several "new shiny things" I like. > > alpha? maybe so: Been using Buster on one machine for 6 months or a > year, no issues... none that lasted more than the next update anyway. > The last couple months zip. > > I have other distros available on the machines. My data is always > accessible. >> >>> apt update && apt upgrade >> With testing, dist-upgrade is the recommended upgrade procedure. That >> would be 'full-upgrade' with apt, if memory serves. Read the >> manual for why. > > my procedure was dead simple: > > using Pluma: > edit both /etc/apt/sources.list and /etc/apt/sources.list.d/base.list > > replace stretch with buster > > using Synaptic: refresh and update ... took about an hour. > > reboot and all was good > >>> today and all seem to go fine, The process seems to be pretty >>> painless >>> for the most part. >> Well I think that's because Debian's alphas are everybody else's betas >> or better. > true that! packages have to be in pretty good shape to get to the > Buster repo > excellent vetting process > > I have a spare netbook, which was running stretch, not really being used > for much as I have my main desktop / netbook for general use / work. > However why not upgrade and test. I am sure given the comments to this > thread with regard to no problems etc is of great comfort to the > developers. > > I can't do much, as I am probably not technical enough. I can run the > update commands, and see what happens, I have an idea on how to pipe > these messages to a file. This can be shared and hopefully be useful. > > If I share issues here others may be able to say if they have the same > issue. For the most part we can discuss the experiences here and > confirm issues. > > The about myself tool still comes up with 'unknown error' when trying to > apply changes. > > xfce menu -> debian - applications -> system - administration - about myself > > enter info - apply - password - unknown error > > > Paul -- Paul Sutton http://www.zleap.net https://www.linkedin.com/in/zleap/ gnupg : 7D6D B682 F351 8D08 1893 1E16 F086 5537 D066 302D
