Arch Way !

[securitybreach]

Josh,Without Internet access, what is the best way to post those 2 files?Thanks,Ian

To manually start dhcp, issue this command as root:

dhcpcd eth0

This should be your /etc/rc.conf entry for networking:

eth0="dhcp"INTERFACES=(eth0)ROUTES=(!gateway)

[ichase]

JoshWhen running

dhcpcd eth0

I get the same exact error as mentioned prior.I went ahead and jotted down the NETWORK section of my /etc/rc.conf

#NETWORKS=(main)eth0="eth0 1192.168.1.5 netmask 255.255.255.0 broadcast 192.168.0.255"eth0="dhcp"INTERFACES=(eth0)gateway="default gw 192.168.1.1"ROUTES=(!gateway)

My /etc/resolv.conf was only 4 short lines total for the entire file:

#Generated by dhcpcd from eth0# /etc/resolv.conf.head can replace this lineNAMESERVER 192.168.1.1# /etc/resolv.conf.tail can replace this line

I keep going back to the tutorial to see if there was something I missed, but can't seem to find it. I am certain it has to be something obvious. I am still quite surprised that it did not automatically detect the network with the ethernet cable plugged in. But don't think for a minute that I am not still very excited about having Arch set up and running. I am continuously adding notes to my "Linux" binder. I am thinking that I may have to start a new binder just for Arch notes. :thumbup:Thanks Josh and thanks to anyone else that pipes in with advice. :)Hope you are all having a great start to your weekend!Ian

[securitybreach]

Well the problem is you have 2 networking entries when only one should be commented out (# in front of):

#NETWORKS=(main)eth0="eth0 1192.168.1.5 netmask 255.255.255.0 broadcast 192.168.0.255"eth0="dhcp"

Should be:

#NETWORKS=(main)#eth0="eth0 192.168.1.5 netmask 255.255.255.0 broadcast 192.168.0.255"eth0="dhcp"

The top entry is only used it you use a static IP, otherwise the second line is used.

[securitybreach]

Now to confuse you even more, here is my entry for a static IP:

eth0="eth0 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255"#eth0="dhcp"INTERFACES=(eth0)gateway="default gw 192.168.1.1"ROUTES=(gateway)

Notice the differences?

[securitybreach]

Crap, I just noticed you did not configure any servers in /etc/pacman.d/mirrorlist:

(no servers configured for repository)

You have not repository mirrors, that is why you are getting the error. To make sure you online, just try to:

ping google.com

This explains it https://wiki.archlinux.org/index.php/Beginn....d.2Fmirrorlist or you could just copy mine. These are the ones I have uncommented out in /etc/pacman.d/mirrorlist:

Server = http://hpc.arc.georgetown.edu/mirror/archl...o/os/$archServer = http://mirror.yellowfiber.net/archlinux/&a...o/os/$archServer = http://mirror.ece.vt.edu/archlinux/$repo/os/$archServer = http://ftp.osuosl.org/pub/archlinux/$repo/os/$archServer = http://mirror.rit.edu/archlinux/$repo/os/$archServer = http://distro.ibiblio.org/pub/linux/distri...o/os/$archServer = http://lug.mtu.edu/archlinux/ftpfull/$...o/os/$arch

You have to have some of the mirrors uncommented in order to install a package. Just uncomment the US mirrors, then finish running the commands from my tutorial.

[ichase]

Crap, I just noticed you did not configure any servers in /etc/pacman.d/mirrorlist:You have not repository mirrors, that is why you are getting the error. You have to have some of the mirrors uncommented in order to install a package. Just uncomment the US mirrors, then finish running the commands from my tutorial.

Josh,Ok, I figured out what the problem was. I had previously gone in and uncommented all of the state side mirrors. I then went ahead and made a backup of my mirrorlist. (mirrorlist.backup) Not sure exactly how I did what I did, but when I went to /etc/pacman.d and typed ls, i saw both files. When I typed

nano mirrorlist

It was blank????When I selected

nano mirrorlist.backup

There was my complete mirrorlist. I just saved this as mirrorlist and over wrote the existing blank file. All is good. Only had a small window to work on the lappy this weekend so It's still a work in progress. Started running into a hickup loading my ATI video. I have guidance from the wiki and will be working on that next.Keep you posted.Thanks and all the best,Ian

[securitybreach]

Sounds good Ian!!!

[ichase]

Well just wanted to give an update and ask a couple of simple questions. I have my KDE desktop environment up and running (once I realized I had to go into my /etc/inittab and uncomment a couple of things) plus I got my ATI video card working.Well the next thing I am trying to do is get my wireless working. I was able to go into my Mandy home directory and snatch the firmware for my wireless card.Started to extract the first tarbal

~$ tar xfvj broadcom-wl-4.150.10.5.tar.bz2

Extracted fine.I then type in:

~$ sudo b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o

I get sudo: command not found? I thought Arch came with Sudo. No big deal, so I type in "su", put my password in then I getb43-fwcutter not found??? I thought when I did the initial install that this was in the base-devel? Maybe because I did not have my network setup I may have skipped it.Well, then I thought, I have b43-fwcutter (the executable file)in Mandy so I snatched and moved it to my /home/ichase I then copied it to /lib/firmware. Now I get when trying to run

[root@myhost ichase]# b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o

I get

bash: b43-fwcutter: command not found

I then cd to /lib/firmware and type -ls and alas....I see b43-fwcutterIn essence, I am trying to set this up pretty much the same way I set up 3 other distros. I also realize that some distros do things different. I also read the wiki in regards to wireless and for the most part it seems pretty much the same way I set my other distros up.I am guessing the best thing to do now is login as root and pacman -S b43-fwcutter when I can't get back on ethernet. :)Hey, but I have a cool looking Arch KDE desktop now!!! Will submit an image of it when I get wireless up and running and install FF. Still remains a work in progress.All the best,Ian

[securitybreach]

Well to begin with, why would you edit /etc/initab instead of ~/.xinitrc? It is much safer and easier to just edit your user's ~/.xinitrc file than to make system wide changing. First:

cp /etc/skel/.xinitrc ~/

Then open the file and uncomment/add whatever window manager you want. For example, using the default .xinitrc you would remove the would change the kde line from:

#!/bin/sh## ~/.xinitrc## Executed by startx (run your window manager from here)# exec gnome-session# exec startkde# exec startxfce4# ...or the Window Manager of your choice

to

#!/bin/sh## ~/.xinitrc## Executed by startx (run your window manager from here)# exec gnome-session exec ck-launch-session startkde# exec startxfce4# ...or the Window Manager of your choice

You can also add other startup apps/daemons for your window manager this way. Here is my for example:

╔═ comhack@Cerberus 11:53 AM ╚═══ ~-> cat .xinitrc#!/bin/sh## ~/.xinitrc## Executed by startx (run your window manager from here)#exec ck-launch-session gnome-sessiongnome-settings-daemon &xscreensaver -no-splash &numlockx &nitrogen --restore &xsetroot -cursor_name left_ptrudiskie &.xmonad/conkyscript &exec ck-launch-session xmonadpidof mpdscribble >& /dev/nullif [ $? -ne 0 ]; then	  mpdscribble &  fi

As far as the broadcom driver, you are going about it wrong. Follow the Arch wiki entry in order to setup the card https://wiki.archlinux.org/index.php/Broadcom_BCM43XX I have used this on a few machines with the same chipset and it works flawlessly.

[ichase]

Well to begin with, why would you edit /etc/initab instead of ~/.xinitrc? It is much safer and easier to just edit your user's ~/.xinitrc file than to make system wide changing.

Because I followed the directions in the Arch wiki about installing KDE in Arch.

Starting KDM through /etc/inittab [preferable] Edit /etc/inittab and comment out: #id:3:initdefault:[...]#x:5:respawn:/usr/bin/xdm -nodaemonThen uncomment: id:5:initdefault:[...]x:5:respawn:/usr/bin/kdm -nodaemonNote: In both methods KDM loads Xorg automatically.

I followed your advice and edited the xinitrc file IAW your guidance. Booted fine. Should I go back into my inittab file and change everything back to the way it was?Thanks for your help as always Josh,Ian Edited February 1, 2011 by ichase

[ichase]

Forgot to ask on my last post. Why can't I use "sudo" ? I guess I need to pacman -S sudo ??Thanks, :)Ian

[securitybreach]

Forgot to ask on my last post. Why can't I use "sudo" ? I guess I need to pacman -S sudo ??Thanks, :)Ian

This will help you get it up and running https://wiki.archlinux.org/index.php/Sudo

Because I followed the directions in the Arch wiki about installing KDE in Arch.I followed your advice and edited the xinitrc file IAW your guidance. Booted fine. Should I go back into my inittab file and change everything back to the way it was?Thanks for your help as always Josh,Ian

I would just leave it alone since startx would read the ~/.xinitrc file first but it is up to you.I would personally load KDM via the daemons line in /etc/rc.conf and comment it out in inittab. https://wiki.archlinux.org/index.php/Displa...r#Daemon_method

[ichase]

Josh,Before I edit my sudoers file, I am graciously asking that you take a look at my proposed:

## Sample /etc/sudoers file.## This file MUST be edited with the 'visudo' command as root.## See the sudoers man page for the details on how to write a sudoers file.#### User alias specification##User_Alias	FULLTIMERS = ichase### Runas alias specification##Runas_Alias	OP = root, operator### Host alias specification##### Cmnd alias specification##Cmnd_Alias	DUMPS = /usr/sbin/dump, /usr/sbin/rdump, /usr/sbin/restore, \			/usr/sbin/rrestore, /usr/bin/mtCmnd_Alias	KILL = /usr/bin/killCmnd_Alias	PRINTING = /usr/sbin/lpc, /usr/bin/lprmCmnd_Alias	SHUTDOWN = /usr/sbin/shutdownCmnd_Alias	HALT = /usr/sbin/halt, /usr/sbin/fasthaltCmnd_Alias	REBOOT = /usr/sbin/reboot, /usr/sbin/fastbootCmnd_Alias	SHELLS = /usr/bin/sh, /usr/bin/csh, /usr/bin/ksh, \			 /usr/local/bin/tcsh, /usr/bin/rsh, \			 /usr/local/bin/zshCmnd_Alias	SU = /usr/bin/suCmnd_Alias	VIPW = /usr/sbin/vipw, /usr/bin/passwd, /usr/bin/chsh, \			   /usr/bin/chfn### Override built-in defaults### Defaults specificationDefaults			   syslog=authDefaults	 ichase timestamp_timeout=0, rootpw# Reset environment by defaultDefaults			env_reset# Set default EDITOR to nanoDefaults		 editor=/usr/bin/nano, !env_editor### User specification### root and users in group wheel can run anything on any machine as any userroot		ALL = (ALL) ALL%wheel		ALL = (ALL) ALL# ichase may run anything on machineichase		ALL = (ALL) ALL# anyone can mount/unmount a cd-rom on the machines in the CDROM aliasALL		CDROM = NOPASSWD: /sbin/umount /CDROM,\		/sbin/mount -o nosuid\,nodev /dev/cd0a /CDROM

Hope I am not being a royal pain in the @$$ I know I am starting to feel like one. Thanks again,Ian

Edited February 2, 2011 by ichase

[securitybreach]

Josh,Before I edit my sudoers file, I am graciously asking that you take a look at my proposed:Hope I am not being a royal pain in the @$$ I know I am starting to feel like one. Thanks again,Ian

Not at all, I will take a look at it.

[securitybreach]

I have only used sudo a couple of times when I was working on an Ubuntu machine, so I am not an expert on sudo. After comparing your /etc/sudoers with the wiki and a sample config: http://www.gratisoft.us/sudo/sample.sudoers , your configuration file looks good to me.

[ichase]

I appreciate you looking at it. :)I have used sudo in other distros but never had I had to configure it.Still working on trying to get the wireless working. Not having much luck there. I had been using an updated driver to the one mentioned in the wiki and substituted it instead of the one they have. But when I try to run b43-fwcutter to the wl_apsta.o file I get an error stating b43-fwcutter does not support this driver. (I'm paraphrasing because I don't have my lappy with me today) but it's something along those lines.So what my next plan is, get rid of the current folder with the updated driver files and DL the one mentioned in the wiki. Can't undertand why this driver worked on 3 other distros but not in Arch? But my thought process is, the more I screw up the more I learn by fixing the problem. If it worked with out a problem I probably would not remember how I did it if I had to do it again. :)Thanks again,Ian

[securitybreach]

I appreciate you looking at it. :)I have used sudo in other distros but never had I had to configure it.Still working on trying to get the wireless working. Not having much luck there. I had been using an updated driver to the one mentioned in the wiki and substituted it instead of the one they have. But when I try to run b43-fwcutter to the wl_apsta.o file I get an error stating b43-fwcutter does not support this driver. (I'm paraphrasing because I don't have my lappy with me today) but it's something along those lines.So what my next plan is, get rid of the current folder with the updated driver files and DL the one mentioned in the wiki. Can't undertand why this driver worked on 3 other distros but not in Arch? But my thought process is, the more I screw up the more I learn by fixing the problem. If it worked with out a problem I probably would not remember how I did it if I had to do it again. :)Thanks again,Ian

Well it may have to do with the fact that Arch uses a more current driver which could work better with the 2.6.37 kernel. I am just guessing but I have found that it is much easier to follow the wiki's suggestions to setup drivers and other things.

[abarbarian]

Well I have a Arch running again. Only a base install up to being able to boot in and log on as root. Still a load more to do but it should not take too long.

Ha I seem to have temporarily lost my Windows, might need to probe around for the answer.

 

[securitybreach]

Glad to hear it man, welcome back to sanity

[abarbarian]

Yeah I am just in rehab at the moment, still a ways to go.

 

Puzzled why Windows disapeared !!!!

 

I put W7 on sda first and it booted and ran ok.

 

Put Arch on sdb and put grub on sdb. Now Arch boots ok but w7 is lost.I disconected sdb and tried to boot sda but it tells me there is a missing os.

 

Did grub mess around with the MBR on sda even though I put it on sdb ??

 

[amenditman]

Yeah I am just in rehab at the moment, still a ways to go.

 

Puzzled why Windows disapeared !!!!

 

I put W7 on sda first and it booted and ran ok.

 

Put Arch on sdb and put grub on sdb. Now Arch boots ok but w7 is lost.I disconected sdb and tried to boot sda but it tells me there is a missing os.

 

Did grub mess around with the MBR on sda even though I put it on sdb ??

 

When doing that kind of install, I always disconnect the inactive hard drive so that it stays unaltered. You could try the ms-sys script on Parted Magic, it has a good success rate of restoring MS MBR.

[securitybreach]

Did grub mess around with the MBR on sda even though I put it on sdb ??

 

Well even if you did put it on the wrong mbr, it should not of touched your windoze partition.

[abarbarian]

Ta amenditman. That has been my practice in the past but for some reason I did not do it this time.

 

Still I am up and running. Have a butt ugly Window Maker and terrible font in FF and managed to get XMarks to sync so I have all my book marks.

 

So hello Arch Way, lets Rock and Roll.

 

Mind you Josh's out of date and riddled with spelling mistakes install tutorial did not really hinder the march forward at all Guess he is too busy over at G+ to keep up to date with the fast pace of Arch.

 

I did try out that EvoLution install cd. I would have got to a working desktop in less than a hour using it.However I seemed to have made a slip up somewhere as I ended up with a black scree instead of a desktop. I chose Awesome which might have been a mistake as I know nothing about it and maybe a black screen is all you get till you configure it, it baffled me so I let it drop. Did think about using Enlightenment but was not sure if it is now in a stable state or if as before it still has quirks.Anyways I needed a solid stable set up and can not afford experimentation at the moment. Pretty dissapointed that the devs did not include Window Maker as it is fast lightweight and pretty bomb proof

All in all as a easy way to start experimenting with Arch I recon EvoLution is not a bad path to follow for a inexperienced peguin.

 

One thing I did notice as I went through the install. I came across a "sudoers" file already set up. So me question is does EL automatically set up "sudo" or is that file just a default file for some other purpose ?

I never use or set up sudo and can not remember seeing a sudoers/sudo related file on my systems before. So was just wondering why it was there ?

 

P.S. was just pulling yer leg Josh.

[abarbarian]

Did grub mess around with the MBR on sda even though I put it on sdb ??

 

Well even if you did put it on the wrong mbr, it should not of touched your windoze partition.

 

That is what I thought too.

 

I got me Windows running first and know everything was ok so where has it gone. I recon it is justy a tweak that is needed. As W7 is just for gaming it is not needed right now. Me Arch is back so I can take me time bug hunting. First important step is doing a full backup before I fiddle too much and end up with a E.Arch install again.

[securitybreach]

I did try out that EvoLution install cd. I would have got to a working desktop in less than a hour using it.However I seemed to have made a slip up somewhere as I ended up with a black scree instead of a desktop. I chose Awesome which might have been a mistake as I know nothing about it and maybe a black screen is all you get till you configure it, it baffled me so I let it drop. Did think about using Enlightenment but was not sure if it is now in a stable state or if as before it still has quirks.Anyways I needed a solid stable set up and can not afford experimentation at the moment. Pretty dissapointed that the devs did not include Window Maker as it is fast lightweight and pretty bomb proof

All in all as a easy way to start experimenting with Arch I recon EvoLution is not a bad path to follow for a inexperienced peguin.

 

One thing I did notice as I went through the install. I came across a "sudoers" file already set up. So me question is does EL automatically set up "sudo" or is that file just a default file for some other purpose ?

I never use or set up sudo and can not remember seeing a sudoers/sudo related file on my systems before. So was just wondering why it was there ?

 

P.S. was just pulling yer leg Josh.

 

There is a sudoers file by default on Archlinux but it is not enabled. As far as Awesome, yes, you have to configure it as it is a tiling window manager and is very minimal.

 

BTW Enlightenment has been stable for a long time now but I prefer i3 (another tiling environment)

[securitybreach]

Also, did you go through all the menu items? Like Configure Base, Generate Fstab, Set Locale, graphic drivers, etc.

[securitybreach]

The reason I ask is because I just did an install in virtualbox with awesome and it should look like this by default:

 

[securitybreach]

D*mmit, your right. Sudo is setup by default. I will have to mention it to the devs(I chat with them on G+).

 

I also mentioned WindowMaker to them as well.

[abarbarian]

The reason I ask is because I just did an install in virtualbox with awesome and it should look like this by default:

 

 

Looks neat. Nope mine did not look like that, just had a black screen. I did take it slow and gentle but I guess I made a slip somewhwere.Shame it would have been fun trying a new desktop. :'(

 

D*mmit, your right. Sudo is setup by default. I will have to mention it to the devs(I chat with them on G+).

 

I also mentioned WindowMaker to them as well.

 

Great that you mentioned WM, be super if they gave it some love.

[securitybreach]

The reason I ask is because I just did an install in virtualbox with awesome and it should look like this by default:

 

 

Looks neat. Nope mine did not look like that, just had a black screen. I did take it slow and gentle but I guess I made a slip somewhwere.Shame it would have been fun trying a new desktop. :'(

 

 

Great that you mentioned WM, be super if they gave it some love.

 

You could also try it out in VirtualBox as well.