Re: [PLUG] VirtualBox on Slackware

[Ben Koenig]

My build order for VirtualBox using the SBo scripts would be as follows:

1) acpica
2) virtualbox-kernel
3) virtualbox

At this point I would test to make sure everything is working. If yes,
build and install virtualbox-extension-pack for other features. You don't
need the 'addon' packages, those are for use in a Slackware guest, not a
host.
Don't forget to create a vboxusers group and add yourself to it.

i'll also keep a copy of the build scripts and source archives on my local
system in case I need to rebuild it. virtualbox-kernel builds a kernel
module, so when you install security updates for your kernel this will need
to be rebuilt and reinstalled.
The other packages should be fine as long as you don't change the version
of the kernel package when you rebuild.

You can install from the self installing script they provide, but you will
probably need to re-run this script every time there is a kernel update. It
would be much cleaner to use a tgz package for it.

Also, these tgz package files you are creating are portable. You can back
them up to an external HDD or something so that you don't have to keep
rebuilding them. In the event that you need to reinstall Slackware or set
up a second computer, you can just install these packages without having to
go through all this compiling again.





On Sun, Dec 2, 2018 at 2:25 PM Tomas K  wrote:

> This is turning into general discussion - still I see the original
> point of this email tread in a need to reuse existing VirtualBox
> virtual machine image/installation.
>
> So it makes little sense to try do anything but VirtualBox.
>
> Often, the decision to use vBox was made decade or even longer ago.
> There was very little of KVM back then, so the choices were Xen, vBox
> or VMware. I would argue that Xen versus vBox 10-15 years ago was
> really matter of taste, remember vBox was being actively opened by Sun
> Microsystem.
>
> I do not think that it is good idea doing fresh long term virtual
> machine build in VMware or vBox today - Given the almost infinite
> desire/need for longevity of these installations; and our experience
> with fully commercial software over the course of multiple
> acquisitions. If VMware or vBox changes their mind about their license
> or support - one would find it extremely difficult, if not impossible,
> to install that VM on your next hardware 3-5 years from now.
>
> Tomas
>
> On Sun, 2018-12-02 at 13:43 -0800, King Beowulf wrote:
> > On 12/2/18 6:13 AM, Chuck Hast wrote:
> > > I see all of this and wonder if you have given thought to VMWare
> > > Player,
> > > for personal use it is
> > > free, I use it all of the time when I cannot get something to run
> > > under
> > > Wine, it sees the USB
> > > stuff quite well.
> > >
> > > I have not had issues with it seeing devices. I use it to program
> > > radios, I
> > > am running Win 10
> > > on a Ubuntu Mate 18.04 host. The radios look like serial USB
> > > devices to the
> > > OS. Most of them
> > > work just fine under wine, but one which seems the program is all
> > > buggered
> > > up and even a
> > > trick to run on Windows. Oh, I also use it for some Garmin stuff
> > > that will
> > > not work on Wine.
> > > Garmin should be ashamed, they sure use Linux behind the GPS
> > > screens on
> > > their products
> > > but cannot come up with a decent piece of software for Linux to
> > > talk to
> > > their products.
> > >
> > > Here is a bit from them about running workstation (player is WS
> > > without the
> > > license)  under
> > > Slack:
> > > https://kb.vmware.com/s/article/113
> > >
> > >
> >
> > Chuck,
> >
> > It all depends on one's linux zealotry and personal preferences.
> >
> > qemu - fully open source
> > Virtualbox - partially open source (uses qemu code in places)
> > VMWare - fully proprietary.
> >
> > qemu uses KVM modules already present in the Linux kernel.  VB and
> > VMware have their own mystery binaries.
> >
> > The link you posted has some factual errors.  Slackware uses a BSD
> > style
> > init system, which is NOT "unusual" and is also fully compatible with
> > System V init scripts.  See also http://www.slackware.com/config/init
> > .php
> >
> > Secondly, the statement
> >
> > "Keep in mind that Slackware is not an explicitly supported
> > distribution, mostly because of its unusual file layout."
> >
> > bespeaks of a great deal of ignorance regarding Linux file systems
> > and
> > layouts.  I personally prefer qemu (fewer extra dependencies but
> > harder
> > CLI configuration), with Virtualbox as a second choice (nice gui).
> >
> > -Ed
> >
> >
> >
> >
> > ___
> > PLUG mailing list
> > PLUG@pdxlinux.org
> > http://lists.pdxlinux.org/mailman/listinfo/plug
> ___
> PLUG mailing list
> PLUG@pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
___
PLUG mailing list
PLUG@pdxlinux.org

Re: [PLUG] KDE (?) Middle Button with Trackpoint

[Ben Koenig]

mouse/keyboard settings are part of the "Input Devices" Settings module.

So K Menu -> System Settings -> Input devices. There's a tab for mouse
settings on the left.

On Sun, Dec 2, 2018 at 9:44 PM Dick Steffens  wrote:

> I had the opportunity to use the Slackware laptop today. There's a
> missing feature. Where do I look for settings for the middle button on
> the laptop? I'm used to being able to hold that button down and scroll
> with the trackpoint. Is that a KDE setting or someplace else?
>
> --
> Regards,
>
> Dick Steffens
>
> ___
> PLUG mailing list
> PLUG@pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

[PLUG] KDE (?) Middle Button with Trackpoint

[Dick Steffens]

I had the opportunity to use the Slackware laptop today. There's a 
missing feature. Where do I look for settings for the middle button on 
the laptop? I'm used to being able to hold that button down and scroll 
with the trackpoint. Is that a KDE setting or someplace else?


--
Regards,

Dick Steffens

___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

[PLUG] Flashplayer for Slackware

[Dick Steffens]

I read news from a number of websites. Sometimes there are videos. I got 
a message telling me that I need flashplayer. Is the one at 
http://www.slackware.com/~alien/slackbuilds/flashplayer-plugin/ the one 
I should use? (pkg64, 14.2)


--
Regards,

Dick Steffens

___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

[PLUG] Was the fellow in Minnesota (?) still looking for work? We have a job posting in Portland

[Vedanta Teacher]

Greetings,

  I'm sorry about the delay but was the fellow in Minnesota (?) still
looking for
a job? We have a job posting for an IT/Network helper @ 50K. We're just
off Highway 26 and Murray in Portland. I do have contact info in recruiting.

Blessings,

Paul W.
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] VirtualBox on Slackware

[Tomas K]

This is turning into general discussion - still I see the original
point of this email tread in a need to reuse existing VirtualBox
virtual machine image/installation.

So it makes little sense to try do anything but VirtualBox.

Often, the decision to use vBox was made decade or even longer ago.
There was very little of KVM back then, so the choices were Xen, vBox
or VMware. I would argue that Xen versus vBox 10-15 years ago was
really matter of taste, remember vBox was being actively opened by Sun
Microsystem.

I do not think that it is good idea doing fresh long term virtual
machine build in VMware or vBox today - Given the almost infinite
desire/need for longevity of these installations; and our experience
with fully commercial software over the course of multiple
acquisitions. If VMware or vBox changes their mind about their license
or support - one would find it extremely difficult, if not impossible,
to install that VM on your next hardware 3-5 years from now.

Tomas

On Sun, 2018-12-02 at 13:43 -0800, King Beowulf wrote:
> On 12/2/18 6:13 AM, Chuck Hast wrote:
> > I see all of this and wonder if you have given thought to VMWare
> > Player,
> > for personal use it is
> > free, I use it all of the time when I cannot get something to run
> > under
> > Wine, it sees the USB
> > stuff quite well.
> > 
> > I have not had issues with it seeing devices. I use it to program
> > radios, I
> > am running Win 10
> > on a Ubuntu Mate 18.04 host. The radios look like serial USB
> > devices to the
> > OS. Most of them
> > work just fine under wine, but one which seems the program is all
> > buggered
> > up and even a
> > trick to run on Windows. Oh, I also use it for some Garmin stuff
> > that will
> > not work on Wine.
> > Garmin should be ashamed, they sure use Linux behind the GPS
> > screens on
> > their products
> > but cannot come up with a decent piece of software for Linux to
> > talk to
> > their products.
> > 
> > Here is a bit from them about running workstation (player is WS
> > without the
> > license)  under
> > Slack:
> > https://kb.vmware.com/s/article/113
> > 
> > 
> 
> Chuck,
> 
> It all depends on one's linux zealotry and personal preferences.
> 
> qemu - fully open source
> Virtualbox - partially open source (uses qemu code in places)
> VMWare - fully proprietary.
> 
> qemu uses KVM modules already present in the Linux kernel.  VB and
> VMware have their own mystery binaries.
> 
> The link you posted has some factual errors.  Slackware uses a BSD
> style
> init system, which is NOT "unusual" and is also fully compatible with
> System V init scripts.  See also http://www.slackware.com/config/init
> .php
> 
> Secondly, the statement
> 
> "Keep in mind that Slackware is not an explicitly supported
> distribution, mostly because of its unusual file layout."
> 
> bespeaks of a great deal of ignorance regarding Linux file systems
> and
> layouts.  I personally prefer qemu (fewer extra dependencies but
> harder
> CLI configuration), with Virtualbox as a second choice (nice gui).
> 
> -Ed
> 
> 
> 
> 
> ___
> PLUG mailing list
> PLUG@pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] VirtualBox on Slackware

[Chuck Hast]

-Ed

I use qemu for dos stuff (Motorola radio programming software that is so
old that it is almost
machine specific, qemu lets you tweak the thing until it decides to run

The Windows 10 VM started out as a windows 7 which got upgraded. I used
VMWare ESXi
while working at a job to hold VM's for food safety databases (the idea
was/is to track food
"from gate to plate" so that you could quickly pinpoint where the bad stuff
came from (guess
it did not work so well with the lettuce) I got used to using VMWare there
and used Player to
test my VM's out before loading them up on the Hypersphere systems (ESXi
system) I tried to
get VB working but it bucked when dealing with weird serial port issues
(see Motorola above)
qemu and Player have done just fine.

Yeah it is closed, but for personal use free. I can spin one up pretty fast
for testing something,
so I have stayed with it.

I should go back and give VB a try again, they have probably solved the
serial port issues
by now since that was back in 2011.

Indeed I use Multisystem which is a VM running in VB. Lets me keep a bunch
of OS images
on a stick, choose and boot them. The app when running on the computer I
use to load new
images into the usb stick runs in VM and does quite well. I had forgot
about that. It is fast and
never seems to give issues. I pull down a new image fire up Multisystem and
stuff it on the
test stick.


On Sun, Dec 2, 2018 at 3:43 PM King Beowulf  wrote:

> On 12/2/18 6:13 AM, Chuck Hast wrote:
> > I see all of this and wonder if you have given thought to VMWare Player,
> > for personal use it is
> > free, I use it all of the time when I cannot get something to run under
> > Wine, it sees the USB
> > stuff quite well.
> >
> > I have not had issues with it seeing devices. I use it to program
> radios, I
> > am running Win 10
> > on a Ubuntu Mate 18.04 host. The radios look like serial USB devices to
> the
> > OS. Most of them
> > work just fine under wine, but one which seems the program is all
> buggered
> > up and even a
> > trick to run on Windows. Oh, I also use it for some Garmin stuff that
> will
> > not work on Wine.
> > Garmin should be ashamed, they sure use Linux behind the GPS screens on
> > their products
> > but cannot come up with a decent piece of software for Linux to talk to
> > their products.
> >
> > Here is a bit from them about running workstation (player is WS without
> the
> > license)  under
> > Slack:
> > https://kb.vmware.com/s/article/113
> >
> >
>
> Chuck,
>
> It all depends on one's linux zealotry and personal preferences.
>
> qemu - fully open source
> Virtualbox - partially open source (uses qemu code in places)
> VMWare - fully proprietary.
>
> qemu uses KVM modules already present in the Linux kernel.  VB and
> VMware have their own mystery binaries.
>
> The link you posted has some factual errors.  Slackware uses a BSD style
> init system, which is NOT "unusual" and is also fully compatible with
> System V init scripts.  See also http://www.slackware.com/config/init.php
>
> Secondly, the statement
>
> "Keep in mind that Slackware is not an explicitly supported
> distribution, mostly because of its unusual file layout."
>
> bespeaks of a great deal of ignorance regarding Linux file systems and
> layouts.  I personally prefer qemu (fewer extra dependencies but harder
> CLI configuration), with Virtualbox as a second choice (nice gui).
>
> -Ed
>
>
>
>
> ___
> PLUG mailing list
> PLUG@pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>


-- 

Chuck Hast  -- KP4DJT --
I can do all things through Christ which strengtheneth me.
Ph 4:13 KJV
Todo lo puedo en Cristo que me fortalece.
Fil 4:13 RVR1960
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] VirtualBox on Slackware

[King Beowulf]

On 12/2/18 6:13 AM, Chuck Hast wrote:
> I see all of this and wonder if you have given thought to VMWare Player,
> for personal use it is
> free, I use it all of the time when I cannot get something to run under
> Wine, it sees the USB
> stuff quite well.
> 
> I have not had issues with it seeing devices. I use it to program radios, I
> am running Win 10
> on a Ubuntu Mate 18.04 host. The radios look like serial USB devices to the
> OS. Most of them
> work just fine under wine, but one which seems the program is all buggered
> up and even a
> trick to run on Windows. Oh, I also use it for some Garmin stuff that will
> not work on Wine.
> Garmin should be ashamed, they sure use Linux behind the GPS screens on
> their products
> but cannot come up with a decent piece of software for Linux to talk to
> their products.
> 
> Here is a bit from them about running workstation (player is WS without the
> license)  under
> Slack:
> https://kb.vmware.com/s/article/113
> 
> 

Chuck,

It all depends on one's linux zealotry and personal preferences.

qemu - fully open source
Virtualbox - partially open source (uses qemu code in places)
VMWare - fully proprietary.

qemu uses KVM modules already present in the Linux kernel.  VB and
VMware have their own mystery binaries.

The link you posted has some factual errors.  Slackware uses a BSD style
init system, which is NOT "unusual" and is also fully compatible with
System V init scripts.  See also http://www.slackware.com/config/init.php

Secondly, the statement

"Keep in mind that Slackware is not an explicitly supported
distribution, mostly because of its unusual file layout."

bespeaks of a great deal of ignorance regarding Linux file systems and
layouts.  I personally prefer qemu (fewer extra dependencies but harder
CLI configuration), with Virtualbox as a second choice (nice gui).

-Ed






signature.asc
Description: OpenPGP digital signature
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] FreeNAS trouble Mac...

[Louis Kowolowski]

Apple has no trouble accessing SMB shares. Apple supports doing everything over 
SMB now, including TimeMachine. Note that FreeNAS doesn’t support this yet. 
There is an open ticket for supporting it. Apple has (for several years now) 
had AFP support as deprecated. Its recommended you move everything to SMB 
(exception being TimeMachine shares).
I’m doing this with mine and it works fine. 

> On Dec 1, 2018, at 2:24 PM, Michael Christopher Robinson 
>  wrote:
> 
> On my Mac Mini 2014 I'm getting this error:
> 
> The operation can't be completed because the original item for
> "MichaelcRobinson" can't be found.
> 
> Note that my AFP share is MichaelcRobinson and yes it exists.  I 
> can access it from Fedora 29 as an SMB share.
> 
> Is it even possible to export the same directory on a FreeNAS 11 update
> 6 box using both Apple and Microsoft style sharing?
> 
> What is this original item that can't be found?
> 
> ___
> PLUG mailing list
> PLUG@pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug

--
Louis Kowolowskilou...@cryptomonkeys.org 

Cryptomonkeys:   http://www.cryptomonkeys.com/ 


Making life more interesting for people since 1977

___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

[PLUG] Resolved: Slackware Wireless

[Dick Steffens]

On 12/2/18 9:19 AM, Ben Koenig wrote:

That's a good question. User-friendly network management tools involve 2
pieces. This is because on Linux platforms you need to be root to configure
network devices.

So for Network Manager, the 2 components are as follows:
- The network manager daemon: this is a background process that runs as
root in order to configure networks on behalf of the user.
- end user applets: These applets, such as the one with the red X in KDE
send the user's requested network preferences to the daemon.

the Wifi interface will be configured by the NetworkManager daemon process,
not by the applet or the user. The configuration of NetworkManager will
define what options are available to the user. So if the daemon process is
not running, the applet returns and error, in the form of that little red X.

The Slackware installer provides a few different options, either to set up
manually or just use DHCP for an automatic address.
If you are on a laptop, then you want NetworkManager to get up and running
with wifi.

Setting up wifi manually is a bit of a pain, and services such as
NetworkManager or WICD can make it a lot easier.

If you want to switch to NetworkManager, use the 'netconfig' command. This
is the tool that comes up during the install and will allow you to make
that change.


Done.


Once you do that, the icon on your system tray will start working
"automagically".


Didn't.


Switch over to it using netconfig, and let me know if you can get it up and
running. NetworkManager provides a great way to learn about daemon services
in Slackware since is one of the easier ones to start/stop.

I'm also curious to know if it runs out-of-the-box for you. There's been
some drama with the NetworkManager devs that can come into play here.


After a restart it works fine. I can now take the laptop down to the 
living room and use it.


I still need to get VirtualBox working, but I don't use it all the time, 
so I can come back to that one.


Thanks! Getting wireless working was fairly painless.

--
Regards,

Dick Steffens

___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Slackware Wireless

[Ben Koenig]

That's a good question. User-friendly network management tools involve 2
pieces. This is because on Linux platforms you need to be root to configure
network devices.

So for Network Manager, the 2 components are as follows:
- The network manager daemon: this is a background process that runs as
root in order to configure networks on behalf of the user.
- end user applets: These applets, such as the one with the red X in KDE
send the user's requested network preferences to the daemon.

the Wifi interface will be configured by the NetworkManager daemon process,
not by the applet or the user. The configuration of NetworkManager will
define what options are available to the user. So if the daemon process is
not running, the applet returns and error, in the form of that little red X.

The Slackware installer provides a few different options, either to set up
manually or just use DHCP for an automatic address.
If you are on a laptop, then you want NetworkManager to get up and running
with wifi.

Setting up wifi manually is a bit of a pain, and services such as
NetworkManager or WICD can make it a lot easier.

If you want to switch to NetworkManager, use the 'netconfig' command. This
is the tool that comes up during the install and will allow you to make
that change.
Once you do that, the icon on your system tray will start working
"automagically".

Switch over to it using netconfig, and let me know if you can get it up and
running. NetworkManager provides a great way to learn about daemon services
in Slackware since is one of the easier ones to start/stop.

I'm also curious to know if it runs out-of-the-box for you. There's been
some drama with the NetworkManager devs that can come into play here.

On Sun, Dec 2, 2018 at 7:48 AM Dick Steffens  wrote:

> This morning I thought I would take a look at what the Interwebs have to
> say about setting up wireless on my Slackware laptop. I recall a
> recommendation from this list to let Ben or Ed help me with that. After
> reviewing several websites, I can see why. So, later this afternoon,
> I'll be ready to hear the recommendations.
>
> When I installed Slackware I recall having to choose something regarding
> networking. One of the options was NetworkManager. I did not choose that
> option. I see an icon down in the task bar that looks like a
> representation of a monitor and keyboard. It has a red X on it's lower
> right corner. When I hover over it it says NetworkManager not running.
>
> This laptop has previously worked with my Buffalo Router, and with WiFi
> access points out in the scary world (such as at motels when we're on
> trips), so I know the hardware works. Now I just need assistance picking
> the right set of instructions to follow.
>
> Thanks in advance.
>
> --
> Regards,
>
> Dick Steffens
>
> ___
> PLUG mailing list
> PLUG@pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] VirtualBox on Slackware

[Chuck Hast]

I see all of this and wonder if you have given thought to VMWare Player,
for personal use it is
free, I use it all of the time when I cannot get something to run under
Wine, it sees the USB
stuff quite well.

I have not had issues with it seeing devices. I use it to program radios, I
am running Win 10
on a Ubuntu Mate 18.04 host. The radios look like serial USB devices to the
OS. Most of them
work just fine under wine, but one which seems the program is all buggered
up and even a
trick to run on Windows. Oh, I also use it for some Garmin stuff that will
not work on Wine.
Garmin should be ashamed, they sure use Linux behind the GPS screens on
their products
but cannot come up with a decent piece of software for Linux to talk to
their products.

Here is a bit from them about running workstation (player is WS without the
license)  under
Slack:
https://kb.vmware.com/s/article/113



On Sat, Dec 1, 2018 at 6:31 PM Dick Steffens  wrote:

> On 12/1/18 3:51 PM, King Beowulf wrote:
> > On 12/1/18 2:51 PM, Dick Steffens wrote:
> > ---snip---
> >
> > I can successfully scan individual files from the command line.
> >> I also installed clamtk, since that's what I'm used to using.
> >>  From the KDE menu I can find "Run clamtk" from the search menu.
> >> However, it doesn't run. I suspect I need to do some configuring
> somewhere.
> >>
> >> So, in general, it looks like I have figured out the process. I'll try a
> >> few more and see how they go.
> >>
> >>
> > Run clamtk binary from the command line. It will spit out an error
> > meesage.  Most likely you forgot to install one of the dependencies.
> > When the dep string gets long enough, I often forget one myself, or I
> > build it but then forget the installpkg step.
>
> Yep. Can't locate Glib.pm in @INC (you man need to install the Glib
> module) ...
>
> In slackbuilds.org/repository/14.2/perl/perl-glib/ there is a
> requirement for a couple of other things, perl-extutuls-depends, and
> perl-extutils-pkgconfig. Do I just treat each of those as a package like
> the ones I've already done?
>
>
> --
> Regards,
>
> Dick Steffens
>
>
> ___
> PLUG mailing list
> PLUG@pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>


-- 

Chuck Hast  -- KP4DJT --
I can do all things through Christ which strengtheneth me.
Ph 4:13 KJV
Todo lo puedo en Cristo que me fortalece.
Fil 4:13 RVR1960
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug