phicode 2017-03-01 01:45:53
Got turned off in a big way years back and am only now using it because I cant use dd anywhere else ;)
phicode 2017-03-01 01:46:54
same. ;)
FinalX 2017-03-01 01:47:23
people have looked at me funny at my department for years for using Windows as desktop OS on my laptop while I administer over a thousand Linux (and formerly *BSD) servers :)
FinalX 2017-03-01 01:47:31
now they just shrug
FinalX 2017-03-01 01:47:44
I like OS X as well, but it's not productive for me
missmbob 2017-03-01 01:47:46
!chat
dpkg 2017-03-01 01:47:46
This is not a chat channel, this is a Debian user support channel. Unless you have a Debian support question, please chat elsewhere, like #moocows on irc.oftc.net or ##chat on irc.freenode.net.
phicode 2017-03-01 01:47:46
im partial to Freedos because it can use things like Norton Commander and Midnight Commander and brings back many unfond memories of MSDOS
stoned 2017-03-01 01:54:10
huh
stoned 2017-03-01 01:54:47
The only productive OS for the stoned guy, is the debian one.
stoned 2017-03-01 01:55:07
Windows, has distractions. Solaris/indiana are not good for desktops. Freebsd is not good for desktops.
stoned 2017-03-01 01:55:22
Debian has all the goodness, and not the crappiness of the rest of them operating systems.
stoned 2017-03-01 01:55:31
For the stoned, I mean. For you, whatever works.
Shadow_7 2017-03-01 01:56:07
I use cwm for my desktop that is a BSD wm with a portable version.
Iridos 2017-03-01 01:56:19
missmbob, tsk, tsk… that factoid calls chanserv a liar… notte goode.
ausinch 2017-03-01 01:56:37
Shadow_7: ran "apt-get install --reinstall linux-image-amd64" - rebooted - lsmod | grep cifs shows nothing loaded
stoned 2017-03-01 01:56:55
why use cifs in kernel module?
Shadow_7 2017-03-01 01:56:59
ausinch: it doesn't load until you try to mount with it
stoned 2017-03-01 01:56:59
I don't understand this.
Iridos 2017-03-01 01:57:05
but yeah… keep focused around technical problems with debian
Shadow_7 2017-03-01 01:57:20
ausinch: or you manually modprobe it. or it loads at boot from /etc/modprobe entry
ausinch 2017-03-01 02:00:32
I have mounts in /etc/fstab that have worked for years until an update last week
pila 2017-03-01 02:00:47
someone used pssh with more than 25+ servers? i had no problems managing 10 servers but with 25+ i get timeouts and some commands are not transferred to some serves
ausinch 2017-03-01 02:00:52
i just tried a manual mount again - always the same error:
Shadow_7 2017-03-01 02:00:58
ausinch: then modprobe cifs and check dmesg
stoned 2017-03-01 02:01:08
There should be a channel for debian people with beards. only beards.
ausinch 2017-03-01 02:01:09
mount error: cifs filesystem not supported by the system
ausinch 2017-03-01 02:01:11
mount error(19): No such device
ausinch 2017-03-01 02:01:13
R
stoned 2017-03-01 02:01:16
I use samba.
stoned 2017-03-01 02:01:21
I have never had to mess w/ kernel/cifs stuff
stoned 2017-03-01 02:01:56
I mount samba/cifs shares from windows all the time.
stoned 2017-03-01 02:02:06
never had to deal w/ kernel stuff. What are you doing?
stoned 2017-03-01 02:02:10
If I maybe ask
Shadow_7 2017-03-01 02:03:16
ausinch: ls /boot/ and uname -r... make sure you're running the kernel you think that you're running.
Shadow_7 2017-03-01 02:04:15
ausinch: also... find /lib/modules/$(uname -r)/ -iname '*cifs*' ... you might have more than one copy of the module there and the wrong one loads or fails to load.
ausinch 2017-03-01 02:05:00
modprobe cifs: ERROR: could not insert 'cifs': Unknown symbol in module, or unknown parameter (see dmesg)
ausinch 2017-03-01 02:05:02
dmesg: [ 695.787160] cifs: Unknown symbol setattr_prepare (err 0)
Shadow_7 2017-03-01 02:06:45
ausinch: that's normally something that happens when you use a module not built for your kernel. I would rm that module and --reinstall and see if it actually is part of the package.
pila_ 2017-03-01 02:07:10
hello is this a really high value on a 4c / 8t machine? load average: 63.47, 37.15, 47.82
ausinch 2017-03-01 02:08:58
s /boot/: config-3.2.0-4-amd64 grub initrd.img-3.2.0-4-amd64 lost+found System.map-3.2.0-4-amd64 vmlinuz-3.2.0-4-amd64
ausinch 2017-03-01 02:09:00
uname รข€"r: 3.2.0-4-amd64
ausinch 2017-03-01 02:09:02
find /lib/modules/$(uname -r)/ -iname '*cifs*' : /lib/modules/3.2.0-4-amd64/kernel/fs/cifs
ausinch 2017-03-01 02:09:04
/lib/modules/3.2.0-4-amd64/kernel/fs/cifs/cifs.ko
missmbob 2017-03-01 02:09:16
that's not a debian kernel
missmbob 2017-03-01 02:09:42
oh by bad, misread
pila_ 2017-03-01 02:10:47
anyone?
NiLon 2017-03-01 02:11:21
pila_ well it's high, more than your system can handle
pila_ 2017-03-01 02:12:02
mhh
NiLon 2017-03-01 02:13:01
pila_ but depending of the load it might not cause any problems
pila_ 2017-03-01 02:13:21
i think it comes from my php-fpm children
NiLon 2017-03-01 02:13:46
then you should see longer loading times
Shadow_7 2017-03-01 02:13:47
ausinch: using wheezy?
pila_ 2017-03-01 02:14:17
i have 250 php fpm children
pila_ 2017-03-01 02:14:36
if i am using less, i get lots of socket not available errors in nginx, but increasing it it drives my load very high
NiLon 2017-03-01 02:15:49
you should maybe tune down how many requests nginx is processing
Shadow_7 2017-03-01 02:17:41
ausinch: have you rebooted?
ausinch 2017-03-01 02:17:43
Shadow_7:yes
ausinch 2017-03-01 02:18:05
Shadow_7: lots of rebooting
ausinch 2017-03-01 02:21:21
Shadow_7: Debian GNU/Linux 7.4.0 _Wheezy
stoned 2017-03-01 02:21:33
I remember potato.
Shadow_7 2017-03-01 02:21:34
ausinch: do you have "other" kernels available to you? It appears to be a kernel issue that one is broke for all intents
stoned 2017-03-01 02:21:55
I fulltime started debian on ALL my home pc when sarge was announced testing.
stoned 2017-03-01 02:22:17
Waiting for stretch.
Shadow_7 2017-03-01 02:22:20
ausinch: it could just be that the initrd image didn't update, or the bootloader is using the wrong one.
ausinch 2017-03-01 02:22:22
No I tidied up apt-get auto-remove
Shadow_7 2017-03-01 02:22:53
ausinch: is cifs-utils still installed?
stoned 2017-03-01 02:22:54
http://sprunge.us/TPAS <- here is an upgrade script I wrote.
stoned 2017-03-01 02:23:07
Well, modified from the idea of another.
ausinch 2017-03-01 02:23:40
Shadow_7: yes i have removed - purged - installed again
Shadow_7 2017-03-01 02:26:08
ausinch: have you depmod -a ?, technically the pm does that for you.
ausinch 2017-03-01 02:27:22
Shadow_7: I have not - tring now
Shadow_7 2017-03-01 02:28:11
ausinch: might be some /boot/ stuff going on too. Like /boot on it's own partition and not mounted when you reinstalled. So the external partition that the bootloader uses has the OLD kernel, but the mount point /boot/... has the new one.
ausinch 2017-03-01 02:33:30
Shadow_7: cross checking with fdisk -l & df -h
Shadow_7 2017-03-01 02:34:35
ausinch: it should be in /etc/fstab if used (correctly). Probably with a ,noauto
Shadow_7 2017-03-01 02:35:09
ausinch: otherwise it's a partition and you shouldn't have many of those (in theory). # blkid
ausinch 2017-03-01 02:36:41
Shadow_7: yesterday I checked fstab against a month old fstab. The UUID is the same so I presume the /boot/ location is the same.
Shadow_7 2017-03-01 02:37:45
ausinch: mount /boot/ and do the --reinstall thing again.
Shadow_7 2017-03-01 02:38:07
ausinch: if /boot/ is not mounted, check that /boot/ is empty before you mount it.
ausinch 2017-03-01 02:39:13
mount /boot: mount: /dev/sda1 already mounted or /boot busy
ausinch 2017-03-01 02:39:15
mount: according to mtab, /dev/sda1 is already mounted on /boot
Shadow_7 2017-03-01 02:39:55
ausinch: can you umount it? and check the /boot is empty
Shadow_7 2017-03-01 02:40:03
s/the/that/
ausinch 2017-03-01 02:40:49
Shadow_7: done and it is empty
Shadow_7 2017-03-01 02:44:57
ausinch: and /boot/ points at that partition? You may need to re-install the bootloader if there are other /boot/ things in play.
