Re: [SLUG] Re: Advice Request for moving a Ubuntu installation to a larger disk and 4Gb RAM
On Wed, 28 Oct 2009 21:04:12 +1100, "Bill Donoghoe" said: > > > Thanks everyone for the advice. > > Following the KISS principle I am going to: > 1. Live within the RAM can access now (just over 3Gb) > 2. Use a single Linux partition (besides boot) on the larger drive I find it useful putting /home on a separate partition. Then if you totally hose your o/s, you can just reinstall and keep all your existing data and app preferences (though of course you'll need to reinstall any additional apps). Sonia. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] OSDC 2009 Early Bird Ends Friday
Hello! This is your last chance to get early bird registration for the Open Source Developers Conference, 2009. Places are running out and the discount ends on the 30th, so get in quick! The Open Source Developers' Conference is a conference run by open source developers, for developers and business people. It covers numerous programming languages across a range of operating systems, and related topics such as business processes, licensing, and strategy. Talks vary from introductory pieces through to the deeply technical. OSDC 2009 will be held at the Bardon Conference Center in Brisbane, Queensland, Australia from the 25th to the 27th of November, 2009. Our programme includes a great array of good speakers, and can be viewed here: http://2009.osdc.com.au/programme Prices: Early bird $275, standard price $300. Early bird ends the 30th of October. You can register for the conference at http://2009.osdc.com.au/register If you're going to be in Brisbane on the 24th of November, you might wish to attend Upstarta Camp: a picnic in the park. A workshop follows a barbecue in the afternoon and while there's no firm cap on numbers at the moment, you'd best register early to ensure you get a place. More info and registration: http://upstarta.biz/Main/UpstartaCamp When: Tuesday 24 November (afternoon before first OSDC day), 12pm-5pm Where: Brisbane, Mt Coot-Tha / Bardon area (near OSDC venue) Cost: $10 for members, $20 for non-members For more information, please feel free to contact us on confere...@osdc.com.au -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Re: Advice Request for moving a Ubuntu installation to a larger disk and 4Gb RAM
Thanks everyone for the advice. Following the KISS principle I am going to: 1. Live within the RAM can access now (just over 3Gb) 2. Use a single Linux partition (besides boot) on the larger drive This will reduce the migration to an rsync and accessing less than an extra 1Gb RAM is not worth the potential costs. Thanks, Bill Donoghoe -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] apt-get purge aftger apt-get remove
Michael Chesterton writes:
> On 28/10/2009, at 9:35 PM, Daniel Pittman wrote:
>> pe...@chubb.wattle.id.au writes:
>>
>>> I've done apt-get remove to get rid of some packages, but I should have
>>> done
>>> apt-get remove --purge. How do I get rid of the config file droppings all
>>> over my system?
>>
>>dpkg --list | grep ^rc
>>
>> # sudo dpkg --purge $(dpkg --list | grep ^rc | awk '{print $2}')
>
> What a waste, piping grep to awk. I suppose you also eat kittens?
> sudo dpkg --purge $(dpkg --list | awk '/^rc/ {print $2}')
I hang my head in shame. I can't believe I didn't spot that myself, even if I
wrote that off the top of my head. :/
Daniel
--
✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
Looking for work? Love Perl? In Melbourne, Australia? We are hiring.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] apt-get purge aftger apt-get remove
On Wed, Oct 28, 2009 at 09:51:34PM +1100, Michael Chesterton wrote:
>On 28/10/2009, at 9:35 PM, Daniel Pittman wrote:
>>pe...@chubb.wattle.id.au writes:
>>
>>>I've done apt-get remove to get rid of some packages, but I should
>>>have done apt-get remove --purge. How do I get rid of the config
>>>file droppings all over my system?
>>
>> dpkg --list | grep ^rc
>>
>># sudo dpkg --purge $(dpkg --list | grep ^rc | awk '{print $2}')
>
>What a waste, piping grep to awk. I suppose you also eat kittens?
>
>sudo dpkg --purge $(dpkg --list | awk '/^rc/ {print $2}')
get rid of awk (too big on tiny machines):
dpkg -P $( dpkg -l | while read a; do if [[ $a =~ ^rc ]]; then a=${a// / };
a=${a#* }; echo ${a%% *}; fi; done )
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Advice Request for moving a Ubuntu installation to a larger disk and 4Gb RAM
On Wednesday 28 October 2009 18:37:16 slug-requ...@slug.org.au wrote: > jam writes: [snip] > > > >> > Based on what you have said do yourself a favour and don't do LVM. > >> > LVM is a wonderful idea but it requires that you understand > >> > statistics related to disk failure and the consequences of that. [snip] > Ah! You are making the assumption that LVM implies multiple disks! I did indeed misread the original posting as 90G AND 500G disks and all of my ramblings were based on that assumption. Apologies James -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] apt-get purge aftger apt-get remove
On 28/10/2009, at 9:35 PM, Daniel Pittman wrote:
pe...@chubb.wattle.id.au writes:
I've done apt-get remove to get rid of some packages, but I should
have done
apt-get remove --purge. How do I get rid of the config file
droppings all
over my system?
dpkg --list | grep ^rc
# sudo dpkg --purge $(dpkg --list | grep ^rc | awk '{print $2}')
What a waste, piping grep to awk. I suppose you also eat kittens?
sudo dpkg --purge $(dpkg --list | awk '/^rc/ {print $2}')
--
http://chesterton.id.au/blog/
http://barrang.com.au/linux/
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Port forwarding weirdities
Hi, > Okay, so, I have a Linksys WRT54G running OpenWrt, serving as the > Internet router for our home. You know the drill — NAT, PPPoE, whatever. > > Router's LAN IP address is 192.168.0.1. Several port forwards are in > place (y'know — SSH, HTTP, SMTP, IMAP, and whatnot) that are already > working beautifully. > > I'm also wanting to forward TCP port 1240 on the WAN side to port 80 on > my box, 192.168.0.23, for running a test web server. (Oh, if only I > could give non-technical people a link to my IPv6 address instead.) Heh.. :) > So here's the OpenWrt config I use to do this. Should look sane, even if > you've not used OpenWrt before: > > config 'redirect' > option 'src' 'wan' > option 'proto' 'tcp' > option 'src_dport' '1240' > option 'dest_ip' '192.168.0.23' > option 'dest_port' '80' > > And when you run `/etc/init.d/firewall restart`, it generates the > following iptables rule as a result: > > r...@openwrt:~# iptables -t nat -L | grep 1240 > DNAT tcp -- anywhere anywhere tcp dpt:1240 to:192.168.0.23:80 What about just dumping NAT table i.e., without the grep magic foo? NAT'ing 1240<->80 is fine but then as Dr. Peter Chubb mentions, 80<->(could_be_any_arbritrary_port_here) which you are obviously not listing it here. Right? > Which all worked fine for a week or two. But then for some mysterious > reason, when I try and access port 1240 from the WAN side, it started to > send traffic to port 95 on my LAN side! (Despite iptables still > reporting port 80.) > > I rebooted the router (to no avail), reset the firewall configs, ran > tcpdump, wireshark, and whatnot, and the mangling of the port is > definitely something that was happening on the router. (tcpdump showed > me packets exiting the LAN side bound for port 95; no pun intended.) > > So as a quick workaround, I made Apache on my box listen on port 95 as > well as port 80, which 'fixed' it. No biggie. > > Except now it's trying to access port 82 on my box when I hit 1240 on > the WAN site. I have not changed any configuration on the router, and if > I type `uptime` I can tell it hasn't even rebooted since it was last > going to port 95. > > This is so totally weird, and driving me absolutely insane. All other > port forwards work perfectly. Oh, somebody shut down the IPv4 Internet > already! One of my mate said he had the same issue (he fixed it but I don't know how he did it, I told him to type a little bit more using his fingers and choose lesser automagic foo configs in his wrt :-) I think it could be a bug in OpenWRT. What specific revision is it? Also, there's a ticket for it if you want to read https://dev.openwrt.org/ticket/2558 and it _seems_ that its related to nat specifically. Also, try newer revision as reported by one users success if you haven't (I do not have my wrtgl with me atm) :-) [...] -- Regards, Ishwor Gurung -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] apt-get purge aftger apt-get remove
pe...@chubb.wattle.id.au writes:
> I've done apt-get remove to get rid of some packages, but I should have done
> apt-get remove --purge. How do I get rid of the config file droppings all
> over my system?
dpkg --list | grep ^rc
# sudo dpkg --purge $(dpkg --list | grep ^rc | awk '{print $2}')
Regards,
daniel
--
✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
Looking for work? Love Perl? In Melbourne, Australia? We are hiring.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] apt-get purge aftger apt-get remove
Hi, I've done apt-get remove to get rid of some packages, but I should have done apt-get remove --purge. How do I get rid of the config file droppings all over my system? (I know I can do: apt-get install pkg; apt-get remove --purge pkg but if the number and locations of config files have changed, this isn't guaranteed to clean everything out) Peter C -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Port forwarding weirdities
I've only ever port forwarded port 80 from external to port 80 on an internal web server. A client picks a high port and sends this request to port 80 on the web server. The web server responds out from port 80 to the high port on the client. So from a router it would port forward any external request into port 80 to an internal host listening on port 80. Otherwise you'd have to port forward every high port to your web server. I have several hosts/domains, all listening on port 80 receiving port forwards from the router which is only port forwarding port 80 to internal. This is all working fine. Unless I'm missing something in your config... Ben Jeremy Visser wrote: G'day SLUG, Okay, so, I have a Linksys WRT54G running OpenWrt, serving as the Internet router for our home. You know the drill — NAT, PPPoE, whatever. Router's LAN IP address is 192.168.0.1. Several port forwards are in place (y'know — SSH, HTTP, SMTP, IMAP, and whatnot) that are already working beautifully. I'm also wanting to forward TCP port 1240 on the WAN side to port 80 on my box, 192.168.0.23, for running a test web server. (Oh, if only I could give non-technical people a link to my IPv6 address instead.) So here's the OpenWrt config I use to do this. Should look sane, even if you've not used OpenWrt before: config 'redirect' option 'src' 'wan' option 'proto' 'tcp' option 'src_dport' '1240' option 'dest_ip' '192.168.0.23' option 'dest_port' '80' And when you run `/etc/init.d/firewall restart`, it generates the following iptables rule as a result: r...@openwrt:~# iptables -t nat -L | grep 1240 DNAT tcp -- anywhere anywhere tcp dpt:1240 to:192.168.0.23:80 Which all worked fine for a week or two. But then for some mysterious reason, when I try and access port 1240 from the WAN side, it started to send traffic to port 95 on my LAN side! (Despite iptables still reporting port 80.) I rebooted the router (to no avail), reset the firewall configs, ran tcpdump, wireshark, and whatnot, and the mangling of the port is definitely something that was happening on the router. (tcpdump showed me packets exiting the LAN side bound for port 95; no pun intended.) So as a quick workaround, I made Apache on my box listen on port 95 as well as port 80, which 'fixed' it. No biggie. Except now it's trying to access port 82 on my box when I hit 1240 on the WAN site. I have not changed any configuration on the router, and if I type `uptime` I can tell it hasn't even rebooted since it was last going to port 95. This is so totally weird, and driving me absolutely insane. All other port forwards work perfectly. Oh, somebody shut down the IPv4 Internet already! Signed, Thief of the last 60 seconds of your time. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Port forwarding weirdities
> "Jeremy" == Jeremy Visser writes: Jeremy> Okay, so, I have a Linksys WRT54G running OpenWrt, serving as Jeremy> the Internet router for our home. You know the drill — NAT, Jeremy> PPPoE, whatever. Yup, same as I have Jeremy> Router's LAN IP address is 192.168.0.1. Several port forwards Jeremy> are in place (y'know — SSH, HTTP, SMTP, IMAP, and whatnot) Jeremy> that are already working beautifully. Jeremy> I'm also wanting to forward TCP port 1240 on the WAN side to Jeremy> port 80 on my box, 192.168.0.23, for running a test web Jeremy> server. (Oh, if only I could give non-technical people a link Jeremy> to my IPv6 address instead.) Jeremy> So here's the OpenWrt config I use to do this. Should look Jeremy> sane, even if you've not used OpenWrt before: Jeremy> config 'redirect' option 'src' 'wan' option 'proto' 'tcp' Jeremy> option 'src_dport' '1240' option 'dest_ip' '192.168.0.23' Jeremy> option 'dest_port' '80' This looks good. Jeremy> And when you run `/etc/init.d/firewall restart`, it generates Jeremy> the following iptables rule as a result: Jeremy> r...@openwrt:~# iptables -t nat -L | grep 1240 DNAT tcp -- Jeremy> anywhere anywhere tcp dpt:1240 to:192.168.0.23:80 Jeremy> Which all worked fine for a week or two. But then for some Jeremy> mysterious reason, when I try and access port 1240 from the Jeremy> WAN side, it started to send traffic to port 95 on my LAN Jeremy> side! (Despite iptables still reporting port 80.) See if there's another iptables rule redirecting output port 80 to somewhere else. I'm using white russian in almost exactly this config, and it's all working for me. Peter C -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
