Fully functional package manager for MacOS

G

GHopper

Guest
GHopper Asks: Fully functional package manager for MacOS
Intro

I am a big fun of Linux. I am going to change my job and will be forced to use MacOS. I know I need to get used to many new things and admit "MacOS way and philosophy" in general. Also I know it is better to agree to some things than try to change them.

Problem

I do care about security and stability and this is why I prefer to update all my system once a week. On Linux I can do it with one command only apt upgrade which updates the system and all installed apps as well.

On MacOS I use homebrew package manager which doesn't allow to update system and GUI apps (actually it does, but it is remove & install, which caused data and privileges lose). This is why on Mondays I have to run every single app and check for updates via internal update mechanism. Furthermore, if an app gets an update, it notifies me about this and it is impossible to turn off such notifications, which will be shown until the app is updated.

I can't bare such behavior and every Monday it makes me sad. I can't believe there isn't an opportunity to update all apps with a single command. And, for example, chrome may get a new update next day and I have to look at this "New update available" icon all the week long ))

Question

Is there a package manager which allows to keep my system updated with minimum routine from my side?

SolveForum.com may not be responsible for the answers or solutions given to any question asked by the users. All Answers or responses are user generated answers and we do not have proof of its validity or correctness. Please vote for the answer that helped you in order to help others find out which is the most helpful answer. Questions labeled as solved may be solved or may not be solved depending on the type of question and the date posted for some posts may be scheduled to be deleted periodically. Do not hesitate to share your thoughts here to help others.
Click to expand...
 
You must log in or register to reply here.

Unreplied Threads

Avoid Storing Plaintext Credentials In Ansible Inventory Plugin

  • N. Kreienbühl
  • Main forum
  • Replies: 0
N. Kreienbühl Asks: Avoid Storing Plaintext Credentials In Ansible Inventory Plugin
I am using the netbox.netbox.nb_inventory inventory plugin to fetch my ansible inventory from NetBox. The inventory file looks like this:

Code: 
---
plugin: netbox.netbox.nb_inventory
api_endpoint: http://10.0.0.12
token: mySuperSecertToken123
validate_certs: false
config_context: true
flatten_config_context: false
fetch_all: true
group_by:
  - is_virtual
  - cluster
  - device_roles
device_query_filters:
  - tag: ansible
vm_query_filters:
  - has_primary_ip: true

As you can see the value for token: is in plain text. Is there any straight forward way to encrypt the secret value used by the plugin?

Cheers and Thanks in Advance!

SolveForum.com may not be responsible for the answers or solutions given to any question asked by the users. All Answers or responses are user generated answers and we do not have proof of its validity or correctness. Please vote for the answer that helped you in order to help others find out which is the most helpful answer. Questions labeled as solved may be solved or may not be solved depending on the type of question and the date posted for some posts may be scheduled to be deleted periodically. Do not hesitate to share your thoughts here to help others.
Click to expand...

Combining dig +short command

sg552 Asks: Combining dig +short command
This command will show the output of MX record:

Code: 
dig @ns1.myname.com myname.com +short MX

and this will output A record:

Code: 
dig @ns1.myname.com myname.com +short A


My question is how to output both A and MX with +short in one output display?



UPDATE: Cakemox this is the output I receive:

Code: 
root@server1:~# dig +noall +answer @ns1.myname.com myname.com MX
myname.com.      86400   IN      MX      10 ASPMX2.GOOGLEMAIL.COM.
myname.com.      86400   IN      MX      10 ASPMX3.GOOGLEMAIL.COM.
myname.com.      86400   IN      MX      1 ASPMX.L.GOOGLE.COM.
myname.com.      86400   IN      MX      5 ALT1.ASPMX.L.GOOGLE.COM.
myname.com.      86400   IN      MX      5 ALT2.ASPMX.L.GOOGLE.COM.

I was hoping I could get this kind of output with just one dig command and without separating with semicolon?

Code: 
root@server1:~# dig @ns1.myname.com myname.com +short MX; dig @ns1.myname.com myname.com +short A
5 ALT1.ASPMX.L.GOOGLE.COM.
5 ALT2.ASPMX.L.GOOGLE.COM.
10 ASPMX2.GOOGLEMAIL.COM.
10 ASPMX3.GOOGLEMAIL.COM.
1 ASPMX.L.GOOGLE.COM.
63.98.113.202

SolveForum.com may not be responsible for the answers or solutions given to any question asked by the users. All Answers or responses are user generated answers and we do not have proof of its validity or correctness. Please vote for the answer that helped you in order to help others find out which is the most helpful answer. Questions labeled as solved may be solved or may not be solved depending on the type of question and the date posted for some posts may be scheduled to be deleted periodically. Do not hesitate to share your thoughts here to help others.
Click to expand...

Windows Kiosk mode: open 'Desktop'

  • Ahmed Ashour
  • Main forum
  • Replies: 0
Ahmed Ashour Asks: Windows Kiosk mode: open 'Desktop'
With Windows 11 Kiosk mode with Edge, the user can't upload files, with an error:

Can't open this location
We can't open 'Desktop'. To help keep your data safe, the location is blocked.
Click to expand...

Is there a way to configure the user to allow uploading files, or restrict the folder to some specific location?

SolveForum.com may not be responsible for the answers or solutions given to any question asked by the users. All Answers or responses are user generated answers and we do not have proof of its validity or correctness. Please vote for the answer that helped you in order to help others find out which is the most helpful answer. Questions labeled as solved may be solved or may not be solved depending on the type of question and the date posted for some posts may be scheduled to be deleted periodically. Do not hesitate to share your thoughts here to help others.
Click to expand...

Setup kerberos with nfsv4 for no_root_squash mounts

tachy Asks: Setup kerberos with nfsv4 for no_root_squash mounts
I am very new to kerberos and nfs. Kindly help to know if this is feasible. The NFS server is Truenas scale and client is ubuntu 22.04 desktop.


  1. nfs v4 is enabled in Truenas server and exports /export/home as no_root_squash and sec=krb5


  2. The requirement is to mount /export/home to /mnt/home of the ubuntu client through fstab. The permission are as per filesystem permission settings. Without sec=krb5 this is working. But no_root_squash has all its security implications. I would like to minimise it by making sure that only those hosts with kerberos keytabs should be able to mount from the Truenas server.


  3. I do not want a user level kerberos principal based auth, rather only host based. This is assuming that the users within the host is trustable.


  4. the kerberos server is on another vm.

I tried by creating host principals for truenas, and client in kerberos server VM. The respective keytabs are scp to truenas and ubuntu client respectively and rkt/wkt is used to update the keytabs into /etc/krb5.keytabs of ubuntu client and GUI is used in case of Truenas.

But the nfs.mount says operation not permitted!!!

Any guidance on how to do this on Truenas scale server and ubuntu client is appreciated.. Also guidance on how to debug this is also very helpful.

-regards tachy

SolveForum.com may not be responsible for the answers or solutions given to any question asked by the users. All Answers or responses are user generated answers and we do not have proof of its validity or correctness. Please vote for the answer that helped you in order to help others find out which is the most helpful answer. Questions labeled as solved may be solved or may not be solved depending on the type of question and the date posted for some posts may be scheduled to be deleted periodically. Do not hesitate to share your thoughts here to help others.
Click to expand...

(111: Connection refused) while connecting to upstream nginx with docker

  • M Safdar Ali Khan
  • Main forum
  • Replies: 0
M Safdar Ali Khan Asks: (111: Connection refused) while connecting to upstream nginx with docker
I am trying to dockerizing a angular universal app using nginx, and it's giving me really hard time. I have looked everywhere and haven't found a solution.

Dockerfile

Code: 
FROM node:14-alpine AS builder
WORKDIR /app
COPY . .
RUN npm i && npm run build:ssr
FROM nginx:alpine
WORKDIR /usr/share/nginx/html
RUN rm -rf ./*
COPY nginx.conf /etc/nginx/nginx.conf
COPY --from=builder /app/dist/front-end-kevi .
ENTRYPOINT ["nginx", "-g", "daemon off;"]

In my server.ts file, I am starting the app on port 4000. So I am starting the docker image using this command

Code: 
docker run -d -p 4000:80 kevin

for the reference, here is my nginx conf file.

Code: 
server {
listen       80;
server_name  localhost;

root   /usr/share/nginx/html;
index  index.html index.htm;

location ~* \.(eot|ttf|woff|woff2)$ {
add_header Access-Control-Allow-Origin *;
}

location / {
    proxy_pass http://localhost:4000;
    try_files $uri $uri/ =404;
}

location /OrderMationApi/api/v3/ {
    proxy_pass http://102.133.225.222;
}

and I am getting this error in error logs

7#7: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:4000/", host: "localhost:4000"
Click to expand...

I have changed localhost:4000 to 127.0.0.1:4000 but still of no use.

SolveForum.com may not be responsible for the answers or solutions given to any question asked by the users. All Answers or responses are user generated answers and we do not have proof of its validity or correctness. Please vote for the answer that helped you in order to help others find out which is the most helpful answer. Questions labeled as solved may be solved or may not be solved depending on the type of question and the date posted for some posts may be scheduled to be deleted periodically. Do not hesitate to share your thoughts here to help others.
Click to expand...

Supermicro: New NVMe is not detected properly

  • user3693367
  • Main forum
  • Replies: 0
user3693367 Asks: Supermicro: New NVMe is not detected properly
We have a Supermicro SuperServer 2029U-TN24R4T with currently 8 U.2 NVMe drives (Samsung PM1725a 1.6 TB) running on CentOS 7 with kernel 5.0.10-1.el7.elrepo.x86_64. After adding a new one (PM1725b 1.6 TB), it shows up for a few seconds in /dev (but only the nvme8, not nvme8n1 as one would expect) and then "gets lost". This is reproducible with different SSD trays of the chassis and even with exactly the same drives we currently use (the new one is a newer model). Adding the drive produces the following in the kernel log:

Code: 
Jul 5 21:54:25 nvme02 kernel: pciehp 10002:02:05.0:pcie204: Slot(37): Card present
Jul 5 21:54:27 nvme02 kernel: pcieport 10002:02:05.0: Data Link Layer Link Active not set in 1000 msec
Jul 5 21:54:27 nvme02 kernel: pciehp 10002:02:05.0:pcie204: Failed to check link status
Jul 5 21:54:31 nvme02 kernel: pciehp 10002:02:08.0:pcie204: Slot(136): Card present
Jul 5 21:54:31 nvme02 kernel: pciehp 10002:02:08.0:pcie204: Slot(136): Link Up
Jul 5 21:54:31 nvme02 kernel: pcieport 10002:02:08.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Jul 5 21:54:31 nvme02 kernel: pcieport 10002:02:08.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Jul 5 21:54:31 nvme02 kernel: pcieport 10002:02:08.0: BAR 13: no space for [io size 0x1000]
Jul 5 21:54:31 nvme02 kernel: pcieport 10002:02:08.0: BAR 13: failed to assign [io size 0x1000]
Jul 5 21:54:31 nvme02 kernel: pcieport 10002:02:08.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Jul 5 21:54:31 nvme02 kernel: pcieport 10002:02:08.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Jul 5 21:54:31 nvme02 kernel: pcieport 10002:02:08.0: BAR 13: no space for [io size 0x1000]
Jul 5 21:54:31 nvme02 kernel: pcieport 10002:02:08.0: BAR 13: failed to assign [io size 0x1000]
Jul 5 21:54:31 nvme02 kernel: pci 10002:07:00.0: BAR 6: assigned [mem 0xc2400000-0xc240ffff pref]
Jul 5 21:54:31 nvme02 kernel: pci 10002:07:00.0: BAR 0: assigned [mem 0xc2410000-0xc2413fff 64bit]
Jul 5 21:54:31 nvme02 kernel: pcieport 10002:02:08.0: PCI bridge to [bus 07]
Jul 5 21:54:31 nvme02 kernel: pcieport 10002:02:08.0: bridge window [mem 0xc2400000-0xc24fffff]
Jul 5 21:54:31 nvme02 kernel: nvme nvme8: pci function 10002:07:00.0
Jul 5 21:54:31 nvme02 kernel: nvme 10002:07:00.0: enabling device (0000 -> 0002)
Jul 5 21:54:31 nvme02 kernel: pciehp 10002:02:08.0:pcie204: Slot(136): Attention button pressed
Jul 5 21:54:31 nvme02 kernel: pcieport 10002:00:00.0: can't derive routing for PCI INT A
Jul 5 21:54:31 nvme02 kernel: pciehp 10002:02:08.0:pcie204: Slot(136): Powering off due to button press
Jul 5 21:54:31 nvme02 kernel: nvme 10002:07:00.0: PCI INT A: not connected
Jul 5 21:54:31 nvme02 libvirtd: 2019-07-05 19:54:31.593+0000: 15899: error : virPCIDeviceNew:1774 : internal error: dev->name buffer overflow: 10002:07:00.0
Jul 5 21:54:34 nvme02 ipmievd: Unknown sensor ff
Jul 5 21:54:40 nvme02 kernel: nvme nvme8: failed to mark controller CONNECTING
Jul 5 21:54:40 nvme02 kernel: nvme nvme8: Removing after probe failure status: 0
Jul 5 21:54:44 nvme02 ipmievd: Unknown sensor ff

The BIOS is only one version behind and the changelog doesn't say anything about this issue. The IPMI lists the new drive without any problems and the locate function also works properly. I assume that a reboot could help, however the disks must be (and are in general) hot-swappable, although we haven't tested it yet as we didn't have any disk failures. Due to the mentioned behaviour we don't want to pull a productive disk just for testing.

Any ideas would be greatly appreciated.

SolveForum.com may not be responsible for the answers or solutions given to any question asked by the users. All Answers or responses are user generated answers and we do not have proof of its validity or correctness. Please vote for the answer that helped you in order to help others find out which is the most helpful answer. Questions labeled as solved may be solved or may not be solved depending on the type of question and the date posted for some posts may be scheduled to be deleted periodically. Do not hesitate to share your thoughts here to help others.
Click to expand...

Restart crontab @reboot rule without actual reboot

ryank Asks: Restart crontab @reboot rule without actual reboot
I'm using crontab with a @reboot entry which starts a script containing a endless while-loop that is processing the output of a tail -F command. Is there any way to stop the currently running script and restart the @reboot rule without a actual reboot? I'm running Debian 6.

SolveForum.com may not be responsible for the answers or solutions given to any question asked by the users. All Answers or responses are user generated answers and we do not have proof of its validity or correctness. Please vote for the answer that helped you in order to help others find out which is the most helpful answer. Questions labeled as solved may be solved or may not be solved depending on the type of question and the date posted for some posts may be scheduled to be deleted periodically. Do not hesitate to share your thoughts here to help others.
Click to expand...

Latest posts

Newest Members

Top