Re: Login shell

[raf]

Richard L. Hamilton wrote:

> Or see https://support.apple.com/kb/HT208050 
>  which describes the new behavior, and 
> how to use Users and Groups to change the default shell, or how to use 
> Terminal preferences to use bash by default from Terminal  (only, i.e. not if 
> ssh'd in) without changing the default shell. It also mentions a few other 
> things,, including how to silence the annoying warning  (which they hardcoded 
> into bash itself, so you can't find some startup file to silence it):
> 
>  To silence this warning, you can add this command to ~/.bash_profile or 
> ~/.profile:
> export BASH_SILENCE_DEPRECATION_WARNING=1
> 
> I wondered why they made the change, so I googled and found 
> https://pawelgrzybek.com/apple-changed-the-default-shell-from-bash-to-zsh-so-did-i/
>  
> 

Luckily, I've been using zsh since about 1990 so I wouldn't notice.
But I can't upgrade to Catalina anyway, or I'd lose a precious 32bit
program.

cheers,
raf

Re: Login shell

[Ken Cunningham]

> there are large closed-source surface areas that you aren't going to be able 
> to keep updated.

You have said that before, and I listened, but: 

all my systems live behind a firewall, and none are exposed to the open web.
I don’t use any MacOS-era software to access anything outside the network. 
Only, really, MacPorts stuff (all with up-to-date security) and TenFourFox 
(also built with MacPorts stuff, also with all up to date security).

I just don’t see the vulnerability, TBH.

If you know of any, please give me an example. I don’t want to be stupid about 
things.

The time daemon, maybe? I heard there was something about that daemon, but it 
just checks Apple’s time server. I could replace that too, I guess...


Sincerely curious,

Ken

Re: Login shell

[Daniel J. Luke]

On May 7, 2020, at 2:48 PM, Bill Cole 
 wrote:
> That looks like my ugly hack. I came up with it shortly after the disclosure 
> of the "ShellShock" vulnerability.
> 
> The reason to do this when replacing a login shell or (most importantly) the 
> system shell at /bin/sh is that you do not want either of those to be 
> breakable by modification of a shared library installed by MacPorts.

alternatively, at the time I believe I downloaded the source from Apple, 
applied the upstream patch, and replaced the system /bin/sh with the result.

> The primary reason that one should replace /bin/{bash,sh} with a newer 
> version on older versions of MacOS X is ShellShock.

People who are running older versions of Mac OS X have chosen not to care about 
vulnerabilities - since they're no longer getting security updates from Apple. 
While it's maybe possible to patch/replace some of the parts of the system - 
there are large closed-source surface areas that you aren't going to be able to 
keep updated.

-- 
Daniel J. Luke

Re: Login shell

[Bill Cole]

On 7 May 2020, at 12:45, Ken Cunningham wrote:

I replace the system bash on older systems with the MP version, esp on 
Tiger.


There was a nice trick presented on the mailing list a year or two ago 
by someone to use static libs to make it less fragile, so I use that:





That looks like my ugly hack. I came up with it shortly after the 
disclosure of the "ShellShock" vulnerability.


The reason to do this when replacing a login shell or (most importantly) 
the system shell at /bin/sh is that you do not want either of those to 
be breakable by modification of a shared library installed by MacPorts.


The primary reason that one should replace /bin/{bash,sh} with a newer 
version on older versions of MacOS X is ShellShock.


--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not For Hire (currently)

Re: Login shell

[Ken Cunningham]

I replace the system bash on older systems with the MP version, esp on Tiger.

There was a nice trick presented on the mailing list a year or two ago by 
someone to use static libs to make it less fragile, so I use that:

Re: Login shell

[Richard L. Hamilton]

Or see https://support.apple.com/kb/HT208050 
 which describes the new behavior, and 
how to use Users and Groups to change the default shell, or how to use Terminal 
preferences to use bash by default from Terminal  (only, i.e. not if ssh'd in) 
without changing the default shell. It also mentions a few other things,, 
including how to silence the annoying warning  (which they hardcoded into bash 
itself, so you can't find some startup file to silence it):

 To silence this warning, you can add this command to ~/.bash_profile or 
~/.profile:
export BASH_SILENCE_DEPRECATION_WARNING=1

I wondered why they made the change, so I googled and found 
https://pawelgrzybek.com/apple-changed-the-default-shell-from-bash-to-zsh-so-did-i/
 


> On May 7, 2020, at 11:40, Daniel J. Luke  wrote:
> 
> On May 7, 2020, at 11:38 AM, Christoph Kukulies  wrote:
>> 
>> I don’t know if that belongs into macports, but I believe a lot of problems 
>> (I currently have) with PATHs may be, that Catalina (?) changed the login 
>> shell from sh (bash) to zsh (or am I wrong with this)?
>> 
>> Where do I change the users’  lofin shell. Unixwise I would say in 
>> /etc/passwd, but I don’t find any (my) username there.
> 
> use the 'chsh' command to change your shell.
> 
>> For instance my anaconda3 installation was totally spoiled after updating to 
>> Catalina.
>> 
>> For the fun of it I started bash, did a . .bash_profile and started 
>> 
>> conda update —prefix /opt/anaconda3  anaconda
>> 
>> and lo and behold, I received a smooth update in that window. 
>> 
>> Would the world be better for me if I go back to bash login shell? And why 
>> did Catalina cause such a mess?
> 
> For my computer, it didn't change my shell - but prints a message telling me 
> that I should. I just installed bash from macports and have it set as my 
> shell :)
> 
> -- 
> Daniel J. Luke
> 
> 

Re: Login shell

[Daniel J. Luke]

On May 7, 2020, at 11:38 AM, Christoph Kukulies  wrote:
> 
> I don’t know if that belongs into macports, but I believe a lot of problems 
> (I currently have) with PATHs may be, that Catalina (?) changed the login 
> shell from sh (bash) to zsh (or am I wrong with this)?
> 
> Where do I change the users’  lofin shell. Unixwise I would say in 
> /etc/passwd, but I don’t find any (my) username there.

use the 'chsh' command to change your shell.

> For instance my anaconda3 installation was totally spoiled after updating to 
> Catalina.
> 
> For the fun of it I started bash, did a . .bash_profile and started 
> 
> conda update —prefix /opt/anaconda3  anaconda
> 
> and lo and behold, I received a smooth update in that window. 
> 
> Would the world be better for me if I go back to bash login shell? And why 
> did Catalina cause such a mess?

For my computer, it didn't change my shell - but prints a message telling me 
that I should. I just installed bash from macports and have it set as my shell 
:)

-- 
Daniel J. Luke

Login shell

[Christoph Kukulies]

I don’t know if that belongs into macports, but I believe a lot of problems (I 
currently have) with PATHs may be, that Catalina (?) changed the login shell 
from sh (bash) to zsh (or am I wrong with this)?

Where do I change the users’  lofin shell. Unixwise I would say in /etc/passwd, 
but I don’t find any (my) username there.

For instance my anaconda3 installation was totally spoiled after updating to 
Catalina.

For the fun of it I started bash, did a . .bash_profile and started 

conda update —prefix /opt/anaconda3  anaconda

and lo and behold, I received a smooth update in that window. 

Would the world be better for me if I go back to bash login shell? And why did 
Catalina cause such a mess?

—
Christoph

Re: X11 Server (Quartz 1.20.4) not having security extensions

[Christopher Jones]

Hi,

I am not an expert on this, but my understanding is this was intentionally 
disabled by default by the Xorg server build system, when XACE was added. The 
MP port stays as close to the upstream defaults as it can.

That said, adding an optional variant to enable this, if the user wishes to, 
seems an option.

https://github.com/macports/macports-ports/pull/7027 


please give the update there a go and report back to the PR if it works for you.

Chris

> On 7 May 2020, at 3:15 pm, Christoph Kukulies  wrote:
> 
> That’s not the issue. I know that. My question see below (I’ll cite):
> 
> "Is there a way to make the server having these extensions? Or are there 
> reasons standing against this?"
> 
> —
> Christoph
> 
> 
>> Am 07.05.2020 um 15:53 schrieb Uli Wienands > >:
>> 
>> Try ssh -Y ...
>> 
>> Uli
>> 
>> On 5/7/20 2:43 AM, Christoph Kukulies wrote:
>>> I found that
>>> 
>>> ssh -X user@remote_host 
>>> 
>>> 
>>> doesn’t do X-forwarding, and that is - I’m told - because the X11 server 
>>> (XQuartz 1.20.4 (xorg-server 1.20.4) doesn’t have security extensions.
>>> 
>>> 
>>> $ xdpyinfo -queryExtensions
>>> 
>>> name of display:/private/tmp/com.apple.launchd.NM3gWpA6AH/org.macports:0
>>> version number:11.0
>>> vendor string:The X.Org  Foundation
>>> vendor release number:12004000
>>> X.Org  version: 1.20.4
>>> maximum request size:  16777212 bytes
>>> motion buffer size:  256
>>> bitmap unit, bit order, padding:32, LSBFirst, 32
>>> image byte order:LSBFirst
>>> number of supported pixmap formats:7
>>> supported pixmap formats:
>>>depth 1, bits_per_pixel 1, scanline_pad 32
>>>depth 4, bits_per_pixel 8, scanline_pad 32
>>>depth 8, bits_per_pixel 8, scanline_pad 32
>>>depth 15, bits_per_pixel 16, scanline_pad 32
>>>depth 16, bits_per_pixel 16, scanline_pad 32
>>>depth 24, bits_per_pixel 32, scanline_pad 32
>>>depth 32, bits_per_pixel 32, scanline_pad 32
>>> keycode range:minimum 8, maximum 255
>>> focus:  None
>>> number of extensions:21
>>>Apple-DRI  (opcode: 128, base event: 64, base error: 128)
>>>Apple-WM  (opcode: 129, base event: 68, base error: 130)
>>>BIG-REQUESTS  (opcode: 134)
>>>DAMAGE  (opcode: 142, base event: 97, base error: 154)
>>>DOUBLE-BUFFER  (opcode: 144, base error: 155)
>>>GLX  (opcode: 148, base event: 101, base error: 159)
>>>Generic Event Extension  (opcode: 130)
>>>MIT-SCREEN-SAVER  (opcode: 143, base event: 98)
>>>MIT-SHM  (opcode: 132, base event: 72, base error: 132)
>>>Present  (opcode: 145)
>>>RANDR  (opcode: 141, base event: 95, base error: 149)
>>>RENDER  (opcode: 140, base error: 144)
>>>SHAPE  (opcode: 131, base event: 71)
>>>SYNC  (opcode: 135, base event: 90, base error: 138)
>>>X-Resource  (opcode: 146)
>>>XC-MISC  (opcode: 137)
>>>XFIXES  (opcode: 139, base event: 93, base error: 142)
>>>XINERAMA  (opcode: 138)
>>>XInputExtension  (opcode: 133, base event: 73, base error: 133)
>>>XKEYBOARD  (opcode: 136, base event: 92, base error: 141)
>>>XVideo  (opcode: 147, base event: 99, base error: 156)
>>> default screen number:0
>>> number of screens:1
>>> 
>>> screen #0:
>>>  dimensions:1680x1028 pixels (445x272 millimeters)
>>>  resolution:96x96 dots per inch
>>>  depths (7):24, 1, 4, 8, 15, 16, 32
>>>  root window id:0x111
>>>  depth of root window:24 planes
>>>  number of colormaps:minimum 1, maximum 1
>>>  default colormap:0x21
>>>  default number of colormap cells:256
>>>  preallocated pixels:black 0, white 16777215
>>>  options:backing-store NO, save-unders NO
>>>  largest cursor:32x32
>>>  current input event mask:0x1a
>>>StructureNotifyMask  SubstructureNotifyMask   
>>> SubstructureRedirectMask 
>>>  number of visuals:80
>>>  default visual id:  0x22
>>>  visual:
>>>visual id:0x22
>>>class:TrueColor
>>>depth:24 planes
>>>available colormap entries:256 per subfield
>>>red, green, blue masks:0xff, 0xff00, 0xff
>>>significant bits in color specification:8 bits
>>> 
>>> 
>>> 
>>> Is there a way to make the server having these extensions? Or are there 
>>> reasons standing against this?
>>> 
>>> 
>>> —
>>> Christoph
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: X11 Server (Quartz 1.20.4) not having security extensions

[Christoph Kukulies]

That’s not the issue. I know that. My question see below (I’ll cite):

"Is there a way to make the server having these extensions? Or are there 
reasons standing against this?"

—
Christoph


> Am 07.05.2020 um 15:53 schrieb Uli Wienands :
> 
> Try ssh -Y ...
> 
> Uli
> 
> On 5/7/20 2:43 AM, Christoph Kukulies wrote:
>> I found that
>> 
>> ssh -X user@remote_host 
>> 
>> 
>> doesn’t do X-forwarding, and that is - I’m told - because the X11 server 
>> (XQuartz 1.20.4 (xorg-server 1.20.4) doesn’t have security extensions.
>> 
>> 
>> $ xdpyinfo -queryExtensions
>> 
>> name of display:/private/tmp/com.apple.launchd.NM3gWpA6AH/org.macports:0
>> version number:11.0
>> vendor string:The X.Org  Foundation
>> vendor release number:12004000
>> X.Org  version: 1.20.4
>> maximum request size:  16777212 bytes
>> motion buffer size:  256
>> bitmap unit, bit order, padding:32, LSBFirst, 32
>> image byte order:LSBFirst
>> number of supported pixmap formats:7
>> supported pixmap formats:
>>depth 1, bits_per_pixel 1, scanline_pad 32
>>depth 4, bits_per_pixel 8, scanline_pad 32
>>depth 8, bits_per_pixel 8, scanline_pad 32
>>depth 15, bits_per_pixel 16, scanline_pad 32
>>depth 16, bits_per_pixel 16, scanline_pad 32
>>depth 24, bits_per_pixel 32, scanline_pad 32
>>depth 32, bits_per_pixel 32, scanline_pad 32
>> keycode range:minimum 8, maximum 255
>> focus:  None
>> number of extensions:21
>>Apple-DRI  (opcode: 128, base event: 64, base error: 128)
>>Apple-WM  (opcode: 129, base event: 68, base error: 130)
>>BIG-REQUESTS  (opcode: 134)
>>DAMAGE  (opcode: 142, base event: 97, base error: 154)
>>DOUBLE-BUFFER  (opcode: 144, base error: 155)
>>GLX  (opcode: 148, base event: 101, base error: 159)
>>Generic Event Extension  (opcode: 130)
>>MIT-SCREEN-SAVER  (opcode: 143, base event: 98)
>>MIT-SHM  (opcode: 132, base event: 72, base error: 132)
>>Present  (opcode: 145)
>>RANDR  (opcode: 141, base event: 95, base error: 149)
>>RENDER  (opcode: 140, base error: 144)
>>SHAPE  (opcode: 131, base event: 71)
>>SYNC  (opcode: 135, base event: 90, base error: 138)
>>X-Resource  (opcode: 146)
>>XC-MISC  (opcode: 137)
>>XFIXES  (opcode: 139, base event: 93, base error: 142)
>>XINERAMA  (opcode: 138)
>>XInputExtension  (opcode: 133, base event: 73, base error: 133)
>>XKEYBOARD  (opcode: 136, base event: 92, base error: 141)
>>XVideo  (opcode: 147, base event: 99, base error: 156)
>> default screen number:0
>> number of screens:1
>> 
>> screen #0:
>>  dimensions:1680x1028 pixels (445x272 millimeters)
>>  resolution:96x96 dots per inch
>>  depths (7):24, 1, 4, 8, 15, 16, 32
>>  root window id:0x111
>>  depth of root window:24 planes
>>  number of colormaps:minimum 1, maximum 1
>>  default colormap:0x21
>>  default number of colormap cells:256
>>  preallocated pixels:black 0, white 16777215
>>  options:backing-store NO, save-unders NO
>>  largest cursor:32x32
>>  current input event mask:0x1a
>>StructureNotifyMask  SubstructureNotifyMask   
>> SubstructureRedirectMask 
>>  number of visuals:80
>>  default visual id:  0x22
>>  visual:
>>visual id:0x22
>>class:TrueColor
>>depth:24 planes
>>available colormap entries:256 per subfield
>>red, green, blue masks:0xff, 0xff00, 0xff
>>significant bits in color specification:8 bits
>> 
>> 
>> 
>> Is there a way to make the server having these extensions? Or are there 
>> reasons standing against this?
>> 
>> 
>> —
>> Christoph

Re: X11 Server (Quartz 1.20.4) not having security extensions

[Uli Wienands]

Try ssh -Y ...

Uli

On 5/7/20 2:43 AM, Christoph Kukulies wrote:

I found that

ssh -X user@remote_host


doesn’t do X-forwarding, and that is - I’m told - because the X11 
server (XQuartz 1.20.4 (xorg-server 1.20.4) doesn’t have security 
extensions.



$ xdpyinfo -queryExtensions

name of display: 
   /private/tmp/com.apple.launchd.NM3gWpA6AH/org.macports:0

version number:    11.0
vendor string:    The X.Org  Foundation
vendor release number:    12004000
X.Org  version: 1.20.4
maximum request size:  16777212 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    7
supported pixmap formats:
   depth 1, bits_per_pixel 1, scanline_pad 32
   depth 4, bits_per_pixel 8, scanline_pad 32
   depth 8, bits_per_pixel 8, scanline_pad 32
   depth 15, bits_per_pixel 16, scanline_pad 32
   depth 16, bits_per_pixel 16, scanline_pad 32
   depth 24, bits_per_pixel 32, scanline_pad 32
   depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  None
number of extensions:    21
   Apple-DRI  (opcode: 128, base event: 64, base error: 128)
   Apple-WM  (opcode: 129, base event: 68, base error: 130)
   BIG-REQUESTS  (opcode: 134)
   DAMAGE  (opcode: 142, base event: 97, base error: 154)
   DOUBLE-BUFFER  (opcode: 144, base error: 155)
   GLX  (opcode: 148, base event: 101, base error: 159)
   Generic Event Extension  (opcode: 130)
   MIT-SCREEN-SAVER  (opcode: 143, base event: 98)
   MIT-SHM  (opcode: 132, base event: 72, base error: 132)
   Present  (opcode: 145)
   RANDR  (opcode: 141, base event: 95, base error: 149)
   RENDER  (opcode: 140, base error: 144)
   SHAPE  (opcode: 131, base event: 71)
   SYNC  (opcode: 135, base event: 90, base error: 138)
   X-Resource  (opcode: 146)
   XC-MISC  (opcode: 137)
   XFIXES  (opcode: 139, base event: 93, base error: 142)
   XINERAMA  (opcode: 138)
   XInputExtension  (opcode: 133, base event: 73, base error: 133)
   XKEYBOARD  (opcode: 136, base event: 92, base error: 141)
   XVideo  (opcode: 147, base event: 99, base error: 156)
default screen number:    0
number of screens:    1

screen #0:
 dimensions:    1680x1028 pixels (445x272 millimeters)
 resolution:    96x96 dots per inch
 depths (7):    24, 1, 4, 8, 15, 16, 32
 root window id:    0x111
 depth of root window:    24 planes
 number of colormaps:    minimum 1, maximum 1
 default colormap:    0x21
 default number of colormap cells:    256
 preallocated pixels:    black 0, white 16777215
 options:    backing-store NO, save-unders NO
 largest cursor:    32x32
 current input event mask:    0x1a
   StructureNotifyMask  SubstructureNotifyMask 
  SubstructureRedirectMask

 number of visuals:    80
 default visual id:  0x22
 visual:
   visual id:    0x22
   class:    TrueColor
   depth:    24 planes
   available colormap entries:    256 per subfield
   red, green, blue masks:    0xff, 0xff00, 0xff
   significant bits in color specification:    8 bits



Is there a way to make the server having these extensions? Or are 
there reasons standing against this?



—
Christoph 

Re: Cannot do anything with port - upgrade, uninstall not possible

[Christopher Jones]

Hi,

Thats because you starting following the instructions *after* upgrading, not 
before.

You need to reinstall macports over the top of your current installation, to 
update to the binary to that for your current system, then try again.

https://www.macports.org/install.php 

Chris

> On 7 May 2020, at 9:46 am, Christoph Kukulies  wrote:
> 
> Following the instructions of migrating macports is a dead end to me right 
> now.
> 
> all attempts to uninstall or do anything woth the port command ends with that:
> 
> kuku@Christophs-MBP ~ % port -qv installed >myports.txt
> Error: Current platform "darwin 19" does not match expected platform "darwin 
> 18"
> Error: If you upgraded your OS, please follow the migration instructions: 
> https://trac.macports.org/wiki/Migration 
> 
> Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform 
> mismatch
> kuku@Christophs-MBP ~ % sudo port -fp uninstall installed
> Password:
> Error: Current platform "darwin 19" does not match expected platform "darwin 
> 18"
> Error: If you upgraded your OS, please follow the migration instructions: 
> https://trac.macports.org/wiki/Migration 
> 
> OS platform mismatch
> while executing
> "mportinit ui_options global_options global_variations"
> Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform 
> mismatch
> kuku@Christophs-MBP ~ % 
> 



smime.p7s
Description: S/MIME cryptographic signature

Cannot do anything with port - upgrade, uninstall not possible

[Christoph Kukulies]

Following the instructions of migrating macports is a dead end to me right now.

all attempts to uninstall or do anything woth the port command ends with that:

kuku@Christophs-MBP ~ % port -qv installed >myports.txt
Error: Current platform "darwin 19" does not match expected platform "darwin 18"
Error: If you upgraded your OS, please follow the migration instructions: 
https://trac.macports.org/wiki/Migration
Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform mismatch
kuku@Christophs-MBP ~ % sudo port -fp uninstall installed
Password:
Error: Current platform "darwin 19" does not match expected platform "darwin 18"
Error: If you upgraded your OS, please follow the migration instructions: 
https://trac.macports.org/wiki/Migration
OS platform mismatch
while executing
"mportinit ui_options global_options global_variations"
Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform mismatch
kuku@Christophs-MBP ~ % 

Re: macports suddenly gone on my system

[Christoph Kukulies]

Interestingly I’m now getting this:

kuku@Christophs-MBP ~ % sudo port selfupdate
Password:
Error: Current platform "darwin 19" does not match expected platform "darwin 18"
Error: If you upgraded your OS, please follow the migration instructions: 
https://trac.macports.org/wiki/Migration
OS platform mismatch
while executing
"mportinit ui_options global_options global_variations"
Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform mismatch

Will now go for reading that chapter


> Am 07.05.2020 um 10:32 schrieb Christoph Kukulies :
> 
> It’s zsh (is that the default on a macOS Catalina, think so)
> No .profile
> .zshrc is there:
> 
> 
> # >>> conda initialize >>>
> # !! Contents within this block are managed by 'conda init' !!
> __conda_setup="$('/Users/kuku/anaconda3/bin/conda' 'shell.zsh' 'hook' 2> 
> /dev/null)"
> if [ $? -eq 0 ]; then
> eval "$__conda_setup"
> else
> if [ -f "/Users/kuku/anaconda3/etc/profile.d/conda.sh" ]; then
> . "/Users/kuku/anaconda3/etc/profile.d/conda.sh"
> else
> export PATH="/Users/kuku/anaconda3/bin:$PATH"
> fi
> fi
> unset __conda_setup
> # <<< conda initialize <<<
> 
> 
> Find the followingat beginning of my .bash_profile (does .bash_profile have 
> impact on zsh? seems so):
> 
> 
> # added by Anaconda3 5.0.1 installer
> export PATH="/Users/kuku/anaconda3/bin:$PATH"
> 
> ##
> # Your previous /Users/kuku/.bash_profile file was backed up as 
> /Users/kuku/.bash_profile.macports-saved_2018-06-23_at_08:25:54
> ##
> 
> # MacPorts Installer addition on 2018-06-23_at_08:25:54: adding an 
> appropriate PATH variable for use with MacPorts.
> export PATH="/opt/local/bin:/opt/local/sbin:$PATH"
> # Finished adapting your PATH environment variable for use with MacPorts.
> 
> 
> —
> Christoph
> 
> 
>> Am 07.05.2020 um 09:55 schrieb Dominik Reichardt > >:
>> 
>> 
>> Maybe it's still there but the PATH variable changed. Check your .profile 
>> and to make sure look at /opt/local/bin
>> 
>> On Thu, May 7, 2020 at 09:39, Christoph Kukulies > > wrote:
>>> 
>>> Funny, suddenly I can’t do any longer 
>>> 
>>> sudo ports selfupdate
>>> 
>>> kuku@Christophs-MBP ~ % sudo port selfupdate
>>> Password:
>>> sudo: port: command not found
>>> kuku@Christophs-MBP ~ % 
>>> 
>>> I can’t remember having uninstalled macports.
>>> 
>>> —
>>> Christoph
>>> 
>> 
>> 
> 

Re: macports suddenly gone on my system

[Christoph Kukulies]

It’s zsh (is that the default on a macOS Catalina, think so)
No .profile
.zshrc is there:


# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/Users/kuku/anaconda3/bin/conda' 'shell.zsh' 'hook' 2> 
/dev/null)"
if [ $? -eq 0 ]; then
eval "$__conda_setup"
else
if [ -f "/Users/kuku/anaconda3/etc/profile.d/conda.sh" ]; then
. "/Users/kuku/anaconda3/etc/profile.d/conda.sh"
else
export PATH="/Users/kuku/anaconda3/bin:$PATH"
fi
fi
unset __conda_setup
# <<< conda initialize <<<


Find the followingat beginning of my .bash_profile (does .bash_profile have 
impact on zsh? seems so):


# added by Anaconda3 5.0.1 installer
export PATH="/Users/kuku/anaconda3/bin:$PATH"

##
# Your previous /Users/kuku/.bash_profile file was backed up as 
/Users/kuku/.bash_profile.macports-saved_2018-06-23_at_08:25:54
##

# MacPorts Installer addition on 2018-06-23_at_08:25:54: adding an appropriate 
PATH variable for use with MacPorts.
export PATH="/opt/local/bin:/opt/local/sbin:$PATH"
# Finished adapting your PATH environment variable for use with MacPorts.


—
Christoph


> Am 07.05.2020 um 09:55 schrieb Dominik Reichardt :
> 
> 
> Maybe it's still there but the PATH variable changed. Check your .profile and 
> to make sure look at /opt/local/bin
> 
> On Thu, May 7, 2020 at 09:39, Christoph Kukulies  > wrote:
>> 
>> Funny, suddenly I can’t do any longer 
>> 
>> sudo ports selfupdate
>> 
>> kuku@Christophs-MBP ~ % sudo port selfupdate
>> Password:
>> sudo: port: command not found
>> kuku@Christophs-MBP ~ % 
>> 
>> I can’t remember having uninstalled macports.
>> 
>> —
>> Christoph
>> 
> 
> 

X11 Server (Quartz 1.20.4) not having security extensions

[Christoph Kukulies]

I found that

ssh -X user@remote_host 


doesn’t do X-forwarding, and that is - I’m told - because the X11 server 
(XQuartz 1.20.4 (xorg-server 1.20.4) doesn’t have security extensions.


$ xdpyinfo -queryExtensions

name of display:/private/tmp/com.apple.launchd.NM3gWpA6AH/org.macports:0
version number:11.0
vendor string:The X.Org  Foundation
vendor release number:12004000
X.Org  version: 1.20.4
maximum request size:  16777212 bytes
motion buffer size:  256
bitmap unit, bit order, padding:32, LSBFirst, 32
image byte order:LSBFirst
number of supported pixmap formats:7
supported pixmap formats:
   depth 1, bits_per_pixel 1, scanline_pad 32
   depth 4, bits_per_pixel 8, scanline_pad 32
   depth 8, bits_per_pixel 8, scanline_pad 32
   depth 15, bits_per_pixel 16, scanline_pad 32
   depth 16, bits_per_pixel 16, scanline_pad 32
   depth 24, bits_per_pixel 32, scanline_pad 32
   depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:minimum 8, maximum 255
focus:  None
number of extensions:21
   Apple-DRI  (opcode: 128, base event: 64, base error: 128)
   Apple-WM  (opcode: 129, base event: 68, base error: 130)
   BIG-REQUESTS  (opcode: 134)
   DAMAGE  (opcode: 142, base event: 97, base error: 154)
   DOUBLE-BUFFER  (opcode: 144, base error: 155)
   GLX  (opcode: 148, base event: 101, base error: 159)
   Generic Event Extension  (opcode: 130)
   MIT-SCREEN-SAVER  (opcode: 143, base event: 98)
   MIT-SHM  (opcode: 132, base event: 72, base error: 132)
   Present  (opcode: 145)
   RANDR  (opcode: 141, base event: 95, base error: 149)
   RENDER  (opcode: 140, base error: 144)
   SHAPE  (opcode: 131, base event: 71)
   SYNC  (opcode: 135, base event: 90, base error: 138)
   X-Resource  (opcode: 146)
   XC-MISC  (opcode: 137)
   XFIXES  (opcode: 139, base event: 93, base error: 142)
   XINERAMA  (opcode: 138)
   XInputExtension  (opcode: 133, base event: 73, base error: 133)
   XKEYBOARD  (opcode: 136, base event: 92, base error: 141)
   XVideo  (opcode: 147, base event: 99, base error: 156)
default screen number:0
number of screens:1

screen #0:
 dimensions:1680x1028 pixels (445x272 millimeters)
 resolution:96x96 dots per inch
 depths (7):24, 1, 4, 8, 15, 16, 32
 root window id:0x111
 depth of root window:24 planes
 number of colormaps:minimum 1, maximum 1
 default colormap:0x21
 default number of colormap cells:256
 preallocated pixels:black 0, white 16777215
 options:backing-store NO, save-unders NO
 largest cursor:32x32
 current input event mask:0x1a
   StructureNotifyMask  SubstructureNotifyMask   SubstructureRedirectMask 
 number of visuals:80
 default visual id:  0x22
 visual:
   visual id:0x22
   class:TrueColor
   depth:24 planes
   available colormap entries:256 per subfield
   red, green, blue masks:0xff, 0xff00, 0xff
   significant bits in color specification:8 bits



Is there a way to make the server having these extensions? Or are there reasons 
standing against this?


—
Christoph

macports suddenly gone on my system

[Christoph Kukulies]

Funny, suddenly I can’t do any longer 

sudo ports selfupdate

kuku@Christophs-MBP ~ % sudo port selfupdate
Password:
sudo: port: command not found
kuku@Christophs-MBP ~ % 

I can’t remember having uninstalled macports.

—
Christoph