IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 30 July 2015   (all times are UTC)

02:21gdi2k has left IRC (gdi2k!~gdi2k@180.191.105.58, Ping timeout: 246 seconds)
04:38AlexPortable has left IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-ufokytywwpxrkrhy, Quit: Connection closed for inactivity)
04:50ltsp has joined IRC (ltsp!bot@ltsp.org)
04:50-kornbluth.freenode.net- [freenode-info] channel trolls and no channel staff around to help? please check with freenode support: http://freenode.net/faq.shtml#gettinghelp
05:02TatankaT has left IRC (TatankaT!~tim@193.190.253.114, Ping timeout: 264 seconds)
05:03TatankaT has joined IRC (TatankaT!~tim@193.190.253.114)
05:16cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
05:17work_alkisg is now known as alkisg
05:44mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
06:22
<gehidore>
nope, cause you didn't stick around
06:24
<muppis>
No wonder why this world is in this shape with that patience. :D
06:25
<gehidore>
muppis: yarr it's a plague everywhere, I myself am effected from time to time
06:26
<muppis>
I confess as well. :D
06:29
<gehidore>
I really need to get back to working on what I need from ltsp but this financial crap has shut down all progress on all my projects :S
06:43cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 244 seconds)
06:54cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
07:33ricotz has joined IRC (ricotz!~rico@p5B2A8EB3.dip0.t-ipconnect.de)
07:33ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
07:41gdi2k has joined IRC (gdi2k!~gdi2k@119.94.4.10)
07:42telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
07:44telex has joined IRC (telex!teletype@freeshell.de)
08:17vmlintu_ has joined IRC (vmlintu_!~vmlintu@dsl-jnsbrasgw2-58c07e-86.dhcp.inet.fi)
08:27vmlintu_ has left IRC (vmlintu_!~vmlintu@dsl-jnsbrasgw2-58c07e-86.dhcp.inet.fi, Ping timeout: 250 seconds)
08:37gdi2k has left IRC (gdi2k!~gdi2k@119.94.4.10, Remote host closed the connection)
09:04alkisg is now known as work_alkisg
10:21uXus has left IRC (uXus!~uXus@217.77.222.72, Quit: ail bi bek)
10:22uXus has joined IRC (uXus!~uXus@217.77.222.72)
10:24simone has joined IRC (simone!4f3a8fed@gateway/web/freenode/ip.79.58.143.237)
10:24Phantomas has joined IRC (Phantomas!~phantomas@ubuntu/member/phantomas)
10:24simone is now known as Guest12497
10:32Guest12497 has left IRC (Guest12497!4f3a8fed@gateway/web/freenode/ip.79.58.143.237, Quit: Page closed)
10:43kwmiebach has left IRC (kwmiebach!sid16855@gateway/web/irccloud.com/x-tzhkvouptwnthzhc)
10:44uXus has left IRC (uXus!~uXus@217.77.222.72, Quit: ail bi bek)
10:49uXus has joined IRC (uXus!~uXus@217.77.222.72)
11:31eemeli has joined IRC (eemeli!3e94cd0c@gateway/web/freenode/ip.62.148.205.12)
11:32Faith has joined IRC (Faith!~paty@unaffiliated/faith)
11:39eemeli has left IRC (eemeli!3e94cd0c@gateway/web/freenode/ip.62.148.205.12, Quit: Page closed)
11:49danau11 has joined IRC (danau11!~durban@12.197.179.122)
11:49danau11 has left IRC (danau11!~durban@12.197.179.122)
12:03mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
12:04Phantomas has left IRC (Phantomas!~phantomas@ubuntu/member/phantomas, Read error: Connection reset by peer)
12:08Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
12:19adrianorg has left IRC (adrianorg!~adrianorg@179.183.64.70, Ping timeout: 255 seconds)
12:20adrianorg has joined IRC (adrianorg!~adrianorg@179.183.64.93)
13:29AlexPortable has joined IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-ogquyewnjtlsolgg)
14:30Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Read error: Connection reset by peer)
14:41Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
14:49
<championofcyrodi>
any tips on ensuring my user's Thunderbird "INBOX" cache doenst grow over 2GB?
14:49
some are like 10GB or more, plus archivals.
14:49
their using IMAP
15:13work_alkisg has left IRC (work_alkisg!~alkisg@srv1-dide.ioa.sch.gr, Remote host closed the connection)
15:17uXus has left IRC (uXus!~uXus@217.77.222.72, Quit: ail bi bek)
15:23geekgirl has joined IRC (geekgirl!ce4a3d81@gateway/web/freenode/ip.206.74.61.129)
15:32uXus has joined IRC (uXus!~uXus@217.77.222.72)
15:38vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
15:52telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
15:54telex has joined IRC (telex!teletype@freeshell.de)
15:57work_alkisg has joined IRC (work_alkisg!~alkisg@srv1-dide.ioa.sch.gr)
15:58work_alkisg is now known as alkisg
15:58alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
15:59
<alkisg>
championofcyrodi: try #thunderbird in irc.mozilla.org
16:01
<championofcyrodi>
lol, thanks.
16:01
i got it
16:02
disable local mail sync on the clients is all.
16:02
under account settings
16:05
<geekgirl>
I have a simple question. I have fat clients. When I update the chroot, should I be running ltsp-update-sskkeys as well? How often is that needed or when should I be using it?
16:06* vagrantc finally has a new real-world LTSP lab in the works
16:06brianr_ has joined IRC (brianr_!~brianr@out.ewbc.com)
16:07
<alkisg>
geekgirl: you don't need to run it unless you change your server's hostname or ssh keys
16:07
It used to be necessary when you changed your server's ip, not anymore
16:07
vagrantc: cool! how many clients?
16:07
And, distro/version/DE?
16:07
<vagrantc>
alkisg: i think it'll be about 60 when all is said and done
16:08
<alkisg>
So, fats + gigabit, I assume...
16:08
<vagrantc>
Debian Jessie with gnome-flashback
16:08
<alkisg>
Nice, my main problem there is locks with sshfs, and the keyboard indicator icon
16:08
<geekgirl>
ok thank you
16:08
<vagrantc>
kind of between a fatclient and a kiosk... trying to get the lightdm guest login feature working
16:09
<alkisg>
https://bugzilla.gnome.org/show_bug.cgi?id=730587
16:09
<vagrantc>
currently only configured as autologin
16:09
alkisg: no sshfs at all, just using a locally generated user
16:09
<alkisg>
That should be more stable :)
16:09
<vagrantc>
hopefully.
16:09uXus has joined IRC (uXus!~uXus@217.77.222.72)
16:10
<vagrantc>
the clients are dual-core 64-bit atoms with 2-4GB of ram ...
16:10
i think most just have two
16:10
<alkisg>
About kiosks etc, why don't we just create a session in /usr/share/xsessions that autolaunches the browser?
16:10
Then we can have autologin as usual, and ldm_session, and it would work with both thins and fats
16:10
<vagrantc>
alkisg: i think the reasoning was running a whole display manager was a waste of resources for that use-case... but maybe that's a way to go.
16:11
<alkisg>
LDM_AUTOLOGIN doesn't display the DM, afaik
16:11
*the greeter
16:11
OK it does run the DM backend
16:11* vagrantc isn't using LDM at all
16:12
<vagrantc>
just lightdm
16:12
but the guest login feature is perplexing me....
16:12
<alkisg>
I think ltsp has better means to create and manage guest logins than lightdm
16:12
<geekgirl>
On occasion & randomly, maybe 2 reboots out of 15... a fat client will get just a black screen. I have looked in auth.log and syslog but I dont see anything odd-ball. Do you know where else I could look for clues?
16:12
<vagrantc>
i looked over the scripts that it uses on ubuntu and copied them, but they're just not even executed
16:13
<alkisg>
E.g. you can create /home/username on an nbd encrypted partition, created dynamically, so that the ram isn't an issue
16:13
<vagrantc>
alkisg: we don't want persistent home dirs
16:13
alkisg: want it to be thrown away on login/logout
16:13
<alkisg>
Not persistent, just to save RAM
16:14
E.g. suppose a user works for 10 hours, and his home dir grows to 2 GB
16:14
<vagrantc>
why NBD ?
16:14
<alkisg>
That all would go to tmpfs, crashing the client
16:14
If you used nbd instead, the RAM would be free for actual programs to run in
16:14
Not for /home/guest...
16:14
It's quite easy to implement it
16:14
<vagrantc>
it already does encrypted swap by default
16:15
just create a bigger swap partition
16:15
then tmpfs will swap out whatever it's not using
16:15
<alkisg>
I think tmpfs is half the physical ram, isn't it?
16:15
It won't use from the available swap...
16:15
<vagrantc>
by default, it's configurable though
16:15
yes it will
16:15
<alkisg>
So you have have e.g. 10 GB swap, 1 GB RAM, and 5 GB tmpfs working fine?
16:16
<vagrantc>
i used to do it all the time on my laptop
16:16
<alkisg>
Cool, I think I tried it once with the ltsp defaults and it didn't work that way
16:16
<vagrantc>
probably the tmpfs was too small
16:17* vagrantc now has more ram for the laptop, but used to do package builds in tmpfs 5 times the size of ram
16:17
<alkisg>
geekgirl: at that point, run `ps aux` to see what's not running when it should. Also, syslog and dmesg
16:25
vagrantc: about this: https://bugs.launchpad.net/ltsp/+bug/1352038
16:25
In aufs, you bind-mount all the mount points over the cow dir, right?
16:25
So, if the cleanup phase makes changes, they're done in the real dirs, not in the cow overlay...
16:25
Right?
16:26
so e.g. if someone had /etc in a different partition, cleanup.d would permanately remove all the users... :(
16:27
I didn't find any other way to do it though, so maybe we could do those bind-mounts, but then also remount the bind-mounts as read-only
16:27
<vagrantc>
alkisg: i don't think so
16:27
alkisg: i make a separate aufs filesystem for each mount, writeable in tmpfs
16:28
<geekgirl>
@alkisg I have one now in the black screen state. I can ping it. it looks exactly the same as all the others in those logs. I did find this in .xsession-errors Xsession: X session started for smain13 at Thu Jul 30 11:58:57 EDT 2015 localuser:smain13 being added to access control list Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. init: at-spi2-registryd main process ended, r
16:28
<vagrantc>
alkisg: i've never seen --cleanup remove all my users, for example
16:28
<alkisg>
Do you have /etc/ in a different partition?
16:28
<vagrantc>
ah.
16:28
i have tested it with a split /home and split /boot
16:29
<geekgirl>
OOOPS sorry. it didnt paste all that. the last 2 lines say:init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd respawning too fast, stopped
16:29
<alkisg>
mkdir -p "$cu_cow${point%/}"
16:29
mark_mount -t "$union_type" -o "dirs=$cu_cow${point%/}=rw:$cu_rofs${point%/}=ro" "$union_type" "$cu_chroot${point%/}"
16:29
That's above the tmpfs, isn't it?
16:29* vagrantc hasn't looked at the code in a while
16:29
<alkisg>
geekgirl: which distro/version/de?
16:29
Desktop Environment?
16:30
<geekgirl>
Unity - ubuntu 14.04
16:30
<alkisg>
geekgirl: and that happens on login? I.e. you see ldm normally, the user types username/password, and then gets a blank screen?
16:31
<geekgirl>
I have the clients auto-logon through lts.conf..
16:32
<alkisg>
Do you have any remote access method to it?
16:32
screen_02=shell, epoptes-client, ssh...?
16:32
<geekgirl>
epoptes... it shows black screen too
16:32
<alkisg>
Right click and open terminal, and run ps aux
16:33
ls /home/username, things like that
16:34
<geekgirl>
I never even seen that! ---root remotely? or user locally?
16:34* vagrantc wonders how hard it would be to generate homedirs in LDM like lightdm's guest-account feature
16:35
<vagrantc>
though i really want to move away from LDM ...
16:41
<brianr_>
geekgirl, are you getting an all black screen after you login?
16:43
if that is the case , that happens to us when a user manually sets their resolution, and then logs into another thin client which doesn't support that resolution. not sure if thats the case with you ...
16:43
<geekgirl>
@alkisg no. Its just randomly across the clients this happens on a reboot. There are 31 other clients running fine on it. If I reboot this one it will be fine...I was trying to catch the problem in the act.
16:44
<alkisg>
geekgirl: yes, epoptes allows you to debug the problem in the act
16:45
<geekgirl>
they reboot often. Its for a library system. I reboot in between people using them. I have a script that copies over the home directory and im hoping it doesnt bomb on occasion... but the home directory looks fine!
16:45
<alkisg>
You can get a shell there and see which thing is not running, what failed etc
16:45
<geekgirl>
i got one and I am trying to compare a good one to a black screen one now
16:46
<alkisg>
vagrantc: lightdm generates them on /tmp so that it doesn't pollute /home, but with ltsp clients, do you need that?
16:46
What's wrong with a plain `adduser guest`?
16:47
...and a `find . -delete; rsync -a /etc/skel` on login...
16:47
(or del/readd user...)
16:48
<geekgirl>
OK strange I notice that the black screen client, when I do a ps aux.... everything is owned by the user... on the working one there are some things owned by root.
16:49
<ogra_>
does the black screen user by chance have a ~/.config/monitors.xml ? (that would try to redefine the resolution after login if teh user played with it)
16:50
<vagrantc>
alkisg: i guess that would work...
16:52
alkisg: i currently add the guest user in an init-ltsp.d hook ... but haven't figured out where to put the account cleanup scripts
16:52
<geekgirl>
hmmmm nope...
16:53
<vagrantc>
alkisg: also, it's a chrootless install, so some of the configuration is on the server-side, although i suppose i could just do everything with init-ltsp.d hooks instead.
16:53
<geekgirl>
@vagrant how about in chroot -->/usr/share/ldm/rc.d/S00-guest-sessions
16:53
<vagrantc>
geekgirl: not using LDM
16:54
<geekgirl>
ohhh ok. :)
16:54
<vagrantc>
don't want to strip the ssh parts out of LDM...
16:54
but in theory it would be possible.
16:55* vagrantc wonders what to call it if we implemented it in LDM
16:55
<alkisg>
!guest
16:55
<ltsp>
I do not know about 'guest', but I do know about these similar topics: 'greek'
16:55
<vagrantc>
since "guest login" in LDM already means something, and "guest login" in lightdm means something else
16:56
alkisg: i've heard greeks treat their guests well
16:56
<alkisg>
:D
16:56
The guest login in ldm is misleading, we should rename it
16:57
I think the guest cleanup script I mentioned in the ML was there: http://sourceforge.net/p/ltsp/mailman/message/25064076/
16:57
...but sf seems down
16:58
Whoops, nope, not that one...
16:58
http://sourceforge.net/p/ltsp/mailman/message/27814821/
16:58
That one
16:58
<ogra_>
vagrantc, "test login" or "temporary login"
16:58
<vagrantc>
transient login
16:58
<ogra_>
yeah
16:59
<vagrantc>
guest login in LDM predates guest login in lightdm
16:59
<ogra_>
or "trial login"
16:59
(we will charge you after 10 min of usage)
16:59
:PP
16:59
<alkisg>
LDM's guest login is not a guest though
16:59
It's a real user
17:00
So that's the one that should be renamed...
17:01
<vagrantc>
fair enough
17:02
yeah, i've used such cleanup scripts before ... but they still require ssh access to the server
17:04
which, for ephemeral logins seems silly
17:04
oh no, maybe i'm going to do more LDM coding...
17:04* vagrantc can sense a TODO overload coming on
17:05
<geekgirl>
AHA! The resolution on the one with a black screen is different...
17:05
<vagrantc>
honestly, if i can just get lightdm's guest login feature working, that solves my problems perfectly.
17:06
<geekgirl>
something must be up with my display settings. I would be surprised if users are trying to change resolution.
17:09
In order to have a decent resolution I have this in my lts.conf XRANDR_COMMAND_0="xrandr --newmode 1368x768 85.25 1368 1440 1576 1784 768 771 781 798 -hsync +vsync" XRANDR_COMMAND_1="xrandr --addmode VGA-0 1368x768" XRANDR_COMMAND_2="xrandr --addmode DVI-1 1368x768" XRANDR_COMMAND_3="xrandr --output VGA-0 --mode 1368x768" XRANDR_COMMAND_4="xrandr --output DVI-1 --mode 1368x768"
17:10
cause oddly.... Ubuntu counts the DVI-VGA adapter as a whole different monitor attached.
17:10
<ogra_>
geekgirl, well, if users try to change it via system-settings then there should be a ~/.config/monitors.xml ...
17:10
system-settings creates that (and hands it to xranrd on login)
17:11
(thats why i asked above if that file exists)
17:12
<geekgirl>
and there is not a .config/monitors.xml... so I am guessing my lts.conf doesn't apply itself every time?? I wonder why so random.
17:12
<vagrantc>
ogra_: so, debconf is in germany this year...
17:12
<ogra_>
vagrantc, yeah, i'll try to come :)
17:13
sadly my new job is called "community liaison" which means i need to do spontaneous travel if required
17:13
so i cant confirm 100%
17:13
but to 90 at least :)
17:13alkisg is now known as work_alkisg
17:14
<work_alkisg>
ogra_, do you know if 15.10 is supposed to have both upstart and systemd, or just systemd?
17:14
...and same question for 16.04?
17:14
<vagrantc>
ogra_: seems like a significant community be will be there!
17:15
<ogra_>
work_alkisg, the phones still use upstart ... and the desktop still uses upstart sessions, so it will still be around
17:15
<work_alkisg>
thanks :)
17:15
<ogra_>
not sure how well supported switching back and forth for init will be though
17:15
<work_alkisg>
init will be systemd, right?
17:15
<ogra_>
(and for 16.04 nobody can say anything concrete yet :) )
17:15
yeah, systemd is default since 15.04
17:16* work_alkisg just tries to see which things will need to be checked for ltsp in 16.04
17:16
<work_alkisg>
Cool... /me waves
17:16
<ogra_>
vagrantc, well, depends how big the interest in snappy is in that community :)
17:16
<brianr_>
alkisg, i still cannot get nbd to work without ipappend =3
17:16
Negotiation failed/8a: Requested export not found
17:16
<vagrantc>
i'd like to explore native systemd hooks for ltsp; currently relying on sysvinit compatibility at the moment
17:17
brianr_: you'll need either ipappend=3 or to specify the NBD server on the boot prompt
17:17
<ogra_>
(i *could* claim i'm going because i want to calm the debian community that .deb wont go away in ubuntu, despite of snappy though)
17:17
:)
17:18
<brianr_>
the boot prompt? like can i put it in the lts.conf?
17:18
<vagrantc>
ogra_: oh, switching packaging systems? yeah, that would stir some muck.
17:19
brianr_: not in lts.conf ... it's a bit more involved
17:19
<ogra_>
well, snappy is more like "meta project packages" than an actual packaging system
17:19
<vagrantc>
brianr_: same file where you would add ipappend=3
17:19
<ogra_>
and you can use debs inside snaps
17:19
or rather binary content from debs
17:19
<vagrantc>
brianr_: and honestly, ipappend=3 is the simpler way to do it.
17:23
<brianr_>
well, it seems my problem was that ipappend 2 got added to pxelinux.cfg/default somewhere
17:23
commenting that out fixed my issue
17:29Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Quit: I Leave)
17:40
<vagrantc>
brianr_: where did you comment it out? it may get overwritten on next update
17:41
<brianr_>
i commented it in the pxelinux.cfg/default to test
17:43
it isn't set in /etc/ltsp/update-kernels.conf
17:43
is there a downside to using NFS over NBD ?
17:48
<vagrantc>
NFS is a bit slower
17:48
but updates go live instantly
17:48
so no need to run ltsp-update-image
17:48
NFS also seems more resilient in cases of temporary network failure
17:52
<gehidore>
I keep looking at the infected windows 7 machine in the corner office and thinking.... MMMMM LTSP
17:54
<elias_a>
gehidore: Which floor? Do not jump! :P
17:55
<gehidore>
hahah elias_a, 2nd floor of a 2 story building
17:55
but I have full control of what they use and dont use I just haven't perfected my ltsp servering skills yet
17:55
I guess that's redundant...
17:55
s/ltsp servering/ltsp/
17:55
:D
17:56
<elias_a>
gehidore: One hint: even you would "have" to use windows, set the computers up so that in case of HDD failure or the like the PC will boot to LTSP.
17:57
<gehidore>
heheh
17:57
the folks here don't need windows
17:57
I'm working on assembling the ltsp image served to them to be a simple lightweight DE with Firefox Thunderchicken and libreoffice
17:57
cause that's all they need
17:58
<elias_a>
"What is my Ubuntu password?" -> Ok, it is a HDD failure so you say "Use your ordinary login and continue working."
17:58
<gehidore>
and these machines are all 64bit p4's with < 1G ram
17:58
I know a couple have 4G so I'm going to pull them all at once and try to get each machine at least 2G
18:15ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
18:34work_alkisg has left IRC (work_alkisg!~alkisg@ubuntu/member/alkisg, Ping timeout: 240 seconds)
18:37work_alkisg has joined IRC (work_alkisg!~alkisg@srv1-dide.ioa.sch.gr)
18:47ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
18:48ricotz has joined IRC (ricotz!~rico@p5B2A8EB3.dip0.t-ipconnect.de)
18:48ricotz has left IRC (ricotz!~rico@p5B2A8EB3.dip0.t-ipconnect.de, Changing host)
18:48ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
19:09vmlintu_ has joined IRC (vmlintu_!~vmlintu@a91-152-200-13.elisa-laajakaista.fi)
19:22
<geekgirl>
UPDATE: fat clients with black screen are showing "screen 0: 320 x 200, current 2734 x 768, 8192 x 8192" with the xandr command. That middle resolution is incorrect but only shows up randomly and results in a black screen. I reran my xandr commands in lts.conf with no change to teh black screen. Only reboot fixes.
20:25geekgirl has left IRC (geekgirl!ce4a3d81@gateway/web/freenode/ip.206.74.61.129, Ping timeout: 246 seconds)
20:35work_alkisg is now known as alkisg
20:39
<alkisg>
64bit p4's? That doesn't sound likely...
20:39
<gehidore>
alkisg: you've never seen the 64bit p4's?!
20:39
<vagrantc>
they definitely existed...
20:39
<alkisg>
Nope
20:40
And never with 4GB RAM
20:40
<maldridge>
they existed they just cost a fortune when they came out
20:40
<gehidore>
hahah
20:40
alkisg: you must have been sheltered
20:41
they where the ones that they hired the blueman group to do the commercial for
20:41
<alkisg>
Maybe schools here went for the cheap ones :)
20:41
<gehidore>
pulling up the infos on these exact machines
20:43
and I'm certain they never *came* with 4g
20:43
<maldridge>
in my experience primary and secondary schools go for cheap machines, but universities pay for the nice ones. No idea why
20:43
<gehidore>
doesn't mean I didn't upgrade a couple :P
20:43
and this is far from being at a school
20:43
<alkisg>
Wikipedia says Prescott (2004) and Cedar Mill (2006) came with 64bit... I haven't seen any of those, the newest P4's here are 3 GHz
20:43
...the oldest ones 1.7 GHz
20:44
And all of them with just 256 RAM, we're upgrading them to 1 GB to become fat clients
20:45* quinox once bought 16MB and was ectatic about his RAM doubling in size
20:45* maldridge is quite happy with his lab that has 16GB of ram as minimum
20:46
<gehidore>
http://ark.intel.com/products/77775/Intel-Pentium-Processor-G3420-3M-Cache-3_20-GHz
20:46
<alkisg>
quinox: haha, the first PCs in schools here only had 2 MB RAM, and they were diskless, booting with Novel
20:47
i386, with the token ring network etc
20:47
gehidore: that's definately not P4 :)
20:47
It's 10 years younger...
20:48
<gehidore>
oh I linked to the wrong one, my bad
20:48
too many tabs open
20:50
second
20:53brianr_ has left IRC (brianr_!~brianr@out.ewbc.com, Quit: Leaving)
20:54
<gehidore>
http://ark.intel.com/products/27480/Intel-Pentium-4-Processor-640-supporting-HT-Technology-2M-Cache-3_20-GHz-800-MHz-FSB there it is
20:55
64 bit p4 :P
21:00
alkisg: ^^
21:03Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
21:04ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
21:05uXus has left IRC (uXus!~uXus@217.77.222.72, Ping timeout: 250 seconds)
21:06uXus has joined IRC (uXus!~uXus@217.77.222.72)
21:11
<alkisg>
Yup, never saw these here...
21:14
No p4 with 775 in cpubenchmark... http://www.cpubenchmark.net/socketType.html#id5
21:14
Only pentium D's, we did have those here as well
21:15
So I'm guessing about 300 score... barely functional as a fat client...
21:19alkisg is now known as work_alkisg
21:28
<gehidore>
pretty damn functional as a fully installed box with XFCE4 on archlinux
21:28
I was shocked this stupid little machine was usable
21:29
the test box was the p4 1G ram and an 80G sata2 drive because it's what I had on hand
21:29
unfortunately we have zero budget to upgrade and the girls here if left to windows destroy them in a matter of days
21:30
and the one guy we've got kills them in hours
22:10ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
22:18telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
22:20telex has joined IRC (telex!teletype@freeshell.de)
22:21
<maldridge>
I've been continually impressed iwth low power machines. I've got a toughbook that only has 512mb on a centrino platform and it works fine
22:32
<gehidore>
aye if you don't slam them with eye candy they tend to be quite efficient
22:32
my e430 thinkpad is way overkill for how I have it configured but I still manage to saturate the full 16G of ram and touch over to swap quite often
22:33
since my thin/fat clients wont be running virtual machines or doing my sort of work it wont matter to them, they essentially need a chromebook but due to HIPPA I can't authorize that
22:37
<maldridge>
a HIPPA/FERPA safe chromebook would make a mint for whoever owned the rights
22:48
<gehidore>
+1