What is Arch Linux?

The below link is a wiki page trying to describe what is Arch Linux. There is no official written document, most likely will never happen keeping Arch open for future possibilities. It is a collection of quotes from Arch Linux Forum and other user discussions commonly said by the "old timers". Currently there are three ongoing documents:
What is Arch Linux - general introduction.
The Arch Way - priciples & philosophy, user comments, and pros & cons.
Crux vs. Arch - difference between Crux Linux and Arch Linux.
Wiki page:
http://wiki.archlinux.org/index.php/ArchLinux

you dont even need a proper desktop environment, thats part of the reason i like arch so much, you can use ~/.xinitrc as your own personal desktop environment.
just put what you want in your ~/.xinitrc
this is mine
xbindkeys &
lxde-settings-daemon &
xfdesktop &
xfwm4 &
xfce4-panel &
exec ck-launch-session startlxde
i have the minimal lxde install (just lxde-common, lxde-settings-daemon & lxsession-lite + lxapperance for my themes) so all my settings like themes etc... are loaded on boot then i just added the panel i wanted, the window manager i wanted etc...
if you want a fast minimal install with only the apps you want then do something similar, load somekind of settings manager so all your settings are loaded every time you boot then pick and choose you favorite panel, window manager etc...

Similar Messages

What will Arch Linux 1.0 become?

I was reading through earlier discussions searching for information about the aims of AL but could not find more what is already said in the documentation.
Current version is 0.4. I am curious to know what will 1.0 become. Is it a bug free version with the latest applications only or something more?
I am not only asking due to my curiosity but wanting to know what I (we users) can expect from AL. Is there anything I/we (if anyone is interested) can help AL with the same motive what was said by Judd Vinet when getting something for free: ".... and to give a little something back to the free software community, since I've taken so much."
Here I am not speaking about financial support but other things what may help achiving version 1.0 into a successful distro.

apeiro wrote:What do you (the users) expect to see from a 1.0 release of Arch Linux? Besides general refinements in packaging/documentation/installation/scalability/etc, what would you like to see?
Before listing "what I want to see" (next post.... I have to think about it), I support several ideas suggested by Jk. I asked him (private message) to explain the technical terms I was not familiar. Here below I have copied points I liked including his description (for others who are not familiar with the terms) and few additions:
- Package rollback in pacman --> "rollback"???
Jk> package rollback means that if an upgrade of a package fails it'll reinstall the old package back.
Within same content, when packages are upgraded (successfully) current config files should be intacted. Example, during apache upgrade current hppd.conf file remain as it is and the new upgraded file is renamed. Its upto the users to update manually.
- Real sandbox building of packages ---> "sandbox"???
Jk> package building to be in a safe environment, ie without the possibility of it touching stuff in the arch installation.
- support for virtual packages ---> how???
Jk> For example bzflag, it depends on OpenGL, but OpenGL can be delivered by several different pieces of software, like MESA or the NVIDIA drivers. Such packages should be able to have a "provides='OpenGL'" argument in them, so a user can choose which one of them to install.
- Menuing system (like Debian's) ---> I am not sure what you mean??
Jk> When you install a package in debian, the menus in the various window managers are automatically updated.
- Package hold feature
I would suggest also to provide a short description about the package and what it does. Also size of the packages (good to know when downloading with 56k modem).
- Possibility to build a custom kernel on install
All Win4Lin users will be happy with this feature . I suggest to include the win4lin patch file.
- Better installation system
I would not suggest to change too much from what it is to keep it simple. But instead designing the kernel and system files to install on it's own all basic stuff (modules) and configs.... internet connection, sound, pcmcia cards, hardware, etc. What I really would like to have is an autodetect recognition engine to run all common hardwares same as what RedHat, SuSE and Mandrake do.
- i586 support
This is very essential if AL is looking forward to have larger number of users. Africa, Mauritius, India and South East Asia what are my working fields (as a social worker), i586 is more common than i686.

Arch Linux Gallery

I am proud to present the re-opening of the new Arch Linux Gallery!
The Arch Linux Gallery is a site dedicated to screenshots of (guess what?) Arch Linux. It is meant to be a repository for screenshots, configs, artistic creations, and anything else Arch Linux-related.
When registering, zenphoto will provide you with your own personal album to which you can upload images and configs.
The only caveat is that, for now, it only supports .txt for text objects. So when uploading configs, they should be of .txt extension. Extensions need to be added, and I'm not sure of all the extensions that will need to be added, so if you want to request an extension to be added please post here and let me know.
Gallery searching, ie. filtering for only Openbox, is tag-driven, so make sure to tag photos with relevant information. Once some content starts being uploaded I can begin to create some dynamic albums of common content. I also plan to have a dynamic album for each month (like the screenshot threads) but I still need to figure out how to make that possible.
Special thanks to dennizjov who provided the server and domain, Ghost1227 for the wonderful logo, and the zenphoto devs, an amazing piece of software found over at http://www.zenphoto.org/
Here's the link, and have fun!
http://www.archlinuxgallery.com/
Last edited by kagutsuchi713 (2009-10-24 00:47:38)

Is nothing being displayed my fault or the site's fault?
I go to gallery, and it lists some names with question mark looking graphics beside them. Then I click the name, and it comes to a page that looks like I should be expecting to see a picture but has nothing.
Oh, and if I click archive after clicking a name, I see:
Notice: Undefined variable: typeGallery in /home/web29205/domains/archlinuxgallery.com/public_html/themes/arch/archive.php on line 14
Either way though, thanks for picking this up and running with it. It looks like a great idea!

What is the significance of the "Arch" in Arch Linux?

Why is this distribution called Arch Linux? What does the "Arch" part mean? Surely there must be a reason, for the developers could have easily named this distribution "Bridge Linux" or "Trapezoid Linux" for that matter.

MkFly wrote:
http://web.archive.org/web/200206050619 … rg/faq.php
[Q] Why the name Arch Linux?
[A] From dictionary.com:
arch
adj.
1. Chief; principal: their arch foe.
2. Mischievous; roguish: an arch glance.
I came across the well-known term "arch-enemy" in a book and clued in that "arch" means "the primary", "the principal", the one that comes first among others. Far from true with regard to Arch Linux perhaps, but I'm proud of it. Now, the second definition may or may not fit; I guess it depends on how you use your computer.
That covers definitions 1 and 3 above. Definition 2 applies in the case of Arch fanboys. Strangely they turn up more often on other forums than here.
But yeah, I should have added that Judd chose the name with the first adjective definition in mind.

What are the benefits of arch linux ?

What are the benefits of arch linux ?
default package management /software installation tool .

This posts fits perfect with my last 2 days xD
Cause a fan problem with arch, I tried to come back in a third partition to Debian. But 1 year and a half with arch makes me impossible to come back to debian because arch owns Debian in lots of ways (package management simplicity and filesystem structure, including this website, maybe the most important detail of this distribution, all info is on this page).
However, Debian's aptitude is extremely faster than pacman, that is the strongest point of Debian in front of Arch. Also I miss a detail on arch that I find indispensable: ICEWEASEL!
Can anyone get a package for archlinux of Iceweasel for me? I prefer weasels than foxs xD
Serious conclusion: Arch is better than Debian for me for the simplicity (pacman is simplier, the rc.conf file is a present of God, and this centralized and simple forum, the aur repository, the extremely great wiki (maybe gentoo wiki is a bit better) and the good organization of the homepage of archlinux.org makes this distribution for me the best for my purposes).
Now I believe I have to say something to you:
Thank you very much to all people that make possible this distribution, users, developers, etc...

What source base the Arch Linux Xorg build from?

I need a complete package of X windows system installed. No idea which directory the Arch Linux X11 install to.
Only find below with "find"
/usr/share/X11
/usr/lib/ghostscript/8.64/X11.so
/usr/lib/X11
/usr/include/X11
/var/cache/man/X11R6
/etc/X11
So I try to get some souce by http://xorg.freedesktop.org/wiki/Releases/7.4
I found its x server is only 1.5.1 and Arch Linux is 1.6.1(show when pacman -S xorg)
I really confused.
Actually what I need is pretty simple, need a xdm and xdm-configure to enable XDMCP so that I can remote connecct to X.
(I tried KDE and GNOME, it doesn't work because X)
Anybody can give me a clue?
Thanks very much,
Mike

tomk wrote:Please consult the wiki.
The Arch Wiki has become simply amazing.. Just thought I'd throw that out there.
Last edited by 10wattmindtrip (2009-06-23 18:29:24)

What's wrong with my Arch linux grub bootup/FSTAB? [Solved]

So ever since I did a fresh install of Arch Linux, every time it boots up and I select the Grub option it says "A start job is running for /dev/drive/" and shortly after it says timed out and continues onto the login screen as normal.
I have two drives, Windows is on the other one and on the Linux one I have just two partitions, root and swap.
I've tried to do a couple of things such as creating another grub option and setting the root to that ID however it still seems to be occurring. It seems to me that it keeps changing because sometimes when I boot it doesn't do it but it is very rare that it doesn't do the start job.
How can I permanently make the GRUB2 menu boot the correct drive and partitions, both root{ext4} and swap without it having to run a start job every time I boot it up?
Last edited by Developer (2015-04-09 19:02:42)

WorMzy wrote:
Note that sda,sdb,sdc... names are assigned on a first-come, first-served, per boot basis, so they are not ideal for use in your fstab. Instead, you should use UUIDs or labels.
https://wiki.archlinux.org/index.php/Pe … ice_naming
The problem is back, the drive names keep changing, how can I use UUID's for the fstab?
I saw something about UUID's above each drive name however, they were commented out. Do I replace the drive name part with the UUID for every drive, so for example:
/dev/sdb1 / ext4 rw,relatime,discard,data=ordered
to
UUID=b411dc99-f0a0-4c87-9e05-184977be8539 /home ext4 rw,relatime,discard,data=ordered
Or do I just uncomment the UUID part? which would leave me with something along the lines of:
UUID=b411dc99-f0a0-4c87-9e05-184977be8539
/dev/sdb1 / ext4 rw,relatime,discard,data=ordered

Dual boot Windows 7 (64) and Arch Linux (64) problems

Hello:
I am new to Arch Linux and just finished installing the 64bit on my laptop. It had a prebuilt Windows 7 (64) installed which I kept but split the hdd from 160Gb to 80Gb and 80Gb. I installed Arch there and set 4 partitions, all of them as Logical - a 64 MB ext2 /boot partition; a 512 MB swap partition; a 15 GB root partition; and the rest as my /home partition. My partitions look like this:
Disk Drive: /dev/sda
Size: 160041885696 bytes, 160.0 GB
Heads: 255 Sectors per Track: 63 Cylinders: 19457
Name Flags Part Type FS Type [Label] Size (MB)
sda1 Primary Unknown (27) 12889.02
sda2 Boot Primary NTFS 106.93
sda3 Primary NTFS [] 73915.11*
sda5 Logical Linux ext2 65.81*
sda6 Logical Linux 509.97*
sda7 Logical Linux ext2 15002.92*
sda8 Logical Linux ext2 57549.55*
The install was succesful(this was running from the core install cd) and I installed GRUB to my /boot but when I restarted it loaded Windows 7. I have used Knoppix USB disc to boot and see my Arch Linux install files and edited the /boot/gur/menu.lst file.
In Windows I installed EasyBCD 1.7.2 and tried to get NeoGrub bootloader working as a dual boot. I tried getting rid of the boot flag for Windows with cfdisk and setting it to my (Logical) sda5. That did not work. So far the only way I have booted into my Arch Linux install has been by going to the Live CD, choosing "Boot from Existing Linux Install" and editing the command files there.
root (hd0,4)
kernel /vmlinuz26 root=/dev/sda3 ro
initrd /kernel26.img
My goal is to get a dual boot working for Windows 7 and Arch Linux 64 and continue installing the Xorg and KDE to Arch. I just don't know what the problem is here. I don't mind reinstalling Arch if something went wrong, but I would like to keep my Windows running in order and add Arch on.
Any help would be greatly appreciated.

I ran the LiveCD and chose "Install to MBR hd0". I ended up with this:
setup hd(0,1)
Checking if "/boot/grub/stage1" exists.....yes
Checking if "/boot/grub/iso9660_stage1_5" exists.....yes
Running "embed /boot/grub/iso9660_stage1_5 (hd0,1)".....failed(this is not fatal)
Running "embed /boot/grub/iso9660_stage1_5 (hd16)".....failed(this is not fatal)
Running "install /boot/grub/stage1 d (hd0,1) /boot/grub/stage2 p (hd0,1) boot/grub/menu.lst".....failed
Error 31: File is not sector aligned
My entry for Windows into the menu.lst looks like this:
# (0) Arch Linux x64
title Arch Linux x64
root (hd0,4)
kernel /vmlinuz26 root=/dev/disk/by-uuid/3841273c-d91e-41d6-9dbf-716a15d03a01 ro
initrd /kernel26.img
# (1) Arch Linux x64
title Arch Linux x64 Fallback
root (hd0,4)
kernel /vmlinuz26 root=/dev/disk/by-uuid/3841273c-d91e-41d6-9dbf-716a15d03a01 ro
initrd /kernel26-fallback.img
# (2) Windows 7
title Windows 7
rootnoverify (hd0,0)
makeactive
chainloader +1

[GUIDE] How to get MapleStory working in Arch Linux

MapleStory is a free-of-charge, 2D, side-scrolling massively multiplayer online role-playing game developed by the South Korean company Wizet. Several versions of the game are available for specific countries or regions, and each is published by various companies such as Wizet and Nexon. Although playing the game is free, character appearances and gameplay enhancements can be purchased from the "Cash Shop" using real money. MapleStory has a combined total of over 50 million subscriber accounts in all of its versions. MapleStory North America (Global), for players mainly in North America and outside of East Asia, Southeast Asia and Europe, has over three million players.
In the game, players travel the "Maple World", defeating monsters and developing their characters' skills and abilities as is typical in role-playing games. Players can interact with others in many ways, such as through chatting, trading, and playing minigames. Groups of players can band together in parties to hunt monsters and share the rewards. Players can also join a guild to interact more easily with each other.
I am an avid mapler myself, however, I am also an avid archer! For some time, I have wanted to get MapleStory working on Arch Linux in some way, but nothing seemed to work. As you might have guessed by now, recently, while playing around with VirtualBox, I discovered a method to get MapleStory working on it! Though in this method you won't actually have MapleStory running on Arch Linux, you'll have it running on a VirtualBox Windows virtual machine, that is still pretty good compared to other people's experiences.
I hope there are at least a few maplers on this forum, and if there aren't, I hope that someone will port this post over to other Linux, or even MapleStory, forums. Anyways, let's begin.
1. Download and install a version of Virtual Box that is version 3.0+. The reason for this is that, only versions 3.0+ support an experimental DirectX Driver with 3D acceleration that is required for MapleStory to run.
2. Create a Windows Virtual Machine, add a hard disk to it, and install and update Windows on it(preferably Windows XP, as it uses less resources than other contemporary Windows installations).
3. Once you have done all you needed and wanted on that Windows installation, restart it, boot it into safe mode by holding F8 at the boot, and wait until the desktop is fully loaded.
4. After you are at the desktop, go to "Devices" at the top of the menu of the Windows virtual machine, and select "Install Guest Additions...". Wait until Guest Additions finishes installing, and when VirtualBox asks you if you want to mount the disk containing the Guest Additions on the virtual machine, say "Yes".
5. Run the main executable on the disk that doesn't have amd64 or x86 following its name. Follow the instructions it gives you, and when it asks you what components to install, make sure both of the boxes it shows you are checked.
6. After the install is completed, the virtual machine will restart. After it restarts, shut it down.
7. Congratulations! You now have DirectX installed on your VirtualBox virtual machine! Now you need to activate the "3D Acceleration", that enables it.
8. In the VirtualBox main window, make sure you have your machine with Windows selected. Then, click on "Machine", and then "Settings...", at the top. A new window should pop up. On the left hand side, click on the display panel, and in the new settings section, tick Enable 3D Acceleration. Click "OK", to save the settings.
9. Start your Windows virtual machine, install MapleStory just as you would on a normal windows computer, and run MapleStory.
Notes: This way of running MapleStory is slower than by running it normally, on a normal windows computer. Also, try to not interact with your Linux desktop while playing MapleStory, because this can cause HackShield to shut down MapleStory, due to the fact that it believes there is a hacking attempt.
If any of you port this guide to any other place on the web, please, credit me, neovaysburd5.
For any further questions or inquiries, this goes to all of you, please contact me at [email protected].
Last edited by neovaysburd5 (2009-08-19 16:51:31)

Alright, I've posted it in the wiki. I don't know if it meets the Arch Linux wiki standards, so if there is absolutely anything wrong with it, please fix it right away. Don't even ask my permission.
http://wiki.archlinux.org/index.php/MapleStory

[solved] Arch linux access point with multiple interfaces for the NAT

Hi, I have a router running Arch linux. It is connected via LAN (let's call it eth0) to the internet. It has a second LAN interface, eth1, and a wireless interface in master mode, wlan0.
Now, Everything works perfectly except providing network connectivity on eth1 and wlan0 simultaneously. I followed the guide in the "Internet share" wiki article and use dnsmasq/hostapd for the AP. It appears as if all traffic from the router is sent to the wlan0 interface, even if it came in through eth1 (for example, dhcp requests). I cannot really find information how to solve this. The words "bonding" and "iptables" are floating around, but there is not really an easy to understand tutorial for this.
What do I need to do to use both the eth1 and wlan0 interface (for different clients!) on my router?
Best regards, and thank you in advance
Jan Oliver
/e: This seems to be my problem: http://www.novell.com/support/kb/doc.php?id=7000318 How do I solve this using the usual iptables? (The way described in the article doesn't work: "RTNETLINK answers: No such process" errors.)
Last edited by janoliver (2013-09-25 22:24:53)

Or you could bridge eth1 and wlan0, and make dnsmasq bind/listen on that bridge...

Installing Multiple Operating Systems with grub and Arch Linux

NOTE: Please keep in mind that there are many different ways to achieve this same result using various loop and ramdisk methods, read this with a separate window to jot down your comments and suggestions... this is ongoing for me so any help would be appreciated!
Read the full article at Install Multiple Os without cds
This is my first post and I plan on making this topic an official HOWTO with www.tldp.org.
I have been into the computer security scene since 1990, but I realized that I had very little experience with the various LInux, Unix, and alternative Operating systems out there.
I have a CD-RW drive but being a struggling computer security researcher I had no money for blank cd-recordables. What follows is how I managed to install various operating systems on my computer (1 hard drive) without having to burn to a CD the ISO and then boot from that.
I first partitioned my 120GB harddrive into 10 partitions, the 2nd partition is a small swap and the last partition is extra large because it holds all the ISO images..
I then wrote a small shell script to automatically download (I love wget!) the following.
OpenBSD
IpCOP
Libranet
Arch-Linux
Fire
Local Area Security
Packet Master
Devil-Linux
FreeBSD
Knoppix
Helix
Gentoo
Yoper-Linux
NetBSD
RedHat
Slackware
The script also downloaded Installation manuals and md5 checksums.. (let me know if I should post... its pretty unsophisticated
I installed Slackware (personal favorite) on hda1 using my last blank CD-R, note that I do not have a separate boot partitino. (Should I?). I also installed grub on the MBR. I love grub, if you read through the man pages and all info you can find about grub, you can learn a whole lot. Grub has much more features and capability than lilo, even though lilo comes installed by default with slack.
I organize my kernel situation as follows... In my /boot directory, I mkdir KERNEL, CONFIG, MAP, INITRD and that is a good way for me to keep my kernels and everything organized.. Another good way is a separate dir for each new kernel.
Since Arch-Linux is a solid distro, I'll use that as a first example.
Here is the Arch-Linux section of my shell script
goge Arch-Linux
$w http://puzzle.dl.sourceforge.net/sourceforge/archlinux/arch-0.6.iso
$w http://unc.dl.sourceforge.net/sourceforge/archlinux/arch-0.6.md5sum
$w http://www.archlinux.org/docs/en/guide/install/arch-install-guide.html
md55
cat arch-0.6.md5sum
md5sum arch-0.6.iso
md55
The first thing to do is to mount the downloaded ISO image so we can use it as if it were an actual CD.
mount -t iso9660 -o ro,loop=/dev/loop0 cdimage /mnt/cdrom
Where cdimage= the ISO image. EX. /usr/local/src/ISO/Linux/Arch-Linux/arch-0.6.iso
This mounts the iso as /mnt/cdrom.
Next you need to copy /mnt/cdrom to a separate partition for the booting process. So mkfs.ext2 /dev/hda9. ( I prefer reiserfs or even XFS to ext but if you use something other than ext2 you could run into some problems because some of the installation kernels and initrds don't include support for reiserfs and so can't recognize the files. Although you could use mkinitrd to create a new initrd with reiserfs support, that might be pushin it IMO... I use the 9th partition consistently for this. I know there is a "right" way to copy the /mnt/cdrom files so everything stays the way it is supposed too, using tar or cpio, but I'm lazy so I just do cp -rp.
(What is the tar or cpio commands to copy with correct permissions etc??)
So you mount the 9th partition as whatever, say /mnt/hd and then copy the files. Now what?
Now edit your /boot/grub/menu.lst file to include the specific options to boot arch-linux installation.
A good idea is to find the isolinux.cfg file somewhere on the distro cd, this will tell you what to include in the menu.lst.
Here is the section in my menu.lst
title Arch Install
root (hd0,8)
kernel /isolinux/vmlinuz load_ramdisk=1 prompt_ramdisk=0 root=/dev/rd/0
initrd=/isolinux/initrd.img
This should be self-explanatory. The root (hd0,8) is pointing to partition 9. So the rest of the commands start from partition 9.
When you experience problems, remember you can always edit the grub boot options by typing 'e' and then edit the section. Also, a good idea is to include several variations in your menu.lst so you can easily try other ways to boot efficiently. And, remember to read up on all the installation guides that come with your distro, specifically, hard-disk installs.
There are special cases, Gentoo, has a semi-new compressed filesystem called squashfs. BTW, this is AWESOME, so check it out. It has to be compiled into the kernel, so some work is in order, but use this recompile to optimize your kernel. You can get the squashfs patch for almost any kernel. I use the latest stable 2.6 kernel. Squashfs is incredible and although I don't think you need it to install from ISO, you do need it to expand the livecd.squashfs filesystem that comes with the cd.
Heres a sample Gentoo section from my menu.lst
title Gentoo Install
root (hd0,8)
kernel /isolinux/gentoo root=/dev/ram0
initrd=/isolinux/gentoo.igz init=/linuxrc acpi=off looptype=squashfs loop=/livecd.squashfs cdroot vga=791 splash=silent
A nother' tip is the shell that is provided if you experience problems, typically busybox or ash. The key tools to get you going from here is mount and chroot. Sometimes you will need to manually create a simulated file system and then chroot into it. For instance, you might have to create boot, etc, bin, directories on the target partition.
I generally install each OS onto the next partition (careful of the logical partition) and add it to my menu.lst after install. A good idea is after installation, copy the kernel and initrd(if there is one) to the slackware(or whatever) boot partition on hda1. I copy kernels to /boot/KERNEL/ and initrd's to /boot/INITRD, then menu.lst is more organized...
You then need to add an updated section to your menu.lst (just comment out the install section for later)
Here is the finished arch-linux section from menu.lst
title Arch Linux 6
root (hd0,2)
kernel /boot/vmlinuz26 ro root=/dev/hdc3
This doesn't use my convenient boot/KERNEL/vmlinuz26 as you can tell by setting the root to partition 3.
***NOTE: Make a backup of MBR using dd and save to floppy, also backup the partition table to floppy, using cfdisk or parted. And boot disks (I use 1 with grub, and 1 with slack, and tomsbootdisk) will invariably come in handy. Tomsbootdisk is recommended, and make the grub boot disk when you install grub. install to floppy.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The final result after some fun experimenting, is when I boot, I have a cool grub boot screen come up with the option to boot into whatever OS I want, this is handy for multiple reasons. One good thing to do after this is to port scan and vuln scan each OS, after you update of course. Write this stuff down and you will know the weaknesses/strengths of the various OS's.
I can boot a custom Firewall, snort, or multiple honeypots using this procedure, as well as a graphical kde environment with a kernel optimized for graphics and my processor/architecture, or an environment devoted to forensics or even an environment suitable for programming.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
P.S. Some of the cooler alternative operating systems are BeOS 5, EOS, ER_OS, V2_OS, and my personal favorite Menuet. Menuet is 100% assembly graphical operating system that fits on a floppy. Its f'in money!
This should be a good enough example to get you started, this kind of thing should be learned and not just copied... Knowing how to do this stuff could prove to be exceptionally useful...

Start by reading all the articles built-in on your Mac - Help > Mac Help, search "printer sharing."
http://desk.stinkpot.org:8080/tricks/index.php/2008/04/how-to-print-to-a-cups-se rver-from-mac-os-x/
http://www.macosxhints.com/article.php?story=20080324224027152&query=share%2Bpri nter
http://members.cox.net/18james/osxprintersharing.html
http://ubuntuforums.org/archive/index.php/t-56940.html

[SOLVED] Ndiswrapper, NetworkManager 0.7 and 64-bit Arch Linux

Hi there!
I am having problems configuring my wireless card. I know I have to use Ndiswrapper, and this is what I have tried to do; however, it didn't go quite well.
This is rather odd because it worked perfectly in the 32-bit version of Arch Linux, but now it doesn't work.
So, here comes the code.
valandil ~ $ lspci | grep Network
0b:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)
I really use ndiswrapper and have already installed what I think is the proper driver (it seems that the list the official ndiswrapper site had has somehow disappeared.
sudo ndiswrapper -l
Password:
bcmwl5 : driver installed
device (14E4:4311) present (alternate driver: ssb)
Here's iwconfig:
valandil ~ $ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
I use NetworkManager 0.7 and have configured properly:
rc.conf:
# /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"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# 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.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="America/Vancouver"
KEYMAP="cf"
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=(fuse ndiswrapper fglrx !b44 !mii bcm43xx !snd_pcsp snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore !pcspkr)
# 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="cipher"
# 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
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(lo !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.1.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=(@stbd httpd !network syslog-ng netfs crond alsa hal dhcdbd networkmanager fam gdm)
hosts file :
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost cipher
# End of file
/etc/NetworkManager/nm-system-settings.conf:
GNU nano 2.0.9 File: /etc/NetworkManager/nm-system-settings.conf
[main]
plugins=keyfile
[keyfile]
hostname=cipher
I hope you can solve this problem; wireless is really crucial.
Thanks for any help,
Last edited by valandil (2012-05-02 18:27:09)

Alleluia!!!
I think I will write a new rule for myself to follow :
Thou shalt never use ndiswrapper again.
Thanks a lot, wonder, and thanks to you too, Xyne.
FYI, I tried to use something else than ndiswrapper before, but it didn't yield satisfying results. Anyway, thanks.

[SOLVED]Arch Linux / UEFI / BTRFS using Grub2 & Windows 8 in a 2nd HDD

PROBLEM:
====================================================================================
Dear fellas
I just purchased an new HP TouchSmart 17.3" laptop that comes with Windows 8.1 pro (1 tb HDD + small SSD for cache only ) and still have space for one more HDD or SSD.
I Google a lot and read a lot but many questions emerged since seems that no one has the same scenario (maybe I pick the wrong choices) like me.
The problem is.. I didn't wish to re-install Windows 8.1 since it came with from factory.. so I purchased a 750 gb hdd and put it into the free slot to install Arch Linux in a different HDD.
As I am not familiar with UEFI what I did was to reorder the hdds. I just put the Windows HDD as second disk and the new disk (For Arch Linux) as primary and changed into Bios from UEFI to compatibility mode and installed Arch Linux into the primary one.
I reaaaally need help to add to grub the correct "path" to Windows 8.1 disk that came with UEFI..
Anyone could please help me?
Thanks in advance!
====================================================================================
SOLUTION:
A huge thanks to @TheSaint and other users for their help and assistance!
More sources:
http://www.kossboss.com/linux---arch-in … -grub-boot
https://www.youtube.com/watch?v=METZCp_JCec#t=146
https://bbs.archlinux.org/viewtopic.php … 1#p1390741
Step by Step Summary:
Use gdisk to create partitions on /dev/sda:
- 512MB - EF02 type partition (for EFI boot)
- 690GB - Linux partition for the BTRFS.
- Create an EF00 (ESP) with 512mb
- Create a Linux System partition with the rest of space
Make the FAT 32 system for EFI boot:
# mkfs.vfat -F32 /dev/sda1
Make the BTRFS partition. If it complains about existing filesystems just add a "-f":
# mkfs.btrfs -L arch -f /dev/sda2
We will make out a root subvolume for sda1, this will be a folder called root located at the root of sda2. The way we will design this is that When the system boots we will not see /root, we will be inside root. Inside root you will have all of your etc,sys,proc,whatever folders etc.
# mount /dev/sda2 /mnt
# cd /mnt
# btrfs subvolume create /mnt/root
This should show you your root
# btrfs subvolume list -a /mnt
Something like this: ID 256 gen 5 top level 5 path root
# cd /
# umount /dev/sda2
Now we will mount sda2 root subvolume as /mnt and we will dump the arch system into there with pacman. We will also enable compress to utilize btrfs compress feature.
# mount -o defaults,compress=lzo,subvol=root /dev/sda2 /mnt
NOTE: the command "mount" will not show which subvolume is mounted, to see how subvolumes are mounted you need to look inside proc (cat /proc/self/mountinfo):
# cat /proc/self/mountinfo | egrep sda2
The line for the mount of sda2 looks like this:
43 21 0:34 /root /mnt rw,relatime shared:30 - btrfs /dev/sda2 rw,compress=zlib,ssd,space_cache
We can see that the subvolume /root is mounted to /mnt from the device /dev/sda3
Notice how with regular mount command its missing:
# mount | egrep sda2
/dev/sda3 on /mnt type btrfs (rw,relatime,compress=zlib,ssd,space_cache)
Pacman will dump stuff into a boot folder, so we better mount our sda1 EFI boot partition to it. Or else all of the boot stuff will go to sda3 instead of sda1:
# cd /
# pacstrap -i /mnt base base-devel
Let us create the directory and mount the EFI partition
# cd /mnt
# mkdir -p /mnt/boot/efi
# mount /dev/sda1 /mnt/boot/efi
Let us generate the FSTAB:
# genfstab -p /mnt >> /mnt/etc/fstab
Let us chroot into the arch installation:
# arch-chroot /mnt /bin/bash
Change password:
# passwd
Then pick the right one like this and associate it with a link to /etc/localtime
# ln -s /usr/share/zoneinfo/US/Pacific /etc/localtime
Let us generate the initial RAM disk
# mkinitcpio -p linux
Let us setup the bootloader (GRUB)
# pacman -Syu grub efibootmgr
Let us generate the grub configuration
# grub-mkconfig -o /boot/grub/grub.cfg
Let us install grub into the HDD
# grub-install /dev/sda
# umount -R /mnt
# umount /mnt
# reboot
From this step you can go straight and forward with the https://wiki.archlinux.org/index.php/Beginners%27_guide
Last edited by erickwill (2014-11-21 20:41:06)

TheSaint wrote:As UEFI BIOS is a boot loader itself. You should make on each HDD an ESP.
When you want to start win8 you go to BIOS and chose its entry, so will do for Arch the same.
For this way I suggest you write to boot the kernel directly from the BIOS. It just take some reading on this topic
Other option you set on you second ESP the boot loader of your liking and it will try to find win8 partition.
Thanks for your reply.
For the second option, may I use the compatibility mode and install the booloader into the first partition along with Arch?
Or in case the first option is still the better option, could you pleaaaase give me some directions from the scratch? Do you have Google Hangout?
Thanks in advance.
Last edited by erickwill (2014-11-18 19:54:26)

[SOLVED] Arch Linux Duke (2007) Fails to Boot

Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch. It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
If you have read this far, you are a trooper. Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
:: Loading udev events [Pass]
:: Mount root Read-only
:: Checking file systems
This is where it stops.
The next thing I see is:
/dev/sda6
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
E2fsck –b 8193 <device>
I then get a sort of character based splash screen that says
**********FILE SYSTEM CHECK FAILED ****************************
* Please repair manually and reboot. Note that the root file system
* is currently mounted read-only. To remount it read-write, type:
* mount –n –o remount,rw /. When you exit the maintenance
* shell, the system will reboot automatically
Give root password for maintenance
At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
/dev/sda6 on / type ext3 (rw)
This is exactly the root partition that the start up complains about. It is clearly there. I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
# mknod “/dev/root2” b 3 6
(“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
image = /boot/vmlinuz26
root = /dev/sda6
label = ArchLinux-Duke
initrd = /boot/kernel26.img
read-only
I am stumped. Thanks in advance for any and all pointers you may be able to offer.
Last edited by mac57 (2014-06-02 17:42:21)

Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next. This is my guess anyway.
I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

[SOLVED] Installing Windows XP after Arch Linux

I'm not sure at all where to post this, so I've decided to do it here since I have the problem on a laptop... Please move if it should be somewhere else.
I installed Arch Linux on my new laptop a month ago or so, and am very pleased to have found the very kind of distro I've been looking for. However, I'm having trouble with my graphics (either wine doesn't support it, or the drivers don't have 2D/3D acceleration), and now I want to install Windows XP next to Arch Linux.
Using a GParted LiveCD, I've repartitioned the harddrive as such: Unpartitioned Space (27GB), Linux (197GB), SWAP (5GB).
I've also removed the bootable flag from the Linux partition, just to be sure. However, when I try to install Windows XP, it gets stuck after unpacking a bunch of drivers, giving me a bluescreen that tells me to make sure the hardware isn't broken, check my harddrive with CHKDSK /F, or look for viruses. Ofcourse I know none of these are true, since I'm running Arch Linux just fine.
A friend suggested that maybe my hardware isn't supported by Windows XP, which sounds like the most reasonable explanation so far, but I can't find a list of supported hardware. The M$ homepage basicly says
"Pentium 233-megahertz (MHz) processor or faster (300 MHz is recommended)"
for CPU, which doesn't help me at all.
My hardware is:
Processor: Intel Celeron 2.2 Ghz
Memory: 2GB DDR2
Graphics: Intel 4500MHD
And the laptop is called an "eMachines E525", though that doesn't say much since there are very, very many called this.
Can anyone give me any hints as to what I might be doing wrong?
Last edited by Noxic (2010-05-29 18:44:32)

Sounds like something I'll want to do. Where did you download the drivers? Do I have to follow some guide? Thanks for the tip
EDIT:
Indeed I will want to install AHCI drivers, otherwise Arch Linux fails to boot quite badly. There is also a problem preventing me from booting when I'm using AHCI though;
At boot, Arch Linux checks /dev/sda1 (NTFS) for errors, and expects to check an ext2 filesystem. Obviously, however, /dev/sda1 is an NTFS filesystem.
Since it tries to read the NTFS partition as an ext2 filesystem, it panics. Arch Linux then prompts me for the root password (or Ctrl+D to reboot), but I've disabled root login and can therefore do nothing at this point.
I have a GParted livecd and the Arch Linux livecd, so editing files on any of the filesystem isn't a problem at all, but I don't know what to do at this point. Help?
Last edited by Noxic (2010-05-29 12:40:33)

What is Arch Linux?

Similar Messages

Maybe you are looking for