IRC Logs

Network: freenode Channel: #debian

	Enter your search terms Submit search form
	Web www.irclog.org

[13:59]<wnyssy>yang: or in the net somewhere google for "card name" linux
[13:59]<jlggsjzgs>well.. it was the debian kernel but it's been recompiled since then
[13:59]<fyr2fn>from debian sources?
[14:00]<fyr2fn>or vanilla?
[14:00]<syddnee>liable: I know that. I'm using subversion and therefore libsvn0 from backports, but i can't get trac working as they've been built differently
[14:00]<jlggsjzgs>well, the drivers i needed for my wireless network card needed to recompile my kernel
[14:00]<jlggsjzgs>also, i've installed alsa from source
[14:00]<syddnee>libsvn0 on backports doesn't seem to have /usr/lib/libsvn_swig_py-1.so.0
[14:00]<jlggsjzgs>that needed some tinckering with my kernel iirc
[14:00]<cxzysw>hmmm, I did a "shutdown -P now" and it looks like the USB-attached external hard drive may have wiped itself clean in the process... is that to be expected?
[14:01]<cxzysw>it's ext3 formatted, and I use it for backups... I didn't need the backups this time, but obviously, I'm a little disturbed...
[14:02]<ggnr>ChrisW: i've had nothing but problems with usb-attached hard drives. there's some sort of method to unmount and desync before unloading the modules.
[14:02]<fyr2fn>ChrisW: no, that is not to be expected..
[14:03]<jjdfm>hi
[14:03]<cxzysw>liable: well, that's what I thought :-/
[14:03]<jjdfm>does anybody know what the floppy boot disks do to get the inet connection from another pc
[14:03]<jjdfm>(because it worked realy great)
[14:03]<cxzysw>Gnea: any idea what that method is and how I can hook it in to ensure it happens on machine shutdown?
[14:03]<ggnr>problem is, i think, that modules stay loaded, and some devices don't get a chance to settle before unmounting
[14:03]<ggnr>ChrisW: no, i never got a chance to look too deeply into it
[14:03]<cxzysw>:-(
[14:04]<cxzysw>I haven't had problems when I do "umount /mnt/backup" before unplugging it
[14:04]<ggnr>i've pretty much sworn off usb hd's until i get the chance to muck with them again, which i hope to be never
[14:04]<cxzysw>*shrugs*
[14:04]<ggnr>right, that's commandline tho
[14:04]<jjdfm>or does anybody know some general things about ip forwarding/ internet connection sharing ?
[14:05]<cxzysw>any other ideas how to backup 180GB of data in a way that I can grab & run if ther's a fire/flood/etc?
[14:05]<ggnr>if it's still mounted and attached when doing a shutdown/reboot, the error occurs there because the system has its own path to do things
[14:05]<cxzysw>okay, but why on earth should that blank the disk?
[14:05]<cxzysw>I mean, I thought ext3 was supposed to be resilient?!
[14:05]<sxzmuz>ChrisW: The word you're looking for is off-site.
[14:05]<ggnr>ChrisW: that's the big question
[14:06]<hjvwyzn>JoyFM: there special distros designed for acting as gateways routers + firewalls
[14:06]<cxzysw>Shadur: yeah, I also rotate these disks so I have one offsite, one onsite
[14:06]<ggnr>ChrisW: offsite backups are pretty efficient, particularly with rsync+ssh
[14:06]<cxzysw>JoyFM: shorewall worked really well for me :-)
[14:07]<jjdfm>Hotwire, yes but my pc works as a gateway (because of ipmasq -> out of the box)
[14:07]<cxzysw>Gnea: well, yeah, I actually suck all my server data down to the disk for expressly that purpose
[14:07]<jjdfm>but the problem is how do configure the client?
[14:07]<wjfs>JoyFM: IP masquerading howto, lartc.org perhaps. They all simply call iptables with the proper parameters
[14:07]<wjfs>JoyFM: static IPs or DHCP?
[14:07]<jjdfm>static
[14:07]<jjdfm>ip is still working
[14:08]<wjfs>so what isn't working?
[14:08]<ggnr>ChrisW: therein lies the weak link in your backup system
[14:08]<jjdfm>wols, internet on the client
[14:08]<cxzysw>Gnea: what? debian doing a shocking job of managign USB-attached storage devices?
[14:08]<eeww>Hi! Is there any official/ unofficial netinst (or full) iso image for debian testing for amd64?
[14:08]<wjfs>set the default gateway to the router's IP. and set the DNS entry correctly
[14:08]<cxzysw>that's not exactly something I'd expect :-(
[14:08]<hjvwyzn>JoyFM: have you set its IP to the internal ip of your network
[14:08]<ggnr>ChrisW: no, the fact that you're copying the files to the usb drive, then rsyncing the files from the usb drive to an offsite location
[14:08]<eeww>If yes, where from can i download it? This apt-get dist-upgrade doesn' t work (for me) correctly.
[14:09]<cxzysw>Gnea: well, that's no actually what I said I did ;-)
[14:09]<vurrsvgr>http://www.scschools.org/jobs/jobs.htm
[14:09]<cxzysw>I backup my remote servers to this local server with the usb-attached disk
[14:09]<ggnr>ChrisW: that's how i interpretted it ;)
[14:10]<jjdfm><Hotwire> JoyFM: have you set its IP to the internal ip of your network <- ?!?
[14:10]<ggnr>backups get pretty hairy when it goes over several gig
[14:10]<wjfs>JoyFM: what is the internal IP of your router?
[14:10]<jjdfm>192.168.0.1
[14:10]<cxzysw>no shit ;-)
[14:10]<ggnr>ChrisW: at that point you might as well have a SAN and some sort of tape backup system
[14:10]<wjfs>JoyFM: so set the client to IP 192.168.0.2 and set its default gateway to 192.168.0.1
[14:11]<cxzysw>I guess the safest thing is just to put a mount in at the start of my backup run and an unmount in at the end?
[14:11]<sxzmuz>tungsten: I note that none of those job offers are even remotely debian-related. Heck, most of them won't even see a computer except to email. So why did you spam that URL here?
[14:11]<ggnr>ChrisW: yes.
[14:11]<sufgzfyguw>Gnea, hello
[14:11]<jjdfm>wols, that is what i've done
[14:11]<ggnr>ChrisW: have the script perform some sanity checks too :)
[14:11]<cxzysw>and yeah, SAN's are cute, but I cant' afford one ;-)
[14:11]<wjfs>JoyFM: and what is the DNS set to?
[14:11]<ggnr>superlinux: good morning
[14:11]<jjdfm>i think 192.168.0.1 too
[14:11]<sufgzfyguw>I found a thing in the samba pkag
[14:12]<cxzysw>CERN's what pretty cool: 5 or 6 Petabyte disk, with much more tape...
[14:12]<ggnr>huh?
[14:12]<wjfs>JoyFM: does your router run a caching DNS proxy?
[14:12]<wjfs>if not: apt-get install dnsmasq
[14:12]<jjdfm>wols, no
[14:12]<syddnee>how stable is testing at the moment?
[14:13]<ggnr>simmerz: it's not
[14:13]<wjfs>and never will be
[14:13]<ggnr>until it becomes the new stable
[14:13]<syddnee>Gnea: it gets more and more stable as time goes on though.
[14:13]<wjfs>testing will always be testing :P
[14:13]<sufgzfyguw>the backend as tdbsam default is /var/lib/samba/passdb.tdb and it's now writable
[14:13]<cxzysw>Gnea: CERN's SAN...rather large :-)
[14:13]<sufgzfyguw>it must be writable
[14:13]<ggnr>simmerz: but it won't be truely stable until it has passed through the frozen stage and emerged as an official stable release.
[14:13]<jjdfm>wols, dnsmasq is already installed
[14:14]<wjfs>JoyFM: can you ping 72.14.207.99 from the client?
[14:15]<zjwd_>My workstation is using testing. Our production server is using stable. I want to install postgres from stable on my workstation to have the same version that we'll use on the server. What is the best way to do it ?
[14:16]<jjdfm>wols, network is unreachable
[14:16]<wjfs>JoyFM: what client OS do you run?
[14:16]<jjdfm>ubuntu hoary
[14:17]<wjfs>then paste the output of ifconfig somewhere
[14:17]<fugyvyc>JoyFM: you're running hoary? /j #ubuntu
[14:17]<wjfs>lunitik: for a client to a debian box doing router duties
[14:18]<fugyvyc>wols: oh

Back to #debian
Or go to some related logs:
#gentoo
#php
#gentoo
#css
#suse