So you want to be a Slacker! What do I do next?

onebuck · 06-02-2023, 12:32 PM

Hi,

Eric (alienbob) just released; Chromium 114 Early Release on Slackware

Quote:

Posted on May 27, 2023 by alienbob

An “early release” of Chromium 114 source code was published a few days ago, the release notes are on the developer blog. Since Chromium 110, Google rolls out new major releases to a small sub-set of its users to monitor any potential breakage and apply fixes before the majority of users get upgraded. The formal release of Chromium will be on May 30th, but I decided to go along with the early release this time, and offer this version to Slackware users already this weekend, to celebrate the Pentecost

Looking at the new stuff in Chromium 114, there’s two things you might want to play with, since they are already contained in the browser and mostly usable in Chromium 114, but not yet enabled by default.

By toggling the flag “chrome://flags/#chrome-refresh-2023” from “default” to “enabled” the ongoing work will be revealed to bring a new User Interface design (Material You) to the desktop browser. A new tab design, new icons and work on the dark theme is visible. This new UI is scheduled for release in September 2023.
The toggle “chrome://flags/#password-manager-redesign” will enable a revamped Google Password Manager. It wants to look more like a standalone application and Chromium will ask you if you want to “install the app” which basically just adds a shortcut to “chrome://password-manager/passwords” in the “three-dots” sidebar menu. I was not yet impressed with this one, as it was unable to show me the passwords I had already saved in Chromium before. Yet is was obvious that my passwords were present since the password manager was able to check them all for compromise and weakness. So, I toggled this one back to “default” and will wait for Google to mature and stabilize it.
Also obvious is the disappearance of the “lock” icon which was an indication that you were visiting a secure “https” site. The lock has been replaced by a settings icon but functionally nothing much changed, as is shown when you click that icon.
Slackware packages (15.0 and -current) for Chromium 114.0.5735.45 are available for download from my repository or any of its mirrors.
The Un-googled version of my Chromium browser package will probably have to wait until May 30th – the formal release date of Chromium 114. There is no sign that Eloston will release a tarball sooner.
Enjoy! Eric

Hope this helps!

onebuck · 06-20-2023, 10:40 AM

Hi,
alienbob has been busy of late;

Quote:

Chromium 114.0.5735.133 packages address critical bug
Posted on June 17, 2023 by alienbob

Chromium, regular and un-googled.
Earlier this week, Google released its 114.0.5735.133 update for Chromium 114.
This is a bugfix release and on the list of addressed security issues, there’s one which is labeled as ‘critical‘, labeled CVE-2023-3214. Three other fixes are labeled with a vulnerability rating of ‘high‘.
As always, it is wise to upgrade to my latest chromium and chromium-ungoogled packages.
The updated Slackware 15.0 and -current packages both for chromium and chromium-ungoogled are available in my repository and its mirrors (like my own US server and in a short while, the UK mirror).
Cheers, Eric

Hope this helps.

onebuck · 06-26-2024, 09:06 AM

Hi,

I frequently use 'mirror-slackware-current.sh' and is still the best way to get your '-current' ISO. Be sure to check your md5sum for the burnt ISO image since the download md5sum is already done for you.

Hope this helps!

r1w1s1 · 06-26-2024, 09:30 PM

Quote:

Originally Posted by onebuck

Hi,

I frequently use 'mirror-slackware-current.sh' and is still the best way to get your '-current' ISO. Be sure to check your md5sum for the burnt ISO image since the download md5sum is already done for you.

Hope this helps!

The best way

my slackpkg running better using local mirror

for sure.

onebuck · 08-29-2024, 12:27 PM

Hi,

I know that this information has been posted before but lately a lot of queries of late could be answered by looking at the informational files available to users.

Code:

ls  /yourISO/mntPoint/slackware/slackware64-15.0/*  

/mnt/sdc2/slackware/slackware64-15.0/ANNOUNCE.15.0          /mnt/sdc2/slackware/slackware64-15.0/README.TXT 
/mnt/sdc2/slackware/slackware64-15.0/CHANGES_AND_HINTS.TXT  /mnt/sdc2/slackware/slackware64-15.0/README.initrd 
/mnt/sdc2/slackware/slackware64-15.0/CHECKSUMS.md5          /mnt/sdc2/slackware/slackware64-15.0/README_CRYPT.TXT 
/mnt/sdc2/slackware/slackware64-15.0/CHECKSUMS.md5.asc      /mnt/sdc2/slackware/slackware64-15.0/README_LVM.TXT 
/mnt/sdc2/slackware/slackware64-15.0/COPYING                /mnt/sdc2/slackware/slackware64-15.0/README_RAID.TXT 
/mnt/sdc2/slackware/slackware64-15.0/COPYING3               /mnt/sdc2/slackware/slackware64-15.0/README_UEFI.TXT 
/mnt/sdc2/slackware/slackware64-15.0/COPYRIGHT.TXT          /mnt/sdc2/slackware/slackware64-15.0/RELEASE_NOTES 
/mnt/sdc2/slackware/slackware64-15.0/CRYPTO_NOTICE.TXT      /mnt/sdc2/slackware/slackware64-15.0/SPEAKUP_DOCS.TXT 
/mnt/sdc2/slackware/slackware64-15.0/ChangeLog.txt          /mnt/sdc2/slackware/slackware64-15.0/SPEAK_INSTALL.TXT 
/mnt/sdc2/slackware/slackware64-15.0/FILELIST.TXT           /mnt/sdc2/slackware/slackware64-15.0/Slackware-HOWTO 
/mnt/sdc2/slackware/slackware64-15.0/GPG-KEY                /mnt/sdc2/slackware/slackware64-15.0/UPGRADE.TXT 
/mnt/sdc2/slackware/slackware64-15.0/PACKAGES.TXT

Hope this helps!