You are not logged in.
Sorry, still no Waldorf, yet.
Anyhow, I have been playing around with updating the Statler images, again. As you might be aware, the 3+ kernel is now available via backports and I updated the #! Mozilla mirror this morning so Iceweasel is now at version 10. Now seems like as good a time as any to update the builds.
The only changes I plan to make are:
Revert to GDM -- whilst SLiM has been working well for me, I understand that it has caused a fair amount of trouble for others. The sensible option is to switch back. The SLiM packages will remain in the repository and are pretty easy to install, if required.
Basic window tiling shortcuts added to Openbox's rc.xml.
'firmware-realtek' package installed by default.
Also, I am thinking about creating backported and non-backported images. The backported images will have backports turned on by default (as with the current image) and the non-backported images will stick to the main Squeeze repos, with the exception of Iceweasel and Geany, which will track the backports repositories.
By doing ^, I am hoping that some people will not feel the need to use the old 20110207 images.
Does anyone have any opinions/suggestions about this?
Offline
Sweet compromise. If you feel like doing the work, by all means. We did form action plans on how to help people recover from Slim eating the data and pets though 
Offline
I am all about the compromise, sometimes 
Offline
Sounds not bad.
Offline
Can only say ty again Corenominal ...
Was skeptical that even you'd be able to beat yourself and improve upon the linuxy goodness of the last #! release. And yet somehow ya did it. You're definitely the man imo when it comes to the 400+ distro's of the world. Can't imagine coming across any that would beat out #!. New iso installed here and o course running like a champ.
Was glad to see you nipped a bunch of things in the bud in the newer #! release. Updated web browser out of da box and think the new gray default theme you went with is super easy on the eyes, more so than the harsher b & white was. Thought it was hecka kewl too though, either way. Long drawn out ... Thank You , Corenominal.
Oops, more babble, opinions/suggestions ... Nah ... would feel like a hypocrite, like telling da Vinci how to paint or Mozart how to play da friggin piano.
Do have one serious concern and gripe with #! though. Made me into a gd fanboi !!! Arghhhh ... the shame, the indignity. Sighs ... but on the other hand there's the crunchy bangy goodness. Oh well, guess will have to learn to live with being a fanboi. 
Last edited by CBizgreat! (2012-02-03 09:58:45)
Some common cbiz abbreviations. This will save me time and yet @ same time tell folks what the babble is supposed to mean.
Vll ! = ( Viva la gnu/Linux !) Vl#!! = ( Viva la #! !) Last but not least, UD ... OD ! = ( Use Debian ... or die !) 
Offline
@corenominal: good job on this. seems to me you made some sensible decisions.
Offline
Hey corenominal, loving your distro, using #! sid, have it now as my only distro on my computer. Having the realtek firmware by default I think would help a LOT of people, those pesky chipsets are everywhere unfortunately. Ive been using lightdm for a while, no problems that I can speak of, things seem to be running smooth with low ram usage. Any reason for the switch back to GDM as opposed to lightdm? I can understand ditching slim though, good choice IMO.
Intel Pentium4-2.40GHZ RAM-1008.3MiB CrunchBang Sid Linux-3.2-6.slh.3-aptosid-686
Offline
Any reason for the switch back to GDM as opposed to lightdm? I can understand ditching slim though, good choice IMO.
LightDM is definitely something to look at for the Waldorf/Wheezy releases, but backporting it to Statler/Squeeze is not something I would like to do.
Offline
What are the keybindings to the tiling? I don't wanna install again and don't really mind sticking to Slim. 
Last edited by duderocks (2012-02-03 11:29:07)
Offline
@duderocks:
<keybind key="W-Right">
<action name="GrowToEdgeEast"/>
</keybind>
<keybind key="W-Left">
<action name="GrowToEdgeWest"/>
</keybind>
<keybind key="W-Down">
<action name="GrowToEdgeSouth"/>
</keybind>
<keybind key="W-Up">
<action name="GrowToEdgeNorth"/>
</keybind>^ nothing too special, but I find them handy 
Offline
Thanks Corenominal!
The tiling keybindings ARE useful.
Offline
From the backports mailing list: http://lists.debian.org/debian-backport … 00011.html
«
Backports are software from Debian's testing and unstable distributions, recompiled and repackaged for the current stable distribution so that they will run without new libraries whenever possible, and without upgrading to testing or unstable.
Backports cannot be tested as extensively as Debian stable, and backports are provided on an as-is basis, with risk of incompatibilities with other components in Debian stable. Use with care!
It is therefore recommended to select single backported packages that fit your needs, and not use all available backports.
»
bootinfoscript - emacs primer - I ♥ #!
Online
good news, sir. will download and try!
edit: ...as as soon as it's there. 
thanks for doing a great job on crunchbang.
Last edited by saneks (2012-02-03 13:15:42)
eee701 user & other lap/desktops
Offline
Thanks for answering my question corenominal, actually its been so long since Ive used Stable that I forgot that it wasnt in the stable repos. Shame slim isnt being developed anymore, was definitely a lightweight DM.
Intel Pentium4-2.40GHZ RAM-1008.3MiB CrunchBang Sid Linux-3.2-6.slh.3-aptosid-686
Offline
I am currently on Statler R20110207 with backports enabled. Booted up with the 3.2 kernel (3.2.0-0.bpo.1-amd64). With the switch back to GDM in the new image, what would the advantage be (if any) of doing a fresh install?
@corenominal: All my thanks for your continued work and making the best linux distro I could have ever hoped for. #! has been a dream come true. Keep it up!
Offline
I have yet to try the new image. Is there a real-time kernel for the 3+ ?
I can confirm that a RT flavor of the amd64 version of 3.2 is available in backports.
while ( ! ( succeed = try() ) );
We've earned a reputation as a nice, friendly community; please help us keep it that way.
Offline
Sounds like a plan, I approve! 
/hugged
Offline
If it's a dual-core, then it's dual-core - use the amd64 kernel. If it's a single-core (even if it's a hyper-threaded single-core that looks like a dual-core to everything else) you need the x86 kernel, and so far I haven't seen a RT version there. (I usually just `aptitude search linux-image` and scan for "-rt-" in the package name.)
while ( ! ( succeed = try() ) );
We've earned a reputation as a nice, friendly community; please help us keep it that way.
Offline
^currently using - linux-image-2.6-liquorix-686
"This package depends on the latest binary image for Linux kernel on PCs
with Intel Pentium Pro/II/III/4/4M/D/M, Xeon, Celeron, Core or Atom; AMD
K6, Geode LX/NX, Athlon (K7), Duron, Opteron, Sempron, Turion or Phenom;
Transmeta Efficeon; VIA C3 "Nehemiah" or C7 processors machines for
liquorix."
Offline
You still wouldn't find a RT 686 kernel...doesn't look like there's even source code for one in backports. 
EDIT: I just found this:
The Debian team has announced that Debian 7.0 'wheezy' will include the Linux kernel 3.2.
According to Ben this is currently in unstable and will soon enter testing. The kernel team is open to backporting some features from later kernel versions, particularly to support newer hardware.
So what new feature to expect from it? The only featureset provided will be 'rt' (realtime), currently built for amd64 only. The team may add realtime support for other architectures if there is interest.
(Well, I pretty much quoted the whole text of the page.
)
Last edited by pvsage (2012-02-03 17:52:34)
while ( ! ( succeed = try() ) );
We've earned a reputation as a nice, friendly community; please help us keep it that way.
Offline
From the backports mailing list: http://lists.debian.org/debian-backport … 00011.html
«
Backports are software from Debian's testing and unstable distributions, recompiled and repackaged for the current stable distribution so that they will run without new libraries whenever possible, and without upgrading to testing or unstable.
Backports cannot be tested as extensively as Debian stable, and backports are provided on an as-is basis, with risk of incompatibilities with other components in Debian stable. Use with care!
It is therefore recommended to select single backported packages that fit your needs, and not use all available backports.
»
From Philip's brain:
I am well aware of the advice that is given and I am more than happy to ignore it. Having thunk that, I am also aware that some people are not as happy to ignore the advice, so I think I should compromise and create a release that tracks backported packages and another release that does not.
Am I hungry? I think I am. Hmm, what is for dinner?

Offline
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.