• General Linux Chat and Small Questions v. Install Arch
    4,946 replies, posted
You could try KDE, it's good if you're not looking for the lightest of the light DE.
[QUOTE=danharibo;39486026]You could try KDE, it's good if you're not looking for the lightest of the light DE.[/QUOTE] KDE is cool and stuff but TBH I think it's too heavy and not worth it. My PC can probably handle it but my OCD is like: "don't use more than necessary"!
[QUOTE=Moofy;39486063]KDE is cool and stuff but TBH I think it's too heavy and not worth it. My PC can probably handle it but my OCD is like: "don't use more than necessary"![/QUOTE] What sort of computer are you running?
[QUOTE=danharibo;39486026]You could try KDE, it's good if you're not looking for the lightest of the light DE.[/QUOTE] KDE is nice if you take the time to make it look less uh, gummy and shiny
[QUOTE=danharibo;39486098]What sort of computer are you running?[/QUOTE] Some medion one. 4GB ram, dual core phenom something. I'm sure it can run.
I run Arch testing and I never have issues for some reason. Go figure. :v: At least issues not necessarily related to Arch as much as whatever WM I'm using at the time.
I find updating in Arch Linux can be tedious if you don't keep up, but by no means is it difficult or broken. I prefer the informed bleeding edge updates than the old dumb system "updates".
Will someone running Gentoo describe what the update process is like? I hear that Arch has a sub-par package manager but want to know what I'm missing out on. Should anyone wonder what an update on Arch is like (if you are considering Arch as a distro), here is my account: 1. If you are feeling adventuresome, just skip to step 2 right now: if there are any warnings or conflicts you do not understand, just answer [b]no[/b] and come back to this step before proceeding. While browsing the web, load the archlinux.org frontpage and look at the most recent posts for any scary words. If you are on IRC anyway, take a look at the #archlinux MOTD and skim through posts for anyone posting issues with recent updates. 2. Run `pacman -Syu`, which instructs the package manager to Sync with the remote repository, downloading a new copy of the master package listing and then doing a system-wide update which calculates any changes in dependencies and installs/updates packages which are out-of-date locally. 3. [b]Read [i]all[/i][/b] warnings and respond to them sensibly: if you know they are innocuous then proceed, if you do not understand them then return to step 1 and do further research. 4. [b]Read [i]all[/i][/b] packages to be updated. Arch is rolling release, and updates to important packages (your X server, your DE/WM, your office-suite, your web browser, etc.) [b]may[/b] require special attention on your part. Try to keep track of major version number changes (from 3.x to 4.x, for example) which usually indicate a lack of backwards compatibility. 5. When you are certain you wish to proceed, respond to the prompt with Y and the package tarballs will be downloaded, unpacked, trust-checked, etc. During this time, you can continue working, or you can keep an eye on the process (have you ever watched paint dry?). 6. If you haven't been watching the update, scroll back up to the start of the process and scan for any update notes (usually package specific and requiring some action on your part) or warnings. Often, warnings concern changes in default configuration files which conflict with the configuration files you currently have on your system: instead of overwriting your custom configuration files, pacman is kind enough to install the file with a .pacnew suffix and even goes so far as to notify you of the change! I highly recommend you have pacman-color installed, because it highlights Warning messages in yellow, making them easy to spot while scrolling through the update log. 7. Although it isn't mandatory, I recommend you just reboot at this point: there is a good chance something (especially the kernel itself) has been update which unloaded some commonly used modules. I like to think that Arch boots quick enough that an update isn't even an inconvenience in most cases. 8. Continue using your system contently until you decide to update again. What's the process like on Gentoo? I'm really interested to know how most people go about their system updates and how long the updates usually take.
[QUOTE=Rayjingstorm;39488228]Will someone running Gentoo describe what the update process is like? I hear that Arch has a sub-par package manager but want to know what I'm missing out on. Should anyone wonder what an update on Arch is like (if you are considering Arch as a distro), here is my account: 1. If you are feeling adventuresome, just skip to step 2 right now: if there are any warnings or conflicts you do not understand, just answer [b]no[/b] and come back to this step before proceeding. While browsing the web, load the archlinux.org frontpage and look at the most recent posts for any scary words. If you are on IRC anyway, take a look at the #archlinux MOTD and skim through posts for anyone posting issues with recent updates. 2. Run `pacman -Syu`, which instructs the package manager to Sync with the remote repository, downloading a new copy of the master package listing and then doing a system-wide update which calculates any changes in dependencies and installs/updates packages which are out-of-date locally. 3. [b]Read [i]all[/i][/b] warnings and respond to them sensibly: if you know they are innocuous then proceed, if you do not understand them then return to step 1 and do further research. 4. [b]Read [i]all[/i][/b] packages to be updated. Arch is rolling release, and updates to important packages (your X server, your DE/WM, your office-suite, your web browser, etc.) [b]may[/b] require special attention on your part. Try to keep track of major version number changes (from 3.x to 4.x, for example) which usually indicate a lack of backwards compatibility. 5. When you are certain you wish to proceed, respond to the prompt with Y and the package tarballs will be downloaded, unpacked, trust-checked, etc. During this time, you can continue working, or you can keep an eye on the process (have you ever watched paint dry?). 6. If you haven't been watching the update, scroll back up to the start of the process and scan for any update notes (usually package specific and requiring some action on your part) or warnings. Often, warnings concern changes in default configuration files which conflict with the configuration files you currently have on your system: instead of overwriting your custom configuration files, pacman is kind enough to install the file with a .pacnew suffix and even goes so far as to notify you of the change! I highly recommend you have pacman-color installed, because it highlights Warning messages in yellow, making them easy to spot while scrolling through the update log. 7. Although it isn't mandatory, I recommend you just reboot at this point: there is a good chance something (especially the kernel itself) has been update which unloaded some commonly used modules. I like to think that Arch boots quick enough that an update isn't even an inconvenience in most cases. 8. Continue using your system contently until you decide to update again. What's the process like on Gentoo? I'm really interested to know how most people go about their system updates and how long the updates usually take.[/QUOTE] or 1) check arch announce for anything critical 2) run -Syu 3) If anything conflicts or wants replacing, think about it. a) double check the announcements, b) Ask in #archlinux 4) Everything will be fine.
[QUOTE=danharibo;39488750]or 1) check arch announce for anything critical 2) run -Syu 3) If anything conflicts or wants replacing, think about it. a) double check the announcements, b) Ask in #archlinux 4) Everything will be fine.[/QUOTE] Yours is more realistic, but I thought I would qualify all of the steps fully as to be unambiguous. There is a lot of text in my post but it boils down to a few quick actions which are marginal compared to the time spent using the system.
[QUOTE=Moofy;39485964]I was thinking about trying Ubuntu with the old GNOME lock and a dock. Since I can't find any good site where to read about Cinnamon things :v:[/QUOTE] I am running cinnamon on ubuntu. What do you need to know?
[QUOTE=kaukassus;39491217]I am running cinnamon on ubuntu. What do you need to know?[/QUOTE] Can't describe. Can I perhaps see your desktop to point out stuff of interest?
[QUOTE=Rayjingstorm;39488228]Will someone running Gentoo describe what the update process is like? I hear that Arch has a sub-par package manager but want to know what I'm missing out on. Should anyone wonder what an update on Arch is like (if you are considering Arch as a distro), here is my account: 1. If you are feeling adventuresome, just skip to step 2 right now: if there are any warnings or conflicts you do not understand, just answer [b]no[/b] and come back to this step before proceeding. While browsing the web, load the archlinux.org frontpage and look at the most recent posts for any scary words. If you are on IRC anyway, take a look at the #archlinux MOTD and skim through posts for anyone posting issues with recent updates. 2. Run `pacman -Syu`, which instructs the package manager to Sync with the remote repository, downloading a new copy of the master package listing and then doing a system-wide update which calculates any changes in dependencies and installs/updates packages which are out-of-date locally. 3. [b]Read [i]all[/i][/b] warnings and respond to them sensibly: if you know they are innocuous then proceed, if you do not understand them then return to step 1 and do further research. 4. [b]Read [i]all[/i][/b] packages to be updated. Arch is rolling release, and updates to important packages (your X server, your DE/WM, your office-suite, your web browser, etc.) [b]may[/b] require special attention on your part. Try to keep track of major version number changes (from 3.x to 4.x, for example) which usually indicate a lack of backwards compatibility. 5. When you are certain you wish to proceed, respond to the prompt with Y and the package tarballs will be downloaded, unpacked, trust-checked, etc. During this time, you can continue working, or you can keep an eye on the process (have you ever watched paint dry?). 6. If you haven't been watching the update, scroll back up to the start of the process and scan for any update notes (usually package specific and requiring some action on your part) or warnings. Often, warnings concern changes in default configuration files which conflict with the configuration files you currently have on your system: instead of overwriting your custom configuration files, pacman is kind enough to install the file with a .pacnew suffix and even goes so far as to notify you of the change! I highly recommend you have pacman-color installed, because it highlights Warning messages in yellow, making them easy to spot while scrolling through the update log. 7. Although it isn't mandatory, I recommend you just reboot at this point: there is a good chance something (especially the kernel itself) has been update which unloaded some commonly used modules. I like to think that Arch boots quick enough that an update isn't even an inconvenience in most cases. 8. Continue using your system contently until you decide to update again. What's the process like on Gentoo? I'm really interested to know how most people go about their system updates and how long the updates usually take.[/QUOTE] when I ran gentoo/funtoo and I was going to update, I just ran emerge -avDNU world, and check if there are any makeopts I'd like to include, if there are I edit /etc/portage/package.use and update, else I'd just go ahead. I'm probably a bad example considering I never checked for news on broken packages
[QUOTE=Moofy;39491484]Can't describe. Can I perhaps see your desktop to point out stuff of interest?[/QUOTE] [t]http://i.imgur.com/6wRz2Uy.jpg[/t] There [editline]6th February 2013[/editline] Pretty generic Cinnamon desktop.
[QUOTE=kaukassus;39492693][t]http://i.imgur.com/6wRz2Uy.jpg[/t] There [editline]6th February 2013[/editline] Pretty generic Cinnamon desktop.[/QUOTE] As far my eyes spot: Cinnamon Theme That terminal thing which I don't remember the name of. (someone tell me please :v:) Faenza icons? And a snazzy wallpaper!
[QUOTE=Moofy;39493207]As far my eyes spot: Cinnamon Theme That terminal thing which I don't remember the name of. (someoe tell me please :v:) Faenza icons? And a snazzy wallpaper![/QUOTE] 1. My cinnamon theme is: Faience. You can get more Cinnamon themes here: [url]http://cinnamon-spices.linuxmint.com/themes[/url] 2. The terminal is called terminator. 3. Faenza Icons is an icon pack. you can get it here: [url]http://www.deviantart.com/users/outgoing?http://dl.dropbox.com/u/9966975/faenza-icon-theme_1.3.zip[/url] 4. You can get some cool wallpapers from here: [url]http://wallbase.cc/home[/url]
[QUOTE=kaukassus;39493236]1. My cinnamon theme is: Faience. You can get more Cinnamon themes here: [url]http://cinnamon-spices.linuxmint.com/themes[/url] 2. The terminal is called terminator. 3. Faenza Icons is an icon pack. you can get it here: [url]http://www.deviantart.com/users/outgoing?http://dl.dropbox.com/u/9966975/faenza-icon-theme_1.3.zip[/url] 4. You can get some cool wallpapers from here: [url]http://wallbase.cc/home[/url][/QUOTE] Thanks, I'm installing Ubuntu 12.04 right now and I'm going to add the Cinnamon PPA right after all updates and stuff! :dance: [editline]6th February 2013[/editline] I ran into some problems trying to install the open source drivers to make my 3D acceleration better, since Cinnamon seems to be a little bit laggy with the animation for me. I use ATI Radeon HD 5670. [URL="https://wiki.ubuntu.com/X/Troubleshooting/VideoDriverDetection?action=show&redirect=X%2FTroubleshooting%2FFglrxInteferesWithRadeonDriver#Problem:_Need_to_purge_-fglrx"]I followed this guide. [/URL] I got to command line 2, and this occured: [code]mathias@mucap:~$ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri fglrx-modaliases Reading package lists... Done Building dependency tree Reading state information... Done Package fglrx-modaliases is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: fglrx-updates:i386 fglrx-experimental-9:i386 fglrx:i386 fglrx-updates fglrx-experimental-9 fglrx E: Package 'fglrx-modaliases' has no installation candidate[/code]
[QUOTE=Moofy;39493207]As far my eyes spot: Cinnamon Theme That terminal thing which I don't remember the name of. (someone tell me please :v:) Faenza icons? And a snazzy wallpaper![/QUOTE] Screenfetch? [editline]6th February 2013[/editline] Also, faience window borders are so ugly obligatory screenfetch now that it has been mentioned [img]http://horobox.co.uk/u/flubbernugget-_1360215469.png[/img]
[QUOTE=Rayjingstorm;39488228]Will someone running Gentoo describe what the update process is like? I hear that Arch has a sub-par package manager but want to know what I'm missing out on.[/QUOTE] 1: Sync the Portage tree with `emerge --sync` (or `eix-sync` if you have eix installed). This could probably be put on a cron job instead of doing it right before every update, though keep in mind they get whiny and could possibly ban you from Portage mirrors if you do it more than once daily. 2: If it says there's a new version of Portage available, run `emerge portage`. If it says "X news items waiting for repository gentoo" or similar, run `eselect news read all`, then when you've read them all `eselect news purge`. 3: `emerge -u world` is what's required. Usually, however, you'd run `emerge -auvDN world`, where auvDN is (in order) "ask" (lists the packages to update and makes sure you want to continue, highly recommended), "update", "verbose", "deep update" (consider everything, not just things you explicitly merged in), and "new USE" (if you changed your USE flags the update should take that into account). 4: Wait. Go make dinner. This is going to take a while. 5: If something has an important message, it will be printed twice: Once when it appears, and once after the whole thing is finished. If you see these messages, read them. 6: If Portage says that some config files need updating, you'll want to update them. I prefer using `cfg-update -u` combined with Kdiff3 for this (cfg-update needs to be installed manually, it's in Portage), though you could do it manually if you wanted to. The original file remains untouched, and a new file, ._cfg0000_filename (or something like that I forget) is placed in the original file's directory.
[QUOTE=Rayjingstorm;39488228]Will someone running Gentoo describe what the update process is like? I hear that Arch has a sub-par package manager but want to know what I'm missing out on. Should anyone wonder what an update on Arch is like (if you are considering Arch as a distro), here is my account: 1. If you are feeling adventuresome, just skip to step 2 right now: if there are any warnings or conflicts you do not understand, just answer [b]no[/b] and come back to this step before proceeding. While browsing the web, load the archlinux.org frontpage and look at the most recent posts for any scary words. If you are on IRC anyway, take a look at the #archlinux MOTD and skim through posts for anyone posting issues with recent updates. 2. Run `pacman -Syu`, which instructs the package manager to Sync with the remote repository, downloading a new copy of the master package listing and then doing a system-wide update which calculates any changes in dependencies and installs/updates packages which are out-of-date locally. 3. [b]Read [i]all[/i][/b] warnings and respond to them sensibly: if you know they are innocuous then proceed, if you do not understand them then return to step 1 and do further research. 4. [b]Read [i]all[/i][/b] packages to be updated. Arch is rolling release, and updates to important packages (your X server, your DE/WM, your office-suite, your web browser, etc.) [b]may[/b] require special attention on your part. Try to keep track of major version number changes (from 3.x to 4.x, for example) which usually indicate a lack of backwards compatibility. 5. When you are certain you wish to proceed, respond to the prompt with Y and the package tarballs will be downloaded, unpacked, trust-checked, etc. During this time, you can continue working, or you can keep an eye on the process (have you ever watched paint dry?). 6. If you haven't been watching the update, scroll back up to the start of the process and scan for any update notes (usually package specific and requiring some action on your part) or warnings. Often, warnings concern changes in default configuration files which conflict with the configuration files you currently have on your system: instead of overwriting your custom configuration files, pacman is kind enough to install the file with a .pacnew suffix and even goes so far as to notify you of the change! I highly recommend you have pacman-color installed, because it highlights Warning messages in yellow, making them easy to spot while scrolling through the update log. 7. Although it isn't mandatory, I recommend you just reboot at this point: there is a good chance something (especially the kernel itself) has been update which unloaded some commonly used modules. I like to think that Arch boots quick enough that an update isn't even an inconvenience in most cases. 8. Continue using your system contently until you decide to update again. What's the process like on Gentoo? I'm really interested to know how most people go about their system updates and how long the updates usually take.[/QUOTE] I just use a few simple commands: `eix-sync` to sync the portage tree and update the eix cache. `emerge -uDNav` to update (also resolve any hard blocks that may occur). `emerge --dep-clean -a` to remove obsolete packages. `revdep-rebuild` to fix any libraries that were broken by the previous command. It takes anywhere from 1-4 hours to complete depending on how many packages need updating.
I really respect the Gentoo philosophy of compiling from source, but I'm far too impatient for such things. In the cases where library dependencies are not satisfied in binary packages, I yearn for source to compile from, but in the case of already FOSS software I prefer to let Arch compile my packages remotely. In cases like the raspberry pi, where binary package updates are painfully slow as it is, a distro which is entirely compiled from source would be painful, unless you set up a local cross-compiler server which acted as a sort of proxy, but at that point you would be just as well to use a binary package manager anyway. Thanks for sharing how Gentoo is updated. Out of further curiosity, how many of those commands are aliased for you guys? I know in Arch I alias `sudo pacman-color` as `pacman` and `pacman -Syu` as `ud`.
[QUOTE=Niteshifter;39496974]I just use a few simple commands: `eix-sync` to sync the portage tree and update the eix cache. `emerge -uDNav` to update (also resolve any hard blocks that may occur). `emerge --dep-clean -a` to remove obsolete packages. `revdep-rebuild` to fix any libraries that were broken by the previous command. It takes anywhere from 1-4 hours to complete depending on how many packages need updating.[/QUOTE] You forgot the step of searching the forums for build errors.
[QUOTE=Rayjingstorm;39498405]Thanks for sharing how Gentoo is updated. Out of further curiosity, how many of those commands are aliased for you guys? I know in Arch I alias `sudo pacman-color` as `pacman` and `pacman -Syu` as `ud`.[/QUOTE] These are the entirety of my aliases: [code]alias checktodos="grep -A 1 -B 1 -nr -e \"TODO\"" alias please=sudo[/code] I don't bother aliasing anything else for whatever reason. Edit: Now that I think about it, I [b]do[/b] have "--ask --verbose" in EMERGE_DEFAULT_OPTS, so I guess that counts [QUOTE=IpHa;39498561]You forgot the step of searching the forums for build errors.[/QUOTE] Never once had to do that.
[QUOTE=Rayjingstorm;39498405]I really respect the Gentoo philosophy of compiling from source, but I'm far too impatient for such things. In the cases where library dependencies are not satisfied in binary packages, I yearn for source to compile from, but in the case of already FOSS software I prefer to let Arch compile my packages remotely. In cases like the raspberry pi, where binary package updates are painfully slow as it is, a distro which is entirely compiled from source would be painful, unless you set up a local cross-compiler server which acted as a sort of proxy, [b]but at that point you would be just as well to use a binary package manager anyway.[/b] Thanks for sharing how Gentoo is updated. Out of further curiosity, how many of those commands are aliased for you guys? I know in Arch I alias `sudo pacman-color` as `pacman` and `pacman -Syu` as `ud`.[/QUOTE] Not if you need specific CPU/MEM features or USE flags enabled/disabled. Then you'd set your system up to cross-compile. You might do both with Sabayon, both Source and Binary package management, but optimized for speed.
[quote=Phoronix]It seems thanks to the increasing market-share of Android devices and the rise of Linux on the desktop thanks to the many commercial Linux gaming initiatives that have been shared in recent months, Microsoft is being forced to take a serious look at Linux and a meaningful look at releasing their popular Office software for Linux in 2014.[/quote] [img]http://horobox.co.uk/u/flubbernugget-_1360263278.png[/img]
Rejoice! [url=http://blog.documentfoundation.org/2013/02/07/the-document-foundation-announces-libreoffice-4-0/]LibreOffice 4[/url] added functionality to export calc charts as image files! I've been taking a screenshot and cropping in gimp to get graphs into my lab reports, but no longer!
[QUOTE=Rayjingstorm;39511696]Rejoice! [url=http://blog.documentfoundation.org/2013/02/07/the-document-foundation-announces-libreoffice-4-0/]LibreOffice 4[/url] added functionality to export calc charts as image files! I've been taking a screenshot and cropping in gimp to get graphs into my lab reports, but no longer![/QUOTE] I really like Libreoffice4.0.0 really liking the increased .docx compatibility.
[QUOTE=Rayjingstorm;39511696]Rejoice! [url=http://blog.documentfoundation.org/2013/02/07/the-document-foundation-announces-libreoffice-4-0/]LibreOffice 4[/url] added functionality to export calc charts as image files! I've been taking a screenshot and cropping in gimp to get graphs into my lab reports, but no longer![/QUOTE] I'm really interrested to try out the Persona thing, but everything in the 4.0 release is so exciting! I doubt it'll be out on my distro before next monday (17th).
So i have debian in my file server. The problem i have is slow transfer speed[B] (15-30Mb/s)[/B] while i copy files inside the server folder to folder or disk to disk example. However, when i copy files from my desktop to my server trough Samba, transfer speed is about [B]70-110Mb/s.[/B] So what is limiting the internal copy speed of my debian server? Oh and also, if i copy files between my desktop and pc trough FTP i also only get 15-30Mb/s.
[QUOTE=T3hGamerDK;39517226]I'm really interrested to try out the Persona thing, but everything in the 4.0 release is so exciting! I doubt it'll be out on my distro before next monday (17th).[/QUOTE] Doesn't appear as though Arch has the new version up yet, but I hope it is before my next lab is due next thursday; I'll just use my old method and swap it out if the repos update in time.
Sorry, you need to Log In to post a reply to this thread.