Waldorf (Debian Wheezy) is the current !# Stable, whereas the upcoming Janice (Debian Jessie) is the current !# Testing and the future !# Stable. As I think most people are probably aware, systemd is to be the initialization process of !# Janice.
As I myself don't really prefer using systemd, any thoughts of
1. How long the current !# Waldorf will be kept around?
(Sure, I can just make sure that my /etc/apt/sources.list file keeps all of its appropriate Debian "wheezy" entries instead of Debian "stable")
2. Whether it even makes any difference how long !# Waldorf and Debian Wheezy will be around if my !# machines are running perfectly smoothly on them as they are and I perform my regular repository apt-get updates and upgrades??
Note: I already realize all too well that Janice/Jessie is implementing systemd to replace Waldorf's/Wheezy's current SysV initialization
TYIA for any +/- thoughts.
The decision has been made --- Debian 8.0 will use systemd (yay!); CrunchBang 12 will use systemd unless someone wants to fork it...
Even though Debian 8.0 (i.e., CrunchBang 12 Janice) looks more and more as though it will be using systemd , there are apparently several systemd workarounds, see https://lists.debian.org/debian-user/20 … 00396.html.
Workaround #3 here would call for maintaining CrunchBang 11 Waldorf (Debian 7.x Wheezy), so that users can stay with the tried-and-true sysvinit just as long as they are able to.
"Workarounds" 4a thru 4e+ of course all call for completely replacing Debian GNU/Linux and CrunchBang with various alternatives.
If anyone has followed the whole initsystem debate, Jessie (and presumably !#'s Janice) is already adopting systemd.
One real question now (which I hope to find out someday) is whether corenominal will ever provide any easy backward compatibility for the current sysvinit once Janice gets released. It's already the end of the 3rd quarter of the calendar year, and Canonical will of course be coming out with Ubuntu v14.11 in less than three mos. Any takers on this one?
Just wondering where the mirror locations are for downloading the latest !# testing .iso images via HTTP and/or FTP ? Or maybe it's best to download the latest debian-testing-i386-netinst.iso at http://cdimage.debian.org/cdimage/daily … 86/iso-cd/, install this, and then just specify the janice-specific !# changes in /etc/apt/sources.list ??
Got a new (for moi) EeePC 901 and already did a test install of the latest Waldorf via last month's Waldorf update post.
This netbook has a 1.6GHz CPU, 2 GB RAM, a 4 GB internal ssd-hd, a 16 GB internal ssd-hd, and a 4 GB sd card in the side slot.
To be used for some webdev, lite-apps dev, constant apt-get update'ing , and a few standard apps (LO, Iceweasel, Chrome, GIMP, VLC, ...etc).
Wondering how I could best optimize the current installation or re-install with even better optimizations?
Already went through the extensive Tips, Tricks, & Scripts posting CrunchBang on the eee pc.
These seem "somewhat" helpful as far as
Not using a swap partition.
Tweaking Firefox preferences, for example set cache to 0mb.
Going into System->Services/Daemons and uncheck unneeded things like computer activity logger
Wondering how helpful zram would be as far as the CB posting Zram: A good idea? ??
Currently on tap are
using the Basic recommendation for partitioning from the Linux Partitioning mini-FAQ
Am using crunchbang-10-20120207-i386 installed to hard drive on an HP/Compaq PC TC 1000 with a internal [drm] nouveau graphics appearing on bootstartup (also appears via 'dmesg').
This tablet/workstation multifunction laptop uses the specific nVidia GeForce2 Go (NV11M-100) graphics controller, at least according to the HP Graphics Specifications for this Tablet PC, http://h20000.www2.hp.com/bizsupport/Te … eId=321957 and according to the results of 'lspci' from the #! command line.
One fix for #! Openbox graphics problems on this system is to append modeset and vga=7xx to the end of the linux (kernel) line of the the normal Crunchbang Linux... menuentry section in /boot/grub/grub.cfg
Whenever I started X, Openbox displayed erratic Xserver graphics and screen redraws in the Openbox startup screen and in menu boxes (e.g., in Terminal). The box containing the System Info and Shortcut Keys, which opens on the upper right of the Openbox startup screen, failed to appear on the TC1000.
Same exact TC1000 that I posted regarding wireless access over a year ago, see #! forum post http://crunchbanglinux.org/forums/topic … pc-tc1000/ User tbradbeer got everything working with #! on the exact same model over a year ago, see forum post of 2011-03-21 at http://crunchbanglinux.org/forums/topic … m/page/14/
OTOH, user IsTI37 reported similar display problems as mine using the same nVidia graphics controller (using xorg.conf files generated by *both* Xorg -config and nvidia-xconfig!) less than a year before that, on 2010-08-30, see http://crunchbanglinux.org/forums/topic … by-demons/ User DeepDayze suggested to add 'nomodeset' to the kernel options line and user Awebb suggested to "...Learn how to deal with HAL/udev (depeding on your xorg version) ASAP" to resolve the display problems.
#! user Paul mentions trying some display hacks for older laptops such as for this tc1000, at http://crunchbanglinux.org/wiki/howto/f … y_problems
Finally, #!'s Openbox DOES display graphics and screen redraws properly when run from a Live Session (failsafe) mode on a USB boot drive created via the suggested UNetbootin. The standard Live Session *without* failsafe did NOT enable proper display graphics and screen redraws, exactly similar to the hard-drive-installed problems I wrote above.
The bootable USB drive uses the following isolinux/live.cfg failsafe entry which gets properly displayed upon starting Openbox:
label livefailsafe .. append initrd=/live/initrd.img boot=live config noapic noapm nodma nomce nolapic nomodeset nosmp vga=normal ..
The Working Solution
A simple edit of the installed hard disk's /boot/grub/grub.cfg file made all the difference in the world!
This grub.cfg now contains the appended nomodeset and vga=7xx words in the normal Crunchbang Linux... menuentry section, as follows:
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=xxxxxxxxxx ro quiet splash nomodeset vga=792
Hope that this fix helps others using #! with similar nVidia GeForce2 graphics controllers!
afterwards, if you have enabled the experimental repo (as per instructions from http://mozilla.debian.net/), you'll be able to install/upgrade iceweasel 4
If you've already gone through these instructions successfully to install/upgrade iceweasel v4.0.0, you can now upgrade to v4.0.1 by running
apt-get update ; apt-get upgrade
from the commandline as sudo or the 'root' user (very temporarily!)
Also, the same http://mozilla.debian.net/ currently offers instructions to further upgrade iceweasel to v5.0 or to "aurora" v5.0a2. In both these upgrades, /etc/apt/sources.list or /etc/apt/sources.list.d/ must be edited either as
deb http://mozilla.debian.net/ squeeze-backports iceweasel-5.0
deb http://mozilla.debian.net/ squeeze-backports iceweasel-aurora
In either case, after appropriately editing /etc/apt/sources.list or /etc/apt/sources.list.d/ , one must then again run
apt-get update ; apt-get upgrade
from the commandline as sudo or the 'root' user.
Not really sure whether or not it is worthwhile to upgrade #!'s iceweasel to v5.0 or to v5.0a2.
Any other thoughts on this??
As you all can see at Crunchbang's download site http://crunchbanglinux.org/downloads/statler/20110207/, you can only download the Crunchbang ISO (at the present time) via BitTorrent.
You simply cannot obtain Crunchbang's current ISO via HTTP/FTP-download from its above centrally-hosted site, nor can you obtain CB this way from a secondary mirror.
I would easily guess that this limitation is primarily due to various hosting issues such as server diskspace, bandwidth and (of course) related cost-savings.
OTOH, for those who have any conceivable type of difficulties using bittorrents, how about reconsidering placing ISO downloads (HTTP/FTP access) for the next versions of CB back onto the centrally hosted site?
Or even making secondary non-torrent mirrors available as well?
Sure, people can still obtain other current Linux distros via HTTP/FTP-download, such as the ISOs for Ubuntu and native Debian GNU/Linux Squeeze at numerous mirrors worldwide.
Indeed, many people who DO have problems with running bittorrent through their networks may decide by themselves to go this HTTP/FTP-download route with such other distros.
OTOH, if there is any possibility that the next Crunchbang ISO-release can be hosted as an HTTP/FTP download instead, then why not do this and thus make it as easy as possible for such people (myself included) to obtain an installable ISO CD of this awesome distro????
I sure would hate for CB to become much less popular 'cause fewer and fewer people can easily obtain it!
You need to add the following entry in /etc/apt/sources.list or a new file in /etc/apt/sources.list.d/:
deb http://mozilla.debian.net/ squeeze-backports iceweasel-4.0
Added the suggested line at the very end of /etc/apt/sources.list as follows:
## DEBIAN BACKPORTS deb http://backports.debian.org/debian-backports squeeze-backports main contrib non-free deb http://mozilla.debian.net/ squeeze-backports iceweasel-4.0
You can install it with the following command:
apt-get install -t squeeze-backports iceweasel
Similar to corenominal's codestring way on top, I ran this through an xterm window as
sudo apt-get clean && sudo apt-get install -t squeeze-backports iceweasel && sudo apt-get update
This seemed to work fine in upgrading iceweasel to v4.0, although I too haven't yet noticed "any problems with font rendering" in v4.0.
Is there a definitive test for possible font-rendering problems under the suggested v4.0 upgrade here??
Until then, thanks for the suggestions here, as well as forthcoming ones on this upgrade
Will the new Iceweasel be added to the Statler repo?
My question too for Iceweasel, now that:
- 'Firefox 4 Released!', http://news.slashdot.org/story/11/03/22 … d?from=rss
- 'iceweasel 4 on squeeze?',http://www.linux-archive.org/debian-use … ueeze.html
- Iceweasel version 3.6 only(!) listed for Squeeze at today's http://mozilla.debian.net/
- Old Iceweasel_4.0 RC packages from back in 08-Feb-2011 (b11) listed at http://packages.crunchbanglinux.org/sta … pool/main/
Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvA Wireless LAN Controller (rev 10)
There was also another similar thread on this, found at http://crunchbanglinux.org/forums/topic … less-card/
Note that one of the links provided in this thread was also the RTL819X-related http://wiki.debian.org/rtl819x , same as the instructions tranche listed above.
In general, I found the Debian WiFi wiki http://wiki.debian.org/WiFi was immensely helpful for my own [SOLVED] wireless issue,
http://crunchbanglinux.org/forums/topic … pc-tc1000/
Offering this for further investigation, just in case the rtl819x wireless issue is not yet fully resolved.
Peppermint is for chewing gums and it tastes nice.
Actually, Peppermint OS is "an Ubuntu-based Linux distribution that aims to be lightning fast and easy on system resources", see http://distrowatch.com/table.php?distri … peppermint
Peppermint is essentially a lightweight variant of Linux Mint, itself a Ubuntu-based OS which claims to "provide a more complete out-of-the-box experience" than its official Ubuntu parent ; see http://distrowatch.com/table.php?distribution=mint
Openbox is a Window Manager, XFCE a Desktop Environment, you can't compare them on the basis of lightweightness.
Although Openbox is a WM and XFCE is a DE, others have already compared these two different "flavors" of #! in terms of resource-usage and diskspace (see above comments).
FWIW I have both "flavors" of #! installed on different lower-end-CPU machines, and both work VERY well!!
Whether installing #!'s XFCE DE or #!'s Openbox WM, the various Tips, Tricks & Scripts found at http://crunchbanglinux.org/forums/forum … s-scripts/ are worthwhile considering for both versions.
I myself received a noticeable performance-boost during the #! installation of both versions by paying a bit more attention to carefully partitioning the hard disk drives on my lower-end-CPU machines, e.g., by setting up appropriate swap partitions before installation.
An excellent Debian guide for this (and by extension, #! guide for this too) is Karsten M. Self's Linux Partitioning mini-FAQ found athttp://linuxmafia.com/~karsten/Linux/FA … ition.html
I think the short answer to both those questions is no. A lot of people in Debian would barely know we exist. There isn't a lot of interest in derivatives amongst the Debian faithful.
Thanks for your reply and an actual answer here
If there really "isn't a lot of interest in derivatives amongst the Debian faithful", then why did the writers/devs of the Debian Wiki spend the effort they did to create and maintain their whole 'Derivatives' site http://wiki.debian.org/Derivatives ??
Wouldn't it seem to make more sense for Debian-project writers to create and maintain the 'Derivatives' site in order to GATHER information from Debian derivatives (such as #!) for the intended primary benefit of Debian developers, rather than their CONTRIBUTING towards the benefit of their derivatives instead???
The former is what seems most likely to me, admittedly through reading a bit into the 'Derivatives' statements I already provided above.
The question might still remain as to how this could possibly affect #! in any way whatsoever ??
I just recently wrote a similar posting in the 'CrunchBang Talk' section at http://crunchbanglinux.org/forums/topic … onship-to/ , and now found this one.
'Awebb' suggested a search there, where I then found this thread.
LinuxMint is already there . . . now, where is the #! Info?
As of about two week's ago, the #! info is at http://wiki.debian.org/Derivatives/Census/Crunchbang
The Debian Wiki has several 'Derivatives' webpages, including:
1. The Debian Derivates Front Desk, http://wiki.debian.org/DerivativesFrontDesk
This is the home of the derivatives frontdesk. This group helps developers of Debian derivative distributions to contribute their changes back to Debian by:
* mentoring them through Debian-specific details (procedures) to get their packages into Debian
* getting them in touch with the right people (teams, etc)
* discussing and establishing processes to share efforts among derivatives and with Debian
2. The Debian Derivatives Census, http://wiki.debian.org/Derivatives/Census
The Debian derivatives census is an attempt to gather information about Debian derivatives that is useful to Debian, for integration of that information into Debian infrastructure and for the development of relationships between Debian and our derivatives.
3. The Debian Derivates Guidelines, http://wiki.debian.org/Derivatives/Guidelines
This page outlines aspects to take care while creating a derivative Debian distribution.
For now it is just an outline to collect relevant information which could be formalized later on in the form of Specification.
What is up with all this Debian Derivates stuff???
E.g., the individual quotes
"gather information about Debian derivatives that is useful to Debian" ?
"development of relationships between Debian and our derivatives" ?
"For now it is just an outline to collect relevant information...." ?
Yes, Debian Derivatives Census has a #! writeup at http://wiki.debian.org/Derivatives/Census/Crunchbang
But are the Debian organizers out to reign-in Crunchbang itself and/or its users??
And are certain things being passed along from Crunchbang and then through Debian in a one-way fashion up to Ubuntu or something ??
Maybe this discussion belongs elsewhere in the #! forums, but just want to know some answers on these.
#! remains an AWESOME effective distro whatever is really going on!!
Here's hoping that at least one person on this thread has tried liveCD-hopping as well!!
Some popular liveCDs in alphabetical order:
Damn Small Linux, http://www.damnsmalllinux.org/
MEPIS, http://www.mepis.org/ and its smaller antiX derivative, http://antix.mepis.com/
Puppy Linux, http://puppylinux.org
Tiny Core Linux, http://www.tinycorelinux.com/
(probably left out several other liveCD distros, but it seems that most people I know who've used Linux for awhile have at least heard of one or more of the above)
So I started building up a minimal Debian system with X and little else, adding one piece at a time. I tried a bunch of live distros as well, but didn't find one that I liked. Well, I liked Puppy's scrappy spirit, but wanted something with a little more control.
As an FYI, now that you've found Crunchbang, you might wish to be perhaps be aware of an even more involved self-build distro.
It's called Linux From Scratch (LFS), its website is http://www.linuxfromscratch.org/lfs/, Puppy was apparently built from LFS, and LFS is much too complicated and time-consuming (really, overkill!) for the likes of me.
OTOH, you, tranche, seem to have extensive background and a little bit more time available as "an old Unix guy, now retired".
Even though this here is a #! forum, I still thought LFS might be an appropriate suggestion for you, besides #!.
#!, Debian Xfce, and Xubuntu are three very nice Xfce distros, with many similarities but also some subtle differences. If you try a Live CD of each, you'll be able to make an informed decision which is best for your needs.
On one old i686 PIII machine, I tried a Debian xfce+lxde installation and the install CD wouldn't even go past 1st recognizing a PCI graphics card I was using.
After verifying that the debian xfce+lxde ISO was checksum'd OK, I gave up on this and then successfully installed #! r20110207 xfce just fine!
Didn't even want to try Xubuntu once #! installed and tweaked (but that's just me)
Just written as an FYI.
(self-note: open texteditor and copy-paste forum message back+forth in case #!-forums logs me out too quickly again!)
Installed #! r20110207 xfce and openbox versions onto several i686 machines and it runs great!
Am in California's SF Bay Area (U.S.) myself
With some Debian background (me), I had good #! success with several startoff things:
1) carefully partitioning hd during install so that I had nice paging/swapfile performance
2) editing /etc/apt/sources.list to weed out excess and non-local repos, for better 'apt-get' and 'synaptic' performance
3) editing out those runlevel start S0x scripts in /etc/rc2.d, /etc/rc3.d, ... \etc.
Will be looking for further #! optimization tweaks here, but as it is, #! is quite fast by default!
Thanks to coreoptimal and other #! contributors for this awesome distro
I eventually reached the Debian wiki 'Atmel at76c506 devices' at http://wiki.debian.org/atmel_pci.
Followed the steps here precisely, and then reached this message:
* No monitor or master mode functionality is available.
* The driver does not support WPA.
That was exactly it!
ALL the wireless networks I have ever used have WPA or WPA2 authentication, and with the TC1000's built-in at76c506, all I can get are the various WEP and LEAP authentications instead. No good.
I now use #!'s NetworkManager with the BCM4318 driver for the Linksys WPC54G card in the TC1000's card slot and this works fine for WPA/WPA2 authentication.
Thanks to Eddy who showed up at the last Berkeley Linux User Group with your expert Squeeze knowledge
Have recently and successfully finished an install of #! Statler Openbox on a Compaq Tablet PC TC1000 (http://h18000.www1.hp.com/products/quic … 29_na.html , USB install instructions from http://crunchbanglinux.org/wiki/statler … stallation ).
Am somewhat confused how to activate this tablet's wireless, and could use some CLEARER pointers here.
1rst, the internal wireless:
IDs the internal adapter as "Atmel Corp at76c606 8-2.11b Wireless Network Adapter (rev 11)", with an "atmel" driver in use.
Went to the Ubuntu thread of four yrs ago at 'Atmel at76c506 can see networks, dhcp times out' at http://ubuntuforums.org/showthread.php?t=365343 , and then re-installed the suggested package from the Debian default http://ftp.us.debian.org/debian squeeze repository through #!'s terminal
sudo apt-get install atmel-firmware
Wired Ethernet is through the internal port "eth1" and
now gives some 20-hex backslash-escaped ESSID gibberish which is NOT the adapter's MAC number as far as I can tell, and I'm confused on what other steps, if any, to carry out from this Ubuntu thread?
Sure, have already viewed the recommended http://crunchbanglinux.org/forums/topic … less-card/ and http://www.linuxhomenetworking.com/wiki … Networking , and am starting to sift through http://wiki.debian.org/WiFi
I fully realize that
Device installation is essentially a two-part process:
1) installing the driver (also called a module) and
2) setting up your WiFi interface.
So what is the proper Linux driver for my TC1000 (kernel 2.6.32-5-686) internal atmel at76c506 adapter and what extra steps (including setting up modules.conf and then running network-manager/wicd/wpa_supplicant ???
2nd, should the driver for the atmel at76c506 adapter be unavailable or incompatible for the #! 2.6.32-5-686 Linux kernel, then how could I then effectively use an available PCMCIA slot for my LinkSys Wireless-G wpc54g card ??
once this LinkSys card is inserted in the PCMCIA slot gives me the ID "Broadcom Corp BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)"
Probably a combo of the advice given at
http://crunchbanglinux.org/forums/topic … less-woes/ and at
I'd prefer to use the internal atmel wireless driver first, if this can be easily set up and activated using network-manager/wicd/wpa_supplicant (method choice out of 3 in http://crunchbanglinux.org/forums/topic … back-wicd/ ??)
You will probably get the correct idea that with all these #! post-links and external WiFi url's I am somewhat confused on activating WiFi here, but that I'm hopefully closing in on the correct course of action(?)
Much thanks on as CLEAR pointers as possible in all this!!
What are the key differences, if any, in the Openbox and Xfce4 ISO images for the latest CrunchBang release 10 "Statler" r20110207 ??
From the CrunchBang 10 "Statler" r20110207 download site http://crunchbanglinux.org/downloads/statler/20110207/ (slightly modified for 32-bit only and w/o the MD5 sums)
* 32-bit: Approx. Size: 684M
* 32-bit: Approx. Size: 679M
I've already reviewed the older pre-"Statler" posts
- Openbox vs XFCE? http://crunchbanglinux.org/forums/topic … x-vs-xfce/
- #! statler openbox vs xfce http://crunchbanglinux.org/forums/topic … x-vs-xfce/
Cannot see too much of an obvious difference between the two images in these posts, so here are maybe a few further defining questions:
Which of the two above "Statler" images might install&work best on a laptop having a lower-end Pentium III CPU (say, 800MHz), 256MB RAM max, and a 20GB/30GB hd ??
And what are some of the more effective hands-on tweaks using the preferred "Statler" image out of these two listed, in order to optimize performance (system&apps' speed) on such an i686 laptop??
Oh, laptop to be used for common desktop tasks such as running OpenOffice, web-browsing, watching YouTube videos, listening to music, ... etc. using Ethernet -or- WiFi.