ArchThis Forum is for the discussion of Arch Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Attempting to install arch-0.5...base package selected..install packages selected...pacman initial entry followed by error staement "mawk" dependency not on CD... abort install and connect to this forum
The CD program is automatic such that the user cannot determine what is going on or what to do if error messages appear. An expert in the arch program is needed to answer the question what to do if "mawk" error message is displayed.
Downloaded the CD iso, recorded the CD and re-ran the install with same result when loading packages.
Examination of the CD in windows shows a package for "mawk" as a tar.gz in the CD contents.
Last edited by lilsirecho; 10-18-2003 at 11:09 PM.
same problem here... i was told to try an ftp install, but am currently having problems configuring the proper module for my nic. But maybe you can get past where i can't... try it let me know btw its not just a mawk dependency issue, if you unselect autoconf, which has a dependency to mawk you just get another dependency warning altogether so something is very wrong with their cd.
Guys, I don't have the answer for you but I'd suggest posting about your problems on the actual arch forums at http://bbs.archlinux.org/
I certainly didn't see any problems with mawk, or anything else for that matter, with my install of 0.5. But I downloaded my version a while back, perhaps there have been some changes in the iso...
well i visited the arch irc where i didn't get any help. some people tried, but to no avail. said screw it, (and believe me i gave it an ample amount of time) and reinstalled mandrake 9.1, and will wait for 9.2. I guess. I was just shocked to find out my beloved distro was manufactured by the french, and started looking around.. but maybe its not that big of a deal.
One known cause of this problem is a user failure to select "DONE" at the bottom of the menu after partitioning and mounting file systems. It's easy to overlook, particularly if your drive has several partitions. You've got to scroll all the way down to the bottom to find it. The documentation available at the distro's website instructs users to take this step. I missed it the first time around and got the mawk message. The installation concludes that the initial steps aren't completed and reacts this way. So don't quit, certainly not for something as bloated as Mandrake. Read the instructions carefully and follow them closely as you install. Good luck!
ok, in an effort to eliminate my need for Mandrake, I will reformat, and try what you described above. I hope it works, but if it doesn't that's the last time I'm trying Arch. I'll let you know what happens. Thanks for the tip by the way.
While I'm certainly pleased to learn that its your intention to attempt a reinstallation of Arch, I would hasten to reemphasize the other main point in my post: That the problem here is due, quite possibly, to user error. I would think that you'd owe yourself at least enough of an effort to ensure that that contingency is ruled out whatever your doing so may require. So if you are interested in learning about GNU/Linux at any deeper level than that offered by the Reddrakes and the Manhats - I know I didn't learn very much about Linux from them in the two years I worked with them - I encourage you to persist until you can, in conscience, lay your problem at Arch's doorstep. Do that one for Rico, eh?