You are not logged in.

#26 2010-04-16 09:17:19

chpln
Member
From: Australia
Registered: 2009-09-17
Posts: 361

Re: Migrating from Windows to Linux

CleanCode wrote:

I need also notes/tasks [to do list] on desktop. What do you use? Conky script? Kde/Gnome applet?

Since you're interested in using Emacs anyway, I highly recommend org-mode.

Last edited by chpln (2010-04-16 09:17:36)

Offline

#27 2010-04-16 14:30:33

tankmcp
Member
From: Tulsa, OK
Registered: 2007-09-17
Posts: 54

Re: Migrating from Windows to Linux

I have used Openoffice for several years. I find it works well with m$ documents and presentations. My personal experience with Ooo/M$ spreadsheets is limited to simple usage, though others I have asked tell of very few problems.

Offline

#28 2010-04-16 15:28:23

A Future Pilot
Member
Registered: 2008-10-17
Posts: 120

Re: Migrating from Windows to Linux

If you're familiar with FileZilla already, I do believe it's in the official pacman repository. You can just

Pacman -Sy filezilla

and it should install.

Glad you're coming to Arch! Hope you like it!

Offline

#29 2010-04-16 20:14:01

pyther
Member
Registered: 2008-01-21
Posts: 1,395
Website

Re: Migrating from Windows to Linux

CleanCode wrote:

It isn't like hard drive space is scarce these days. Maybe for those that have a cap on their net connection, then I might see it.

Well, aren't gnome/kde apps slower than lightweight apps?

Depends on the app. For example I'm a heavy user of gnome-terminal, gcalctool, and use gedit occasionally and those load up nearly instantly. Granted it takes a bit longer on my netbook, but I don't mind waiting the initial 2-3 seconds it takes to load. Also once the libs are loaded the are cached in the ram for the most part, so they don't have to be reloaded.

Last edited by pyther (2010-04-16 20:14:16)


Website - Blog - arch-home
Arch User since March 2005

Offline

#30 2010-04-17 02:15:32

1LordAnubis
Member
Registered: 2008-10-10
Posts: 253
Website

Re: Migrating from Windows to Linux

CleanCode wrote:

3) Now applications:

Jabber (OpenPGP encryption) - Psi
Outlook - I like Kmail (Native OpenPGP support). Is it possible to have Kmail without whole KDE and with Openbox? Is Kmail fast?
Emacs, Nano - file editing (Emacs has steep learning curve so Nano is there only for emergency use.)
File manager - I am used to native Windows Explorer. But I would like to use efficient, productive tool (Emacs/Vim philosophy).
uTorrent - What torrent client is similar to uTorrent? I have such a great time with him.
FTP Client - I use FileZilla. What is you favourite in Linux?
Wifi Network settings - What can I use to have all my settings in system tray like at Windows?

1) Jabber(XMPP) - otr plugin for encryption (very secure) - Pidgin
2) nano/vim, kate/kwrite are good, there are lots of these
3) file manager - dolphin (you can do network stuff to, you can browse another machine's stuff via ssh, or your samba shares (if configured))
4) my personal favorite is ktorrent
5) ftp client - My favorite on linux is filezilla
6) i personally recommend wicd, especially if your connection changes a lot. if you connection never changes, than a auto commandline utility could be more efficient...

You can run any linux app (kde apps (use the qt toolkit), gnome apps (use gtk toolkit) python, etc... in openbox. openbox is light, as it only loads the window border, and anything you additionally customize.  kde, on the other hand, will load a desktop environment - settings, hotkeys, accessibility, all types of candy, and preload qt libraries and programs.
In the end, its very usable, and the best when it comes to polish.
Openbox is 100% stable, period. and its dam small, usability and polish are things you do yourself and quite frankly after a little config it can turn into a pretty easy to maintain machine thats just what you want.

Last edited by 1LordAnubis (2010-04-17 02:16:33)


Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw

Offline

#31 2010-04-18 18:56:50

CleanCode
Member
Registered: 2010-04-15
Posts: 17

Re: Migrating from Windows to Linux

Hello again after a day with Arch Linux,

ArchLinux is such a great OS experience.

But I've got one new question.
My laptop HP4510s contains 14e4:4315 which is supported from kernel 2.6.32+ [here]. I read also wiki so I decided to use AUR.

I added (b43 !b43legacy) to rc.conf and installed b43-git-tools and b43-newest-firmware.  Reboot and after that I turned on my wifi in BIOS and run Archlinux. Unfortunately my system freezes at loding modules or uvdev.

Before b43 installation my computer froze at uvdev loading also but when I turned off my wifi everything worked like a charm. I expected that after b43 installation everything will be fine. Where is the catch? Is it better to use manual b43 installation?

Last edited by CleanCode (2010-04-18 19:02:01)

Offline

#32 2010-04-19 09:23:21

CleanCode
Member
Registered: 2010-04-15
Posts: 17

Re: Migrating from Windows to Linux

My wifi is now working with WICD. But I can only use it with ACPI=OFF. Everything boots fine when I edit rc.conf and disable interfaces !eth0 !wlan0 but network isn't working. I am a little bit confused, because this is recommended settings in WICD wiki [disable interfaces]. Is there a possibility to enable these interfaces after successful boot?

Offline

#33 2010-04-19 10:09:45

hokasch
Member
Registered: 2007-09-23
Posts: 1,461

Re: Migrating from Windows to Linux

Not sure if I understood that one...
booting + wifi works with wicd and acpi=off?
booting works when interfaces are disabled in rc.conf (and no acpi=off), but then wicd won't work? Can you post rc.conf?

To bring up an interface after boot, use ifconfig. You should describe your problem in a new thread, since it makes more sense to have one thread-per-problem instead of one thread-per-person... wink

edit: didn't see you already opened a new thread...

Last edited by hokasch (2010-04-19 10:13:15)

Offline

#34 2010-04-19 10:14:33

CleanCode
Member
Registered: 2010-04-15
Posts: 17

Re: Migrating from Windows to Linux

hokasch wrote:

Not sure if I understood that one...
booting + wifi works with wicd and acpi=off?

Yes.

booting works when interfaces are disabled in rc.conf (and no acpi=off), but then wicd won't work? Can you post rc.conf?

Yes.

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Prague"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(b43 !b43legacy)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="skynet"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="dhcp"
eth0="dhcp"
INTERFACES=(eth0 wlan0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng hal !network wicd netfs crond)

To bring up an interface after boot, use ifconfig. You should describe your problem in a new thread, since it makes more sense to have one thread-per-problem instead of one thread-per-person... wink

I just did it, you're right. [link]

Last edited by CleanCode (2010-04-19 10:16:14)

Offline

#35 2010-04-19 12:13:15

mythus
Member
From: MS Gulf Coast
Registered: 2008-05-15
Posts: 509
Website

Re: Migrating from Windows to Linux

You need to do the following...
#eth0="dhcp"

INTERFACES=(!eth0 !wlan0)

as well. Otherwise wicd won't work. You see, wicd replaces the default method of network use, so you have to disable the default method in your rc.conf.


Legends of Nor'Ova - role playing community devoted to quality forum-based and table-top role play, home of the Legends of Nor'Ova Core Rule Book and Legends of Nor'Ova: Saga of Ablution steam punk like forum based RPG

Offline

#36 2010-04-19 12:19:19

Misfit138
Misfit Emeritus
From: USA
Registered: 2006-11-27
Posts: 4,189

Re: Migrating from Windows to Linux

mythus wrote:

You need to do the following...
#eth0="dhcp"

INTERFACES=(!eth0 !wlan0)

as well. Otherwise wicd won't work. You see, wicd replaces the default method of network use, so you have to disable the default method in your rc.conf.

QFT. The Arch 'network' daemon is a generic (and relatively versatile) way of managing network interfaces. Wicd is simply an alternative (and mutually exclusive) method which offers a simple GUI and is a bit more 'wireless-centric'.

Offline

#37 2010-04-19 12:20:04

CleanCode
Member
Registered: 2010-04-15
Posts: 17

Re: Migrating from Windows to Linux

Good news! Problem solved. I removed b43 and used [BCM4312 Wiki Page]. It is working like a charm. I don't know why b43 did'nt work, but I am satisfied Archlinux customer now. Thank you for your time and effort.

This topic actually might help to a lot of people. There are really many desperate 4510's owners out there.

Boot with acpi=off and use [BCM4312 Wiki Page]. That is my solution. B43 didn't work for me.

Last edited by CleanCode (2010-04-19 12:30:59)

Offline

#38 2010-04-20 07:36:56

sonoran
Member
From: sonoran desert
Registered: 2009-01-12
Posts: 192

Re: Migrating from Windows to Linux

If you haven't found it already, this is the place to look for openbox themes:
http://box-look.org/index.php?xcontentmode=7402

Offline

#39 2010-04-20 09:31:40

wizulis
Member
From: Riga, Latvia
Registered: 2010-04-19
Posts: 27

Re: Migrating from Windows to Linux

CleanCode wrote:

Boot with acpi=off and use [BCM4312 Wiki Page]. That is my solution. B43 didn't work for me.

i have an emachine with bcm4312 .. broadcom-sta is a completely different driver. But has problems with 2.6.33. I updated and compiled it, it loads fine and everything, but it wont connect to wpa wireless. Everything else works for me.So watch out, it may be a problem for you too, and wait for the 2.6.33 support for the driver, as developers of it supports it only up to 2.6.32 kernel.

Offline

Board footer

Powered by FluxBB