What bugs me about him pushing GNU/Linux is that it puts GNU above all the amazing work that has gone into the kernel beyond GNU. GNU is a very tiny part of Linux.
A lot of projects wouldn't exist without things like GCC, automake, binutils, libc, etc. GNU is bigger than you give it credit for.
This is the only instance I can think of where someone wanted the name of their platform tossed on top of something made with it.
What about NT/Photoshop? It just doesn't make sense. It gives too much credit to the developer of the platform the product is built upon.
edit: I guess BSD/OS X would be a more accurate comparison.
I hope I have not open a can of worms here.
I'm just curious if there is a distro not related to RMS/FSF.
Archsorcerer on
XBL - ArchSilversmith
"We have years of struggle ahead, mostly within ourselves." - Made in USA
What bugs me about him pushing GNU/Linux is that it puts GNU above all the amazing work that has gone into the kernel beyond GNU. GNU is a very tiny part of Linux.
A lot of projects wouldn't exist without things like GCC, automake, binutils, libc, etc. GNU is bigger than you give it credit for.
This is the only instance I can think of where someone wanted the name of their platform tossed on top of something made with it.
What about NT/Photoshop? It just doesn't make sense. It gives too much credit to the developer of the platform the product is built upon.
edit: I guess BSD/OS X would be a more accurate comparison.
I hope I have not open a can of worms here.
I'm just curious if there is a distro not related to RMS/FSF.
Yes. BSD-based stuff (not Linux), and minimalist distros that use BusyBox. Most people just use GCC, but there are a number of other compilers around.
Alternate answer: to hear RMS go on, no. Not really. There are, however, many distributions which use GPL and are traitors to the cause. Stallman has been loosing credibility for a while now, though.
I'm still totally going for that reinstall tonight, though, but man.. that's something to keep in mind.
So, I'm just got my Windows 7 and I'm thinking format all drives, install Windows 7, then install Arch.
I'm assuming there's no major problems with this?
So at some point your computer only had Windows on it.
FUCKING DISGUSTING
I actually canned the dualboot idea, so I went to the setup I always have: My desktop computer, which is used for music and video production runs Windows and my much more used laptop runs Linux only.
I have been having this idea for the past few days now. Basically, I've been using my EeePC a lot since I arrived in Cambridge, specifically for taking notes.
My work scheme is basically using a a notebook (pen & paper) or gedit to take the notes and then I later compile them in HTML with Geany since my idea is to make a personal web page in which I will be able to put them online . So far it has been pretty good, the whole having to compile the notes in HTML helps me study while I learn at the same time HTML.
Anyway, this is not that relevant. What sometimes annoys me is that for that extra layer of security I have assigned a password so that I can login. All fine and dandy, but what I really want is to just get to the desktop in the least time possible.
Is it by any chance possible to make it so it will actually get to the desktop without asking for a password but for any action such as accessing my /home folder or open any app at all it will ask for root permission?
I have no idea if it is feasible at all. It seemed to make sense when I had this idea but now that I have written it down it doesn't sound that great at all. :P
Note: I'm on an EeePC 901, running the latest UNR 9.10 beta which gets to the desktop in 18/19s.
I'm not sure of the locking down everything (should be possible, of course, I've just never done it), but if you want to boot faster you probably need to tweak some more low-level stuff, maybe scrap some daemons you don't need and perhaps use the preload daemon. I'm sure Arch forums have some general tweaking threads that would apply.
Maybe even custom kernel. Depends how serious you are about wanting it to boot quicker.
I have been having this idea for the past few days now. Basically, I've been using my EeePC a lot since I arrived in Cambridge, specifically for taking notes.
My work scheme is basically using a a notebook (pen & paper) or gedit to take the notes and then I later compile them in HTML with Geany since my idea is to make a personal web page in which I will be able to put them online . So far it has been pretty good, the whole having to compile the notes in HTML helps me study while I learn at the same time HTML.
Anyway, this is not that relevant. What sometimes annoys me is that for that extra layer of security I have assigned a password so that I can login. All fine and dandy, but what I really want is to just get to the desktop in the least time possible.
Is it by any chance possible to make it so it will actually get to the desktop without asking for a password but for any action such as accessing my /home folder or open any app at all it will ask for root permission?
I have no idea if it is feasible at all. It seemed to make sense when I had this idea but now that I have written it down it doesn't sound that great at all. :P
Note: I'm on an EeePC 901, running the latest UNR 9.10 beta which gets to the desktop in 18/19s.
You basically want to not have to wait for your desktop to load after you enter your password, right? There is a way!
Basically, you'll use the Login screen or GDM options (I don't remember what it's called in older versions of Ubuntu, I'm running a beta of 9.10) and set your account to login automatically. Next, you'll open the Startup Applications preferences and find the Screensaver entry. Edit the command to read "gnome-screensaver && gnome-screensaver-command -l". This will lock the screen via screensaver as soon as the daemon has started. It should require your password to unlock it.
Everything else will continue to load in the background. It's only faster by the amount of time it takes you to react and type your password in, but it feels just that much snappier. Oh, there's also likely some way this can be circumvented. But if someone has physical access to your machine they can already pretty much get all your data (possibly sans encrypted disks), so no biggie.
I have been having this idea for the past few days now. Basically, I've been using my EeePC a lot since I arrived in Cambridge, specifically for taking notes.
My work scheme is basically using a a notebook (pen & paper) or gedit to take the notes and then I later compile them in HTML with Geany since my idea is to make a personal web page in which I will be able to put them online . So far it has been pretty good, the whole having to compile the notes in HTML helps me study while I learn at the same time HTML.
Anyway, this is not that relevant. What sometimes annoys me is that for that extra layer of security I have assigned a password so that I can login. All fine and dandy, but what I really want is to just get to the desktop in the least time possible.
Is it by any chance possible to make it so it will actually get to the desktop without asking for a password but for any action such as accessing my /home folder or open any app at all it will ask for root permission?
I have no idea if it is feasible at all. It seemed to make sense when I had this idea but now that I have written it down it doesn't sound that great at all. :P
Note: I'm on an EeePC 901, running the latest UNR 9.10 beta which gets to the desktop in 18/19s.
You basically want to not have to wait for your desktop to load after you enter your password, right? There is a way!
Basically, you'll use the Login screen or GDM options (I don't remember what it's called in older versions of Ubuntu, I'm running a beta of 9.10) and set your account to login automatically. Next, you'll open the Startup Applications preferences and find the Screensaver entry. Edit the command to read "gnome-screensaver && gnome-screensaver-command -l". This will lock the screen via screensaver as soon as the daemon has started. It should require your password to unlock it.
Everything else will continue to load in the background. It's only faster by the amount of time it takes you to react and type your password in, but it feels just that much snappier. Oh, there's also likely some way this can be circumvented. But if someone has physical access to your machine they can already pretty much get all your data (possibly sans encrypted disks), so no biggie.
So I've finally jumped into linux. The only experience I've had with it before is using a Live Ubuntu disk when shit got messy on a Windows PC.
I have Ubuntu installed and downloaded a driver for my ATI card.
But every example I google'd up on what to type into the terminal to install won't work.
I did open the properties up and click something along the lines of "allow to execute in terminal" or something when clicked. Which ran and everything but it wants me to do it with sudo.
Which would be dandy if I knew what to type.
So I've finally jumped into linux. The only experience I've had with it before is using a Live Ubuntu disk when shit got messy on a Windows PC.
I have Ubuntu installed and downloaded a driver for my ATI card.
But every example I google'd up on what to type into the terminal to install won't work.
I did open the properties up and click something along the lines of "allow to execute in terminal" or something when clicked. Which ran and everything but it wants me to do it with sudo.
Which would be dandy if I knew what to type.
Drivers are a bit different in Linux compared to windows. It sounds like you went to ati's site and downloaded a driver. I think it's easier to get drivers through Ubuntu's repository.
I'd just like to say to you that as a new user you'll find Linux to be pretty difficult, and I don't blame you. It took me three years to get to the point where I actually prefer using it over Windows. Basically, it's different. Very different. It's the weird Cuban communism to Microsoft and Apple's familiar capitalism. A lot of people assume this makes Linux "worse", because after a week, or a month, they can still do things more easily with Windows than they can with Linux. The fundamental problem with that outlook is that you're not really comparing this to the first time you ever used Windows, but rather what you're able to do with Windows *today*.
But God, those ATI instructions look ugly. :S It really annoys me that ATI are so lax with their Linux drivers.
Yeah, but take a look at that link CmdPrompt provided.
Instructions for Ubuntu 9.04 (Jaunty)
Enable the accelerated ATI graphics driver in the 'Hardware Drivers' (System->Hardware drivers), then do:
sudo dpkg-reconfigure -phigh linux-restricted-modules-`uname -r`
sudo insmod /lib/modules/`uname -r`/volatile/fglrx.ko
Log out and log in.
JAUNTY NOTICE
The above Jaunty 9.04 instructions don't actually work because the latest ATI driver is incompatible with XOrg 1.6. To see a guide on instructing how to downgrade XOrg and install the ATI driver, view this link: http://tan-com.com/posts/technology/fix-ubuntu-904-ati-driver-issue
OH. OKAY. That's nice, it doesn't actually work. Let's take a look at that link, shall we?
It appears we have to downgrade xserver to get the latest ATI drivers working! I can see why those Linux folks hold it in such high esteem, being as functional and efficient as it is.
In gedit, simply select the word “jaunty” anywhere in the file and click on “Replace” on the tool bar. When the dialogue box comes up, type “intrepid” into the box labeled “Replace With:” and click “Find” then “Replace All”
When everything is finished installing, you will want to open up Synaptic Package Manager and lock all of the xserver-xorg*, fglrx*, xorg-driver-fglrx, libdrm2, gnome-session, and fast-user-switch-applet packages at their current version. This is done by selecting the package then going to the “Package” menu and clicking on “Lock Version”.
Once all of the xserver and ATI driver packages have been locked, run
EDIT 06/05/09: After you restart, make sure to go to the Hardware Drivers manager under the “System” menu: Administration > Hardware Drivers and enable that ATI driver and reboot again. (Thanks Nicholas)
So yeah, its his first day in Linux and he's expected to fucking do that. And we're supposed to be surprised that people get scared off by how technical Linux is? The bit that pisses me off is that this isn't even a problem with Linux. This is on ATI, and they damage the reputation of the OS by making something so important so fucking obtuse to get working.
Eeebuntu is so much better than the last time I tried it. It's crazy. Extremely snappy even with Compiz, which basically means functionality + eye candy = one happy user.
Thanks, Improvolone!
Also, Firefly Linux is really cool. Extremely lightweight thanks to LXDE and everything just works. I was baffled using it but then I hit a pretty serious bug. I couldn't install it because the installer is broken.
So basically the distro works fantastically well but you can't really install it. That's the definition of hilarious right there. :P
Man, those instructions are bullshit, they remind me of setting my first Linux back when support was awful. It's not supposed to be now and then you get something like that? Really?
So it looks like the wifi card I bought is a fucking broadcom card.
Is there a way to just download some .debs and copy them to my Ubuntu partition, and depackage them there? I can only get the internet working in Windows, and I can't go lugging my new tower around everywhere looking for a lan line.
Sure, you can download a .deb, put it on a USB drive or something and "dpkg -i stuff.deb", I believe. Or you could install an ext driver in your windows to gain access to your Ubuntu partition from windows.
Gah, I can't get tags to display as words instead of numbers in Awesome. That snippet you gave me and every other snippet I've found just makes Awesome not appear as I boot. I have checked versions as well, I'm using 3.3.4 and snipåets from other people's configurations aor even their entire rc.luas make my awesome crash.
I have a broadcom card and I don't need ndiswrapper. What card do you have?
Visti: is your awesome up to date? Awesome updates very frequently and I bet the snippets you are trying to use are probably out-dated. I would go ask how to do it on awesome's mailing list/forum directly, if it's not on their wiki.
Actually I think that is the problem. Any given snippet you pull off the net is probably too old. Awesome changes faster than internet examples can keep up.
Long time lurker, first time poster. I started using awesome and arch linux mainly due to this forum and tended to lurk this thread. As I see, Visti had some trouble with the named tags in Awesome 3.3.4, so I decided it might be a good idea to offer my setup of that part.
From my rc.lua:
$ tail -n+97 .config/awesome/rc.lua | head -25
-- {{{ Tags
-- Define tags table.
tagging =
{
-- Name Layout Additional
{ name = "irc", layout = layouts[3], mwfact = 0.725 },
{ name = "2", layout = layouts[1], mwfact = 0.5 },
{ name = "3", layout = layouts[1], mwfact = 0.5 },
{ name = "4", layout = layouts[1], mwfact = 0.5 },
{ name = "float", layout = layouts[10], mwfact = 0.5 },
{ name = "bg_proc", layout = layouts[10], mwfact = 0.5 }
}
tags = {}
for s = 1, screen.count() do
tags[s] = {}
for i, v in ipairs(tagging) do
tags[s][i] = tag(v.name)
tags[s][i].screen = s
awful.layout.set(v.layout, tags[s][i])
awful.tag.setmwfact(v.mwfact,tags[s][i])
end
tags[s][1].selected = true
end
Also, remember that things change a lot between Awesome updates. I personally had a problem wherein the theme file changed names and the entire Awesome wouldn't start (rc.lua processing error, probably). The solution was to look at the 'skeleton' rc.lua file in (I think) /etc/xdg/awesome/ and check what was really different. If your rc.lua is for a really old version, I wouldn't be surprised if it were easier to just cp that default file and apply desired changes all over again.
Also, are you sure the other's configuration files you're using are for the recent version? If they're for an older version, they're almost guaranteed to crash something.
so, are you sure the other's configuration files you're using are for the recent version? If they're for an older version, they're almost guaranteed to crash something.
So anyway, went through those lovely instructions last night with a friend. Most of the way through it worked and I was quite happy about everything finally coming together.
However my friends prompted that we finish with the instructions, something about upgrades possibly breaking it, I dunno, to late to comprehend.
Posts
FUCKING DISGUSTING
I hope I have not open a can of worms here.
I'm just curious if there is a distro not related to RMS/FSF.
"We have years of struggle ahead, mostly within ourselves." - Made in USA
Yes. BSD-based stuff (not Linux), and minimalist distros that use BusyBox. Most people just use GCC, but there are a number of other compilers around.
Alternate answer: to hear RMS go on, no. Not really. There are, however, many distributions which use GPL and are traitors to the cause. Stallman has been loosing credibility for a while now, though.
I actually canned the dualboot idea, so I went to the setup I always have: My desktop computer, which is used for music and video production runs Windows and my much more used laptop runs Linux only.
My work scheme is basically using a a notebook (pen & paper) or gedit to take the notes and then I later compile them in HTML with Geany since my idea is to make a personal web page in which I will be able to put them online . So far it has been pretty good, the whole having to compile the notes in HTML helps me study while I learn at the same time HTML.
Anyway, this is not that relevant. What sometimes annoys me is that for that extra layer of security I have assigned a password so that I can login. All fine and dandy, but what I really want is to just get to the desktop in the least time possible.
Is it by any chance possible to make it so it will actually get to the desktop without asking for a password but for any action such as accessing my /home folder or open any app at all it will ask for root permission?
I have no idea if it is feasible at all. It seemed to make sense when I had this idea but now that I have written it down it doesn't sound that great at all. :P
Note: I'm on an EeePC 901, running the latest UNR 9.10 beta which gets to the desktop in 18/19s.
They still have to mature a lot to be seen as reliable alternatives to vanilla Ubuntu.
Anyway, recent updates messed up my 9.10 beta install so... Yeah.
Maybe even custom kernel. Depends how serious you are about wanting it to boot quicker.
Alternatively, install arch.
I should just include "alternatively, install arch" at the end of all my posts.
http://fireflylinux.com/
"We have years of struggle ahead, mostly within ourselves." - Made in USA
You basically want to not have to wait for your desktop to load after you enter your password, right? There is a way!
Basically, you'll use the Login screen or GDM options (I don't remember what it's called in older versions of Ubuntu, I'm running a beta of 9.10) and set your account to login automatically. Next, you'll open the Startup Applications preferences and find the Screensaver entry. Edit the command to read "gnome-screensaver && gnome-screensaver-command -l". This will lock the screen via screensaver as soon as the daemon has started. It should require your password to unlock it.
Everything else will continue to load in the background. It's only faster by the amount of time it takes you to react and type your password in, but it feels just that much snappier. Oh, there's also likely some way this can be circumvented. But if someone has physical access to your machine they can already pretty much get all your data (possibly sans encrypted disks), so no biggie.
I love you guys.
The only thing that makes sad is their stance with Mono
"We have years of struggle ahead, mostly within ourselves." - Made in USA
I have Ubuntu installed and downloaded a driver for my ATI card.
But every example I google'd up on what to type into the terminal to install won't work.
I did open the properties up and click something along the lines of "allow to execute in terminal" or something when clicked. Which ran and everything but it wants me to do it with sudo.
Which would be dandy if I knew what to type.
Find the driver manager in the system menu.
Edit: also can't seem to turn on visual effects. But I'm gonna guess that's because I don't have video drivers yet? Maybe?
Running this thing basically says "yea run this just like this in the terminal but do it with sudo"
I just don't know command line business for shit.
I know what I have to do, just not what exactly I need to type.
This is what's going on - what he says to type does nothing though.
http://www.youtube.com/watch?v=dw3aaitaDnA
But God, those ATI instructions look ugly. :S It really annoys me that ATI are so lax with their Linux drivers.
OH. OKAY. That's nice, it doesn't actually work. Let's take a look at that link, shall we?
It appears we have to downgrade xserver to get the latest ATI drivers working! I can see why those Linux folks hold it in such high esteem, being as functional and efficient as it is.
But all you have to do is plug in these commands:
So yeah, its his first day in Linux and he's expected to fucking do that. And we're supposed to be surprised that people get scared off by how technical Linux is? The bit that pisses me off is that this isn't even a problem with Linux. This is on ATI, and they damage the reputation of the OS by making something so important so fucking obtuse to get working.
Anyway, concerning netbooks.
Eeebuntu is so much better than the last time I tried it. It's crazy. Extremely snappy even with Compiz, which basically means functionality + eye candy = one happy user.
Thanks, Improvolone!
Also, Firefly Linux is really cool. Extremely lightweight thanks to LXDE and everything just works. I was baffled using it but then I hit a pretty serious bug. I couldn't install it because the installer is broken.
So basically the distro works fantastically well but you can't really install it. That's the definition of hilarious right there. :P
So it looks like the wifi card I bought is a fucking broadcom card.
Is there a way to just download some .debs and copy them to my Ubuntu partition, and depackage them there? I can only get the internet working in Windows, and I can't go lugging my new tower around everywhere looking for a lan line.
Seriously, fuck broadcom.
Gah, I can't get tags to display as words instead of numbers in Awesome. That snippet you gave me and every other snippet I've found just makes Awesome not appear as I boot. I have checked versions as well, I'm using 3.3.4 and snipåets from other people's configurations aor even their entire rc.luas make my awesome crash.
Pff. Kids these days.
I will say that ndiswrapper has been very kind to me in the past.
Visti: is your awesome up to date? Awesome updates very frequently and I bet the snippets you are trying to use are probably out-dated. I would go ask how to do it on awesome's mailing list/forum directly, if it's not on their wiki.
From my rc.lua:
$ tail -n+97 .config/awesome/rc.lua | head -25 -- {{{ Tags -- Define tags table. tagging = { -- Name Layout Additional { name = "irc", layout = layouts[3], mwfact = 0.725 }, { name = "2", layout = layouts[1], mwfact = 0.5 }, { name = "3", layout = layouts[1], mwfact = 0.5 }, { name = "4", layout = layouts[1], mwfact = 0.5 }, { name = "float", layout = layouts[10], mwfact = 0.5 }, { name = "bg_proc", layout = layouts[10], mwfact = 0.5 } } tags = {} for s = 1, screen.count() do tags[s] = {} for i, v in ipairs(tagging) do tags[s][i] = tag(v.name) tags[s][i].screen = s awful.layout.set(v.layout, tags[s][i]) awful.tag.setmwfact(v.mwfact,tags[s][i]) end tags[s][1].selected = true endAlso, remember that things change a lot between Awesome updates. I personally had a problem wherein the theme file changed names and the entire Awesome wouldn't start (rc.lua processing error, probably). The solution was to look at the 'skeleton' rc.lua file in (I think) /etc/xdg/awesome/ and check what was really different. If your rc.lua is for a really old version, I wouldn't be surprised if it were easier to just cp that default file and apply desired changes all over again.
Also, are you sure the other's configuration files you're using are for the recent version? If they're for an older version, they're almost guaranteed to crash something.
Well, back to lurking...
so, are you sure the other's configuration files you're using are for the recent version? If they're for an older version, they're almost guaranteed to crash something.
This is what I was getting at
However my friends prompted that we finish with the instructions, something about upgrades possibly breaking it, I dunno, to late to comprehend.
Long story short we broke it.