#! was one of my first linux experiences.
It was the first distro i used in Virtualbox to experiment with web dev beyond shared hosting. This was the foundation of my career.
It's been a great live-cd distro for recovering friends documents on old slow pcs.
It revived my college laptop in it's sad older years.
It was an early source of my admiration for beautiful and functional minimalist design (seriously, the default theming on #! is perfection).
I have lurked the forums on and off over the years, I've always enjoyed the screenshot threads immensely. The SUB 100 club thread was one I remember in particular, great learning experience.
Thank you so much for #!, it's been great.
Quick word, I actually love having abiword, gnumeric, gimp, gparted stock (even if i would remove replace them later). I think without those utils, you would lose some of the spirit of #!: minimalism but completely robust.
As it stands now #! is not only great to install, but that completeness vs. lightweight ratio makes it my favorite livecd as well.
I have used #! for recovering/backing up old windows pcs without network, you never know when you'll want to take a peek at a spreadsheet or word doc while rummaging.
Will that setup work with a VM? Do you have an iso or by any chance know which option to check and which to not.
Yes, that was done in virtualbox
Really the steps bullet points I outlined are all it took, but you should be comfortable with no login manager, a WM besides openbox and understand a little about the processes that are starting up.
I would highly recommend running through an archlinux install a few times. I'm still a beginner, but it really helped me grasp the lower levels of ramping up a full desktop environment from scratch
Then when you come back to #!, you get to go in the opposite direction (uninstalling things, tweaking the startup). #! is already ~120MB idle out of the box, so you have pretty much the best start possible.
I remember looking at this thread and was blown away at how you guys optimized. Here is my shot
87MB with crunchbang forums loaded!
I have a new appreciation for #! which makes this goal way too easy, the lazy man's sub 100
purge slim -> .xinitrc
dwb (newly discovered, awesome!)
I also ended up doing this at work on our cruddy 3GB dell towers to squeeze a 1GB windows VM + pidgin, irc, music, lots-o-chrome tabs.
And I never knew #! forums had such sexy responsive layouts, great exercise all around.
I really want to fix the quirks, but this made all wine and google chrome flash player sounds way too fast! How can we fix this without screwing up other things?
I'm guessing that happens as a result of the these lines:
default-fragments = 8 default-fragment-size-msec = 10
Try mixing, matching or removing the settings to see what works best. Also try googling for that specific issue.
pulseaudio has been very finicky for me on waldorf, but I finally solved it with some google and hackery.
I had two major problems:
If I lowered the volume to say 50% and opened a gmusicbrowser to play a song, the volume would raise itself to 100%.
This was not limited to gmusicbrowser. VLC, chrome (youtube) and other audio apps were doing the same. I nearly blew out my speakers because of this behavior
In an attempt to copy xubuntu, here were the lines I uncommented/added in my #! config:
flat-volumes = no resample-method = speex-float-1 default-fragments = 8 default-fragment-size-msec = 10 deferred-volume-extra-delay-usec = 1
After adding these, the volume now works as expected. Other apps do not auto boost the volume to 100%. I added these options all at once, but you might have success with just the flat-volumes option.
Skype or VLC audio would be very distorted and fuzzy
to the load module settings.
# /etc/pulse/default.pa ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect tsched=0 .else ### Use the static hardware detection module (for systems that lack udev/hal support) load-module module-detect tsched=0 .endif
There are some implications to adding this option, but it's a nice quick fix. Check out the arch link above for a good discussion.
When modifying these settings, make sure to restart pulseaudio:
pulseaudio -k # or pulseaudio --kill && pulseaudio --start
Spent a while creeping the threads, I think it's finally time for my first screenshot post!
Spent the holidays vbox distro hopping and learning the arch way, finally got to put them on my main box.
Pretty vanilla archbang:
Really liking it, the defaults are nice. Feels very light and clean compared to normal buntu.
Tried plain buntu too, but bailed as soon as I saw the amazon search in the gnome shell. Disappointing.
First of all, #! is now my main distro at work. I started with Ubuntu -> Xubuntu -> #! statler. Couldn't be happier.
I run a Win XP VM on a work PC at all times with only 3GB of ram, heavy outlook/photoshop usage. On #! it flies, where the buntu setups would get very sluggish.
Second, the style and configuration of everything out of the box is fantastic. Minimalist and easy on the eyes, just excellent (waldorf is great too).
Third, the install scripts for first run/dropbox/chrome. They're not that tough to setup manually, but it's a really nice touch.
Lastly, as many have said the forums are great. Almost every question I had was answered in detail in a previous post by extremely knowledgeable people. Love seeing screenshots and configs from other people too.
Hope to be involved more in the future, i'll be on crunch for a long time!
Looking for a little help with setting up dual monitors. Both are 1440x900, but 1 monitor uses a DP -> VGA cable.
Here is the default xrandr output
Screen 0: minimum 320 x 200, current 2880 x 900, maximum 8192 x 8192 VGA1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 370mm x 230mm 1440x900 59.9*+ 75.0 1280x1024 75.0 60.0 1280x800 59.8 1152x864 75.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0 720x400 70.1 HDMI1 disconnected (normal left inverted right x axis y axis) DP1 connected 1360x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1360x768 59.8 1024x768 60.0 800x600 60.3 56.2 848x480 60.0 640x480 59.9 59.9
So my first step was to add the 1440x900 mode for the DP1 output
xrandr --newmode "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync xrandr --addmode DP1 "1440x900_60.00"
Then I used arandr to generate a configuration script:
xrandr --output HDMI1 --off --output DP1 --mode "1440x900_60.00" --pos 1440x0 --rotate normal --output VGA1 --mode 1440x900 --pos 0x0 --rotate normal
This successfully updates the display, but here is what I see on the monitors
[ ][ ||]
Where the left side is the VGA (which is good), and the right side is DP. The || is a black bar that i cannot move my mouse past.
When I take a screenshot of this, I see the full screen (no black bar). Also when I move my mouse from screen to screen, it disapears for a few seconds, then appears.
Clearly the right black bar is some sort of right margin that pushes the screen over.
I moved from xubuntu to crunchbang, and here is the old arandr script
xrandr --output HDMI1 --off --output DP1 --mode 1440x900 --pos 1440x0 --rotate normal --output VGA1 --mode 1440x900 --pos 0x0 --rotate normal
As you can see the 1440x900 was natively detected, I did no manual adding there.
$ lspci 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
Any ideas of what to try?
Yea, that was pretty frustrating.
I've looked into it a little. I know lxpanel is related to trayer in a way. The tint2 look is just so damn nice though.
Really good guide here: http://code.google.com/p/tint2/wiki/Install
I noticed after testing after removing tint v 0.6 from the startup that nitrogen cooperated. So now testing with tint2
The tray seems nonexistent. There was no section in the tintrc for the tray as I've seen in posts. According to synaptic I have version 0.6, but #! lists 0.7.x.x, so I'll try that out (oops). Ahh that's why using tint as a command works, should be tint2.
Yes I have a delay on nitrogen already. I'm stumped. I'll post my autostart.
#Global . $GLOBALAUTOSTART #lx lxsession & #powermanager gnome-power-manager & #conky conky -q & #Tint2 tint -c ~/.config/tint/mytint & #stalone #(sleep 4s && stalonetray) & #network (sleep 5s && wicd) & #Nitrogen (sleep 3s && nitrogen --restore) &