Pages

2016-05-07

Installing and configuring NAS

Motive: I already had some 7 computers and 2 e-book readers in household. I am working on 2-3-4 different machines... - file syncing and backuping started to bother me ... if we put it mildly. Problem was somehow aggravated by unholy mixup of systems: xp, 7, wheezy, antix, slackware etc.
Idea: Obvious - build a NAS for centralized sync and backup.
Easier said than done.

Hardware, very nonpro, as I didn't want to spend hugely for SOHO  solution...
MB: H110I-plus D3
CPU: Pentium
Memory: 16GB non-ecc,
OS: on 16GB USB stick,
HDD: WD red NASware, 4x2TB,
Ethernet: onboard realtek 8111H (and additional Intel NIC for some lagging),
Case: Bitfenix' Phenom (real nice, heavy metal, no bending, easy hdd-selves, good layout).
Build went quite smoothly - with one hickup: (small) cpu-cooler I bought was still a bit wide for cramped ITX. Intel stock cooler it was, then.

OP-system
Note: I am total noob in both NAS and BSD - the following AAR is therefore kinda simplistic, erratic and occasionally silly.
There were some reasons for not picking Linux - like I wanted to try BSD, and I didn't find satisfactory Linux-solution (whatever that means).
I started with current Nas4free. It installed nicely from usb to usb, booted (not very fast) ... and didn't have usable network driver. And I am talking - maybe - about a month of waiting, as freebsd 10.3 (with proper driver) is already released, but nas4free base is still 10.2 ... But I didn't feel like waiting and/or compiling patched driver in jail etc:
Freenas 9.10 (freebsd kernel 10.3) got downloaded, dd-d, installed, and it booted (a bit faster) with realtek support.
Install was uneventful - and went very much according to manual.
Then I shut down, connected HDDs to motherboard and rebooted.
And discovered the one problem with this install - new intel H110 chipset doesn't want to boot USB-system. Fortunately, the motherboards' bios has 'force boot from usb' option. So, F2 every time, and monitor+keyboard have to be close... Irritating, but survivable. Solution would be to use small SSD for system - but then we loose one SATA port (and PCIe sdd-s are sillily expencive).

When adding such a - well, revolutionary - part to old, self-accumulated home network, it's also good time to check the old shit over. My oldest is an  AMD X3 from 8 years past. And not to forget switches... I did check - and replaced one 10/100 switch and added one 1000 NIC to old AMD-box. No need to leave bottlenecks in new shiny installation.

As hardware building was easy and installing a tiny bit less so, then the following was quite frustrating and enormously time-google-wasting.

Configuration

# System
Now - it's possible to do quite a lot from webGUI, remotely. Still, there are some things which are better by console. So, one has to know at least some bsd commands and syntax (default csh is not unavoidable - bash is also installed).
WebGUI is big - so I am not going to blab of it. Read the same aforementioned manual. It's comprehensive. Not reciting manual goes also for text below.
I confed System first, then Storage (created volume and datasets), then user accounts. I planned to use both NFS and CIFS/Samba (afterthought - in mixed systems, maybe it's easier to stick with one - Samba). NFS - seems - wants your owner-user to have the same ID and GID as in client machine, which can be quite tiresome to achieve. If you have several differently dedicated datasets, then you probably also have to play around with groups - to give your users access to different places.
Also, NFS and some Windowses have relation-problems (win7pro doesn't recognize NFS natively, for example).
Next, Network, then Services (in my case: cifs, nfs, rsync and smart for starters) and then Sharing. The last one is absolutely essential - sharing opens datasets up for remote access. Among other conf options - here it's possible to close sharing(s) down for only LAN access, and/or for specific IPs.
This made me reorganize some of my boxes' IPs from dynamic to static - additional small hassle.

# CIFS/Samba
1. Additionally to (relatively simple) setting up CIFS service and share in NAS, samba(clients) need to be set up in client-machines. In Win7 it's as simple as connecting to server via explorers' network mapping. In Slackware there has to be - additionally to default-installed samba - valid /etc/samba/samba.conf. Daemon - /etc/rc.d/rc.samba does not need to be started, though.
I used Spacefms' plugin to mount samba shares. Doing it manually looks like this:
sudo smbclient //192.168.1.x/foldername -U username
The same can be achievad also with proper entry in /etc/fstab and then, if 'noauto' - mount /mnt/sambamountpoint.

# NFS
The same here, of course - client-machines have to be able to communicate with nfs-server. As mentioned, there is no satisfactory free solution for Win7Pro. In Slackware (in Antix 15.1 - nothing needs to be done, it works), start rpc daemon: sudo chmod 755 /etc/rc.d/rc.rpc && /etc/rc.d/rc.rpc start,
then, terminal way:
sudo mount -t nfs 192.168.1.x:/mnt/volume/dataset /mnt/mountpointname
fstab way looks something like that:
192.168.1.x:/mnt/volume/dataset /media/mountpointname nfs rw,noauto,noatime,user 0 0
So, afterwards it's only mount /media/mountpointname. Mount command for this can also be made in Spacefm as a, well, saved 'command'.
About confing: As I have couple of users for NFS, then I had to use 'mapall' in NAS' NFS-sharing options. Took me some time to figure that out. Also - I use nfs as passwordless 'guest' domain.

With both - smb and nfs - it's quite a lot of playing with user permissions - especially after in comes 'syncthing'.

# SYNCTHING
... comes with Freenas as an installable plugin-script. Script downloads stuff and installs it to jail. That ends the easy part.
For me, syncthing was the biggest time-waster to configure. It's wiki is not by far as comprehensive as Freenas one; it has bugs, it has quirks.
Still, after I got it running, I quite like it. I stress, though - be very careful, have a backup before experimenting! Syncing means that fucked-up (you, bug, ...) folder can fuck up all other synced folders... For important folders, do check versioning - if worst happens, you can get your shit back from trashcan - .stversions folder will be created when deletion occurs.

Syncthing creates user 'syncthing' (983:983) in jail. This complicates things with perms - some manual chowning needs to be done, myuser (same id-s as in dataset) needs to be created in jail; and syncthing should be member of this user group... Supposedly, it's easier to change 'syncthing' to have the same id/gid as main owner of dataset. This requires changing of conf: /var/db/syncthing/config.xml, otherways - console-based changes will be overwritten by GUI.
When creating datasets and connecting them to syncthing (can be quite time-consuming anyway)- avoid mistakes and renaming datasets, changes afterwards seems to drive syncthing totally bonkers.
In GUI, everything is reasonably clear: pick your folders, apply various options, sync. Yeah, right - but it took me 4 evenings to get all perms between win/linux/nas/syncthing correct. Syncthing forum, though, gives some nice advice about various obstacles.

And last - which should be the first - thing: Make plan/schema what and how to sync. I mean, really plan - as some changes are shit to do and, can fuck up good part of your already confed syncing.
This means: organizing location and naming of folders; which of synced folders is the master, how many boxes are going to access this dataset, how data really flows (do you really need to install one more syncthing, or maybe flow is one-directional - and rsync is enough) and so on ...

Moral: Syncthing is nice thing - if and when you get it smoothly running. To get it there might be enormous wrangling, though. I presume that some sysadmin experience before is certainly helpful...

And general moral: NAS is nice thing to have, and Freenas as its' op-system looks perfect to me.

2015-10-18

Lenovo S20-30 Touch + Crux 3.1

PART 3  | See Part 2 and Part 1

So, Crux is meant to be keeper. And this post will be long and occasionally detailed - as Crux' manual is not very long and help is only in form of mailing-list.

Made usb installer: dd if=crux-3.1.iso of=/dev/sdd bs=1M, booted and had auto-login as root.
Did whole fdisk /dev/sda, mkswap/swapon, mkfs -t ext4 /dev/sda2 (and sda3) again.
mount /dev/sda2 /mnt    #sda1=swap, sda2=/, sda3=all stuff
setup

Picked packages manually - left some things out. Installer finished with no errors and then it was time to chroot.
It's not particularly important in which order you do things when chrooted - and some of following can also be done after reboot.
setup-chroot  #script with all needed chroot-things
passwd  #create root password
adduser myuser  #can be done later but I did then
mkdir /media/back  #mount point for sda3
chown myuser:users /media/back
nano /etc/fstab  #has to be fixed, otherways - no boot.
nano /etc/rc.conf  #can be done later, but why wait:
FONT= default
KEYMAP=us   #all availables are in /usr/share/kbd/keymaps
TIMEZONE=Narnia/Mytown  # /usr/share/zoneinfo/
HOSTNAME=cruxlap
SYSLOG=sysklogd
SERVICES=(crond net)  #here go all started services, e.g: alsa gpm ntp sshd
localedef -i en_US -f UTF-8 en_US.UTF-8
cp /usr/share/zoneinfo/America/Yourplace /etc/localtime
hwclock --set --date="2012-04-19 16:45:05" --localtime
hwclock --hctosys

# I have habit to use localtime - because of windows dualboot in my desktop-machine. If Linux is single-system, then it's no problem using UTC.

Created udev/rules.d/70-persistent-net.rules with card mac number as eth0 - otherways udev changes card-name to something - and net is not going to load automatically on boot.

Kernel compilation.
Thought to be clever - and compiled newer kernel (3.18.22) than one provided by Crux. Well, it hanged when booting. Tried changing things / recompiling - but nothing worked. Copied confs to sda3 and reinstalled Crux (to be safe of leftovers). Copied confs back, and compiled original kernel.
Which booted alright. But - surely I was in some totally retarded mode - as I left Intels' video driver out. Recompile. Then I discovered that I left out also sound drivers. Recompile. And afterwards I discovered that I left out i2c - needed by coretemp... well, not essential - no recompile.
Anyway, compiling went exactly like it's written in Crux' page:
cd /usr/src/linux-3.12.24
make menuconfig
make all
make modules_install
cp arch/x86_64/boot/bzImage /boot/vmlinuz
cp System.map /boot


grub-install /dev/sda  &&  grub-mkconfig > /boot/grub/grub.cfg
I didn't like what grub created - so I made my own simple cfg file (can be copied from Crux' page, and then modified).
Copied all my desktop-Crux user-confs to laptop and changed ownership to my user.
exit && reboot

mount /dev/sda3 /media/back  #if not already in fstab
Before starting with updates I changed ports confs - made /media/back/ports and media/back/pac folders and edited /etc/pkgmk.conf and /etc/prt-get.conf accordingly. Also - every .rsync file in /etc/ports has to be changed too.
The point is - all sources+compilations grow very big, very soon. No need to stuff your root.
mv contrib.rsync.inactive contrib.rsync  #enable contrib, also in prt-get.conf
ports -u  #update ports list
prt-get sysup  #whole system upgrade - takes hours!

Only error I had was with xorg-server: missing libepoxy. Installed that and xorg compiled OK.

And then it was installing everything I normally do install. Troubles:

- gpm  # Only thing that worked was usb-mouse. Hacked /etc/rc.d/gpm:
/usr/sbin/gpm -m /dev/input/mice -t imps2
stop/start gpm and all touch-things started to function.
- openbox # cp /media/back/ports/openbox media/back/pac, then edited Pkgfile '--enable-imlib2 \' and also added imlib2 to depends line. The same goes for conky.
- xdotool  # Now there is package to be taken (1,5 years ago there wasn't)
- man needs pager - put into .bashrc: export pager='less'
- tint2 # has waken from long coma - and there is new version 0.12.2
Url in Pkgfile didn't work, though - the one in slackbuilds.org did, so I downloaded tar from there.  
- wmctrl  # url is slightly wrong - /dist has to be taken out.
- volumeicon 4.6  # last version with gtk2, needs patching.
- pale moon binary package to /opt, ln -s /usr/local/bin (I have a habit to put apps to local/bin... In Crux, this folder has to be created.)
- mplayer + smplayer  # Like previous time, there were severe problems. Basically , smplayer didn't play anything and whined about mplayer error. To cut it short - after almost 3 hours of aborted compilations I installed mpv, smplayer started to work with mplayer BUT not with mpv... &^%&#$$#^.
- compton  # Packages point to very old version. I dowloaded new git version but didn't succeed with make install (missing some dep). So I was impatient and ended up with just make and cp compton /usr/local/bin. And it works alright.
- mtpaint  # 3.40 doesn't compile - libpng-16 is too new for it. Git-version compiles ok.
- libunibreak  # is newer liblinebreak. There is no package in Crux - but it's easy to make. Fbreader needs it - and fbreaders' Pkgfile needs then fixing (liblinebreak out).
- libtorrent-rasterbar  # For qbittorrent. But - 1.0.5 from Pkgfile is a WRONG one. Qbittorrent needs 1.0.6 from git.
- qbittorrent  # Refused to make package (error - package is empty) - BUT at the same time - installed it.

And so on... Installing/upgrading Crux and adding your stuff takes 30 hours or probably more. But when all is done - it's real fast and lean. Exactly what fits with shity Celeron.

Lenovo S20-30 Touch with Funtoo and Alpine

PART 2  | See part 1

2. Funtoo, from 21. Sept stage 3 tarball.
Install went as per manual.
- Made systemrescue disk, also as per manual.
- Booted, used stage3-intel64-silvermont-pure64-funtoo-current-2015-09-21.tar.xz
Fixed fstab and some other stuff, rebooted successfully - but had no networking. Did:
rc-update add dhcpcd default && rc

Some things to write into make.conf (I am still talking of specific Lenovo netbook):
-CFLAGS="-march=native -O2 -pipe"
CXXFLAGS="-march=native -O2 -pipe"
MAKEOPTS="-j2"
-VIDEO_CARDS="intel"
-INPUT_DEVICES="evdev synaptics"


And then I started with defining USE flags ('emerge app-portage/ufed', an helper app)...
After spending some hours with flag-lists, and reading a bit more about vast system of emerge I came to conclusion that I do not want to build advanced spaceship and make 18 trips to Jupiter JUST for using a distro on my ships console.
I suppose it's bad influence of Slackwares' and Cruxs' minimalistic package-system approach... but really... is such a system of building life from premordial soup neccessary?
Not for me - format.


3. Alpine Linux 3.2.3 64bit.
Installation instructions in Alpines' site are ... a bit unclear... you almost think that to install it, you already HAVE to have Alpine installation, and no other way.
Fortunately, it can be done without:
Unetbootin made nice working usb-image (and dd didn't!). Booted it and:
login: root / 'enter'
(and the usual warning - MY root-part is sda2, YOURS might be different)

mount -t ext4 /dev/sda2 /mnt
setup-timezone
setup-alpine -q
setup-sshd  # if you are going to remote into it
setup-ntp  # if you want to use time from network


setup-disk -m sys /mnt

Now, why I said things about fdisk etc? Because I forgot to format properly, and ended up with borked installation. Syslinux didn't want to live in grub-infested MBR.
Fixed it with:
- dd if=/usr/share/syslinux/mbr.bin of=/dev/sda bs=440 count=1
Then some confing ... aaand ... boot succeeded.

adduser myuser;
edited /etc/group , added new user to users, disk, wheel, audio, video, cdrom, plugdev (the last one has to be made - spacefm needs it)
apk update && apk add sudo
enabled wheel in /etc/sudoers
apk add bash bash-doc bash completion  # if ash is not your favourite...
changed user-shell to bash in /etc/passwd

... read Alpines' helps, package lists and installed various things.

Then I did change main repos to 'edge' (means testing). I certainly do not advice to do that, they are testing for reason. But - I wanted my favs - spacefm, tint2 etc. Did:
apk upgrade
/etc/apk/repositories  # changed repo to edge
apk upgrade --update-cache --available
sync
reboot

... And there wasn't any net. Imbecilic udev had changed cards' names.
I made file /etc/udev/rules.d/80-net-setup-link.rules with mac number (which can be found with ifconfig), and for good measure, did:
ln -sf /dev/null /etc/udev/rules.d/80-net-name-list.rules
After that, it's easiest to reboot.
Once after that I lost network again - and discovered that it was because kernel time had reverted to UTC and was three hours in future...
Did 'date' and 'hwclock' to diagnose - first was wrong, the second was right, so:
hwclock --hctosys

Then I started to have some problems I didn't know how to fix.
And it all culminated with X starting without any input but usb-mouse (yes, yes - I did install evdev and synaptic, I did try to X -configure...).
Lot of curse-words, and ... yes, format it was.
Moral: Alpine  is recommended as lean and fast distro - provided that you stay with 'main' repo AND do not have touch-things. Also - can't have overly specific software needs...

Lenovo S20-30 Touch + Linux

Turning little Win-8.1-laptop to Linux-laptop.

Some relevant (drivers etc) technical data:
Resolution - 1366x768,
CPU - Celeron N2840 2,16 ghz 64bit Silvermont,
Graphics -  Intel HD,
Sound - Intel + realtek,
Ethernet - Realtek RTL8101E/RTL8102E,
Wifi - Qualcomm Atheros QCA9565/AR9565,
Touchpad - Elan.
Most of info came from lspci, lsusb, lscpu and inxi.

Original state.
I bought this little thing (11.6") in December 2014.
It had 'Windows 8.1 with Bing' OEM x86_64 installed (original dvd: IR3_CCONA_X64FREO_EN-US_DV9.iso), AND totally bloated with Lenovo crapware, including infamous Lenovo superfish-spyware (this link, or other thousands).
After struggling a bit with remove-all-shit, I tried - as a passtime - to install Slackware 14.1 for dual-boot. With partial success only - X refused to start (might have been problem of oldish kernel).
Fortunately, in process, I messed up EFI and Windows didn't start anymore - so I had an excuse to reinstall vanilla win8.1 (registration is automatic, in bios).
Tuned it, played around, and hated whole thing. You can't make bread out of shit, even with helpful addons. Also, whole system tended to be quite sluggish (not a surprise really, with Celeron N2840).
So, after a long while (it laying around mostly unused) I decided to wipe whole disk and install Linux.

The machine has efi+secure boot, but - BOTH can be disabled. And that makes installing Linux markedly easier.
My initial goals were something like:
- fast and lean distro; with little bloat (no fullblown desktop environment);
- reasonably stable;
- with all my favourite software available;
- without let-us-be-new-Windows like crap - from systemd to gnome shell.
Which made me pick Crux (crux.nu and do local search to find my three previous Crux-posts). But - because I also had a waiting-list of 'I should try this one', then I decided to try first those of the list (Antix 15, Funtoo, Alpine 3.2.3).

To action:

1. Antix 15, 64 killah p. 
A distro based on Debian 8 Jessie, but with systemd carefully removed. Full iso comes with four window managers which are swappable on fly, in X. It includes control center and various other scripts. Means - sounds interesting.

Antix' install is from the live session (I think I dd-d the usb-stick...).
username/passwd - demo/demo.
I deleted all Lenovo partitions, made swap, root and home partitions: traditional MBR, as I don't see why I should use GPT with one 500GB disk. And mind - after several installs and different bootloaders it's wise to use fdisk, gdisk, mkfs and such - for wiping disk really clean.
With little helpful trick - reading ability - the installation is a cakewalk, nothing need to be explained here.
Rebooted and logged to JWM.
Checked other WMs ... didn't like default confs and looks, as it always happens with me... So, here come short bits as 'How to tune debian distro, and also brake it':

... Synaptics, enabled more repos. Installed xapian-index (gives a search-window on toolbar);
... rebuilt JWMs menu and launchbar, reordered everything (Joe's site is very helpful as of howto);
... ~/.jwm/theme - seems to have a syntax error: not 'dejavu sans 10', but 'dejavu sans-10'. Otherways it doesn't react to any size change.

There were several annoyances from the beginning:
- Cursor jumping around when typing (very &^%&^#@$%!).
- medit and geany started occasionally new window instances - as opposed to keeping things in tabs...
- when changing window managers various things happened, including some apps closing, some forgetting tabs... But here I doubt very much if it's possible at all to smoothly integrate very different WMs and (different) default apps ...
- few usual app-related-bugs every distro tends to have: Here - clipit didn't start and xmahhjong crashed whole JWM.

So I started to remove Antix goodies, first other WMs and then all antix-scripts and antix-libs.
Re-tuned confs and shit... and, of course, ended up with one-or-two hidden, not-so-easily-findable leftover-quirks ...
My curiosity about Antix satisfied and not willing to spend more time with detective-work I formatted the whole thing.
Some general moral here: If not having unlimited time - do not full-rebuild prebuilt distro.
Ah, well... but it WAS interesting when it lasted. :)

As long you do not have touchscreen and -pad; and do not change 'desktops' on fly - Antix is recommended. It's nice, lean piece of work.
It also ended up as my 6-year old son desktop system. Who seems to be entirely OK with it.

2015-09-18

Mimetype problems

Environment: Slackware 14.1 + Openbox + spacefm 1.0.3

Problems: 

Wrong (already deleted etc) apps in filetype open with list + wrong epub icon.
1. Newer version of Spacefm looks for .desktop files in ~/.local/share/applications and rearranges things in mimeinfo.cache. Result - apps list for given file-type gets strange and occasionally irrelevant.
(How and what to do with mimetypes in Spacefm.)
2. xml file in /usr/share/mime shows one icon listed, filemanager shows something complitely unrelated. Why, is unknown to me.

Solutions:
1. All mime defaults should go to
- either .local/share/applications/mimeapps.list,
- or to .config/mimeapps.list.
Entries look like this, for example:
[Default Applications]
application/vnd.oasis.opendocument.text=libreoffice-writer.desktop;
application/pdf=qpdfview.desktop;


Moral: As long as something is not rewriting your .local/share/applications/mimeinfo.cache too frequenty - you can change things there. It's easier and more flexible, you can also tune what app appears in second, third or whatever place on the list.
BUT, mimeinfo.cache IS prone to be rewritten, so let's change the .list with Spacefm:
rightclick on file - open - choose app for default - rightclick on it - make it default.
The same way you can remove or add apps to or from your available handlers list.
And the same for all filetypes what are not yet defined (fun and giggles for 0.5-1 hour).

2. Changing mimetype icons can also be done manually or with Spacefm:
a) copy yourproblematic.xml from /usr/share/mime/applications to ./local/share/mime/applications/packages
There is a line with <general-icon name=.../> in it. Change it from general-icon to icon, and replace icon name with your favourite icon in  ~/.icons/yourtheme/mimetype/ folder.
Run update-mime-database ~/.local/share/mime
b) A bit easire way, with Spacefm - rightclick on file - open - rightclick on default app - pick line with ...xxx.xml - click. Spacefm copies xml file from /usr/share/mime to your .local/share/mime/packages and opens it in editor.
Edit it the same way as in a).
Done.

2015-08-21

Linuxes + windows 7

Goal: Multiboot with Windows 7, installed after linuxes.
I do not use Steam and - except maybe two-three games - linux-native gaming is crap. So after some 2,5 years I finally reinstalled OS for gaming.

First of all - it's enourmosly good to have two hdd-s. So You can keep MBR boot-sectors separately. Means - no worry of Windows overwriting your grub-parts.

What I did?
- changed boot order - to-be-windows-disk went to first in bios. That is - until usb-win-installer came to play...
I booted my win7 usb and installed. All finished in less than half an hour - with no lan, audio, or proper video drivers... Windows 7 is kinda oldish, and my box is kinda newish - so, no real surprise here.
Went to another machine (or - better to do it before), downloaded all shit from my motherboard manufacturer and added fresh nvidia driver. copy / unzip / install / reboot.
Downloaded usable browser (Pale Moon for me). Got essential things:
Classic shell, dexpot, linux reader, qttabbar, MS security essentials etc. Hacked various things in register.
At the same time - updated 200+ kb-s.
Do You want every KB? No? Make a choice - first, install all security updates. After that - check them ALL, every update is not needed (useless) and some of them are to avoid:
- 971033 (Windows Genuine Advantage - spy/telemetry for checking legalness of Your Windows, repeatedly);
- 949810 (the same for Your Office)
- 2505438 (not sure if it's still actual - but, the same, it checks Your licence.
- AND a bunch for upgrading to Windows 10: Can't say here anything very precise... but suspects are: 2951664, 2990214, 3021917, 3035583, 3065987, 3068708, 3075851.
I have my win7 totally legit ... but I don't want two things:
Spying for 'legitimacy' (check-process (they say) errs a lot, after what one has to whine+plead with MS support);
OR, 'upgrade to win10' - to OS what, in my opinion, is total 'be a bitch receiving it from behind, while singing your whole life-story'.
Whole process to get Win7 to OK shape took me markedly longer than, say, Slackware clean-install with all custom bells-and-whistles. Shrug.

Second phase - boot Windows from Grub.
- Rebooted from Windows, entered bios, changed boot order back to my grub-master hdd, rebooted to linux. Now, opened up /boot/grub.cfg and added entry to 40_custom section (change the following according to your hdd, of course).
menuentry "windows 7 pro (on /dev/sdc1)" --class windows --class os { 
 insmod part_msdos
 insmod ntfs
 set root='(hd2,msdos1)'
 chainloader +1
 }
If you want to be correct and/or You plan to use 'update-grub' or similar command that recreates grub.cfg, add the same entry to /etc/grub.d/40_custom.
Done.

2015-05-17

Grub2 problem

Grub 2 in Debian Wheezy, MBR, multiboot.
Symptoms:
1. Grub started not with my customized look but with default big reso and look.
2. or it skipped conf and went stright to 'grub' prompt.
3. but approximately only in a half of starts.
4. and there was marked delay in Grubs' menu-loading.

What it means is - Grub couldn't find its config file(s), sometimes.
And, in this case, that there is some intermittent issue - appearing and disappearing. I have to say that such kind of behaviour was new to me. In almost three years of various linux installs etc I never met such kind of inconsistent behaviour - things either work or not...

Solution is simple: As we are talking about Debian, then it's 'update-grub' you wan't to run.
And that's it. Loading lag disappeared together with inability to load confs...
So, something got corrupted (and it didn't show in file dates in any way)... Fortunately it also uncorrupted itself in a simple way.

2015-01-25

Changing themes in Openbox

Skackware64 14.1, Openbox, tint2, conky, feh.
## After using three month almost only Slackware with my slightly-Steampunk theme, I got bored and recalled idea I had - to make script to start X+OB (without display manager) with visual theme I like at that moment, with choice of others.
So I made it happen. In most primitive bash (me - bash-n00b).

# There are one Chooser and four Swapper scripts (as I have currently four themes):
-- 1. Created conf-number file, like:
if [ ! -f obtheme/theme ]; then echo "1" > 'obtheme/theme' ; fi
Get the number:
theme=$(grep -o '[0-9]*' obtheme/theme)
Every time theme is chosen, new number is also written into theme-file.
Those above are for marking previously chosen theme ('if then echo') - and also to let wallpaper-randomizer script to know which one is current.
Then I set some variables;
did 'while' and 'if' between choices, 'read' those 'if'-s, and 'break'-ed with correct answer;
And final 'if-elif' then does
if ... ; then exec "ob-thx.sh"
with chosen theme-swapper script.

-- 2. Swappers
I Collected everything possible to ~/obtheme/xx folders. Like tint-stuff and wallpapers and conf files to be swapped.
For various reasons - there are either symlinks or files overwritten (respectively 'ln -sf' and 'cp').
- Two gtk confs (.gtkrc-2.0 and .config/gtk-3.0/settings.ini = gtk-theme swap);
- my wallpaper randomizer script for that theme (symlink). But - randomizer can also be modified to pick folder according to already existing theme-file number, and then there is no need to swap it | Edit - Done, see the end of the post |;
- .fehbg in ~/ (to pick up another wallpaper-folder);
- rc.xml (OB-theme swap) and autostart in ./config/openbox. Those are also symlinks which point to theme-specific files. Different tint2 and conky confs are opened from swapped auostart;
- and lastly, 'startx'. Or for debugging - as Slackware without display-manager doesn't want to log X-errors - startx 2>.xsession_errors

So, I now start my X either with alias 'sx' - no change, stright to X;
with 'sxz' - which opens up dialog of theme-change;
or, I can pass that and use aliases for swappers: sx1, sx2... .

For anyone fluent with bash - to make such scripts is totally no issue. What takes time is preparing themes - from various conf changes to actual pic-making or theme-tweaking.
But I have to say - it's most satisfactory to see my whole "desktop" instantly and totally changed.

Addon: Here is a simple script for swapping wallpapers inside the current theme wp-folder. Also, keyboard W+1 is mapped in rc.xml as 'swap desktop to first one and run randwp1.sh'.

#!/bin/bash
## very simple random wallpaper picker, through feh or nitrogen
## --------------------------

sp1="/home/user/obtheme/sp/wp"
sf2="/home/user/obtheme/sf/wp"
fan3="/home/user/obtheme/fan/wp"
nat4="/home/user/obtheme/nat/wp"

# theme number variable from theme file
theme=$(grep -o '[0-9]*' /home/user/obtheme/theme)
echo $theme
# directory containing images
DIR=$(if [ $theme -eq 1 ] ; then echo "$sp1" ; 
 elif [ $theme -eq 2 ] ; then echo "$sf2" ; 
 elif [ $theme -eq 3 ] ; then echo "$fan3" ; 
 elif [ $theme -eq 4 ] ; then echo "$nat4" ; 
 fi)
echo "$DIR"
# select a random jpg from the directory
PIC=$(ls $DIR/*.jpg | shuf -n1)
echo "$PIC"

# use nitrogen to set wallpaper
# nitrogen --set-scaled $PIC
# use feh
feh --bg-scale $PIC

exit 

2015-01-18

Slackware64 14.1 + new kernel

Yeah, compiled a new 3.14.28 kernel - in a bit leaner way than slackware generic is.
So here comes concisely how I did it.

# First, open up this page and read it - my description here is almost the same, with occasional addons. And - I did everything on desktop terminal until Nvidia drivers' reinstall (logout, console, init 3).

1. Download the source (and pgp .sign) from kernel.org, copy to /usr/src, unxz the source file (tar needed afterwards), then unpack source to folder. To be nice and orderly, do: rm linux && ln -s /usr/src/linux-3.14.28 linux
cd linux
zcat /proc/config.gz > /usr/src/linux/.config  # or use some other handy config...
make oldconfig  # to insert kernel changes into old config file.
make menuconfig # Which probably takes two hours at least. But it's worth to be alert and click everything - for not to miss, for example, your network drivers.
make bzImage modules
make modules_install
cp arch/x86/boot/bzImage /boot/vmlinuz-custom-3.14.28
cp System.map /boot/System.map-custom-3.14.28 
cp .config /boot/config-custom-3.14.28
  # instead of 'custom' comes of course your special name you gave to your kernel (when menuconfiging).
/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 3.14.28
This nicy script gives you exact command for creating initrd. Do it.
cd /boot
There should be three links to: kernel, system.map and config. Change those to point to your new files (ln -sf filename link).
Done with the kernel.

2. There is link /etc/rc.d/rc.modules which points to old rc.modules-3.10.17; copy this old modules file, rename it according to new kernel modules folder name (or 'uname -r' - which you can't use as kernel is not yet installed :) and change rc.modules link to point to this new file.

3. Grub or Lilo - has to be rerun for introducing new kernel. I have Grub2 in Wheezy (which I still keep only for hosting my multiboot) - I mounted Wheezys' partition and simply edited /boot/grub/grub.conf file. And that was that.

4. GPG-check. (Additionally to AlienBobs' tutorial there is also nice explanation in kernel.org.)
wget http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.14.28.tar.sign
Put it into the same folder where you have linux-3.14.28.tar
gpg --verify linux-3.14.28.tar.sign linux-3.14.28.tar
What results 'no key', but there is id=6092693E , use this and import:
gpg --keyserver hkp://keys.gnupg.net --recv-keys 6092693E
gpg --verify linux-3.14.28.tar.sign linux-3.14.28.tar
"This key is not certified with a trusted signature" - let it be like that, done.

5. NVIDIA
Kernel 3.14 and nvidia 319, seems, are not friends - no compile, BUT newer 331.86 did the trick. Before run, delete /etc/X11/xorg.conf - and then let installer make a new one. Sometimes there is a difference - as X starting or not starting (missing screens). No, I do not know why it sometimes matters.
Last part in following is for compiling for not yet installed kernel.
sh NVIDIA-Linux-x86_64-331.89.run --kernel-name='3.14.28'
It compiled, but whined over wrong arch in  /usr/lib64/libEGL.la
Anyway - X started up. I checked aforementioned .la - and it appeared that Nvidia removed it totally. Found it in /var/log/nvidia/103, copied back and also deleted in it one dependency that was obviously 32bit... We'll see what happens next time when compiling.
According to web, reinstalling mesa also fixes .la issue.

But never mind.
I have my new kernel running and everything seems to function OK.

Slackware + apps and stuff

I happened to look around for some new apps and so on... Found some and installed.
So it seems to be a good opportunity to flash MY list of apps, and blab a bit of some of them. This list, of course, is not a template for greater awareness and being godlike, but it might give some app-ideas... Like I found when peeking into other people choices ...
And here, some bollocks then:

## The patient: Slackware64 14.1, Nvidia 331.86 binary, Openbox. My Slack-install was not the 'full' one, but rather castrated - I left out everything possible... Including vim&family - which means that dotnew didn't want to compare anything (missing vimdiff). But never mind - new config files are for promptly deleting anyway.
Not-full install means that I might mention some things as 'new' that normally get installed automagically.
- Usage of my Linux(es): Educational playing-around, no serious work done, strictly desktop. No plan to use vi or emacs, no apache et al, not even ssh and ntp; no social bullshit and fraternizing (skype, chats and so on).
So - rather simple setup with net, writing and graphic tools, and occasionally test-stuff (for example, see my silly tour with linux games)

## Beginnings of apps:
-- I always use stright Nvidia binary (sh NVIDIA....run). It blacklists nouveau, reboot, run it again, let it make conf for X. For n00bs: for every kernel or x-server upgrade - nvidia driver has to be recompiled!

-- nano is installed from ISO - so console is survivable without various vi-s;

-- slackpkg+ and sbotools - get package for the first one, and SlackBuild for the second beforehand, makes a little less fussing now.
Slackpkg+ is a wrapper for official slackpkg. It has the same tools, but it provides multi-repo capability. Ie, various ready-made packages can be retrieved from several repos (see slakfinder.org). As a bonus - playing around with slackpkg+ conf keeps you occupied for an hour, or more.
Sbotools is freebsd-like ports-script. It installs, removes and keeps account of your sbo packages. It also checks dependencies (provided those are notified in .info file). Means, makes life easier - a lot easier if install is of 8-10 depending sbo packages ...
Sbotools has .SlackBuild in slackbuilds.org and compiles easily, no deps.
Run sudo sboconf (all sbotools are sudo / su) first, change something - and you get /etc/sbotools/sbotools.conf file created. Now fill it according to wishes and documentation (man sbotools).
I find it smart to keep sbo tree (and distfiles) on different partition (not in default /usr/sbo) - the same goes for made packages.
sbosnap fetch, and off we go - sboinstall, sboupdate etc etc.
As a rule I check .SlackBuild file for compile flags - before I commit. I tend to change them flags occasionally. Means that in serious cases I also unpack source and check for all possible flags, run: ./configure --help .
NB! If using other partition - better mount it already in fstab with 'defaults' - to avoid that file manager (maybe) mounts it "safely" with 'noexec, nosuid' etc.

-- xdotool, wmctrl are helpers for certain things one can do in openbox menus.

-- xarchiver, xfce4-terminal, medit, spacefm+udevil, openbox (I want icons - dep: imlib2 and --enable-imlib2 \ in .SlackBuild too), obconf, tint2 (svn version, with launchers), conky (same with imlib2, but check .SlackBuild also for things you do not need - and '--disable'), compton, feh, gtk-nodoka-engine, various fonts, gksu.
There is no display manager and I startx (alias sx) from init 3.
As I copied all confs already earlier, my desktop is essentially finished.

## Second group, installs are already from terminal:
-- New kernel - if one feels like compiling one. The point - Slackwares' generic is really quite big and has very probably some useless stuff there. But, let's be honest - it doesn't matter - and whole compile-thing can be considered just a merry exercise of showing who is the boss.
Also do: lsmod and see if you have some pointless modules loaded (for example, I take down parallel-port, printer and some other things - either by blacklisting or in kernel).

-- firejail+firefox. "Firejail is a SUID security sandbox program..." - but take a look yourself, there is quite a lot of explaining available.

-- dotnew+meld+diffuse. No vim = no vimdiff. So I installed diffuse (sbo), and swapped every gvimdiff in /usr/bin/dotnew-gtk script to diffuse. Strange enough, it works.

-- mplayer+smplayer+volumeicon. The last one has to be ver .46 if staying with gtk-2, the later versions demand gtk-3.

-- qpdfviewer, FBReader, Geany. To mention - FBReader is nice lightweight epub and mobi reader. It remembers your last read page too.

## And, third - those things which come when really needed:
-- gparted, unetbootin, bleachbit, fslint, libreoffice, qbittorrent, galculator, gcolor2, calibre, convertlit, inkscape (gimp is in official ISO), sigil, clementine.

-- If slightly paranoid: rkhunter from sbo, and for quite nice simple tutorial looka here.
And others...

2014-11-08

Games + Slackware

Yes, something frivolous... And NO - NO STEAM games here, never.
But about installing free natural-linux games in Slackware 14.1 (64bit).
SBO = slackbuilds.org (buildscripts+source=compile)
SF = slakfinder.org (ready binaries=install)

# Battle of Wesnoth - can be easily installed from SF, Salix. There is also option to compile it from SBO, and tuning the build specifically.
deps: It might need lua (according to SBO, but not according to SF). I had lua installed previously, so I don't know.
- Wesnoth is 'turn-based tactical strategy game'. See here for more in-depth info.
Nothing more to say - I haven't played it yet.

# Tales of Maj'Eyal - Not so easy install at all. Has to be compiled from SBO, and has a bunch of deps: premake - SBO (deps: lua), OpenAL - SF binary, SDL2 + SDL2_ttf + SDL2_image - all three from SBO.
SDL2_ttf gave me error about missing/wrong libGL. Fixed it in usr/lib64/libGL.la - changed obviously wrong libdir='/usr/lib' to libdir='/usr/lib64', and compile finished without further problems. ... I have no idea why it had such a wrong address in libdir...
- Maj'Eyal is 'roguelike RPG, featuring tactical turn-based combat and advanced character building' - see here.
The game is quite enthralling, 'just one turn more' type. It's also not easy, and has various ways to die stupidly. For example: walking in sand-tunnels without digging worm ahead; lack of attention with bosses is often strightly fatal...

# Freeciv - Install is compile from SBO. No deps. Easy-peasy.
- Freeciv is 'a free turn-based multiplayer strategy game'. Has big and quite well-stocked site.
The game has several diffrent modes and mods, including civ1 and civ2. Default mode is not especially easy - certainly for those whos experience runs only in wimpy and feebleminded civ 4 and 5.
Anyway, confs are easily hackable - for example: nations' files reside in /usr/share/freeciv/nation; and in /usr/share/freeciv/default one can find all general conf files. And they all are plain txt.
At the same time, creating a new nation - by tutorial - gave somehow buggy result...
The games' gui is not especially good and easily-usable, but as a civ-game - it's very OK.

# FreeDoom - SBO, and what you get are wads only, engine has to be get separately. And it would be mightily good, if there are old Dooms', or Heretics', or Hexens' original wads available - those are also playable with zdoom or gzdoom engines.
So, pick one of them...
gzdoom seems to be newer: SBO, deps - fmodapi.
zdoom - SBO, and has more deps - TiMidity++, fmodapi, p7zip.
- Doom is a shooter - or should I say The Shooter, at least for me it was first ever game played overnights with sysadmin and some developers (right, over 20 years ago).
Take a look here.

# Lips of Suna - Well, that installation took me some 5 hours of silly wandering around. The game has to be compiled as is, no slackbuild scripts here. For guidelines see here.
Basically, by default it installs to /home/xxx/ :
cd lipsofsuna-X-X-X
./waf configure
./waf install
./lipsofsuna
Here are deps. All are available in SBO, thank god. Ogre compile, though, is long as shit.
Most entertaining was that 'lips...' didn't compile - with nicy orange-bold error. Let's cut it short and reveal my winning configure line:
LDFLAGS=-lboost_system ./waf configure --ogre-plugindir=/usr/lib64/OGRE
Part before 'configure' ensures compile, part after, that ./lipsofsuna also starts.
It bloody compiled, with one orange part (but not bold)... jeez. I am sure it wasn't worth of it. But I won the struggle! :)
- No idea what the game is about, but the word 'naked' in description got me.

# Summoning wars 5.6! - SBO. Pile of deps, for me it was - after previous games: freealut SF Slacky (deps: OpenAL), physfs SBO, CEGUI SBO, poco (deps: mysql-connector-c++, unixODBC, both SBO).
Tried to compile games' new ver.058... and no luck - cegui-084 compile crapped out with windowsy (irrelevant) message ... As this games' description hasn't any word 'naked' in it - I didn't see reason to spend more than an hour with this particular problem ... And stayed with old version - 056 - and readymade SlackBuild. CEGUI compile was slow like dead AND decomposed snail, almost like shitpile firefox ... poco was as bad - like bloody half an hour... physfs compile was short and nice. What a ... letdown..., for example ginormous gcc compiled only an hour in the same box...
a..n..d..I am already compiling sumwars! Lotsa green text! It even moves! err... slowly...! OHHHHH, it erred out, unbelievably, and for your convenience, last lines were:
collect2: error: ld returned 1 exit status
make[2]: *** [sumwars] Error 1
make[1]: *** [CMakeFiles/sumwars.dir/all] Error 2
make: *** [all] Error 2
doh!
| add next day| Fix was like that, in sumwars.SlackBuild:
-DCMAKE_CXX_FLAGS="-lboost_system -ldl" \   # added here '-ldl'.
That was that, compile finished and game started...
- 'Summoning Wars is an role-playing game'.
As all time went for compile, not for play... Only thing I can say just now - games' graphics is horrible, as expected.

| ADD |
# Naev - SBO (deps: OpenAL), two source files, naev and ndata are needed. It compiled/started with no whining...
- Naev is a 2D space trading and combat game. 
Take a look, see...

# Dink Smallwood. (Flare, Baldur's Gate)
Those three are vague future plans. If they, or something else, materialize , I ADD.

All-in-all: Native Linux games mentioned here
- look like shit of various degree,
- play good IF they are out of pre-alpha (infrequent miracle!),
- and install mostly ... like shit.
I am sure that next year is Linux-Desktop Year. :)

2014-08-16

URxvt, Slackware, Crux = problems

Or - more precisely: Those mentioned in headline WITH Nvidia binary driver AND Compton compositor (and xorgs' version is also a player here).

So the following is obviously about the same thing as in this post - Compton and Nvidia not getting along. But - it's also a slight overview of urxvt.

I installed rxvt-unicode (exec: urxvt) as fun and games and novelty to my new Crux 3.1 (Crux home, my Crux install blah: 3.0 -1, 2, 3 and 3.1) and Slackware 14.1 (and my blah). The outcome was somewhat different in those distros.

But first, what it is this urxvt?
In essence, a terminal born from xrvt, with unicode support. And do a simple search 'rxvt+unicode'. At least two pagefuls give extremely relevant tutorials and stuff. Go.
But, just to mention:
- its' conf is in .Xdefaults (or in .Xresources if going more modern)
- it has transparency in two ways. And colors up to 256.
- it's UTF-8, of course,
- tabs and perl-extensions are configurable, among other things.

- It had lag at bottom of terminal (new-line) in both Crux and Slackware. It didn't wrap lines at all in Slackware.
- Doh.

# CRUX
Only problem: new line at the edge of terminal bottom - a lag of 1-2 seconds.
What I have: Nvidia binary driver 331.xx and compiled compton-master 20140729.
Problem was solved with remade compton start-line in Openbox autostart:
compton --backend glx --vsync opengl-swc --glx-no-rebind --glx-no-stencil --glx-swap-method 3 --unredir-if-possible --paint-on-overlay --shadow-exclude "! name~=''" --config ~/.compton.conf &
Magical part here is '--glx-swap-method 3'. Other is fluff what I think makes my screen look better. There is also option '--backend xr_glx_hybrid' - BUT, that gave me horrible desktop flickering.

# Slackware (and Salix), Nvidia 319.xx and the same Compton as in Crux
Additionally to lag, there was no line-wrap at all (commmand doesn't brake to next line, but acguires '>' and continues from last char...And then also kinda copies whole text to line above of last command. Very bloody confusing and obviously very wrong.
- Compton conf didn't do a thing,
- Compiling everything with Crux defs - no result,
- Copying other terminal-related confs from Crux - no result.
- Means, nothing I tried worked.

So, in Slackware, I ended up installing xfce4-terminal (deps: libxfcegui4, libxfce4util), and - lag disappeared just like that.

# Ah, yes - when digging in confs - as a bonus, I cracked the mystery of 'different looking man-pages for different users' in Crux. Has to have: export PAGER="most" in all .bashrc files. :)

# General notes about urxvt:
If dealing with .Xdefaults (.Xresources)
- might stick in Xft.dpi: 96 there too, it probably makes the console look a little less hairy.
And those -
Xft.hinting:1
Xft.hintstyle:hintfull


- OB autostart - urxvt in daemon mode goes like that: urxvtd -q -o -f &

- browse all possible settings:
urxvt --help 2>&1| sed -n '/:  /s/^ */! URxvt*/gp'

- Transparencies:
# True:
URxvt.depth: 32
URxvt.background: [90]#000000
# native transpency
URxvt*.transparent: true
! URxvt*.shading: 0 to 99 darkens, 101 to 200 lightens
URxvt*.shading: 110

- Scrollbar. Have to define it, have to place it etc:
# scrollbar style - rxvt (default), plain (most compact), next, or xterm
URxvt.scrollstyle: rxvt
# and so on, look it up.


- what icon you want to see in window corner:
URxvt*iconFile: /home/myname/.icons/mytheme/apps/terminal.png

- tabs. Perl-extension thing. Has to be compiled in.
URxvt.perl-ext-common: default,tabbed
URxvt.tabbed.tabbar-fg: 2
URxvt.tabbed.tabbar-bg: 0
URxvt.tabbed.tab-fg: 3
URxvt.tabbed.tab-bg: 0
URxvt.tabbed.new-button: true


# rxvt-unicode is not bad terminal. BUT, if using real Nvidia driver  + Compton + too-new-xorg, it might not be worth the hassle. There are other terminals available - with no config-wrestling.

# PS! Compton + more new Nvidia driver = more likely there are lag-problems... I just downgraded newest 340 to 331 in Crux - as 340 bloody lagged with everything.

2014-08-10

Icon cache refresh

Sometimes I play with icons - change them or create new ones. And most excitedly, the folder they are in gets broken/unknown icon pics into it after that.
That means - icon-cache needs to be refreshed. Many distros have a script for that which runs on startup. Or something similar - on one way or another, depends on distro and desktop environment.
But if not, one needs to update cache manually.
Basic and primitive way to do this is gtk-update-icon-cache command. That same app is used also by a lot of nice frontends. The command, in terminal, looks like that, in foolproof way:
gtk-update-icon-cache -f -t /path to your icondir - dir where index.theme is
'-f' means force overwrite old cache despite of it state, '-t' means don't worry if there is no index.theme  file.
Dandy. Yeah, but quite frequently not so - and what you get is:
gtk-update-icon-cache: The generated cache was invalid.
You also see that miscreated file starts with '.' - and it's useless as cache.
I happened to have exactly that sad outcome when trying to refresh my icon-theme cache. After exceptionally frustrating googling, I found that - in my case:
- Only thing that mattered (of multiple web-hints), was spaces in icon names. Not existence of icon-size folders, or of index.theme... or something else...
That means, of course, only that I didn't have other possible problems ... if there are more.

Anyway, I got my very big collected icon-theme validated after I removed all spaces from filenames, and nothing else (well, I also checked if my index.theme was correct. It was).

The script below (Thanks to Michael, stackoverflow) looks also to subdirs so, in idea you can run it from /icons or ~/.icons and get every spacy filename switched.
I did it in slow way - as I wanted to know where problems were. I created test-folder and copy/pasted iconfolders to there one by one, and tried to make cache again. Of course, it's easier to change the script to have 'echo' to show which files were changed... in case you are fluent in bash. I'm not, I am outright moron in it. So I did it mechanically, and found that 3 of 12 folders had 'space-problems'.
And here is the script that fixed it:

#! /bin/sh
# Script what finds spaces in filenames and replaces them with _
# to get gtk-update-icon-cache to validate.

# Change this folder according to needs
cd /home/homeros/.icons/test/mimetypes

find . -depth -name '* *' \
| while IFS= read -r f ; \
do mv -i "$f" "$(dirname "$f")/$(basename "$f"|tr ' ' _)" ; \
done
That was that.

2014-08-07

Announcement


As it's obvious, my posting has been somewhat lacking after May.
There are quite simple reasons for that: I seem have reached the last strech of my Linux adventures.
-- I have found two Linux distros I like and keep - Slackware and Crux,
- and so I have lost motivation for more digging around.
-- Also, I do not like at all how modern Linux development turns more and more toward way-of-Windows - sensless bloat, binary blobs, forced unification, idiotic GUI-changes... etc,
- and that means: I am going to try some Bsd's in future (if some of them happen to install this time), but probably not any new Linux distros.

... Might write about some interesting problem (related to those two 'keeper' distros), though.

Crux 3.1, install and so on

# Install is mostly the same as 3.0
- There were slight differences in installable apps - some of them important, see release notes. Also, see Handbook - surprisingly enough, it is corrected for new release (simply, such kind of care is not so common).
So, let's note here some diffrences from 3.0 install:
- fstab (but you still have to fill it out, mostly)
- kernel pre-made conf is more complite/generally-usable.
- network has been split to lo and net scripts, AND those files are already functional.

# Later stuff
. See this and this of Crux 3.0 - a lot went the same way.
What differs:
- prt-get sysup. One update was xorg-server. Dependency 'libepoxy' was not noted and compile failed (but I think it's already fixed). Also, after update xorg-server needs drivers reinstalled (I picked libevdev, evdev, vesa, libva and got X started ok).
- Kernel, as a cautionary tale: Despite I was very eagle-eyed when in kernels' make menuconfig, I still missed my sound driver somehow... doh.
So I thought that I create it as a module. Downloaded alsa-driver (and alsa firmware) packages for make&kmod ... and spent an hour with googling/fixing 'configure' (version.h in wrong folder). And then - it still erred (some ioctl stuff) when 'making'. Fuck. So I went and recompiled the kernel. Took me less than 5 minutes... One reboot, alsactl init and sound appeared. What a waste of time - but superbly educational. Maybe.
- dbus is not installed out of box. Now, I didn't have that problem in 3.0 - which might simply mean that I got it at early stages as dependency... Whatever - it needs to be installed now.
- xdotool. Used Pkgfile this time... and got libxdo also installed.
- man: This time, it worked for root OK, BUT, still not for user (error was different of 3.0). prt-get depinst most - and man started up, colors and all ... for a user, BUT not for root. Strange. | Missing export PAGER="most" in root .bashrc, nothing else :) |
- jdk - version in Pkgfile is wrong, fix it.
- gegl (for gimp), footprint mismatch = delete footprint. And Gimp installed without whining despite threatening text in readme. Check URL in Gimps' Pkgfile - at some point of time it is/was incorrect.
- qpdfview, qbittorrent. Neither could make package (bsdtar: *: Cannot stat: No such file or directory). I couldn't find any reasonable lead for fixing that... As I didn't have such a message with any other (NOT-QT) apps, I tend to guess that it had something to do with QT. But finally, I went for simple 'make' and they installed with no fuss.
- fbreader. Missing libpng15.so.15 , ln -s from ver 16 helped.
About libpng - this new one craps pointless wrong-srgb warning messages to everywhere. Very bloody annoying.
- smplayer not recognising mplayer version-and-stuff. It started but didn't play a thing, no video, no audio. I reinstalled mplayer, installed docutils... did something ... and smplayer started to function. Oh good - but, I really don't know what that was about.

That's it for now. I'm sure there will be more. I haven't finished with apps, and I also have some unresolved errors... like 'cannot ioremap fb base' (nvidiafb) at startup...

All-in-all, I am a bit dissappointed - not sure if more in myself or in nature of Crux. Means, I hoped it goes easier second time around. It didn't.
Summary: My level of Linux plus Crux means that it will remain as my second distro after Slackware. I simply don't have multitude of hours to spade-work in google-piles. The perspective of continuous fixing of results of updates makes me ...depressed.
But - as I really like Cruxs' ideas and choices - it's a keeper without question.

2014-05-31

Crux 3.0 - 3: later problems

Crux, part 1 and 2.

So, after happyness of 'it's installed, yee' comes usual 'oh shitty, and this doesn't work too'. Means - there appeared more quirks, and some of them still unsolved.
The following is not only 'how to fix Crux', but also 'how to fix certain things in quite general way'.

Advice - good places to track deps and script-configs: http://slackbuilds.org and http://slakfinder.org; BUT, do visit also LFS - as there you get not only deps lists but also explanations and advices. And lastly - apps' home. Last because a lot of those are without any sensible info, or filled with irrelevant drivel.

# GUI su or sudo (as it's annoying to have multitude of terminals hanging around for menu-started sudo apps).
-- First, I tried ktsuss. Made it from different sources, with different configs etc. But - if it wasn't stright segfault, then the thing simply failed with recognizing passwd.
-- Then I tried xdg-su. That worked alright from OB menus, sprouting xterm (after checking for all possible 'friendly' alternatives like kdesu, gksu ...). Xterm for that can be confed as small and in corner of screen. That is - if you have other terminal for normal work. But! - Spacefm doesn't start xdg-su. It looks like it has wrong '-c' parameter in source... As of now - I simply do not know what is good replacement parameter to recompile with. So, no satisfactory gui-sudo-solution yet.

# startup blah: couldn't mount (ext2,3) because of unsupported optional features - Put 'rootfstype=ext4' into your boot command and this message goes away.
# startup blah: Drivel about lvm. If you don't use it, uninstall lvm. I think it comes as dep for something... ie - I definitely didn't pick it...

# SHUTDOWN. I do not have PAM and *kits installed. My usual exit-py-script simply hung ... So I changed script to do shutdown in old way:
groupadd shutdown
In /etc/group , add user to shutdown group, in /etc/sudoers:
%shutdown ALL=(ALL) NOPASSWD: /sbin/reboot  # and the same for /halt
-- if using bash script, make tiny file like this (and another for /halt):
    #! /bin/sh
    sudo /sbin/reboot $*

-- OR - If having some py-script:
Define: os.system("sudo /sbin/reboot") , and the same for /halt
It works alright - and looks especially nice after you add some colored 'echos' to rc.shutdown (and/or rc.multi). Which needs some 'shell-colors' resource-file in /etc ... 

# Windows partitions (ntfs-3g) - no write access:
Add your-user to group 'disk',
ln -sv ../bin/ntfs-3g /sbin/mount.ntfs
chmod -v 4755 /sbin/mount.ntfs

reboot (or logout/login) - and you can write.

# No man-pages displayed at all, but error: sh: most: command not found. Error executing formatting or display command...
-- First, (installed) man port-folder had no packages downloaded or made. At the same time, 'isinst' claimed it IS installed ...
I reinstalled man (-d -u) and packages appeared. Man for root started up - almost. Ie, with silly ESC chars hanging everywhere. After adding 'R' to 'man.conf' line:  
PAGER /usr/bin/less -isR
ROOT started to get clear and readable man-pages. But, for USER man remained with an 'error'.
Then, I installed libslang2 , and after that, 'most'...
Halleluya!! Suddenly I had sillily colorful man for a user working.
... What's odd - there is no colors for root. Seriously perplexed, me. How comes that the app behaves so cardinally differently for different users?
| edit: Well, I certainly had a heavy moment of idiocy - not getting that only problem was missing ' export PAGER="most" ' in roots' .bashrc |

# Spacefm and udevil: Udevil comes 'out-of-repo'. And it has problems with umounting... do for udevil: sudo chmod +s /usr/local/bin/udevil

# I still have startup error for terminus-console-font. No idea why.

# And some solved problems with apps:
-- gcolor2: needs patches (three!). I took them from SBO, patched, and the result compiled ok (no segfault as with vanilla).
-- gimp: problems with deps pkgfiles' URLs. Fixed them. AND there is missing udev machine-id, do:
sudo dbus-uuidgen --ensure
The same id-fix is needed for making qbittorrent!
-- fbreader: also needs a patch, then compiles ok.

Crux 3.1 will be released very soon. That means - I will format my Debian Sid (there will be NO systemd init in my box!) - and install new Crux to this partition. We'll see what gives, compared to 3.0...

2014-05-16

Crux 3.0 - 2: Beefing it up

See part 1 - Installation.

So, we have system and xorg installed, network-capable, and bootloader fixed. Time to:
# Get back to Crux and see what gives ... and start adding stuff.

As mentioned before, I complitely missed checking network driver in kernel, and so spent some time seeking non-existing conf-problem ... before discovering that there isn't any driver. After quick re-chroot and re-compile everything was dandy. I system-upgraded and started building desktop:

ports -u  # update/get ports. Downloaded ports go to /usr/ports/
ports -d  # see versions' difference between installed and available
prt-get sysup  # system-upgrade. Take a nap. A loooong nap.

Problems / not-upgraded:
- Perl gave error 404 - version in /usr/ports/core/perl/Pkgfile was old, incorrect. Fix it, and delete md5sum file. Then it compiles.
- atk, gdk-pixbuf, pango, gtk - all missing gobject-introspection. Install it.

Next I got proper video going:
sudo prt-get depinst nvidia
sudo prt-get depinst gl-select
sudo nvidia-xconfig
sudo gl-select use nvidia


I had some strange permissions for and in my /home and X didn't start. Check, fix if needed. Everything there should be 1000:1000 or username:users (if you changed ids to 1000). If things look fishy, do
sudo chown -r 1000:1000 /home/username

Installed apps needed for my Openbox environment (conky, lm_sensors, tint ...)

Exited root and as user:
cat >> /home/username/.xinitrc << EOF
exec openbox-session
EOF


startx

When I was meanwhile in my grub-master Wheezy, I copied most of my various conf files to Crux, and fixed them accordingly. So I got new Openbox with menus and shit up at once (as opposed to normal black nothing).
- First observation - not Openbox nor Conky got image support. Recompiled them with --enable-imlib2 option added to Pkgfile.
- Sensors (in Conky) were not working. I probably left them out in kernel (?). Anyway, they can be added as external module: Did 'sensors-detect', and got names of module(s). For me it was coretemp. I downloaded coretemp.c and its Makefile, did 'make' and then insmod coretemp.ko
Stuck it also to /lib/modules/linux-xxx/kernel/drivers/hwmon/coretemp.ko
It worked and temps showed up.

! To stress trivial: All personal conf -  like .bashrc, .bash_aliases, .profile, .dircolors etc - has to be created or copied from somewhere. Well, of course you personalize as you want ... Crux is not some silly we-know-better-Ubuntu.

# Package management. Yes, see Handbook and see wiki and see prt-get manual, I am not going to quote commands here.
Time to install all those still-missing packages ... after making sure that at least /contrib - besides 3 main ones - is also enabled.

To mention some essentials here (from those 3 main repo-folders):
alsa-utils, alsa-plugins; bash-completion; gdk-pixbuf; gobject-introspection; imlib2; pango; lsof; startup-notification; rxvt-unicode; xorg-font* ... etc etc. After that, and also in between come things from /contrib. I didn't enable any other repos yet - but used separate rsync in some cases.
Crux' packages are really just bash install-scripts, with source URL. Dependencies are mostly listed (and consequently downloaded && installed). That's if you do 'prt-get depinst packagename'. But, dep-listing is not a requirement. Expect surprises once and a while.
When taking Pkgfiles from peoples' repos, always check Pkgfiles - those might be outdated and/or not with conf you expect. Well, there are few errors even in base 3 repos.
Package availability is quite good - for my tastes. And - everything missing can be cooked from source - with Pkgfile && pkgmk -d -i for easier maintenance, or - if Pkgfile-making seems too difficult - with simple ./configure && make && make install (or whatever source wants).

Some notes on installed packages:
- Installed Firefox esr. Unpacked it to /opt  && ln -s binary to /usr/local/bin. This folder has to be created and 'path'ed. Repo has this new nasty chrome-puke version 29 for taking - if one likes such stuff.
- There is spacefm package (Yee!) ... but no udevil. Ignorantgurus' installer works alright, though.
- tint2 is available in antique form only. No surprise here, as tint seems to be quite comatose. I did my usual, and didn't bother with Pkgfile.
- There is wmctrl package, but no xdotool (they both fit in with my openbox setup - not that they are relatives). Xdotool was the last simple 'make' for me (after that I started to create Pkgfiles). Xdotool compiled alright but, didn't copy its' libxdo library. So I did that with cp and then ldconfig to update libs.
- compton+libconfig compiled OK, so did lxappearance.
- With volumeicon there was more hassle - I didn't want to install gtk3 (ver 0.5.0 dep), so I went with 0.4.6. And this one has glib bug (= no compile). At the end, I found the patch, unpacked the source and patched it manually, repacked and compiled successfully.
- I briefly considered installing gksu - but the bloody crap has as many dependencies as a street-dog has fleas... No deal.

All-in-all, I have Crux nicely running, without *kits, gtk3 and display-manager.
Only serious problem still remaining - 'man' is not working. Only thing i get is error about 'display and formatting'. Still no idea what it wants.

# Conclusion.
My home-distro presently is Slackware-current - and I tend to put Crux to nearly same level of pleasantness. Crux is kinda more flexible... dealing with Slackware takes a bit less time. Slackwares' slackpkg (with +) seems to me, maybe, a bit more convenient than prt-get system. But it might be habit talking.
Anyway, I am going to keep Crux, and when 3.1 comes out (with eudev, ie - no systemd perversions), it will rule my linux-roost together with Slack.
Crux is recommended to anyone who wants play with Linux without all bloaty crapware... And doesn't mind messing with compile.
Part 1: Crux install, Part 3: Later problems

Crux 3.0 - 1: Install

Visiting fringes chapter 3. See 1 and 2
http://crux.nu

Now - including Crux to fringes is a lot misleading, especially after pitiable three in 'Fringes 2'. Crux is totally OK source-based distro, pleasantly conservative, works eminently... but, it's definitely out of distros' top 20. Only reason for such a situation - I think, is - Crux is time-consuming to install and renew... seeing gcc compile flicker epileptically for an hour, for example, induces some negative thoughts. Oh, well, Crux also doesn't have anything preinstalled, you have to sweat to get your satisfaction.
But, let's:

# I wrote ISO with dd to USB and booted with no problem.
And landed as auto-loginned root in console. Not being especial fan of fdisk, I had sda8 previously created - and that was the only new partition. I see no reason for swap (with 8GB of RAM), and I don't use separate /home in traditional way. Now:
mount /dev/sda8 /mnt
setup
 
I picked /sda8 as my root partition, and next came choosing packages.
Mind! Those packages you see here in repo, in /core, /opt, and /xorg - are NOT all in your puny 250-meg ISO. ISO contains minimal selection for you to get system up and running, and kernel compiled.
It's wise to do a walkthrough in repo-folders, and make clear what is what, what those packages do, and what you really need.

# Package selection.
-- CORE. I left out only btrfs-progs, exim, reiserfsprogs, vim, xfsprogs - as unneeded.
-- Take most of XORG. That, if you are not planning to stay with console.
-- Pick from OPT. Now, picks here depend very much on what you plan to install ... well, as in 'optional' :)
Anyway, here are my picks, according to 'I am going to use X with Openbox and some apps':
atk, cairo, cmake, dialog, expat, fakeroot, fontconfig, freetype, gdk-pixbuf, glib, gperf, gtk, harfbuzz, hicolor-icon-theme, intltool, keyutils, lib*, mdadm, mtools, nano, nfs-utils, openbox, pango, python, rp-pppoe.
After selection, some packages got added as dependencies.
-- As already said, most of packages needs to be compiled/installed afterwards. Whole run takes hours. So, be smart and pick maximum of compiled ones here.

# 'OK' and it copies your selections to disk. Done, no errors on last line?
Ok then, let's chroot, fix some confs and compile our virgin kernel. See here for manual. Next comes, very concisely, what I did:

setup-chroot  # script, puts you stright into fresh Crux system.

passwd  # create your admin passwd

nano /etc/fstab  # fix it, add missing parts. something like that:
/dev/sda8   /          ext4      defaults         1   1
devpts      /dev/pts   devpts    gid=5,mode=620   0   0
proc        /proc      proc      defaults         0   0
sysfs       /sys       sysfs     defaults         0   0
tmpfs       /dev/shm   tmpfs     defaults         0   0


nano /etc/rc.conf  # See here for guidelines. Services I put there were only crond and net. Later I added more - like alsa and gpm...

localedef -i en_US -f UTF-8 en_US.UTF-8

useradd -m -s /bin/bash -G audio,lp,video,wheel -U yourusername
passwd yourusername
nano /etc/sudoers
  # enable wheel for sudo.
! Mind! Crux creates ids as 100:101. Which means, when you start to meddle with your other installed Linuxes, you get 'permission denied' shit - as at least Debian, Slackware and even Alpine all go 1000:1000. I fixed that like this:
usermod -u 1000 yourusername
groupmod -g 1000 users
usermod -g 1000 yourusername


Network. See here. I went for dhcp and used example script, and it worked (well, after I got missing driver added and kernel recompiled).
Don't forget to create /etc/udev/rules.d/70-persistent-net.rules
Some silly-looking stuff in there - better copy it from your other Linux.

cd /etc/ports
mv contrib.rsync.inactive contrib.rsync
/etc/prt-get.conf
- uncomment - prtdir /usr/ports/contrib
For other repos you have to create rsync files (and add entries in prt-get.conf), like:
cat >> /etc/ports/xfce.rsync << EOF
host=crux.nu
collection=ports/crux-3.0/xfce/
destination=/usr/ports/xfce
EOF

! Good thing: you can also use your local make-dir (where you collect your sources and create packages) as 'prtdir' - and prt-get can see it and operate with your packages.
! Mind! When you do prt-get sysup afterwards, the bloody shit overwrites your freshly-fixed prt-get.conf. So, make a copy before...
For confing pkg and ports, see here.

# Kernel compiling. I went with provided oldish 3.6. That's because Crux 3.1 seems to be coming soon (fingers crossed) - with newer stuff and so on. Also, as my linux-life has shown me several times: Do not go with newest, it might not work!

In 'make menuconfig', take your time and pick all needed... I compiled twice as I missed my network driver at first run. Whole process of kernel creation:

cd /usr/src/linux-3.6.x
make menuconfig
make all
make modules_install
cp arch/x86/boot/bzImage /boot/vmlinuz
cp System.map /boot


Fix/install your bootloader.
Done. exit. umount. reboot. If multibooting, fix your master-bootloader.

! By the way - quite a lot of this command-line conf can be done on other Linux' desktop, in more relaxed way than nano.
! Just to mention: runlevel 1 = single-user, 2 = multiuser, 3,4,5 = not used.

End of part 1. Part 2 - Beefing it up, Part 3 - Later problems

2014-05-08

Minix, OpenIndiana, Haiku

Visiting fringes, chapter 2. See chapter 1

Going to extremes now... Fortunately for me, what comes here is more like educational overview, a total hearsay - otherways, I am afraid - I would be now complite drooling and gibbering wreck. I mean - not just slightly nuts as now ... errr ... This longish sentence meant that I didn't install any one of those three, but simply tried to get A Picture by reading various bits and pieces.
The goal of that: Are those three usable as desktop systems?

# Minix
A review, and another.
Minix is independent operating system, not a variation of linux at all. Though it uses Clang as a compiler and some Gnu utilities. There is closer connection with Netbsd nowadays - Minix3 uses their userland stuff. Which is probably very good thing - so they have at least something to use... Package management uses Netbsds' pkgsrc with 'pkgin' frontend.
It's development team has always been marginal - and that's sure way NOT to get WHOLE operational system properly done. Which is, it seems, recognized by Minix project - as focus lately tend to be on embedded ARM.
Some info-bits:
- tutorials and help in Minix3 page are .... kinda like afterthought, semi-finished, raising questions like 'what?', 'and?', 'eh?'.
- installation is non-trivial and by some comments - can be frequently unsuccessful.
- hardware support can be considered ... errr.. hugely lacking.
- There are three window managers available. I myself quite like JWM - but choice of only three here simply means - Minix is not for desktops.
- Quoting: 'Currently, only text-mode browsers are supported under MINIX 3'.
- From 'Goals' of project it's also quite clear that Minix is NOT trying to be usable desktop.
So don't bother to try Minix as desktop system. For embedded systems with arm processor - it seems to be OK. Google Minix Neo X5 and X7, for example.

# Haiku
There are some reviews from 2012-13, this for example.
Quoting: 'The key highlights that distinguish Haiku from other operating systems include: specific focus on personal computing ... blah-blah' - so it's for desktops.
- First - it looks childish and outdated. So, one has to have certain dispositions to like and use it at all...
- Haiku has graphical installer, nothing overly complicated here. That is - if you reach that point - Haikus' hardware-support is (of course) rather limited.
- It uses its own BFS file system - do not expect any other op-system to read Haikus' partition.
- Whole desktop+apps complex is incomplete. There seems not to be any seriously taken and/or flawless app in existence.
Taking to account how difficult and time-consuming it is to create and maintain an operational system WITH usable whole-range bunch of apps, then - Haiku never will be complite. Not ever. No.
According to Haiku looks and (not)functioning - is there any point to try it? No, not really - a) If looking for simplicity, take some flavour of linux-for-simpletons and you get what is not so bloody win31-looking and it even works and has thousands of apps. b) Or if you want reasonably functional retro-look, why not to install Trinity on Ubuntu?
Conclusion:
Last Haiku alphas make colorful desktop-like picture alright, but ... You can't use it really for anything remotely serious.
Oh, well, I can say it, alright: But its obviously interesting for devs which is so good. See?

# OpenIndiana
A review here, quite nice by the way.
Quoting: 'OpenIndiana is a robust enterprise operating system, based on the illumos kernel. Blah-blah ..., and suitable for servers and desktops.'
OI is the only one of three which seems to me usable as desktop op-system. Quite simple to install, though somewhat buggy, and unfortunately in semi-zombie state.
Anyway, brave people who tried, say: it makes (gnome2) desktop and has some (great) apps.
It's based on SunOS and/or OpenSolaris... whatever. Commandline is allegedly close to bsd.
- tutorials, support and helps are quite pitifully lacking,
- It only has x86-version. At the same time - looks like zfs is only installable file system - which some people drool over, but which I consider serious overkill for average desktop-user (and there are compatibility issues with linux),
- when installing, Grub (legacy) has NO where-to choice. Beware.
- there are several good server-apps,
- desktop looks antique. OI has quite a lot of apps ... that is - compared to Haiku. But it lacks others, and really, repos are not big at all. It has several conf-utilities, it has nifty backup-utility...
XFCE and KDE are also installable, but allegedly very buggy.

Despite boasting (on their homepage) enterprise-quality, heritage, and more-big-words; it's one of those op-systems severely lacking dev-resources - and probably will be put to sleep after some more futile struggle.
As I noticed somewhere - a user opined that OI should stick with server-side and stop with desktop... I agree, but I think that it's too late for that. I would be very (pleasantly) surprised if OI survives and prospers.
OI really is a functioning system - as opposed to some which simply pretend. Good.
But there isn't any reason to pick it as your desktop platform. If one doesn't like linuxlands' late antics with systemd, gnome3 and tendencies to blindly fuck-up as much as possible - then PC-BSD is your unix-like desktop system.

For those who prefer shorter forms of information. Usable as a desktop:
Minix - No;
Haiku - hell, No;
OpenIndiana - Yes, maybe, but why?

2014-04-29

Slackware, Sid, lags + Nvidia 334.21

To make this shortish story a bit longer, let's start with that I clean-installed Slackware-current over my 14.1 ... because after last patches etc it had developed various quirks which annoyed me a bit. And when the choice is between spending x-hours hunting mysterious faults or spending some 3 hours with new and virginal install/rebuild - I'll pick the last one, period.
Install and rebuild were quite uneventful - nothing to whine over ... Maybe of the contrary - some 2-3 bugs with apps in 14.1 had resolved themselves meanwhile. And it helps to have previous install-list of apps, deps and shit.

But when attempting to install (previously used in 14.1 ) binary Nvidia driver 331.49, I had sudden 'unknown libEGL.so' problem, and no install. So I went for the latest beta - 334.21, which installed with no problems.
... Well, week before or so also smxi in my Debian Sid had got the same driver installed (after Xorg update, as the 'current nvidia'). And I had started to experience some lagging with mouse and keyboard. Sorta, occasional 1-2 seconds before slider moved, or mouse click registered or typed letter appeared. Bloody annoying, that! But, frankly, I thought that the culprit is some other critter of myriad of Sids' upgrades - and that it goes away with next bunch.
Now, after I installed the same driver to Slackware - and at once started to experience lags, I sure reconsidered. As an afterthought - it was most probably some kind of not-syncing between this Nvidia driver and Compton compositor.
Anyway, I didn't want to part with Compton, so I downgraded the Nvidia driver - and successfully, despite:

1. Slackware - previous installers' libEGL crap and no install.
I went to runlevel 3, did separate
sh NVIDIA-Linux-x86_64-334.21.run --uninstall
without letting Nvidia to restore previous xorg.conf (no idea if that matters), then slackpkg search mesa && slackpkg reinstall mesa-9.1.7-x86_64-1 to be sure I don't have leftovers from Nvidia (as I heard, Nvidia overwrites some of mesas' files). Then:
sh NVIDIA-Linux-x86_64-319.49.run
with 32bit support and 'yes' to overwrite xorg.conf.
Success, no whining from installer, AND - no more lags!

2. Sid. Not with smxi help this time, but manually:
telinit 1
sh NVIDIA-Linux-x86_64-334.21.run --uninstall

That finished with installers' ominous whine about leftover symlinks. Whatever... I decided also not to bother with mesa and press on and see what happens:
sh NVIDIA-Linux-x86_64-331.49.run
'Yes, do install' - to installers' worry about 'maybe runlevel 1 is not good...'
With 32bit support, 'Yes' to overwrite conf.
Success, and no more lags!

Simpleminded conclusion: If you experience lags (especially after pointless upgrade to latest/greatest Nvidia driver), try downgrading a bit. Beta really was Beta, in my case.