IRC Logs for #crux-devel Sunday, 2015-03-15

*** Feksclaus has quit IRC01:40
Romsterand i thought my commocore 63 was old and apple ][e that sparc looks just as old.02:26
Romsters my old 486sx 25 i once had.02:27
frinnstjue: figured out why I had issues with a nfs mount during boot: resolve error02:35
frinnststrange since the network should already be up at that point02:35
frinnstalso noticed that I dont get any output from init - just kernel log and the output from rc.modules02:36
Romsterguess sent to /dev/null?02:50
*** mavrick61 has quit IRC03:31
*** mavrick61 has joined #crux-devel03:32
*** Romster has quit IRC05:05
*** nilp has quit IRC05:25
*** nilp has joined #crux-devel06:17
*** Romster has joined #crux-devel06:18
*** nilp has quit IRC07:31
*** nilp has joined #crux-devel09:15
*** Romster has quit IRC09:42
*** Romster has joined #crux-devel09:56
frinnstRomster: nah, forgot to manually add /dev/console to my pre-udev /dev10:37
frinnsti changed ssd a month or so ago10:37
*** nilp has quit IRC10:37
frinnstjue: with proper output i noticed this:10:38
frinnstfredrik@nibbler:~$ sudo /etc/rc.d/nfs restart10:38
frinnstNo process in pidfile '/var/run/rpc.statd.pid' found running; none killed.10:38
frinnstjust an empty file10:38
frinnst-rw-r--r-- 1 nobody root     0 mar 15 11:37 rpc.statd.pid10:39
frinnstthe file was created during boot10:39
frinnstoh well, i'll look into it later on10:41
Romsteroh10:42
*** nrxtx has quit IRC11:12
*** nrxtx has joined #crux-devel11:15
*** diverse has quit IRC12:30
juefrinnst: if you are using dhcpcd I'd suggest to add the --waitip option13:27
juesorry, no idea about the stale pid file of statd13:29
frinnstno, static ip14:15
frinnstadded the hostname to etc/hosts so that should take care of that14:16
frinnstbut its only a ugly workaround. no clue why sometimes i couldnt resolve the hostname..14:17
rmullfrinnst: Probably not related, but sometimes my init processes finishes, I get a login prompt, and then I get a kernel message that tells me my network link just came up15:40
rmullstatic assignment fwiw15:40
rmullSo I assume that means that networking is not active for the duration of the init process15:41
rmullI have Intel NICs15:42
*** deus_ex has quit IRC16:58
*** deus_ex1 has joined #crux-devel16:58
frinnstsame here18:39
frinnstintel that is18:40
frinnstI'll add some debug stuff in the scripts and see if I can find something18:41
rmullIf you find anything interesting, let me know. I have a postgres init script that I always have to manually restart after reboot which may be affected by the issue, but I haven't bothered confirming18:56
juehmm, we should probably wait until the interface is up19:00
juesomething from /sys/class/net/<if_name> should show the up status if the interface19:01
jues/if/of/19:01
juehave to go now, bbl19:02
*** nilp has joined #crux-devel19:20
*** deus_ex1 has quit IRC19:25
nomiusHey folks19:53
nomiusDoes anyone knows the difference between gcc 4.8.x and 4.9.x series?19:54
*** nilp has quit IRC20:08
*** Feksclaus has joined #crux-devel20:09
*** deus_ex has joined #crux-devel20:21
*** deus_ex has quit IRC20:52
*** deus_ex has joined #crux-devel20:53
frinnstnomius: check out gcc.gnu.org21:05
rmullThe crux-contrib bugtracker defaults to 3.0 instead of 3.1 for the "reported version" dropdown menu. The regular crux bugtracker has it correct.21:23
rmullfyi.21:23
rmullsmall detail.21:23
rmulljaeger: contrib/libass could be updated 0.10.2 -> 0.12.1: https://github.com/libass/libass/releases21:41
rmullAlso google code is shutting down, so getting the sources from github is probably a better idea21:42
jaegerrmull: you should tell the maintainer21:45
rmullOh sorry, I never remember which is it21:45
rmullRomster: Ping, contrib/libass update21:45
*** nilp has joined #crux-devel22:03
rmullSo I don't know if this is because of the recent util-linux update, but my previous nfs4 mount fails with mount.nfs4: an incorrect mount option was specified23:41
rmullWhen turning up the verbosity, the options it creates magically are:mount.nfs4: trying text-based options 'addr=10.0.0.4,clientaddr=10.0.0.3'23:41
rmuller, sorry, actually, it was: mount.nfs4: trying text-based options 'vers=4.1,addr=10.0.0.4,clientaddr=10.0.0.3'23:42
rmullBut in order to get it to work I had to do this: mount.nfs4 10.0.0.4:/mnt/array /mnt/array -v -o "vers=4,"23:42
rmullWhich removed the "vers" from the magic options for some reason: mount.nfs4: trying text-based options 'addr=10.0.0.4,clientaddr=10.0.0.3'23:42
rmullAnd now I was able to mount23:42
rmullIs there something I'm supposed to configure differently? How come the vers=4.2 breaks the nfs options, and where does it come from anyway?23:43
*** nilp has quit IRC23:44
rmullThe mount options now that the share is mounted shows vers=4.023:45
rmullAdditionally: I need to run vgscan --mknodes manually after my crux fileserver boots in order to get my /dev node up. Why is that? It shows up in the rc script... do I need to add a delay or something?23:49

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!