SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,105
Rep:
Quote:
Originally Posted by SqdnGuns
'83 - '95 (Medically Retired)
H&MS-16 @ MCAS (H) Tustin (Supply)
H&MS-13 / MAG-13 HQ / H&HS @ MCAS El Toro (Supply / Group CO Driver / Water Safety Survival Instructor)
2nd LAV Bn @ Camp LeJeune (Supply / Weapons Company LAV Crewman)
3rd LSB @ Camp Foster / Camp Hansen (Bn Primary Marksmanship Instructor)
CSSD-36 @ Pohang, S Korea (Guard Chief Team Spirit)
12th MCD @ RS Orange (Recruiter and NCOIC)
MWHS-3 @ MCAS El Toro (Sqdn Gunny)
Semper Fi!
Hey Gunny!
My, you did get around.
I've wondered over the years if there wasn't a guardian angel looking over my shoulder. At one time everyone I served with was a combat vet.
It was MCRD in San Diego. ITR at Camp Pendleton. The Marine Barracks at Navy Memphis. Huge base, now closed, IIRC. The Marine Barracks at NAS, Willow Grove, PA, another closed base. Henderson Hall and, finally, The American Embassy, Paris, France. After my active duty tour was up, I picked up my DD-214 at the Embassy one morning and that was that. For whatever reasons the DD-214 says I separated in Germany, but is not correct. Doesn't matter at this point. The Honorable Discharge arrived by mail later once the six year obligation had been completed. Is it still six years for enlisted? IIRC, once one becomes a SNCO, it is extended?
I've heard Henderson Hall is now some sort of "joint base" with Fort Myer?
I was only there for a less than two months and didn't even know it was next to Fort Myer.
https://en.wikipedia.org/wiki/Hender...gton,_Virginia)
It is just a short walk down Columbia Pike to the administrative offices of HQMC.
The Commandant lives at 8th and I, in the District. That place is a fortress in and of itself. https://en.wikipedia.org/wiki/Marine...ashington,_D.C.
Went to check it out one day and they wouldn't let us, another Embassy School Marine and myself, with proper ID, through the gate. They did, finally, let us step just far enough inside the gate we could see the entire base. It is only about two blocks long, if not one long block, and one block wide. The Commandant's home is at the north end and from inside the gate it looks like a beautiful old Victorian. From the outside, on that end, all you can see is a tall concrete wall, with two or three heavy duty metal 'garage doors" equally spaced along the wall.
Just rambling on.
Thanks for listening.
Last edited by cwizardone; 08-20-2021 at 08:11 PM.
Reason: Typo.
1 members found this post helpful.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,105
Rep:
Quote:
Originally Posted by SCerovec
Speaking of fishing, I usually am apt in drowning the worm or any other kind of bait in any surface of water of choice. } .......
Ditto.
Then someone told me about Panther Martin lures. These things are just amazing, especially when fishing for trout. If you can't catch a fish with the right lure (for what your trying to catch) there are no fish in the river or lake. https://www.panthermartin.com/
Edit in: One of the things I like about the lures is it keeps you active, that is, you just don't toss in your line and wait.
With the lure you cast and retrieve. On one trip I was standing at the edge of the stream, in the water, and while reeling in the lure the last several feet I wasn't paying much attention and looked down to see a trout chasing the lure. He was in fractions of an inch to biting the lure when, I guess, he saw me, just a couple of feet ahead and turned around and darted away. Strange looking trout. It was what is called a Tiger Trout. A cross between two types. This one actually had stripes, unlike the photo in Wikipedia.
I've had great luck with the simple gold barrel lure. They use to be made in Italy, but the last time I bought a few, several years ago, they were made in china. I sent the company a "unfriendly" letter.
As my children are now grown, I don't get up to the mountains as much as I would like.
Last edited by cwizardone; 08-22-2021 at 09:27 AM.
I've been running Slackware starting with version 3.0 back in 1998. Over the years I occasionally tried a few other Linux distros but for me Slackware always is King. My early versions of Slackware came as CDs in books. I bought my last few up to 14.2 when they were available as subscriptions through the Slackware store (as a way I could support Slackware; now I'm a Slackware patreon).
Like everyone else, I'm patiently waiting for version 15. Before now, I didn't follow development of the "current" version. I'm a simple user, only having time to just install and use Slackware OS and add apps, mostly from Alien Bob or SBo as I need them. I've downloaded "current" a few times recently but am confused having to keep upgrading it. For the simple way I use Slackware, should I just keep using 14.2 until a stable 15 version is released?
... For the simple way I use Slackware, should I just keep using 14.2 until a stable 15 version is released?
First of all, you are free to do wherever you want. Any reply here must be understood as a suggestion... Well, here is mine. If all apps that you use are working perfectly fine (no conflict/request version for libraries and other apps), you should always keep the stable version. Keep doing the security updates and enjoy the stability and simplicity of Slackware. I think that one should install Slackware-current only in three situations: (i) if you want to be a tester, report problems, etc; (ii) if you need some applications that doesn't work with the last stable version, although a partial update could solve that; (iii) if you want a system always updated and are not worried about eventual breaks that a development branch can bring.
For the simple way I use Slackware, should I just keep using 14.2 until a stable 15 version is released?
Only you can answer that. Of the 3 computers I have with Slackware, 2 are still on 14.2 and 1 is on -current, and even then only because the hardware is so new stock 14.2 won't run on it. 14.2 is still going strong, but it seems like 15.0 is so close. I'm waiting for 15.0 to be released to upgrade my 2 older computers.
@carriunix and @ drumz, Thanks, you guys, for your helpful suggestions. You both confirmed what I was thinking: to stick with 14.2 since 15.0 seems so close. I wish I knew enough to help test -current, but I'm not a power user. I simply enjoy using Slackware. My only problem with 14.2 really is that it has an old GLIBC version and a couple newer apps that I want to try won't install without a newer version. I can wait, though, and I'm sure the wait will be worth it.
My only problem with 14.2 really is that it has an old GLIBC version and a couple newer apps that I want to try won't install without a newer version. I can wait, though, and I'm sure the wait will be worth it.
You can hack around this Grab the glibc from current, extract somewhere (e.g. /opt/glibc) and ONLY when running those applications set LD_LIBRARY_PATH to point there, so it will prefer the newer glibc over the system glibc. You may need additional libraries from current, as well.
You can hack around this Grab the glibc from current, extract somewhere (e.g. /opt/glibc) and ONLY when running those applications set LD_LIBRARY_PATH to point there, so it will prefer the newer glibc over the system glibc. You may need additional libraries from current, as well.
Thanks for the info on this hack! I didn't know it would be that simple but I understand your explanation. I'll try this as soon as I get some time.
@carriunix and @ drumz, Thanks, you guys, for your helpful suggestions. You both confirmed what I was thinking: to stick with 14.2 since 15.0 seems so close. I wish I knew enough to help test -current, but I'm not a power user. I simply enjoy using Slackware. My only problem with 14.2 really is that it has an old GLIBC version and a couple newer apps that I want to try won't install without a newer version. I can wait, though, and I'm sure the wait will be worth it.
What programs do you want to use. I may be able to help. Slackware current has been super stable over the last 15 months.
Just upgrading the kernel a bunch. If you have a proprietary GPU like nvidia not that hard.
just keep a copy of the driver in /root
What programs do you want to use. I may be able to help.
The program fldigi for digital amateur radio is in 14.2 SlackBuilds.org but its version is very old: 4.0.12. I was able to use the SBo script to get fldigi version 4.1.16 compiled and installed but as of July 2021 they are now up to 4.1.19. Nothing beyond 4.1.16 that I compile and install will run on Slackware 14.2 due to glibc 2.23 (it needs 2.27). My opinion is that the programmers of fldigi should make it a little more backward compatible, but maybe they have a good reason. Anyway, just for curiosity sake, I want to test the hack and see if that makes it work (so I'll know how to do it). I know that fldigi 4.1.18 works on Slackware 15.0 because I tried it on -current and it is fine there. I'd be happy to upgrade to -current, because as you say it probably is very stable, but I think the final release should be soon.
In post #22 I have a solution to that issue. I am including reference here to help others that may have the same problem. Really frustrating and was a simple fix that I spent a lot of time trying to dig into a solution. As I stated; 'Patience is a virtue'.
Quote:
"Do what you love. Know your own bones; gnaw at it, bury it, unearth it, and gnaw it still." - Thoreau
I like to use Eric's script; mirror-slackware-current.shto keep my local '-current' tree up to date. If you are like me then the use of a USB flash drive is the economical way to use the ISO file. So I use as 'root';
Please note that the above in red is my local path, yours will vary. Your device '/dev/sdx' where x is your device id. You can use either 'fdisk -l' or 'lsblk' as root to get the USB device to use. Be sure to identify the correct device as you can get into issue(S) with the wrong device id when using 'dd'. New users should always use the 'man command' to get information concerning semantics & syntax. For future references; https://www.slackwiki.com/Install_Sl...SB_Flash_Drive
Just a gentle reminder on how there is a way to use the 'slackware64-current-install-dvd.iso' with a USB Flash.
With a new rc coming anytime then it is a way to get the ISO for your use economically.
Hope this helps.
Have fun & enjoy Gnu/Linux Slackware!
Last edited by onebuck; 09-07-2021 at 10:21 PM.
Reason: typo correction
I like to use Eric's script; mirror-slackware-current.shto keep my local '-current' tree up to date. If you are like me then the use of a USB flash drive is the economical way to use the ISO file. So I use as 'root';
If you want to skip the isohybrid option when creating your installation media, you can either change the defaults in the script or pass an option to automatically run isohybrid on the resulting ISO(s).
Code:
# If you want a 'hybrid' ISO image which can be copied directly to a USB stick
# to create a bootable USB media, set HYBRID to '1'.
# Corresponds to the '-u' option.
HYBRID=${HYBRID:-0}
Either change the above in the script or your custom conf file to 1 or pass HYBRID=1 to the script when running it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.