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.
I suggest you to wait a little before syncing your mirrors, because it seems this time Pat hasn't used the --delete rsync flag to sync his own, so old version of the packages are still there.
I think the new release is very close, read the changelogs:
Nope. Hold your horses, this is just a simple change in one file. It shows what the next version will be called.
Expect to see release candidates and other humdrum prior to an actual release.
Nice set of updates, especially for KDE fans. I was hoping to see some XFCE bumpage, but I've waited this long, I can wait a little longer.
BTW, Anyone else notice Pat's use of "slackware-next" in the comments for the kernel package? Far more descriptive name than "slackware-current" which has always seemed a bit of a misnomer. I like it.
I will wait for my local mirror to sync, but I am curious about this.
Quote:
n/network-scripts-14.00-noarch-1.txz: Upgraded.
Fixed handling of unique options for DHCP on multiple interfaces.
Thanks to irfan.acar and FeyFre. Added support for bridging. Thanks to alienBOB.
I will wait for my local mirror to sync, but I am curious about this.
From the new rc.inet1.conf file:
Code:
# Example of how to configure a bridge:
# Note the added "BRNICS" variable which contains a space-separated list
# of the physical network interfaces you want to add to the bridge.
#IFNAME[0]="br0"
#BRNICS[0]="eth0"
#IPADDR[0]="192.168.0.1"
#NETMASK[0]="255.255.255.0"
#USE_DHCP[0]=""
#DHCP_HOSTNAME[0]=""
Setting up a bridged interface will be helpful to get a virtual machine connected to the network. For some scenarios a bridge works better than a NAT solution - a bridged network connection will allow your VM's to be accessible from the network so that you can run network services inside the VM.
See my rc.vdenetwork script for an example of how to setup a bridged configuration which uses VDE to connect virtual machines (QEMU in my case) to the LAN.
This is the configuration I use to build all my packages.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.