Posts by cl_music_fan

cl_music_fan · Help & Support (Stable)

When I installed #! yesterday, I wasn't able, for some reason unknown to me, to pick ext4 for /boot. I was forced (as I recall) to set /boot to be in ext3. But all other main Linux divisions are set as ext4. Is this arrangement OK or not?

cl_music_fan · Help & Support (Stable)

I just installed #! Waldorf (32 bit) the other day-- I'm new to #! (but I've used MEPIS since 2005).

Today when I wanted to run Synaptic, which I found on the menu, I first tried my root password but that didn't work which I thought was odd. So I tried my general user password and Synaptic ran. But why? Shouldn't it only run as root? Then in file manager, I checked the permissions for Synaptic. I saw that it's set for root. Why then was I able to run it with the general user password?

cl_music_fan · Introductions

Two days ago I installed #! Waldorf (32 bit) in an older P4 desktop tower. Before #!, I had in that tower aptosid as sole OS. In another older P4 desktop tower and in an older IBM laptop I have MEPIS (currently v. 11, 32 bit) as sole OS. [I've been using MEPIS as sole OS in a series of a few desktop towers since 2005 and in the laptop since May 2011. But I'm no Linux expert-- I get in trouble now and then. When that happens I turn to the always helpful forum for MEPIS users.]

In this forum, I hope I learn more about #! when I do and don't get into trouble and when I just want to know how to do something. I'll be posting in a moment. I have a question about Firestarter installation, for my firewall.

CrunchBang Linux

SEARCH

#1 Help & Support (Stable) » The ext's I chose when installing: /boot is in ext3, others not » 2013-04-17 02:50:07

#2 Help & Support (Stable) » Synaptic being run by general user password » 2013-04-17 02:33:03

#3 Introductions » Hello fellow #! users » 2013-04-16 18:24:51

Board footer