Search Debian Channel Logs

Saturday, February 4, 2017

#debian channel featuring irc2000, kang0, CuSn, SynrG, mmm4m5m, jscoder, and 5 others.

jscoder 2017-02-03 23:45:17
irc2000: the install will use about 4gb for a full desktop environment, my system is currently running off a 32gb thumbdrive with about 9gb for my root partition and 19gb for my /home
jscoder 2017-02-03 23:46:02
irc2000: I currently have 5.2gb used on / but I have a bunch of extra crap installed
irc2000 2017-02-03 23:46:26
hmm.. alright. That's modern times I guess.
irc2000 2017-02-03 23:46:43
Usually I just put up a 200MB arch server.
jscoder 2017-02-03 23:47:23
irc2000: I installed with mate desktop and I think it was under 4gb, 3 and some change initially
irc2000 2017-02-03 23:47:27
setting up a webserver. Lazy question. But how much ram does it need? :p
jscoder 2017-02-03 23:47:54
irc2000: depends, webservers have drastically different needs.
jscoder 2017-02-03 23:48:32
irc2000: things to consider are number of potential clients accessing it, if there are additional components with overhead like php, sql, etc
jscoder 2017-02-03 23:49:22
irc2000: I can run a webserver on my Alphasmart Dana, and it onle has a Motorola 68k 33mhz cpu and 4mb ram
jscoder 2017-02-03 23:49:36
its not going to host facebook or youtube
mmm4m5m 2017-02-03 23:49:41
Seems like it is solved. I found how to start rescue mode: https://www.debian.org/releases/stable/i386/ch08s07.html.en . And re-installed GRUB on MBR of my external hdd. The only mystery is why it did not work first time OR what were the actual question...
jscoder 2017-02-03 23:55:28
idk, I'm f'n baffled.. uname -p definitely does say "unknown", but this never checks uname -p, just uname -m (i686) and uname -s (Linux)
debish 2017-02-03 23:55:50
hey!
jscoder 2017-02-03 23:56:11
hay is for horses and other barn animals
jscoder 2017-02-03 23:56:26
dpkg, yinzersmite debish
debish 2017-02-03 23:56:59
Sure, jscoder
jscoder 2017-02-03 23:57:48
dpkg yinzersimte .*? ~ s/awhile/ahwile/
dpkg 2017-02-03 23:57:48
jscoder: I don't know, could you explain it?
jscoder 2017-02-03 23:58:03
no, probably not, my perl-fu isn't that great
debish 2017-02-03 23:58:12
it's also a widely accepted onomatopoeia
jscoder 2017-02-03 23:58:39
debish: yeah, well did you need something? ;-P
debish 2017-02-03 23:58:57
anyway, I was wondering if anyone here is experiencing trouble with the last kernel included in debian testng
debish 2017-02-03 23:59:23
version 4.9.0-1
CuSn 2017-02-03 23:59:28
Hi, I have 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) GNU/Linux. I'm trying to find out which named release this is, eg "jessie" or which. Is there a mapping somewhere?
debish 2017-02-03 23:59:39
for some reason I can't start xserver with the new kernel
jscoder 2017-02-03 23:59:49
I am not authorized to speak for anyone, here or elsewhere.
CuSn 2017-02-04 00:00:06
debish: are you getting a specific error message?
debish 2017-02-04 00:00:14
nothing
debish 2017-02-04 00:00:17
it freezes
jscoder 2017-02-04 00:00:19
the xserver not working is likely due to the video driver which would be rebuilt using dkms likely on kernel upgrade
debish 2017-02-04 00:00:20
no logs
debish 2017-02-04 00:00:41
jscoder, it may be enough if you speak for yourself
CuSn 2017-02-04 00:01:00
debish: he may not want to get married.
CuSn 2017-02-04 00:01:11
(Cue miles standish)
jscoder 2017-02-04 00:01:43
CuSn: there are ways, like checking /etc/apt/sources.list and /etc/debian_version but the most reliable is checking dpkg -l libc6 against package versions
debish 2017-02-04 00:01:44
jscoder, I'm going to check that, thanks
CuSn 2017-02-04 00:01:56
jscoder: can you fall back to a previous driver or downgrade to a more basic one?
jscoder 2017-02-04 00:02:01
,versions libc6
judd 2017-02-04 00:02:02
Package: libc6 on amd64 -- wheezy: 2.13-38+deb7u10; wheezy-security: 2.13-38+deb7u11; jessie-security: 2.19-18+deb8u3; jessie: 2.19-18+deb8u7; sid: 2.24-9; stretch: 2.24-9
CuSn 2017-02-04 00:02:20
jscoder: gracias.
jscoder 2017-02-04 00:02:46
CuSn: sometimes, depends on what harware and driver you're using. If you got nvidia's 3rd party you could fall back to noveau(nv) or such for example
debish 2017-02-04 00:03:26
I'm leaving for a min to do some tests
jscoder 2017-02-04 00:03:27
CuSn: well a system is a moving target once its installed, the admin can do whatever they want.. thats why those sorts of things are unreliable markers of version
debish 2017-02-04 00:03:34
thanks both! ;)
jscoder 2017-02-04 00:04:27
CuSn: the most reliable test of debian version is comparison of libc6 version which is perhaps one of the most core and integrated packages
CuSn 2017-02-04 00:05:14
jscoder: if someone modifies the install config information after install, thats clearly on them. :-) but it would be nice if it started out correct.
debish 2017-02-04 00:06:04
I'm back
jscoder 2017-02-04 00:06:19
debish: I noticed
debish 2017-02-04 00:06:30
jscoder, it was the video driver that for some reason was not rebuilt
debish 2017-02-04 00:06:51
X up and running with new kernel :)
jscoder 2017-02-04 00:06:52
debish: in the words of Ford Prefect, "That does happen"
jscoder 2017-02-04 00:07:20
especially when you installed your driver yourself with a rube method that the system isn't aware of
debish 2017-02-04 00:07:51
I didn't
jscoder 2017-02-04 00:07:57
dkms has made those sorts of things a lot more rare though..
debish 2017-02-04 00:08:17
that's for tech hipsters
jscoder 2017-02-04 00:09:03
p0g0: you're suppose to know where your towel is
p0g0 2017-02-04 00:09:34
jscoder: I know, I know... it is under this pile of rubble that used to be my house, I think.
CuSn 2017-02-04 00:11:59
judd: thank you.
jscoder 2017-02-04 00:12:48
judd botsnack
jscoder 2017-02-04 00:13:06
oh well, judd doesn't take food from people :-P
jscoder 2017-02-04 00:13:15
dpkg, botsnack
dpkg 2017-02-04 00:13:16
aw, gee, jscoder
jscoder 2017-02-04 00:13:22
I'll just give it to dpkg instead
jscoder 2017-02-04 00:14:44
dpkg cmd: yinzersmite .*? ~= s/awhile/ahwile/
dpkg 2017-02-04 00:14:44
jscoder: wish i knew
jscoder 2017-02-04 00:15:09
dpkg cmd: yinzersmite (.*?) =~ s/awhile/ahwile/
dpkg 2017-02-04 00:15:09
jscoder: OK
jscoder 2017-02-04 00:15:24
yay! got it on the 3rd try
CuSn 2017-02-04 00:16:10
per version of libc, I have "Jessie". eg - which was whatever was latest on Jan 8-th or so. :-)
jscoder 2017-02-04 00:18:42
CuSn: what I find curious is that judd reported that the Jessie libc is newer than the Jessie-security version
CuSn 2017-02-04 00:19:49
I assume thenewest version of glibc hasn't been built into/integrated into the security release yet?
CuSn 2017-02-04 00:20:03
(assume == guess) :-)
jscoder 2017-02-04 00:20:14
CuSn: heh, that doesn't make any sense
jscoder 2017-02-04 00:20:40
once a stable version is released it's frozen and doesn't change except for point-releases through security/volitile
nicofrand 2017-02-04 00:20:56
Hi
jscoder 2017-02-04 00:21:08
nicofrand: not yet, but we're working on it
nicofrand 2017-02-04 00:21:16
hm :) ?
nicofrand 2017-02-04 00:21:33
already working on an issue I haven't told, so great \o
CuSn 2017-02-04 00:21:34
jscoder: well if changes were mad to libc, you would want them in the secure release until thos changes had been properly regressin tested in case they introduce vulnerabilities to the system. libc is pretty pervasely used wo ity could provide a large attack surface.
CuSn 2017-02-04 00:21:39
*made
jscoder 2017-02-04 00:21:44
nicofrand: no, working on being "hi"
jscoder 2017-02-04 00:21:50
it was a joke
CuSn 2017-02-04 00:22:25
*would->wouldn't
nicofrand 2017-02-04 00:22:26
oh, sorry :D !
jscoder 2017-02-04 00:22:37
CuSn: which is the whole reason stable doesn't get updates.
CuSn 2017-02-04 00:22:42
yup
jscoder 2017-02-04 00:23:04
which is why its odd that judd said that
nicofrand 2017-02-04 00:23:21
I am having some issues while using debconf-apt-progress with apt-get update whereas apt-get update alors works fine. I was wondering if somebody could help ? Here are the logs : https://framabin.org/?ac58b0261e8eeb52#C0fTgH8EXfenIeYeZU7NYNGrXsM97YKyUw9pfCXuET8=
nicofrand 2017-02-04 00:24:11
s/alors/alone/ *
CuSn 2017-02-04 00:24:27
I once worked for a firm that didn't have a proper build system in place. They built telecomm hardware for the military. back in the 1980' they lost the code for an entire product release. They had to patch binaries to do bug-fixes. (They became totally committed to proper source code management afterthat :-D )
jscoder 2017-02-04 00:26:59
nicofrand: wtf is debconf-apt-progress?
kang0 2017-02-04 00:27:06
Is it possible to convert debian into .wim file?
jscoder 2017-02-04 00:27:21
also, use paste.debian.net in the future. .that site has popups and is in french
nicofrand 2017-02-04 00:27:28
jscoder something used to display a nice progressbar while the command does its job
nicofrand 2017-02-04 00:27:31
oops, sorry
jscoder 2017-02-04 00:28:16
@.@
nicofrand 2017-02-04 00:31:12
jscoder something like that http://pix.toile-libre.org/upload/original/1254245539.png (still in french but you get the idea)
nicofrand 2017-02-04 00:31:45
("Téléchargement du fichier" meaning "Downloading file")
jscoder 2017-02-04 00:33:17
nicofrand: I think its a dumb idea personally. Synaptic shows progress bars .. the whole point of acommand line is to see whats happening
jscoder 2017-02-04 00:33:41
nicofrand: where did you get this from?
nicofrand 2017-02-04 00:34:24
jscoder yup but I am just trying to understand a script here that fails because of that. (https://github.com/YunoHost/install_script/blob/master/install_yunohost#L94 from YunoHost which is a self-hosting helper)
nicofrand 2017-02-04 00:35:09
debconf-apt-progress works fine on my local computer based on ubuntu though
SynrG 2017-02-04 00:37:46
nicofrand: are you trying to solve it on debian? you're welcome to try what you learn on debian on other OSes, but we confine ourselves to debian support here. otherwise, see your own distro's channel for support.
jscoder 2017-02-04 00:37:52
the error is pretty explicit in explaining the error and where it is. The problem is that this isn't a debian issue, you'd be served best contacting the developer
nicofrand 2017-02-04 00:38:24
SynrG yup, the issue is on my server, Debian 8.7
nicofrand 2017-02-04 00:38:50
The developer of… ? debconf-apt-progress ?
jscoder 2017-02-04 00:39:14
yes, that and perhaps seeing #perl if you need help actually debugging
jscoder 2017-02-04 00:40:28
the scope of this channel is helping debian users with debian specific things we all know about. If it were a debian package you'd be advised to check the BTS and file a bug report, in this case you're gonna be advised to contact the upstream maintainer and file a bug report :-P
nicofrand 2017-02-04 00:41:03
I don't remember installing this package, I though it came with debian someway
nicofrand 2017-02-04 00:41:17
thought*
jscoder 2017-02-04 00:41:36
nicofrand: *shrug* I never seen or heard of it, but I've also been under a rock so to speak for several years
SynrG 2017-02-04 00:41:38
it is a part of debconf itself
SynrG 2017-02-04 00:41:46
apt-file search debconf-apt-progress
jscoder 2017-02-04 00:42:00
I asked where you got it from
nicofrand 2017-02-04 00:42:05
is there anyway I can tell from where this package comes from ? If this is a dependency or some other package or something like that ?
jscoder 2017-02-04 00:42:11
you mentioned github
nicofrand 2017-02-04 00:42:27
jscoder yeah the script that uses it
nicofrand 2017-02-04 00:42:35
sorry if I was misleading
SynrG 2017-02-04 00:43:00
?
jscoder 2017-02-04 00:43:05
heh
SynrG 2017-02-04 00:43:17
"this package" = debconf?
nicofrand 2017-02-04 00:43:22
you were advising not to use it, but instead using the command directly so I just told you I was using a script that was using it.
SynrG 2017-02-04 00:43:23
yes, that's standard.
SynrG 2017-02-04 00:44:03
nicofrand: i use 'apt' frontend now since jessie ...
SynrG 2017-02-04 00:44:10
shows progress bars all on its own just fine
SynrG 2017-02-04 00:44:14
no need for hackery
nicofrand 2017-02-04 00:44:40
yup, but I would be glad if I could make it work without modifying the whole script that calls it
jscoder 2017-02-04 00:45:07
nicofrand: so what you were saying is, you use some wrapper to access apt, and this progress behavior you like works when you use app directly and not when you use this wrapper script?