[01:06] <kgoetz> hi all. how can i check if sasl is using the correct backend? postfix calls sasl, and sasl tries to look up its /etc/sasldb2 file. saslauthd is configured to connect to ldap, and isnt getting called at all by postfix :\
[01:07] <kgoetz> the othe rthing is that the file does exist
[06:47] <Zylstra555> About how many users can a server with a 366MMHz Processor and about 80MB free space handle? (Ubuntu server)
[06:47] <Zylstra555> (doing your basic PHP forum and HTTP pages)
[06:51] <macd> you can always use things like seige and php-benchmark to test that
[06:51] <macd> also httperf, autobench are apache tools
[06:52] <macd> so to test your php enabled pages/site just disable the login and let one of them test a page that uses php
[06:52] <Zylstra555> Interesting
[07:51] <kraut> moin
[08:32] <XiXaQ> moin :)
[08:32] <XiXaQ> I'm looking forward to trying JeOS.
[09:01] <vetri> ntp server means ?
[09:02] <vetri> how can i configure....
[09:02] <vetri> what is the use of ntp server
[09:03] <Kamping_Kaiser> its a time server
[09:03] <Kamping_Kaiser> as per its package description
[09:22] <sergevn> you can synchronise with an time server on the internet.
[09:22] <sergevn> localmachine => time.microsoft.com for example
[09:23] <sergevn> ;)
[09:25] <PanzerMKZ_> oh shame on you
[09:26] <PanzerMKZ_> atleast not post addy of m$ ntp server
[09:27] <vetri> i installed ntp server
[09:27] <vetri> how can check whether its working or not
[09:27] <PanzerMKZ_> have you synced with a ntp server?
[09:27] <Kamping_Kaiser> ntpq -p
[09:27] <Kamping_Kaiser> or syslog
[09:35] <sergevn> PanzerMKZ_: was a joke :)
[09:36] <PanzerMKZ_> i know
[09:36] <sergevn> vetri: is most of the cases your ISP has an ntpserver
[09:39] <vetri> sergevn,thanks
[10:16] <vetri> how can i check
[11:48] <soren> ivoks: Hey.
[11:49] <soren> ivoks: I've been thinking.. I don't see any harm in having dovecot always put its auth socket (by bind mounting) inside postfix' chroot.
[11:50] <soren> ..so we "just" need postfix to use it if it's available.
[11:52] <ivoks> what if someone has dovecot and exim?
[11:52] <soren> The are a few paths to this.. a) Postfix gets installed, and dovecot is already installed => postfix should get configured to use dovecot for SASL auth.. b) dovecot gets installed while postfix is already installed => postfix should be configured to use dovecot for SASL auth.. c) as a result of either a) or b), postfix has been configured to use dovcecot for SASL auth, but the admin doesn't want that. He should have an option to stop postfix from 
[11:53] <soren> ivoks: Screw them.
[11:53] <soren> ivoks: :)
[11:53] <ivoks> haha
[11:53] <ivoks> i agree, but we do have exim in main
[11:53] <ivoks> so, we support it
[11:54] <soren> exim and postfix conflict.
[11:54] <soren> ...so they won't be installed at the same time anyway.
[11:54] <ivoks> that's not the problem
[11:54] <ivoks> problem is that you have dovecot, which by defaults looks at /var/spool/postfix/
[11:54] <soren> Er?
[11:55] <soren> Why would dovecot look in postfix's spool?
[11:55] <ivoks> for dovecot-postfix-sasl, you have to tell dovecot where to put it's auth socket
[11:55] <soren> Oh, right.
[11:55] <soren> Yes, that's why I want it to be bind mounted.
[11:55] <ivoks> and, since postfix is chrooted, only solution is /var/spool/postifx
[11:55] <ivoks> yes, binding is an option
[11:55] <soren> ...so that its real socket stays in /var/run/dovecot, where it belongs.
[11:55] <ivoks> atm, dovecot-auth can't listen on tcp port
[11:56] <soren> There's a reason for that, I guess. There's no way to limit access to it that way.
[11:56] <soren> Well... Yes, with iptables and such, but then it gets hairy.
[11:57] <ivoks> i'm ok with binding during postfix start()
[11:57] <ivoks> if [ -e /var/run/dovecot/auth-socket ]; mount bind; fi
[11:58] <ivoks> + making sure dovecot start before postfix
[11:58] <soren> Right.
[12:00] <soren> ...and while its doing the bind mount, it can check if e.g. /etc/postfix/dovecot_sasl_configured.stamp exists, and if not, do the configuration and create that file. If the admin decides to revert that change, it won't get reinstated.
[12:00] <soren> On upgrades, we can just touch that file so that we won't fudge existing configurations.
[12:01] <soren> ...and put a note in the release notes that removing that file will set up this cool new configuration.
[12:01] <ivoks> hm...?
[12:01] <soren> It's quite common for us to provide fancy new features that don't get enabled on upgrades as there's often no proper, safe way to do so.
[12:02] <soren> ..and by doing it this way, we don't need an extra package and we don't depend on stuff being installed in the right order.
[12:02] <ivoks> well, postconf should be more than great:)
[12:02] <ivoks> with postconf we can check existing configuration
[12:03] <soren> True.
[12:03] <ivoks> well... hmm....
[12:03] <soren> it's just a fairily intrusive change on a running system.
[12:03] <ivoks> it is
[12:03] <ivoks> we can't tell with postconf :(
[12:03] <soren> s/fairily/fairly/
[12:03] <soren> Exactly.
[12:04] <soren> The common way to do this is to add it to the release notes.
[12:05] <soren> Let me rephrase: If we can get this to work on fresh installs (not just completely new ubuntu installs, but also just for people who haven't had these packages installed before), I'll be happy. If we can make it work on upgrades as well, that's even better, but not a requirement in any way, IMO.
[12:08] <ivoks> we can do both
[12:08] <ivoks> whit is what postconf returns on non-sasl-enabled systems:
[12:08] <ivoks> smtp_sasl_auth_enable = no
[12:08] <ivoks> so, if it's no, enable it and set if up; if yes, move along and don't touch anything
[12:08] <soren> Maybe the admin doesn't want sasl?
[12:09] <ivoks> true...
[12:09] <ivoks> i can't think of one that don't want that... but ok :)
[12:10] <soren> I can't think of anyone who'd like to use Windows, but nevertheless..
[12:11] <ivoks> :)
[12:14] <ivoks> so, you would like to disable it by default on new installs
[12:14] <soren> No.
[12:14] <soren> Not at all.
[12:14] <ivoks> on upgrades then
[12:15] <soren> Upgrades of postfix probably shouldn't enable this feature, right.
[12:15] <soren> Talk to lamont about that bit, though.
[12:15] <ivoks> does postinst knows the difference between install and upgrade?
[12:16] <ivoks> right, as a motu, i should know that :D
[12:16] <soren> Sure.
[12:17] <soren> $1 = install, $2 = previous version
[12:17] <ivoks> ok
[12:17] <soren> [ -z "$2" ] || echo this is a new install
[12:17] <ivoks> then i can do that
[12:18] <ivoks> then postfix start() should check if dovecot is set as sasl engine
[12:18] <ivoks> and do binding
[12:18] <ivoks> but, people will hate us if we do that in start() and they change dovecot's config
[12:19] <soren> ivoks: Why?
[12:19] <soren> ivoks: What's the use case?
[12:20] <ivoks> hunderds of howtos on dovecot+postfix sasl
[12:20] <ivoks> they all say change dovecot's config
[12:20] <ivoks> and postfix's
[12:21] <soren> I refuse to keep from making things smarter because there are howto's somewhere on the internet that explain how to do things the hard way.
[12:21] <ivoks> i know couple of admins that would break exsisting setup and then do it their way
[12:22] <soren> That's fine.
[12:22] <soren> ?
[12:23] <ivoks> they would be surprised to find out that their socket isn't there, despite dovecot's config
[12:23] <ivoks> ok.. i think i know how to do it
[12:23] <ivoks> in dovecot, we leave path as /var/run/dovecot/sasl/auth
[12:24] <ivoks> and then bind /var/run/dovecot/sasl as /var/spool/postfix/dovecot-sasl
[12:24] <soren> Precisely.
[12:24] <ivoks> this is self explanatory
[12:24] <ivoks> and everybody would figure it out
[12:25] <soren> It's dovecot's sasl socket. a) It's dovecot's socket. It belongs there. b) Other services might look there for it.
[12:25] <ivoks> so, even if they change config of dovecot
[12:25] <ivoks> there would still be /var/run/dovecot/sasl, and it could be mount-binded to postfix chroot dir
[12:25] <soren> Um.. That looked wrong. You know what I meant. :)
[12:26] <ivoks> yeah... ok, i think we have a solution :)
[12:26] <soren> Hm... dovecot -p might be a better choice than checking for the socket.
[12:26] <soren> Or using dovecot -p to find the right path.
[12:27] <ivoks> i have to start vmware to figure out what dovecot -p does
[12:27] <ivoks> :)
[12:28] <ivoks> i don't have it on any of my gutsy machines
[12:28] <soren> It corresponds to postconf (no options)
[12:29] <soren> It dumps the config.
[12:29] <soren> Er... dovecot -a
[12:29]  * soren can't read.
[12:29] <ivoks> uh...
[12:29] <ivoks> hard to parse...
[12:30] <soren> Yeah, a bit.
[12:31] <soren> brb
[12:32] <ivoks> i'm open for better than:
[12:32] <ivoks> dovecot -a | grep -A9999 auth | grep -A9999 socket | grep path
[12:32] <ivoks> :)
[12:32] <ivoks> ok ^auth :)
[12:41] <soren> sudo dovecot -a | sed -n -e '/^auth default/,/^[a-zA-Z0-9]/ p' | sed -n -e '/^  socket:/,/^  [a-zA-Z0-9]/ p' | sed -n -e '/^    client:/,/^    [a-zA-Z0-9]/ p' | grep path | cut -d: -f2 | cut -d\  -f2
[12:41] <soren> Booyah!
[12:41] <soren> It can sure do with a clean up, but it works.
[12:50] <ivoks> heh, this returns nothing for me :)
[12:50] <ivoks> error is ^client
[12:50] <ivoks> should be client
[12:51] <soren> It doesn't say ^client anywhere?
[12:51] <ivoks> right, bad pasting
[12:51] <soren> It says '/^    client/'
[12:51] <ivoks> but we shouldn't count whitespaces
[12:55] <soren> There. Done. I'll pastebin..
[12:56] <soren> http://pastebin.ubuntu-nl.org/46677/
[13:00] <ivoks> lol, nice
[13:02] <ivoks> hm... anyone did installation of vmware-server in gutsy?
[13:05] <soren> ivoks: I belive I did.
[13:05] <soren> ivoks: why?
[13:05] <ivoks> i just installed it and it reports that newer version is available
[13:05] <ivoks> and when i upgrade, it installs the same version
[13:06] <soren> Known issue.
[13:06] <ivoks> and again reports that newer version is available :)
[13:06] <soren> iz soyuz bug
[13:06] <ivoks> oh... ok then
[13:09] <ScottK> ivoks: You know that the openssl that vmware-server uses has an unpatched remote code execution exploit open against it, right?
[13:10] <ivoks> ScottK: that vmware isn't available to the outside world
[13:11] <ScottK> ivoks: OK.  Just making sure.  Canonical uploaded it to partners with that known vulnerability, so I thought I'd mention it.
[13:11]  * ScottK is particularly burned because he expended a lot of effort to get openssl097 removed before the Gutsy release.
[13:12] <ScottK> Very disappointing to see it reappear.
[13:18] <ivoks> am i wrong, or this is canonical-only problem?
[13:19] <ivoks> openssl0.9.7 is in partner, right?
[13:19] <soren> Yes.
[13:19] <ScottK> ivoks: Well if you look on the LP page for Ubuntu, it lists partner and partner is in Ubuntu's default sources.list, so while only Canonical can fix it, I think it is an Ubuntu problem.
[13:21] <ScottK> If Canonical wants to distribute security deficient code, I really wish they would do so in a way that is clearly distinct from Ubuntu.  Partner is much less distinct than Commerical used to be.
[13:21] <ivoks> ScottK: partner isn't enabled by default
[13:21] <soren> Partner is enabled by default?
[13:21] <ScottK> No, but it's listed.
[13:21] <ivoks> mozilla plugins are in firefox bookmarks too, but you can't say that bug in plugin is a bug in ubuntu
[13:23] <ScottK> ivoks: Mozilla plugins aren't listed on the main LP page for Ubuntu either.
[13:25] <ScottK> ivoks: Look at https://launchpad.net/ubuntu and tell me partner doesn't look like part of Ubuntu?
[13:25] <ivoks> it does, that's true
[13:25] <ivoks> and should be changed
[13:26] <ScottK> There's a bug against LP on that.
[13:26] <ivoks> but that doesn't change the fact that there's no libssl0.9.7 in ubuntu
[13:26] <ivoks> there's a bug in LP, yes
[13:26] <ivoks> but not in ubuntu
[13:27] <ScottK> Actually the bug in LP on openssl097 for Gutsy for this issue describes it as in Ubuntu.
[13:27] <ScottK> We may feel it's separate, but it's really not managed that way.
[13:48] <ivoks> take care, see you tomorrow
[13:48] <soren> ivoks: Likewise!
[13:49]  * ivoks hugs you like this http://image.dnevnik.hr/media/images///gallery/Dec2007//86528.jpg
[13:49]  * soren chuckles
[13:50]  * soren wonders which one he's supposed to be
[13:54] <dendrobates> clifter1: welcome
[13:56] <soren> clifter1: Jason?
[13:56] <clifter1> dendrobates: Thanks!
[13:56] <dendrobates> soren: yep.
[13:56] <soren> clifter1: Ah, welcome!
[13:57] <soren> Now, please fix all my bugs. kthxbye.
[13:58] <clifter1> soren: Thank you!  is that the task for today ? ;)
[14:00] <dendrobates> soren: could you go over setting up a development environment and basic packaging?
[14:00] <dendrobates> soren: with jason.
[14:02] <soren> Um..
[14:02]  * soren ponders where to start
[14:03] <soren> clifter1: You could start by registering your nick, so that we can /msg each other.
[14:03] <soren> !register
[14:03] <ubotu> By default, only registered users can send private messages - Information about  registering your Freenode nick can be found at http://freenode.net/faq.shtml#userregistration
[14:04] <clifter1> soren: Thx.  Going through it now.
[14:07] <ScottK> soren: If you're going to do a basic packaging overview, you might want to do it in #ubuntu-motu so that people who are learning there would benifit and the other MOTUs there could help out.
[14:08] <soren> ScottK: That's the plan :)
[14:09] <clifter1> register
[14:09] <clifter1> register Glamdring5
[14:09] <soren> Heh..
[14:10] <soren> Better come up with a new password, and then: /msg nickserv register yournewpassword
[14:10] <clifter1> hide email on
[14:10] <clifter1> set email clifter1@yahoo.com
[14:11] <soren> clifter1: You need to type "/msg nickserv" before the commands
[14:11] <clifter1> soren: yea I got it and my email set.
[14:11] <soren> You're not registered..
[15:03] <soren> nealmcb: I just did a gutsy install (using the server iso) inside the hardy qemu and that worked like a charm.
[15:50] <dosnubbie> Hey how would one install Ubuntu-Server onto a Gateway Server that doesn't like to boot of CD/DVD drives?
[17:06] <lamont> what is it with people popping in, asking a question, and leaving 2 minutes later?
[17:07] <sommer> lamont: I think it's a personal attack on my ability to answer questions... :-)
[17:07] <lamont> heh.
[17:08] <lamont> PXE is the answer, of course.
[17:08] <lamont> now what was the question?
[17:08] <sommer> heh... maybe he found the answer and was like "see you peeps... I'm out"
[17:11] <lamont> maybe google helped him.  I hear it sometimes has answers.
[17:29] <zul> lamont: maybe they had an epiphany
[17:31] <MenZa> badum-chi
[17:51] <kshah> I somehow locked myself out of ssh'ing into my server, I reconfigured sshd_config after noticing many login attempts from an unknown IP on port 22 I switched to another port and set up iptables, I reinited and everything was working fine, but somehow, somewhere I just lost the ability to log in remotely - I can enter my username and I never get prompted for a pass then my connection deads
[17:51] <kshah> help?
[17:52] <soren> kshah: Which client are you using?
[17:53] <ScottK> I don't suppose you happen to have convenient physical access to the server?
[17:53] <kshah> soren: putty
[17:53] <soren> kshah: Thought so. Putty asks for your username before it attempts to connect.
[17:53] <kshah> ScottK: i do, i'm sitting there right now, this actually happened a few days ago, but I want to make sure when I go back home I can use it
[17:54] <soren> kshah: So it's not like ssh is half working or something. You're probably completely locked out.
[17:54] <kshah> soren: oh.. wow, that was both good (cause i know the answer) and upsetting
[17:54] <kshah> so switch client or...
[17:54] <soren> Well, what's the iptables command you used?
[17:54] <kshah> is it an actual problem
[17:54] <soren> No, it's not the client that's at fault.
[17:54] <kshah> oh
[17:54] <kshah> i thought that was what you were implying
[17:55] <kshah> for iptables I followed the HowTo Guide on help.ubuntu.com
[17:55] <soren> Because putty acts the way it does (opening the window and asking for your username) it looks as though you're connected and then gets kicked off or something, but that's not the case at all.
[17:55] <kshah> and I saved the rules, let me check to see if they stuck cause i just restarted
[17:55] <kshah> oh i see
[17:56] <soren> ..so it can sometimes fool you into thinkig that your ssh server is b0rken, while it's really the network that's acting funny.
[17:56] <kshah> and iptables did not save, when I restarted and ran sudo iptables -L I'm back at sq. 1
[17:57] <soren> kshah: No iptables rules? And you still can't connect?
[17:58] <kshah> soren: yeah, still can't connect, i'm going to restore my original sshd_config settings and just change the port, reinit and see if it works
[17:58] <soren> kshah: What did you change in sshd_config ?
[17:59] <kshah> the options they suggested changing only, login time, AllowUsers, lLogLevel
[18:00] <soren> They?
[18:00] <kshah> sorry: https://help.ubuntu.com/community/IptablesHowTo
[18:01] <soren> That doesn't even mention sshd_config?
[18:01] <kshah> i'm an idiot, i linked the wrong one
[18:01] <kshah> I meant https://help.ubuntu.com/community/AdvancedOpenSSH
[18:02] <kshah> I have both open, my bad
[18:02] <soren> Well, if you have no iptables rules in place, then you actually did botch your sshd_config.
[18:02] <soren> :)
[18:02] <soren> I don't know if you consider that a good thing, but there you go :)
[18:03] <kshah> my iptables rules didn't save after I wrote them the other day
[18:03] <kshah> I read that they go back to default unless you save them properly
[18:03] <kshah> so I assume that is what happened
[18:03] <kshah> and I still can't ssh in... which is very very strange
[18:03] <kshah> I restored my original rules
[18:07] <kshah> soren: i restored the default settings save the port and i'm accessing it locally 192.168.1.100:22 and now I can't even put in my username in putty
[18:07] <kshah> i somehow made the situation worse by allegedly making it better
[18:10] <soren> Ok, maybe putty has been changed since I used it last. That's good :)
[18:11]  * soren needs to run
[18:12] <kshah> k thx
[18:13] <kshah> is there another client i should perhaps use?
[18:17] <ScottK> kshah: On Windows you can instally cygwin and use ssh.
[18:18] <kshah> doing that now :)
[18:18] <kshah> my sshd problem is a whole nother mess now though
[18:19] <kshah> yay works
[18:25] <kshah> does iptables-save allow me to not have to edit etc/network/interfaces and place a pre-up and post-down iptables-restore directive? or is that still necessary?
[18:32] <bieb> i will be putting my server up at the company I work for (ie. job.com) currently any of the windoze servers are named somename.job.com, where is that during the ubuntu setup? would I have to enter the whole string? bieb.job.com? or just name the server bieb?
[18:36] <centaur5> bieb: That would be the host name field during the install.
[18:36] <bieb> centaur5 just the name of the server (ie bieb) not bieb.job.com?
[18:37] <centaur5> bieb: I just did the bieb part but I couldn't tell you if it would work either way.
[18:37] <bieb> I see
[18:38] <bieb> I am going to build a jabber server for internal use, anything else I should keep in mind?
[18:38] <centaur5> bieb: Yeah, get a hammer or some migraine medicine.  I attempted that last week but didn't quite finish.
[18:39] <bieb> ohhh?? that bad huh?
[18:39] <centaur5> Well the howto I was following off the community doc site didn't go very far in depth so I searched around for other howtos and there just wasn't much information for when things didn't quite work like they should.
[18:40] <bieb> which server you setting up?
[18:40] <centaur5> I thought it was going to be a piece of cake.
[18:41] <bieb> ejabberd? jabber? openfire?
[18:41] <coNP[uni]> Can someone refer me to some documentation regarding how to set up PostgreSQL authentication in Apache2 (for Gutsy)?
[18:41] <centaur5> just jabber from the package manager
[18:41] <centaur5> I used this site: https://help.ubuntu.com/community/SettingUpJabberServer
[18:42] <bieb> ejabberd is in the ubuntu package manager now
[18:42] <bieb> I installed it from synaptic
[18:42] <centaur5> Is ejabber supposed to be easier?  I guess that howto is probably kind of old.
[18:43] <bieb> ejabberd has some other things I needed, like active directory authentication
[18:44] <ScottK> kshah: I have a script that I use to set them up.  I just run that as one of my init scripts.
[18:45] <bieb> what script ScottK?
[18:45] <centaur5> bieb: Well good luck, I'm hoping to attack jabber again this weekend or next.
[18:45] <bieb> I guess I will look for more docs
[18:45] <bieb> the ##jabber channel is pretty quiet
[18:46] <ScottK> bieb: One I wrote, but I think it's not relevant to your question.  I was answering a question that kshah asked before you joined.
[18:46] <bieb> ohhh I see
[18:46] <bieb> thanks
[18:47] <kshah> ScottK: but I can achieve the same by editing /etc/network/interfaces, right?
[18:47] <ScottK> kshah: I'm really not sure.  I just know how I do it.
[18:48] <centaur5> bieb: ejabberd looks a little easier, perhaps I'll try that and remove my previous work.
[18:48] <bieb> cool
[18:48] <bieb> good luck
[18:48] <bieb> I will be getting back at it soon too
[18:48] <centaur5> same to you  :)
[18:48] <bieb> thanks
[18:49] <bieb> is it better to build the ubuntu server with the regular 7.10 disk? or one of the other 7.10 options?
[18:50] <kshah> what are the major differences between 7.04 and 7.1 ?
[18:50] <kshah> 7.10 rather
[18:59] <centaur5> kshah: all the "implemented" plans were added to gutsy https://blueprints.launchpad.net/ubuntu/gutsy/
[18:59] <kshah> checking it out
[19:09] <bieb> centaur5  any thoughts on my question?
[19:09] <centaur5> bieb: if you want a command line server use the alternate cd
[19:10] <bieb> so other than X, they are the same install?
[19:11] <centaur5> bieb: Well alternate actually has a "server" install option to where it does very basic packages whereas the live cd installs all the desktop apps.
[19:11] <bieb> I see
[19:12] <bieb> centaur5 what server items need to be running for jabber? just apache?
[19:12] <centaur5> bieb: If you want lightweight gui use the Xubuntu cd
[19:12] <bieb> are you using your jabber server for more than jabber?
[19:12] <centaur5> bieb: Yes, I'm using it for lots of services and applications.
[19:12] <bieb> I see
[19:13] <bieb> if it is just a jabber server, I dont need php, mysql, or any of that do I?
[19:14] <centaur5> bieb: I haven't checked the dependencies of ejabberd but you can look in the package manager.
[19:15] <bieb> ok.. thanks centaur5
[19:15] <centaur5> no prob
[19:15] <centaur5> For JUST jabber, I would go command line...but that's me.
[19:21] <centaur5> Does anybody know of a site that I can get some really good information on the best way to calculate the amount of inodes needed on a partition?
[19:26] <ScottK> dendrobates, soren, others ... I was thinking it might be nice to also add http://www.catb.org/~esr/faqs/smart-questions.html to /topic.  Any thoughts?
[19:29] <dendrobates> ScottK: It looks good to me, but the real bad offenders won't read it.
[19:30] <ScottK> dendrobates: OTOH, if it gets even one person to stop and think ....
[19:30]  * ScottK will add it.
[19:50] <Burgundavia> did everybody see that sun released the apoc stuff today?
[19:51] <mralphabet> ScottK: the topic is so long it cuts off the url after https://help.ubuntu.com/7.10/server/C/
[19:52] <ScottK> mralphabet: Thanks.  I'll shorten it.
[19:53] <ScottK> mralphabet: How's that?
[19:53] <mralphabet> ScottK: much better
[19:55] <proprietarysucks> anyone know the kickstart command to make ubuntu not ask to continue after being unable to reach security.ubuntu.com or to turn this check off?
[20:00] <mralphabet> proprietarysucks: wasn't that asked and answered like a week ago?
[21:07] <Gnomonic> I don't know if this is a Ubuntu Server question, but it is certainly not a Desktop question :). I have got a cheap VPS at vps4less.de. The problem is, that no locales are setup. How am I to do this excactly?
[21:07] <Gnomonic> ( oh, and hello guys and gals, by the way :) )
[21:08] <fujin_> *no* locales?
[21:10] <Gnomonic> fujin_: Well, I suppose that 'POSIX' is there.
[21:11] <fujin_> when you type `locale`
[21:12] <Gnomonic> fujin_: it says POSIX all the way down.
[21:13] <Gnomonic> The real problem is, that I had some help some while ago, and I managed to get da_DK.UTF-8 working.
[21:13] <fujin_> and what does locale-gen say?
[21:15] <Gnomonic> But it's very unstable. When I log in, it's standard POSIX. If I do export 'LANG=da_DK.UTF-8', locale returns the correct things. But if I log onto IRC irssi (which is the main use of the VPS), UTF doesn't seem to be active. But sometimes it works. It seems kinda voodoo-like.
[21:15] <Gnomonic> I was just searching for the 'correct' way to set up locales.
[21:15] <fujin_> yeah sorry I've never had to do it.
[21:15] <Gnomonic> locale-gen says da_DK.UTF-8... up-to-date
[21:16] <Gnomonic> fujin_: me neither :). It has seemed to be a part of a standard install since Redhat 4.
[21:16] <Gnomonic> I don't even know if the system is Debian specific :(
[21:17] <Gnomonic> The annoying thing is that the vps-hosts standard Debian image seems to work. But then I have to set up sudo and some other stuff manually, which I don't fancy either.
[22:31] <kshah> hey, I want to redo parts of my RoR installation on 7.04 server, how can I get a list of currently installed packages by me?
[22:33] <kgoetz> kshah: afaik you cant list only packages installed by you
[22:34] <kshah> kgoetz: thats even better, is that dkpg command?
[22:34] <kshah> or?
[22:34] <kgoetz> kshah: `dpkg -l |less`
[22:35] <kshah> thanks
[22:35] <somerville32> All packages are installed by root
[22:37] <kshah> i really just wanted to see why zlib isn't working for me
[22:38] <kgoetz> whats zlib, and whats 'not working'?
[22:44] <fujin_> dpkg --get-selections
[22:44] <fujin_> will show all that is installed
[22:44] <fujin_> kshah: that'd odd, what part of zlib isn't working?
[22:44] <fujin_> kgoetz: zlib is open-source compression
[23:10] <nealmcb> soren: ahh - interesting!  any idea what changed in qemu so that it works now?  did you try it with the gutsy qemu and see problems?
[23:10] <soren> No, I didn't have a qemu system handy.
[23:10] <soren> er...
[23:11] <soren> bollocks
[23:11] <soren> gutsy system.
[23:20] <kshah> fujin: now I fixed that.. kinda, now I get gem_original_require
[23:20] <kshah> : no such file to load -- zlib (LoadError)
[23:20] <kshah> I perhaps should be asking this in the RoR channel
[23:22] <kgoetz> anyone else running gutsy and updatedb not being run automatically?
[23:25] <fujin_> I don't believe it ever is run automatically?
[23:25] <fujin_> unless it's in /etc/cron.*
[23:31] <kgoetz> i've never seen a debian box where its not updated before :\
[23:31] <soren> nealmcb: I'll probably try again tomorrow.
[23:36] <DrSmall> Hello
[23:37] <DrSmall> If install a server, install X, and then pull the video card, will X still work and be able to launch apps over SSH ?
[23:40] <kgoetz> you should only need x on the client, not server
[23:42] <DrSmall> Oh, really ? I thought I would have needed it on the server too. This sounds good. Thanks :)
[23:53] <proprietarysucks> does anyone know if there is a way, using a kickstart file, to tell ubuntu either: don't try to contact security.ubuntu.com or: don't ask to continue when it's not reached?
[23:54] <keescook> proprietarysucks: don't know.  perhaps plunk a /etc/hosts file entry to redirect to a local apache server?
[23:56] <proprietarysucks> very interesting