search for: slackware64

Hi, I have just installed Slackware64 13.0 Linux as a HVM guest with Xen 3.5-unstable changeset 20143 pv-ops dom0 kernel 2.6.31.4. For more details, please refer to the following link: http://enmingteo.wordpress.com/2009/11/01/picture-tutorial-how-to-setup-slackware64-13-0-hvm-domu-with-xen-3-5-unstable-pv-ops-dom0-kernel-2-6-31-4-in-...

Hi, I have just installed Slackware64 13.0 Linux as a HVM guest with Xen 3.5-unstable changeset 20143 pv-ops dom0 kernel 2.6.31.4. For more details, please refer to the following link: http://enmingteo.wordpress.com/2009/11/01/picture-tutorial-how-to-setup-slackware64-13-0-hvm-domu-with-xen-3-5-unstable-pv-ops-dom0-kernel-2-6-31-4-in-...

im having a error compiling wine version 1.3.0 on slackware64 i have the multilib gcc and 32 bit packages installed and i cannot compile i am getting this error. make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/root/wine-1.3.0/dlls/windebug.dll16' make[1]: Entering directory `/root/wine-1.3.0/dlls/windowscodecs' gcc -m32 -c -I....

...ect' > collect2: ld returned 1 exit status > make[3]: *** [nut-scanner] Error 1 > make[3]: Leaving directory `/home/cade/bad/nut-2.6.3/tools/nut-scanner' > make[2]: *** [all] Error 2 > =========================================================================== > > OS is Slackware64 Linux, -current > ah, Slack! my first (and so oldish now) run into the Linux world. gcc --version > gcc (GCC) 4.5.3 > > make --version > GNU Make 3.82 > Built for x86_64-slackware-linux-gnu > > tell me if you need more info? > > Thank you! > you have an installed...

On 04/16/2014 02:15 PM, Didier Spaier wrote: > Running "syslinux -s /dev/dsb" during installation of Slackware64-14.1 > (to make a bootable USB stick) fails like this: > > Error converting to codepage 850 Invalid argument > Cannot initialize 'S:' > Bad target s:/ldlinux.sys > syslinux: failed to create ldlinux.sys > > But running the same command in the installed system succ...

On 16/04/2014 23:46, H. Peter Anvin wrote: > On 04/16/2014 02:15 PM, Didier Spaier wrote: >> Running "syslinux -s /dev/dsb" during installation of Slackware64-14.1 >> (to make a bootable USB stick) fails like this: >> >> Error converting to codepage 850 Invalid argument >> Cannot initialize 'S:' >> Bad target s:/ldlinux.sys >> syslinux: failed to create ldlinux.sys >> >> But running the same comman...

Hello List, I'm trying to get libvirt to work on slackware64-current (slackware64-14.2 beta) and while it compiles just fine, it refuses to run because of an undefined symbol: 2016-03-01 20:09:26.822+0000: 27849: error : virDriverLoadModule:73 : failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_storage.so /usr/lib64/../lib64/libfl.so...

Running "syslinux -s /dev/dsb" during installation of Slackware64-14.1 (to make a bootable USB stick) fails like this: Error converting to codepage 850 Invalid argument Cannot initialize 'S:' Bad target s:/ldlinux.sys syslinux: failed to create ldlinux.sys But running the same command in the installed system succeeds. In both cases we are using syslin...

On 04/16/2014 04:07 PM, Didier Spaier wrote: > > Confirmed, thanks Hans. > Don't call me that, please. > > So I assume that we need to ship iconv in the initrd. > Or ship the "linux" version instead of the "mtools" version of syslinux, or use the extlinux installer and mount explicitly. -hpa

I am running Samba 4.4.16 on Slackware64 14.2. I have a domain member Windows 7 workstation. I upgraded the hardware on this computer a couple of weeks ago. I deleted the computer from the domain, the re-joined after finishing the upgrade. This computer show in the list with 'samba-tool group listmembers "Domain Computers"&...

Hello all, I'm having trouble compiling ocfs2-tools-1.6.3 on slackware64-13.1 These are my configure flags (the last 2 I added after googling this problem, but didn't help): ./configure \ --sbindir=/sbin \ --bin=/bin \ --libdir=/usr/lib${LIBDIRSUFFIX} \ --sysconfdir=/etc \ --datadir=/etc/ocfs2 \ --sharedstatedir=/var/ocfs2 \ --libexecdir=/usr/libexec...

...sed on what I consider rather expert advice, but it's not working as expected. I'm trying to determine if I've done something wrong with basic configuration or if there are AD/DC nuances afoot. The main nameserver is the domain Active Directory/Domain Controller running Samba 4.4.16 on Slackware64 14.2. This has been running for a few years w/o problem. It's domain IP is 192.168.0.2. I've attempted to configure a DNS slave on another Linux Slackware64 14.2 system, IP 192.168.0.3. This host is on the domain LAN, but is not a domain member. When bind is running on the slave, the zone...

I have a troubling circumstance. I've installed a new domain member running Slackware64 14.2. This computer is practically a clone of another domain member I've had set up and running for over a year. Most everything seems to work. I have joined the domain and it does show up as a domain computer. The domain user can log onto the computer just fine. I can run `wbinfo -u`, `wbinfo...

Has anyone gotten NTLM working with Dovecot and Outlook? I have a Samba4 domain controller / active directory running just fine on Linux Slackware64 14.1. PLAIN authenticiation works just fine if I create /etc/passwd accounts for the domain users. I've tried for over two weeks to get NTLM working from Outlook 2007 on a domain workstation without success. I end up with various permission errors and ultimately procmail won't deliver i...

...t. No success so far. When I choose the xen menu entry except from some characters being wiped from the bottom of the screen nothing is happening. I have made a typo in the xen kernel filename. Nothing changed, no errors about wrong a filename were displayed Initially I compiled syslinux 6.03 (slackware64, gcc 4.8.2). After this I used the efi64 files from a debian package (syslinux-common_6.03+dfsg-10_all.deb) Nothing changed. It looks like the system stops after loading mboot.c32 grub.efi is able to boot the same xen and vmlinux files. The bios: Version 2.16.1243. Copyright (C) 2013 America...

Hi, Some time ago one of my public servers (running Slackware64 14.0) got attacked and was misused to send phishing emails. This misadventure made me more concerned about security, so I spent the last few weeks catching up on security, reading docs about SELinux and how to use it, etc. I have a public sandbox server running CentOS 7, and I'm currently exp...

...on regarding interoperability with OpenSSL 1.1. I respect that entirely. That said, I've recently had to deal with a couple of users who had a specific set of requirements with building OpenSSH 7.7 using patches for OpenSSL 1.1 found in the slackware package. (http://slackblog.com/slackware/slackware64-current/source/n/openssh/) I found it annoying that this patch absolutely required OpenSSL 1.1 so I modified it to provide a single patch that will compile under OpenSSL 1.1 as well as earlier versions. Mostly it's just a whole lot of #if/#else/#endifs to work with the different interfaces....

I have a Samba4 AD/DC running on Slackware64 14.1, Samba version 4.2.12. This computer has been serving a Domain of several Windows 7 and one Linux domain members for about 2 years without problem. On a few occasions lately I've run the following command on the AD/DC: $ ntlm_auth --username="user" --password='password'...

...dvice on how to approach (or solve) this particular problem. I use Slackware Linux and compile Openssh from source. I prefer to compile it statically so it doesn't get messed up if I update openssl libraries. Up until now this approach was working OK for me. Lately I have been challenged with Slackware64 installations and I have come across a problem with Openssh version (5.3p1, but result is the same with 5.2p1). What happens is that sshd daemon keeps accepting connections as long as no one disconnects. On the first DISconnection the server daemon dies with segfault message, of which a strace outp...

...ook a peek in /etc/cron.daily, and the package already installed an /etc/cron.daily/0squidanalyzer script. I wanted to know at what time CentOS ran the cron.daily scripts, so I typed crontab -l, but there was only "no cronjobs defined for root". Here's how things look on a public Slackware64 14.0 server I administrate: # crontab -l ... # Run hourly cron jobs at 47 minutes after the hour: 47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: 40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30...