Re: [CentOS] Unable to get dummy interfaces to persist across reboots in CentOS 8
A colleague actually figured this out. There is an entry in /lib/modprobe.d/systemd.conf that seems to override any other user configurations applied. options dummy numdummies=0 ...needs to be removed from this file (or at least modified, but since my configuration already lays that down in /etc/modprobe.d this just needs to be removed for my purposes). On Wed, Oct 28, 2020 at 2:34 PM Strahil Nikolov via CentOS wrote: > > Requirement is a very strong word , but you should consider using it and here > is a short demo why: > > - By default, RHEL uses NetworkManager to configure and manage network > connections, and the /usr/sbin/ifup and /usr/sbin/ifdown scripts use > NetworkManager to process ifcfg files in the /etc/sysconfig/network-scripts/ > directory. > > [root@system ~]# ls -l /usr/sbin/ifup > lrwxrwxrwx. 1 root root 22 21 окт 21,29 /usr/sbin/ifup -> > /etc/alternatives/ifup > > [root@system ~]# alternatives --list | grep ifup > ifupauto/usr/libexec/nm-ifup > > [root@system ~]# rpm -qf /usr/libexec/nm-ifup > NetworkManager-1.22.8-5.el8_2.x86_64 > > - the old networks-scripts have been deprecated and are not the defaults > anymore > > > It's about time to switch to NM, but you got some 5-8 years till next EL > release. > > Best Regards, > Strahil Nikolov > > > > В сряда, 28 октомври 2020 г., 12:47:12 Гринуич+2, Frank Even > написа: > > > > > > No. Network Manager is always disabled on our builds since at least > Cent5 days. The network stack has always been able to be managed > properly without relying on Network Manager. Is that now an absolute > requirement? It never has been prior. > > On Mon, Oct 26, 2020 at 6:26 PM Strahil Nikolov via CentOS > wrote: > > > > Have you tried to use NetworkManager ? > > After all ,anything network related should be done by it. > > > > [root@system ~]# nmcli connection add con-name dummy0 ifname dummy0 type > > dummy > > Connection 'dummy0' (9fdd74fa-c143-4991-9bac-0e542704ac89) successfully > > added. > > > > [root@system ~]# reboot > > Shared connection to glustera closed. > > > > > > [root@system ~]# uptime > > 03:23:44 up 0 min, 1 user, load average: 1,57, 0,48, 0,17 > > [root@glustera ~]# nmcli connection show > > NAMEUUID TYPE DEVICE > > dummy0 9fdd74fa-c143-4991-9bac-0e542704ac89 dummydummy0 > > > > > > [root@system ~]# ip a s dummy0 > > 3: dummy0: mtu 1500 qdisc noqueue state > > UNKNOWN group default qlen 1000 > >link/ether ce:c9:83:97:10:ee brd ff:ff:ff:ff:ff:ff > >inet6 fe80::599:a978:9457:df10/64 scope link noprefixroute > > valid_lft forever preferred_lft forever > > > > P.S.: This is the first time I hear about dummy interfaces. What are those > > used for ? > > > > Best Regards, > > Strahil Nikolov > > > > > > > > > > > > > > > > > > > > В вторник, 27 октомври 2020 г., 02:42:06 Гринуич+2, Frank Even > > написа: > > > > > > > > > > > > Anyone have any ideas? It's rather annoying that I can't get these to > > persist across reboots without using some kind of helper script. > > > > On Fri, Oct 16, 2020 at 6:37 AM Frank Even > > wrote: > > > > > > Hello all, hoping someone can help me out here. > > > > > > I cannot get dummy interfaces on a new Cent8 build to persist across > > > reboots. > > > > > > On Cent7 - this is the process I use: > > > > > > Create Dummies: > > > # cat /etc/modules-load.d/dummy.conf > > > dummy > > > # cat /etc/modprobe.d/dummyopts.conf > > > options dummy numdummies=4 > > > # ip link add dummy0 type dummy > > > ## - repeating a/ ascending dummyN adapters for as many needed > > > # service network start > > > # dracut -f > > > > > > Now this was different than even how 6 handled it, forget how I > > > finally dug that up (possible I even asked here). I've applied this > > > same configuration to a Cent8 box I'm trying to stand up and it all > > > appears to work fine, but unlike the Cent7 boxes, when the Cent8 box > > > comes back up, all the dummy adapters are missing. I've been > > > searching all over trying to find some documentation on this to no > > > avail. I'm hoping someone has some suggestions here to help out. > > > > > > Thanks, > > > Frank > > ___ > > CentOS mailing list > > CentOS@centos.org > > https://lists.centos.org/mailman/listinfo/centos > > > ___ > > CentOS mailing list > > CentOS@centos.org > > https://lists.centos.org/mailman/listinfo/centos > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] crontab query
On Thu, Nov 12, 2020 at 03:59:09PM +0100, Ralf Prengel wrote: > Hallo, > doesn t it make more sense to start the script every hour and check all > conditions in the script? > Ralf > > Von meinem iPad gesendet I prefer to develop the script standalone. The date/time restriction can be added in crontab or a separate script that does the date/time validation and calls the standalone script. If the date/time checks are added to the script, I recommend adding an option to override the checks and forces execution of the script when needed. Jon > > > Am 12.11.2020 um 15:42 schrieb Frank M. Ramaekers Jr. : > > > > I need to schedule a process/program every hour on the hour between 9am > > and 4pm on the 2nd through the 9th of each month except on Saturday and > > Sunday. So, I tried this entry: > > > > 0 9-16 2-9 * 1-5 ./myprog.sh > > > > Unfortunately it runs outside of the 2nd through the 9th and still runs on > > Sat. through Sun. > > > > Is there a way to do this (outside the program itself)? > > > > -Frank > > > > ___ > > CentOS mailing list > > CentOS@centos.org > > https://lists.centos.org/mailman/listinfo/centos > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos >>> End of included message <<< -- Jon H. LaBadie j...@labadie.us ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] run firefox via an ssh tunnel
On Thu, Nov 12, 2020 at 03:21:02PM -0500, Jonathan Billings wrote: > yum --setopt='proxy=socks5://localhost:8000' update It occurs to me that my private networks have working DNS, so if yours doesn't, you should use: yum --setopt='proxy=socks5h://localhost:8000' update (note the extra 'h' in the URI scheme) This means that the DNS lookups happen on the other side of the proxy, so the yum command doesn't need to do any DNS lookups. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] run firefox via an ssh tunnel
On Thu, Nov 12, 2020 at 03:21:02PM -0500, Jonathan Billings wrote: > What part? For the first part, either define 'DynamicForward 8000' in > a Host section in ~/.ssh/config, or run 'ssh -D 8000 hostname' to set > it with command line options. Then just set your SOCKS5 proxy > settings in Firefox to localhost:8000. (I'm just using port 8000 as > an example here, it can be any unused port above 1024 for regular > users.) If you need a full tunnel (and not just HTTP) and don't have a VPN server, but you do have an SSH connection, I heartily recommend the tool 'sshuttle' (https://github.com/sshuttle/sshuttle, in EPEL). It requires root locally but not on the remote side. Then you can just use firefox without messing with proxy settings or anything. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] run firefox via an ssh tunnel
On Thu, Nov 12, 2020 at 10:02:57AM -0700, S Bob wrote: > On 11/12/20 7:50 AM, Jonathan Billings wrote: > > If this is actually something you want to do with regularity, I > > suggest using the SSH SOCKS proxy (with the DynamicForward port), and > > configure Firefox to use the localhost:port as a SOCKS5 proxy. Then > > all traffic in firefox will be routed over the ssh connection. It > > won't break SNI and for the most part, everything will work in firefox > > as if you were connecting from the remote side of the connection. > > > > It works with yum and dnf too, where you can use RemoteForward to set > > up a proxy port on the remote side, set the 'proxy' settings in the > > configuration, and all yum/dnf traffic will go over the established > > SSH connection. Why would you do this? Well, if you've got a system > > that's sitting inside a private, not NAT'd network and your > > workstation/jumphost has a VPN enabled but you don't have it enabled > > on the remote side, you can update a system without doing a lot of > > complicated network magic. Now imagine using Ansible to do this, > > which is already setting up SSH sessions... > > > Sounds interesting, can you point me to any examples / how to's to set this > up? What part? For the first part, either define 'DynamicForward 8000' in a Host section in ~/.ssh/config, or run 'ssh -D 8000 hostname' to set it with command line options. Then just set your SOCKS5 proxy settings in Firefox to localhost:8000. (I'm just using port 8000 as an example here, it can be any unused port above 1024 for regular users.) For the second, it's largely the same thing, except you'd use 'RemoteForward 8000' or 'ssh -R 8000 hostname' with the command line, and on the remote side, set 'proxy=socks5://localhost:8000' in the yum.conf or dnf.conf, or set it on the command line with: yum --setopt='proxy=socks5://localhost:8000' update (replace 'yum' with 'dnf' for c8) If you are curious if it is actually doing anything, add a -v to your ssh connection and it'll send debugging information to your terminal, and you'll see each proxied connection from yum/dnf. For ansible to use it, you'd set 'ssh_connection' in your ansible.ini to have the extra -R option, and then deploy a yum/dnf config that uses the proxy. I've found this useful for managing some systems on our campus that are on a private LAN but are routed to campus only, so they can't reach 'the world' but my computer can. I would still recommend that people run their own private mirror if they are running their own private cluster but this is useful in a pinch. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MIDI on a VM
On 12/11/2020 17:26, Ralf Prengel wrote: Hallo, witch virtualizer are you using. KVM/QEMU Sure that the virtual sound-device is connected with the right hardware? I can play CDs and listen to YouTube on the host, so I'm assuming the hardware is fine. Ralf Von meinem iPad gesendet Am 12.11.2020 um 18:00 schrieb J Martin Rushton via CentOS : I have an application (Frescobaldi/Lilypond) that generates and plays MIDI files. Due to problems with flatpak I can only run it on C8 or Fedora, both of which live on VMs. The host is running C7. I've tried "adding hardware", specifically a virtual sound card, to the VMs, but still they remain silent. How do I connect the virtual sound cards to the physical sound card so that I can hear the music? Thanks, Martin -- J Martin Rushton MBCS ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos -- J Martin Rushton MBCS ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MIDI on a VM
Hallo, witch virtualizer are you using. Sure that the virtual sound-device is connected with the right hardware? Ralf Von meinem iPad gesendet > Am 12.11.2020 um 18:00 schrieb J Martin Rushton via CentOS > : > > I have an application (Frescobaldi/Lilypond) that generates and plays MIDI > files. Due to problems with flatpak I can only run it on C8 or Fedora, both > of which live on VMs. The host is running C7. I've tried "adding hardware", > specifically a virtual sound card, to the VMs, but still they remain silent. > How do I connect the virtual sound cards to the physical sound card so that I > can hear the music? > > Thanks, > Martin > > > -- > J Martin Rushton MBCS > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] run firefox via an ssh tunnel
On 11/12/20 7:50 AM, Jonathan Billings wrote: On Thu, Nov 12, 2020 at 12:56:15PM +, Bernstein, Noam CIV USN NRL (6393) Washington DC (USA) via CentOS wrote: If the point is to access a specific web site only the remote machine can get to, you can also do it with port forwarding: ssh -L 8000:ip_of_web_site_to_access_from_remote:443 remote_machine and then locally run any browser, and access https://localhost:443 (assuming it's https. If it's plain http, use "http" and 80). Note that you'll be breaking some aspects of https security such as man-in-the-middle protection and perhaps others, and you'll need to accept some security exceptions. This will be useful if the point is to get to a web site only only the remote machine can connect to, but all the browser code/plugins will be the local ones. If this is actually something you want to do with regularity, I suggest using the SSH SOCKS proxy (with the DynamicForward port), and configure Firefox to use the localhost:port as a SOCKS5 proxy. Then all traffic in firefox will be routed over the ssh connection. It won't break SNI and for the most part, everything will work in firefox as if you were connecting from the remote side of the connection. It works with yum and dnf too, where you can use RemoteForward to set up a proxy port on the remote side, set the 'proxy' settings in the configuration, and all yum/dnf traffic will go over the established SSH connection. Why would you do this? Well, if you've got a system that's sitting inside a private, not NAT'd network and your workstation/jumphost has a VPN enabled but you don't have it enabled on the remote side, you can update a system without doing a lot of complicated network magic. Now imagine using Ansible to do this, which is already setting up SSH sessions... Sounds interesting, can you point me to any examples / how to's to set this up? Thanks ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] MIDI on a VM
I have an application (Frescobaldi/Lilypond) that generates and plays MIDI files. Due to problems with flatpak I can only run it on C8 or Fedora, both of which live on VMs. The host is running C7. I've tried "adding hardware", specifically a virtual sound card, to the VMs, but still they remain silent. How do I connect the virtual sound cards to the physical sound card so that I can hear the music? Thanks, Martin -- J Martin Rushton MBCS ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] crontab query
On Wed, Nov 11, 2020 at 10:35:48AM -0600, Frank M. Ramaekers Jr. wrote: > > I need to schedule a process/program every hour on the hour between 9am and > 4pm on the 2nd through the 9th of each month except on Saturday and Sunday. > So, I tried this entry: > > 0 9-16 2-9 * 1-5 ./myprog.sh > > Unfortunately it runs outside of the 2nd through the 9th and still runs on > Sat. through Sun. > > Is there a way to do this (outside the program itself)? From the crontab(5) man page: Note: The day of a command's execution can be specified in the follow‐ ing two fields — 'day of month', and 'day of week'. If both fields are restricted (i.e., do not contain the "*" character), the command will be run when either field matches the current time. For example, "30 4 1,15 * 5" would cause a command to be run at 4:30 am on the 1st and 15th of each month, plus every Friday. So it looks like it is going to run either time. A systemd timer might be able to be more exclusive, but parsing the 'systemd.time' man page makes my head hurt. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] crontab query
Hallo, doesn t it make more sense to start the script every hour and check all conditions in the script? Ralf Von meinem iPad gesendet > Am 12.11.2020 um 15:42 schrieb Frank M. Ramaekers Jr. : > > I need to schedule a process/program every hour on the hour between 9am and > 4pm on the 2nd through the 9th of each month except on Saturday and Sunday. > So, I tried this entry: > > 0 9-16 2-9 * 1-5 ./myprog.sh > > Unfortunately it runs outside of the 2nd through the 9th and still runs on > Sat. through Sun. > > Is there a way to do this (outside the program itself)? > > -Frank > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] crontab query
On Wed, Nov 11, 2020 at 10:35:48AM -0600, Frank M. Ramaekers Jr. wrote: > I need to schedule a process/program every hour on the hour between 9am and > 4pm on the 2nd through the 9th of each month except on Saturday and Sunday. > So, I tried this entry: > > 0 9-16 2-9 * 1-5 ./myprog.sh > > Unfortunately it runs outside of the 2nd through the 9th and still runs on > Sat. through Sun. > > Is there a way to do this (outside the program itself)? > Perhaps 0 9-16 * * 1-5 [[ $(date +%d) == 0[2-9] ]] && ./myprog.sh Please replace ./ with full path to myprog.sh jl -- Jon H. LaBadie j...@labadie.us ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 vncserver
On Thu, Nov 12, 2020 at 09:12:42AM -0500, Jerry Geis wrote: > > I am trying to get vncserver working on CentOS 8. Fully updated. > > On the console - logged in as a normal user I run: > export DISPLAY=:0.0 > xhost + > /usr/bin/x0vncserver -display :0 -rfbport 5901 -passwordfile > /home/silentm/.vnc/passwd > > I get this error: > Invalid MIT-MAGIC-COOKIE-1 key/usr/bin/x0vncserver: unable to open display > ":0" > > Based on the error I changed the DISPLAY=:0 and tried again - but same > error. > > Am I doing something wrong? I dont really need this to start as a service > was just trying to start by hand. Is there an X11 server running, listening on display :0.0? It sounds like you said you logged in on the console, that sounds like you aren't running X yet, but are at the text console. If you want to run vncserver, I suggest using the xvnc@.service included in the package: https://git.centos.org/rpms/tigervnc/blob/c8/f/SOURCES/xvnc.service There are instructions in the comments. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] run firefox via an ssh tunnel
On Thu, Nov 12, 2020 at 12:56:15PM +, Bernstein, Noam CIV USN NRL (6393) Washington DC (USA) via CentOS wrote: > > If the point is to access a specific web site only the remote > machine can get to, you can also do it with port forwarding: > ssh -L 8000:ip_of_web_site_to_access_from_remote:443 remote_machine > and then locally run any browser, and access > https://localhost:443 > (assuming it's https. If it's plain http, use "http" and 80). Note > that you'll be breaking some aspects of https security such as > man-in-the-middle protection and perhaps others, and you'll need to > accept some security exceptions. > > This will be useful if the point is to get to a web site only only > the remote machine can connect to, but all the browser code/plugins > will be the local ones. If this is actually something you want to do with regularity, I suggest using the SSH SOCKS proxy (with the DynamicForward port), and configure Firefox to use the localhost:port as a SOCKS5 proxy. Then all traffic in firefox will be routed over the ssh connection. It won't break SNI and for the most part, everything will work in firefox as if you were connecting from the remote side of the connection. It works with yum and dnf too, where you can use RemoteForward to set up a proxy port on the remote side, set the 'proxy' settings in the configuration, and all yum/dnf traffic will go over the established SSH connection. Why would you do this? Well, if you've got a system that's sitting inside a private, not NAT'd network and your workstation/jumphost has a VPN enabled but you don't have it enabled on the remote side, you can update a system without doing a lot of complicated network magic. Now imagine using Ansible to do this, which is already setting up SSH sessions... -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] crontab query
I need to schedule a process/program every hour on the hour between 9am and 4pm on the 2nd through the 9th of each month except on Saturday and Sunday. So, I tried this entry: 0 9-16 2-9 * 1-5 ./myprog.sh Unfortunately it runs outside of the 2nd through the 9th and still runs on Sat. through Sun. Is there a way to do this (outside the program itself)? -Frank ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 8 vncserver
I am trying to get vncserver working on CentOS 8. Fully updated. On the console - logged in as a normal user I run: export DISPLAY=:0.0 xhost + /usr/bin/x0vncserver -display :0 -rfbport 5901 -passwordfile /home/silentm/.vnc/passwd I get this error: Invalid MIT-MAGIC-COOKIE-1 key/usr/bin/x0vncserver: unable to open display ":0" Based on the error I changed the DISPLAY=:0 and tried again - but same error. Am I doing something wrong? I dont really need this to start as a service was just trying to start by hand. Thanks Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] centos8 / anaconda EFI regression / HFS+ ESP
Am 11.11.20 um 14:41 schrieb Fabian Arrotin: On 10/11/2020 17:18, Leon Fauster via CentOS wrote: Hi folks, years ago I had no problem installing CentOS7 on my iMac workstation (iMac Late 2015). The installation worked out of the box. Today I wanted to upgrade to CentOS8 and while configuring the partitions I get an error that the installation can not start because: "HFS+ ESP needed and mounted on /boot/efi". In fact they are the same partition as for CentOS7. Is this a regression of anaconda, implying that the EFI partition must be HFS based? I can boot CentOS7 with the vfat EFI partition ... -- Leon Hi Leon, Same problem for me on my wife's iMac (24" , 2018 model) : running CentOS 7 perfectly fine but I replaced original sata HDD with a SSD some months ago and wanted to reinstall with CentOS 8 and same result, so I finally reinstalled it with 7 again, and put that on my "TODO" list. As you can see, some upstream changes landed in anaconda when detecting Mac/Apple hardware and it works fine with Fedora (tested already) because both hfs/hfs+ support exist in kernel and hfsplus-tools package too. Yes, I also tested a F33 installation and it went smoothly. Of course it was removed from RHEL kernel (and packages list) so I have some ideas in mind but never had time to investigate further (as iMac also runs fine with CentOS 7) One idea was to "modify" on the fly anaconda (with updates.img) to *not* use HFS+ part but instead vfat. There are ways to do that but one first need to find which python code to mod in anaconda (and then see if such method still works : https://arrfab.net/posts/2011/Jun/11/modifying-anaconda-behaviour-without-rebuilding-the-whole-install-media/) Other idea : respin an iso/tree that would use different kernel and access to hfsplus-tools pkg and so no need to "hack" anaconda So many ideas, but not enough time to investigate this for now ... Because of the missing hfs support it would be the hard way to keep everytime in mind that the kernel-plus is mandatory for having /boot/efi mounted and the tools must be also provided. So, I think the "easiest" way would be a fallback to vfat in anaconda. A quick look into the code shows that this platform is recognized as "macefi". Forcing it to "efi" would allow anaconda going the path with vfat. https://github.com/rhinstaller/anaconda/blob/55492ad6166f2cd7aed0e802bdf5b4875dc20f29/tests/nosetests/pyanaconda_tests/modules/storage/platform_test.py Line 171 (efi) and 207 (macefi) Not sure if upstream is interested but I filled a bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1896960 -- Leon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] run firefox via an ssh tunnel
Am 12.11.20 um 13:56 schrieb Bernstein, Noam CIV USN NRL (6393) Washington DC (USA) via CentOS: If the point is to access a specific web site only the remote machine can get to, you can also do it with port forwarding: ssh -L 8000:ip_of_web_site_to_access_from_remote:443 remote_machine and then locally run any browser, and access https://localhost:443 (assuming it's https. If it's plain http, use "http" and 80). Note that you'll be breaking some aspects of https security such as man-in-the-middle protection and perhaps others, and you'll need to accept some security exceptions. This will be useful if the point is to get to a web site only only the remote machine can connect to, but all the browser code/plugins will be the local ones. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos This would not allow having access to SNI hostings (without dns tricks). Anyway, the original question was to forward a _native_ OSX output via X11 to the linux workstation. That is not possible but you can enable remotedesktop service on the osx machine and passing this through a ssh tunnel like "-L 5900:localhost:5900 -N" and accessing the osx machine via VNC. A complete different option is: having a opensource port distribution installed (like macports.org) and installing firefox that runs under https://www.xquartz.org/. Not quite centos related ... -- Leon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] run firefox via an ssh tunnel
If the point is to access a specific web site only the remote machine can get to, you can also do it with port forwarding: ssh -L 8000:ip_of_web_site_to_access_from_remote:443 remote_machine and then locally run any browser, and access https://localhost:443 (assuming it's https. If it's plain http, use "http" and 80). Note that you'll be breaking some aspects of https security such as man-in-the-middle protection and perhaps others, and you'll need to accept some security exceptions. This will be useful if the point is to get to a web site only only the remote machine can connect to, but all the browser code/plugins will be the local ones. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS-announce] Release for CentOS Linux 7 (2009) on the x86_64 Architecture
Release for CentOS Linux 7 (2009) on the x86_64 Architecture We are pleased to announce the general availability of CentOS Linux 7 (2009) for the x86_64 architecture. Effectively immediately, this is the current release for CentOS Linux 7 and is tagged as 2009, derived from Red Hat Enterprise Linux 7.9 Source Code. As always, read through the Release Notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users. -- Updates, Sources, and DebugInfos Updates released since the upstream release are all posted, across all architectures. We strongly recommend every user apply all updates, including the content released today, on your existing CentOS Linux 7 machine by just running 'yum update'. As with all CentOS Linux 7 components, this release was built from sources hosted at git.centos.org. In addition, SRPMs that are a byproduct of the build (and also considered critical in the code and buildsys process) are being published to match every binary RPM we release. Sources will be available from vault.centos.org in their own dedicated directories to match the corresponding binary RPMs. Since there is far less traffic to the CentOS source RPMs compared with the binary RPMs, we are not putting this content on the main mirror network. If users wish to mirror this content they can do so using the reposync command available in the yum-utils package. All CentOS source RPMs are signed with the same key used to sign their binary counterparts. Developers and end users looking at inspecting and contributing patches to the CentOS Linux distro will find the code hosted at git.centos.org far simpler to work against. Details on how to best consume those are documented along with a quick start at : http://wiki.centos.org/Sources Debuginfo packages are also being signed and pushed. Yum configs shipped in the new release file will have all the context required for debuginfo to be available on every CentOS Linux install. This release supersedes all previously released content for CentOS Linux 7, and therefore we highly encourage all users to upgrade their machines. Information on different upgrade strategies and how to handle stale content is included in the Release Notes. Note that older content, obsoleted by newer versions of the same applications are trim'd off from repos like Extras/ and Plus/ However this time we have also extended this to the SIG content hosted at mirror.centos.org, and some older End of Life content has been dropped. Everything we ever release, is always available on the vault service for people still looking for and have a real need for it. -- Download In order to conserve donor bandwidth, and to make it possible to get the mirror content sync'd out as soon as possible, we recommend using torrents to get your initial installer images: Details on the images are available on the mirrors at http://mirror.centos.org/centos/7/isos/x86_64/0_README.txt - that file clearly highlights the difference in the images, and when one might be more suitable than the others. sha256sum x86_64: e33d7b1ea7a9e2f38c8f693215dd85254c3a4fe446f93f563279715b68d07987 CentOS-7-x86_64-DVD-2009.iso 689531cce9cf484378481ae762fae362791a9be078fda10e4f6977bf8fa71350 CentOS-7-x86_64-Everything-2009.iso 07b94e6b1a0b0260b94c83d6bb76b26bf7a310dc78d7a9c7432809fb9bc6194a CentOS-7-x86_64-Minimal-2009.iso b79079ad71cc3c5ceb3561fff348a1b67ee37f71f4cddfec09480d4589c191d6 CentOS-7-x86_64-NetInstall-2009.iso Information for the torrent files and sums are available at http://mirror.centos.org/centos/7/isos/x86_64 Additional Images The Cloud images are posted here: https://cloud.centos.org/centos/7/images/ The container and Vagrant images are being prepared and will be released in the next few days. Look for an announcement posted to the centos-announce list for more information on availability for these in the coming days. -- Getting Help The CentOS ecosystem is sustained by community driven help and guidance. The best place to start for new users is at http://wiki.centos.org/GettingHelp We are also on social media, you can find the project: on Twitter at : http://twitter.com/CentOSProject on Facebook at : https://www.facebook.com/groups/centosproject/ on LinkedIn at : https://www.linkedin.com/groups/22405 And you will find the core team and a majority of the contributors on irc, on freenode.net in #centos ; talking about the finer points of distribution engineering and platform enablement. -- Contributors This release was made possible due to the hard work of many people, foremost on that list are the Red Hat Engineers for producing a great distribution and the CentOS QA team, without them CentOS Linux would look very different. Many of the team went
[CentOS-announce] Release for CentOS Linux 7 (2009) on armhfp aarch64 i386 ppc64 ppc64le and power9
I am pleased to announce the general availability of CentOS Linux 7 (2009) for across our alternative architectures. Effectively immediately, this is the current release for CentOS Linux 7 and is tagged as 2009, derived from Red Hat Enterprise Linux 7.9. As always, read through the Release Notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users. -- Updates, Sources, and DebugInfos Updates released since the upstream release are all posted, across all architectures. We strongly recommend every user apply all updates, including the content released today, on your existing CentOS Linux 7 machine by just running 'yum update'. As with all CentOS Linux 7 components, this release was built from sources hosted at git.centos.org. In addition, SRPMs that are a byproduct of the build (and also considered critical in the code and buildsys process) are being published to match every binary RPM we release. Sources will be available from vault.centos.org in their own dedicated directories to match the corresponding binary RPMs. Since there is far less traffic to the CentOS source RPMs compared with the binary RPMs, we are not putting this content on the main mirror network. If users wish to mirror this content they can do so using the reposync command available in the yum-utils package. All CentOS source RPMs are signed with the same key used to sign their binary counterparts. Developers and end users looking at inspecting and contributing patches to the CentOS Linux distro will find the code hosted at git.centos.org far simpler to work against. Details on how to best consume those are documented along with a quick start at : http://wiki.centos.org/Sources Debuginfo packages are also being signed and pushed. Yum configs shipped in the new release file will have all the context required for debuginfo to be available on every CentOS Linux install. This release supersedes all previously released content for CentOS Linux 7, and therefore we highly encourage all users to upgrade their machines. Information on different upgrade strategies and how to handle stale content is included in the Release Notes. Note that older content, obsoleted by newer versions of the same applications are trimmed off from repos like Extras/ and Plus/ However this time we have also extended this to the SIG content hosted at mirror.centos.org, and some older End of Life content has been dropped. Everything we ever release, is always available on the vault service for people still looking for and have a real need for it. -- Special notes Altarch kernel: After RedHat's decision to deprecate power9 and aarch64 releases during the 7.7 cycle, and our decision to keep building them with the others (using the kernel from RHEL8), we decided to keep down this road. As 7.x and 8.x releases are not in sync, released kernel is 4.18.0-193.28.1 (8.2), but we're working on updating it to 4.18.0-240 (8.3) soon. -- Download In order to conserve donor bandwidth, and to make it possible to get the mirror content sync'd out as soon as possible, we recommend using torrents to get your initial installer images: Details on the images are available on the mirrors in a file called 0_README.txt next to the isos. That file clearly highlights the difference in the images, and when one might be more suitable than the others. Altarch images can be downloaded at : http://mirror.centos.org/altarch/7/isos/ sha256sum for ppc64 1f53ccce8867412a91eca3d0dd99333ebef871ffba3b6fb3af7eb14e280dc653 CentOS-7-ppc64-Everything-2009.iso dbc2d0609140f5d689dd16cdb64bfa181bf2c31f72ff41b9ab9dd5241dd74e0e CentOS-7-ppc64-NetInstall-2009.iso 2cae62d1e24965de6d62c8031d0be745f836c99f9640184055fc4d99e29be966 CentOS-7-ppc64-Minimal-2009.iso sha256sum for ppc64le 1e1f4a7cebd9fa99af5de34543ae8d874c2fa2ac9ca16b17dbef85a7f36f8ea4 CentOS-7-ppc64le-Everything-2009.iso 76423e534281666d00c0989ab7e4cb48e0b412207a9e8fd6269bfef23a7e71c7 CentOS-7-ppc64le-NetInstall-2009.iso 145286cee095acc549b6fb9ebcaa394bb6d4919b7f95a0b0aa4a707a57ea80ed CentOS-7-ppc64le-Minimal-2009.iso sha256sum for power9: d7b93fe2c33dd4ed01c1b83c7abd20d20e5a46e9da469c1df1f506f19f1278b3 CentOS-7-power9-Everything-2009.iso 4795492d5361268aad79be27123c78909925f5648489f790718df6d6b7c0b039 CentOS-7-power9-NetInstall-2009.iso e4bd38480e65a4462004f30f69c4b193c687e77b7ad96d567c33581a64873568 CentOS-7-power9-Minimal-2009.iso sha256sum for i386: dd238357e1750cfb25fc87e5c21891598599bf5df3ee2a749a6fd1a8fe5ec937 CentOS-7-i386-Everything-2009.iso 96c3ae101f200cac2c0d6d03a1642d69cc8f501a568ce2cc3e5ffdfdc090145f CentOS-7-i386-NetInstall-2009.iso bcbde5d345c5013fa618c38380765547be01a354883b3055f32d7067dd7b5bca
