stop

> Send users mailing list submissions to
>    [e-mail]
>
> To subscribe or unsubscribe via email, send a message with subject or
> body 'help' to
>    [e-mail]
>
> You can reach the person managing the list at
>    [e-mail]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of users digest..."
>
> Today's Topics:
> Re: Samba config - (Bob Goodwin)
> Re: Output text color (was dnf list color bad) (Todd Zullinger)
> Re: Samba config - (Ed Greshko)
> Re: setting up PPPoE on fedora with recent network tools
> (Patrick Mansfield)
> Re: Output text color (was dnf list color bad) (Beartooth)
>
> Date: Sun, 5 Jul 2020 12:46:52 -0400
> From: Bob Goodwin 
> Subject: Re: Samba config -
> To: [e-mail]
> Message-ID: 
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> On 2020-07-05 10:48, Ed Greshko wrote:
> > > Check the settings on 192.168.50.149
> >
> > Also, what do you get when you do....
> >
> > smbclient -L 192.168.50.149 -U bobg
> >
> > You will be prompted for your smb password on the remote system.
>
> .
> > [bobg@WS1 ~]$ smbclient -L 192.168.50.149 -U bobg
> > Enter SAMBA\bobg's password:
> >
> >     Sharename       Type      Comment
> > Â Â  Â ---------Â Â Â Â Â Â  ----Â Â Â Â Â  -------
> >     print$          Disk      Printer Drivers
> > Â Â  Â IPC$Â Â Â Â Â Â Â Â Â Â Â  IPCÂ Â Â Â Â Â  IPC Service (Samba
> > 4.12.3)
> >     bobg            Disk      Home Directories
> > SMB1 disabled -- no workgroup available
>
> Not sure what it wants from SMB1 or why whatever it is is disabled? I
> probably need to enter something for that but do not have any Windows to
> deal with here ...
>
> --
> Bob Goodwin - Zuni, Virginia, USA
> http://www.qrz.com/db/W2BOD
> FEDORA-32/64bit LINUX XFCE Fastmail POP3
>
> Date: Sun, 5 Jul 2020 12:59:10 -0400
> From: Todd Zullinger 
> Subject: Re: Output text color (was dnf list color bad)
> To: [e-mail]
> Message-ID: 
> Content-Type: multipart/signed; micalg=pgp-sha256;
>    protocol="application/pgp-signature"; boundary="Z58pRedRDwOEwTeD"
>
> --Z58pRedRDwOEwTeD
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> Beartooth wrote:
> > On Fri, 03 Jul 2020 12:02:40 -0700, Samuel Sieb wrote:
> > > On 7/3/20 11:59 AM, Beartooth wrote:
> > > > That one is the color dnf upgrade uses to list what it proposes to
> > > > change. (What it reports while making the changes is fine.) At present
> > > > it shows bright chartreuse on pale blue -- which just fuzzes out.
> > >
> > > =20
> > > If the only problem is the one color from dnf, then either disable dnf
> > > colors or use the information from the last thread to adjust the color
> > > that's causing the problem.
> >
> > =20
> >    I found /etc/dnf/DIR_COLORS,  /etc/dnf/DIR_COLORS.256color, and=20
> > /etc/dnf/DIR_COLORS.lightbgcolor.
>
> I'm pretty sure those are in /etc, not /etc/dnf.  If they're
> in the latter, can you confirm that and check what package
> provides them (rpm -qf /etc/dnf/DIR_COLORS*)?  I don't see
> anything providing them.
> > In the first one, I found among much else=20
> > # If you use DOS-style suffixes, you may want to uncomment the
> > following:
> > #.cmd 01;32 # executables (bright green) I changed 32 to 31; removed=20
> > both hashmarks; no joy; rebooted; still no joy.
> > =20
> >    Am I editing the wrong file? That comment about suffixes doesn't=20
> > quite sit right, but I didn't see anything else that looked likelier.
>
> Assuming you really meant /etc/DIR_COLORS*, then to be
> clear, 1) that will affect ls rather than dnf; and 2) you
> _are_ most likely editing the wrong file if you edit
> /etc/DIR_COLORS.
>
> The logic for which of the 3 files is used is in
> /etc/profile.d/colorls.sh (for bourne-style shells like
> bash).  Most modern terminal support 256 colors (at least),
> so they'll most likely use /etc/DIR_COLORS.256color.
>
> After you edit it, you must source /etc/profile.d/colorls.sh
> to pick up the changes.
>
> You can also copy the proper DIR_COLORS* file to your home
> dir to avoid having a clean install overwrite your changes
> in /etc.  The paths which the colorls.sh script uses are:
> $HOME/.dir_colors.$TERM
> $HOME/.dircolors.$TERM
> $HOME/.dir_colors
> $HOME/.dircolors
>
> The first one found is used.
>
> --=20
> Todd
>
> --Z58pRedRDwOEwTeD
> Content-Type: application/pgp-signature; name="signature.asc"
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.14 (GNU/Linux)
>
> iQFEBAEBCAAuBQJfAgbeJxhodHRwczovL3d3dy5wb2JveC5jb20vfnRtei9wZ3Av
> dG16LmFzYwAKCRBDJZOLvq8M495uCAC1ibv9QCPF4jp2BcTrefdlhhYzv8uwftLl
> LYoPtnPBjND/BoPnQnWmR7fGEQIeS7wvxwsFJWZolbJ4sj0PEXRD6/P9liUn2fu1
> zrbFAPwX7mkVE0ek52iw9oGYclycrrRerJSx7SgGAoYnWy+thMtgvG0d04nDXg6A
> yqRtDykVmIBXGcvmH/WzGQCDroRihvIxrcEBmSnHLbWcpB+TYR2sEw485wRxaKjE
> zyeMv2ly5+LFzu+0+tbw1qXLUv8Y18SYnF+t/u9ypGvVqwosLXCKQGJcULiHyP/3
> nDBZ2NSibiSVscMeh7RS/sgFiaOrCSF4YgbYVZMcn55haUwhboWl
> =ZoDG
> -----END PGP SIGNATURE-----
>
> --Z58pRedRDwOEwTeD--
>
> Date: Mon, 6 Jul 2020 01:02:17 +0800
> From: Ed Greshko 
> Subject: Re: Samba config -
> To: [e-mail]
> Message-ID: 
> Content-Type: text/plain; charset=utf-8
>
> On 2020-07-06 00:46, Bob Goodwin wrote:
> > On 2020-07-05 10:48, Ed Greshko wrote:
> > > > Check the settings on 192.168.50.149
> > >
> > > Also, what do you get when you do....
> > >
> > > smbclient -L 192.168.50.149 -U bobg
> > >
> > > You will be prompted for your smb password on the remote system.
> >
> > .
> > > [bobg@WS1 ~]$ smbclient -L 192.168.50.149 -U bobg
> > > Enter SAMBA\bobg's password:
> > >
> > >     Sharename       Type      Comment
> > > Â Â  Â ---------Â Â Â Â Â Â  ----Â Â Â Â Â  -------
> > >     print$          Disk      Printer Drivers
> > > Â Â  Â IPC$Â Â Â Â Â Â Â Â Â Â Â  IPCÂ Â Â Â Â Â  IPC Service (Samba
> > > 4.12.3)
> > >     bobg            Disk      Home Directories
> > > SMB1 disabled -- no workgroup available
> >
> > Not sure what it wants from SMB1 or why whatever it is is disabled? I
> > probably need to enter something for that but do not have any Windows to
> > deal with here ...
>
> That's not important.
>
> What is is Sharename=bobg.
>
> So, on WS1 the command would be....
>
> mount -o uid=bobg,credentials=/home/bobg/cred  //192.168.50.149/bobg
> /media/smb
>
> And back to sleep I go.....
>
> --
> The key to getting good answers is to ask good questions.
>
> Date: Sun, 5 Jul 2020 10:29:02 -0700
> From: Patrick Mansfield 
> Subject: Re: setting up PPPoE on fedora with recent network tools
> To: Community support for Fedora users 
> Message-ID: 
> Content-Type: text/plain; charset=iso-8859-1
>
> On Sat, Jul 04, 2020 at 10:19:32AM +0800, Ed Greshko wrote:
> > On 2020-07-04 04:19, Patrick Mansfield via users wrote:
> > > Anyone know where to find details setting up and using a PPPoE client
> >
> > on fedora with
> > > current network tools?
> > >
> > > I used nm-connection-editor to add one, but haven't figured out how to
> >
> > actually bring
> > > it up nor if it's actually working.
> > >
> > > I installed rp-pppoe, I'm not sure if it's needed or if it's
> >
> > integrated with NM.
> >
> > Well, if you've set it up then you should be able see it in the list
> > when you issue
> >
> > nmcli connection
> >
> > The details will be shown if you do...
> >
> > nmcli connection show name-of-connection
> >
> > And then....
> >
> > nmcli connection up
> >
> > will attempt to bring up the connection.� The results should be
> > displayed and you can check the
> > journal for any error messages.
>
> Ah, thanks: I had tried to bring it up using nmcli, but missed this error:
>
> Jul 04 10:53:23 umbrella NetworkManager[1183]: <warn>  [1593885203.4348]
> device (wan0): PPPoE failed to start: the PPP plugin
> /usr/lib64/NetworkManager/1.20.12-1.fc31/libnm-ppp-plugin.so is not
> installed
>
> I installed it:
>
> dnf install NetworkManager-ppp
>
> And was able to get PPPoE working.
>
> I don't think rp-pppoe is needed, but have left it installed for now.
>
> PITA as I'm trying to get rid of my combined modem router (actiontech
> C3000A) with
> new Centurylink internet service, and I can't modify the modem settings
> once I put
> it in bridge mode - it has to be physically reset if I want to change
> anything, like
> put it back to PPPoE mode, or to disable the VLAN.
>
> -- Patrick
>
> Date: Sun, 5 Jul 2020 17:52:56 -0000 (UTC)
> From: Beartooth 
> Subject: Re: Output text color (was dnf list color bad)
> To: [e-mail]
> Message-ID: 
> Content-Type: text/plain; charset=UTF-8
>
> On Sun, 05 Jul 2020 12:59:10 -0400, Todd Zullinger wrote:
>    [....]
> > I'm pretty sure those are in /etc, not /etc/dnf.  If they're in the
> > latter, can you confirm that and check what package provides them (rpm
> > -qf /etc/dnf/DIR_COLORS*)?  I don't see anything providing them.
>
> You're right. My bad. They're in /etc. And I get # rpm -qf /etc/
> dnf/DIR_COLORS*
> error: file /etc/dnf/DIR_COLORS*: No such file or directory
> > > In the first one, I found among much else
> > > # If you use DOS-style suffixes, you may want to uncomment the
> > > following:
> > > #.cmd 01;32 # executables (bright green) I changed 32 to 31; removed
> > > both hashmarks; no joy; rebooted; still no joy.
> > >
> > > Am I editing the wrong file? That comment about suffixes doesn't
> > > quite sit right, but I didn't see anything else that looked likelier.
> >
> > Assuming you really meant /etc/DIR_COLORS*, then to be clear, 1) that
> > will affect ls rather than dnf; and 2) you _are_ most likely editing the
> > wrong file if you edit /etc/DIR_COLORS.
> >
> > The logic for which of the 3 files is used is in
> > /etc/profile.d/colorls.sh (for bourne-style shells like bash).  Most
> > modern terminal support 256 colors (at least), so they'll most likely
> > use /etc/DIR_COLORS.256color.
>
> Am I remembering wrong? Istr that I could tell a given machine
> *once* that I want to see dot files, and it would *always* display them.
> > After you edit it, you must source /etc/profile.d/colorls.sh to pick up
> > the changes.
>
> "source" is a verb?? Sorry -- you lost me. What does it mean?
> > You can also copy the proper DIR_COLORS* file to your home dir to avoid
> > having a clean install overwrite your changes in /etc.  The paths which
> > the colorls.sh script uses are:
> > $HOME/.dir_colors.$TERM $HOME/.dircolors.$TERM $HOME/.dir_colors
> > $HOME/.dircolors
> >
> > The first one found is used.
>
> Sigh. The curse of the autodidact strikes again. I know that
> "HOME" in all upper case has a standard meaning, and I suppose "TERM"
> must, too. But I can never remember what it is, nor where to look it up.
>
> --
> Beartooth Staffwright, Not Quite Clueless Power User
> Remember I know little (precious little!) of where up is.
>
> Subject: Digest Footer
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>
> End of users Digest, Vol 197, Issue 33