@axxer
Just did an update/upgrade an hour ago. Speed is fine for me.

@Acid
Wah!! ... It's actually a simple question, but the answer can be very, very longwinded >_<... Basically, upstart was created to replace init, but it hasn't been set in stone. One benefit of upstart is that it takes load off the kernel while booting, and allows for greater levels of concurrency and event-based loading of services. The old init's benefit is stability and compatibility over various architectures (one reason why Debian doesn't use it, since they make iso for a lot of different platforms).

Just google init vs upstart and you'll get a LOT of explanations.

Both kinda suck in my opinion, but if you asked me to choose one, I'd probably stick with sysv/init for now. There are better alternatives out there, like initng, which I'm currently running on my ArchLinux partition. It's pretty good, and boot up is quite fast, it's not as modular/tweakable (no scripts available for XFS right now)

There's also the much discussed systemd, which should make it's way to most distros soon. Not sure about Ubuntu, since they have their own plans for Upstart, Btrfs and ureadahead, but Debian should be including it in their Unstable/Sid sources soon, probably after Squeeze gets officially released and 2.6.37 has benn out in the wild for a bit longer, or maybe at 2.6.38. The systemd package is currentlu available in Experimantal, and I'm using it right now, and indeed it does improve boot and shut down times, but you need to know some kernel-foo if you want to get it working.
You can read up here: http://wiki.debian.org/systemd
Warning: Use only if you know what you're doing, and it's advisable you compile your own kernel for this. It can break your install if you're not careful.


Cheers

---

Added on February 3, 2011, 10:17 pmPossibly a mounting issue. What filesystem are you using (Ext3, Ext4, XFS, Btrfs..etc?)
I remember a post in the Liquorix or Debian forums about tweaking your etc/fstab for specific use with newer Liquorix kernels.... try searching... it might be a simple noatime fix that's needed.

This post has been edited by G-17: Feb 3 2011, 10:22 PM

./~Acidus
Great choice of distro, Crunchbang!! Which version of Statler are you using, OpenBox or Xfce? I'm a huge fan, and it's one of the better out-of-the-box distros. Standalone Openbox > Lxde, and #!'s implementation of Openbox is one of the best around (a lot of distros that use OB copy #!'s style). The Xfce version is pretty stonking as well, very light. Good choice.

./~Flamey
10.04 is what name already? Loco Lucy or Masturbating Margaret? Anyways, the Kubuntu Backports seems to have versions for both, though I can't verify since I'm not on *buntu. https://launchpad.net/~kubuntu-ppa/+archive/backports

This post has been edited by G-17: Feb 5 2011, 02:23 PM

Did you try "apt-get --no-install-recommends install gnome-system-tools" ?

---

Added on February 6, 2011, 9:58 pmStable Debian releases have never been a big thing for me, thanks to Debian's "It's stable only once it's outdated" policy.
What I'm really looking forward to is the unfreezing of Sid main and testing sources. Let the breakage happen!!


This post has been edited by G-17: Feb 6 2011, 09:58 PM

@Acid
Oh wow!! In all my years on Debian, I've never once dared to do that. Experimental is like a Nuclear EMP waiting to happen and you should be very selective with individual package/lib/dependency upgrades. Good luck, man

Oh, any Sid/Unstable users here? Just a note, there's a very risky Xorg update that came out recently, and I recommend you don't do a dist-upgrade for at least teh next 2 weeks, as there's bound to be breakage.

Also, for Unstable 32bit users, there's discussion over at the dev channels about a very dodgy ffmpeg upgrade coming soon ... you've been warned.

Lastly, anyone on Unstable is urged to dist-upgrade outside X from now onwards (unless it's just non admin/system related packages like Gimp, Rhythmbox...etc)

Can't be helped, since everything just got unfrozen and everyone's struggling trying to allocate dev manpower between Squeeze (for server client support) and Testing/Unstable/Upstream.

This post has been edited by G-17: Feb 7 2011, 11:34 PM

^I have very limited experience with Jboss (I despise it, tbh) but I know it works fine on Ubuntu and other Linux distros. I think the Ubuntu repositories should contain the Jboss Application Server 4 package. Your best resource is undoubtedly the community.jboss.org forums

I have even less experience with regards to cross-platform comparisons (especially the Windows side, since I haven't used Windows since 1998/99), so I can't really give you any findings on load comparisons. Sorry.

I'm not quite sure I understand you, but I'm assuming you're trying to remotely connect to your server (which is another location) via pppoe?

Something like this, perhaps?
http://imranasghar.blogspot.com/2009/05/pp...untudebian.html

If not, could you clarify which section your predicament is related to?
http://wiki.debian.org/Network

Apologies, as I'm the last person you should ask when it comes to networking. I'd assume you got all the usual tips from the Networking/P2P section of these forums and this is a Ubuntu/Debian/Linux specific issue you're facing here?

---

Added on February 8, 2011, 7:14 pmI can confirm that there are (a lot of) people experiencing xorg related breakage on Unstable, but Testing seems to be fine. I haven't had any issues dist-upgrading my Testing-based setups other than some wireless driver issues.

This post has been edited by G-17: Feb 8 2011, 07:15 PM

@scorps
If you really need a working Nvidia + Xorg setup, you can try this, but I don't recommended (since most of the time I get the impression you don't know what you're doing).

After some testing, this helped recover one of my broken Sid boxes,

Add Experimental sources to your sources.list (usually etc/apt/sources.list, but may be different depending on your distro)

Then exit your desktop (Ctrl+Alt+F1) and go to root (su) and then



and then;


then;


and then exit;


If everything works, remember to remove the experimental sources from your rources.list

Important: Like I said, I do not recommend this method for most people, and so far only those with affected Sid/Unstable/Aptosid/Grml have applied this, and I can't vouch for a Testing-based setup. Remember, Experimental is like an angry Egyptian mob.... things can get very dangerous in the blink of an eye.

If your computer explodes, it's not my problem.

If you're afraid, install Ubuntu .... or Windows.

This post has been edited by G-17: Feb 8 2011, 09:40 PM

Sorry to hear about your Aspire. On a slightly comforting note, it died on the same day a former great company died as well... Nokia. Well, they're not really dead, but becoming a Microsoft lapdog because they had nowhere else to turn to = R.I.P anyways.

About your netbook and Win7;
I've always wondered which moron at MS decided it was a good idea to have Win7 on Atom netbooks. Even XP, once you'll installed a firewall, antivirus and other monitoring/maintanence apps tools runs a but slow (and gets slower as time passes) on an Atom, so I can't even imagine how much it would struggle with Win7. O_o



Actually, on reletively recent hardware (anything from the last 5 - 6 yrs), There's not much difference, speed-wise between XFCE and LXDE (vanilla Xfce, not Xubuntu's metapackage). Even their memory footprint is around the same (maybe Lxde just edges it) Personally, I never really got the whole LXDE craze, especially when standalone Openbox is faster/lighter/modular.

It'd be great if you started a thread telling us about all the networking adventures you've had with Linux.
You call me a "guru", but seriously, there's very little I know (I don't work in the IT/computing industry aside from some small GPL/BSD/FOSS projects), and I'm probably a noob compared to most people on the networking side of things. I'd be very thrilled if you found time to share your experiences with us, as I presume there's a lot I could learn from you.



I wasn't trying to discourage you or anything like that. It was just an observation on my part (on my hardware). Use whatever you're comfortable with, man. More power to you.

This post has been edited by G-17: Feb 12 2011, 09:24 PM

@Chyan
What do you use to see your battery status? Gnome Power Manager, conky, htop, acpi?

@Chyan
Sorry for the late reply. I was out for the last 2 nights.
Your battery might have a defective sensor somewhere.

First remove your battery and clean the contacts. Then put it back in and boot into your OS. After about 10 minutes, unplug the power cord to make it run on battery power, and in terminal do ;





...and paste the output here.

This might also be a kernel or BIOS issue. I can't help with teh BIOS, since it's different for each system (and I don't want to be responsible for screwing up your BIOS), but do you have a LTS kernel (2.6.32.xx). If yes, boot with it and see if your battery info is available of not.

This post has been edited by G-17: Feb 15 2011, 11:14 PM

@Acid
Do "free -m" in terminal.
System monitor might be showing used + cached memory. Looking at the output from "free -m" and doing some math should be able to tell you what's showing. Conky has an option to show cached and buffered memory as well, but I forgot the variable/syntax. >_<

@farkinid
Hmph!! ... I only watch real pron... no big-eyed cartoons.
I like your avatar, btw. I just saw Cat_Shit_One for the first time a few days ago. It was awesome.
Packy!!! ...... Botasky!!!!

There's no M'sian Debian mirror, as far as I know.
I think some uni had one a few years ago, but it sorta disappeared.
Anyways, Debian prides itself on being pure and clean, and Malaysia is probably too corrupt for it. Libya will probably get and official Debian mirror before Malaysia.


What problems?
Scorps? ... He ALWAYS has problems..... it's neverending

@scorps
DHCP won't cause this directly, but dhclient might.

Try this;

(1) Edit your resolv.conf and put your desired settings/variables

(2a) Edit /etc/dhclient.conf and add the following line;


if that doesn't work, then remove step-2a and do 2b (below) instead.

(2b) Create a file called /etc/dhclient-enter-hooks (as root, obviously) and put this inside ;


If those don't work, check your startup services. install rcconf and run it (as root). You can see a list of daemons/services you can disable.

This post has been edited by G-17: Feb 24 2011, 07:03 PM

That's bullshit!! If you read the article properly, you'd realize that it was a play with words, meant to reinforce Debian's importance.

Seriously, Debian is not perfect, but if there ever was this hypothetical scenario where all Linux distros performed some sort of deathmatch, I'm pretty sure Debian, RedHat and Gentoo would be the last 3 men standing. The amount Debian contributes, the belligerent focus on stability and it's ability to run on so many architectures pretty much make Debian unique, and in some ways, peerless.

What most desktop users use is only a small bit of what Debian offers. Ubuntu devs are also Debian devs, some of them only part-time for Ubuntu and concentrate most of their efforts on Debian (remember, I'm talking about the actual devs from mailing lists and dev channels, not people you get empty rumors from on IRC or forums). Whether Ubuntu decides to go-solo in future is entirely up to them, but building a base as solid as Debian's will take a lot of time, and is probably an investment Ubuntu can't afford, despite the wealth of their founder.

Debian, Free-BSD, Open-BSD and Gentoo are the only distributions that have stayed on any of my boxes for extended periods throughout all these years. QNX is another one, but that's not open source. Others have come and gone.

Sure, nothing lasts forever, and Debian will probably die one day, but it'll probably get forked and return as something better.

---

Added on February 27, 2011, 2:52 pmDunno about Network Manager (it's crap, imo, so I don't use it unless I need to connect to those USB-3G dongles)
So, is your problem solved or not? You're always like this. People take time to write possible solutions for you, but you don't reply with feedback and go off-tangent with a new question instead.

This post has been edited by G-17: Feb 27 2011, 03:06 PM

@Chyan
It's been so long, I forgot what your initial question was
Battery monitor problem, right? I don't seen anything wrong with your output. I'll check some more and update you with suggestions if I can.
Did you manage to get a 2.6.32 LTS kernel yet, per chance?


Ah, so the dns problem is solved, then.
Your new problem is Network Manager related.
Well, you could try inserting the 'ifup eth1' in a start file, autostart.sh or create a script for it. What is your eth1, anyway? wired or wireless? I assume it's wireless since you wouldn't really need Network Manager for wired connections.

Regarding the network manager problem.... if you're not using a USB 3G type, get rid of it and install wicd.

90% of users find their connection problems go away once they replace network manager.

This post has been edited by G-17: Feb 28 2011, 02:21 AM

Well, I did see "remaining capacity: unknown" which is a bit of a concern. Did you take that when it was on battery power like I suggested, or was the notebook plugged into the wall power?

I suggested the older LTS kernel because newer kernels sometimes contain modules that aren't compatible with older hardware. Either way, I can't say unless I inspect your kernel modules, but I suspect that isn't the issue here.

He'll probably be doing another fresh install before his dns changes.
It doesn't help that I sometimes find it sort of difficult to comprehend what his problem is from the way he phrases them.

^ I mean, sometimes I don't completely understand what your problem is.
Not your fault. It's just my understanding of certain terms is probably different from yours.

Download 1080p Packy & Bota, obviously.

...and Hentai Pron, of course. Join the club!! =P

@Acid
Sorry for not noticing earlier. Is the hash sum problem still there?
Sometimes it's package related and might be fixed the next day. Sometimes you'll need to redownload the keyring if it's from an third-party repo/PPA. Sometimes it's related to your apt config.