That�s why I hope to meet guys into slack. Tomorrow night�s meeting? The email below is about my climb in life and the three technical things foremost in my concerns. If you�re not into slack, there�s no need to continue reading. tks, Brian - - - - - - - - - - - - - I'm a newbie with just a little Fortran experience and a 1 gig HDD machine with Windows 98 and no printer either! Nonetheless I�m feeling the need to choose Slackware 9.1. It�s because I�ve read a bit of craft obligation and personal challenge in the following: �Slackware is Linux's oldest living distribution. It does not try to emulate Windows, it tries to be as Unix-like as possible. It does not try to cover up processes with fancy, point-and-click GUIs(Graphical User Interfaces). Instead, it puts users in control by letting them see exactly what's going on. Slackware is for people who enjoy learning and tweaking their system to do exactly what they want. Slackware's stability and simplicity is why people will continue to use it for years to come.� But simple does not mean easy, does it? Back in the days when men were Men........... I�m up in years (you�ll know me when you see I�m fat, ugly, and bald with white hair), but in my day I made 5 violins under a master (before life took me somewhere else). The only power tool I used was a band saw to cut smaller pieces out of a split log. You can make a violin out of very few knives, chisels, scrapers, and a block plane. I made my own patterns, knives, and scrapers. I had never worked wood before, even by power tools. (I never had had interest in those.) Those early instruments were slow going and not a little agony, but I knew with control of the hand and discipline of the heart that I could step up in my work, and take it to the level of art, well beyond anyone skilled with power tools. Am I a bit competitive and still trying to be a man�s man? Anyhow, I believe you see the parallel. I want to get to command line and not rely at an emotional level on commercial distributions what with all *their* packaging schemes (read: complications) and *their* bloatware GUI�s. It�s a bit about control and pride, isn�t it? How else can I bypass the Windows mentality and hope to step up in open source as a craft? I want to be a thinker and doer in this game, not just a consumer or user of various Distributions. My goal longer term is art, not just sitting at the feet of documented Authority. Another parallel: how can you design a Cadillac with no skills to build a model T Ford? Man or not, I�m scared! At the least I�m feeling a little shaky, and here�s why. Switching back to the violin story, I knew how to make those knives out of straight razors and scrapers out of blue shim stock. I could sharpen on my own the blade of a block plane until no one could see the edge. It was intuitive and it wasn�t rocket science. It took no prior reading or class instruction. I put in plenty of sweat time at the bench. It took me eight days (no kidding) to cut my first bass bar to a perfect fit, and I never backed off once from the challenge. Of course I knew my master was back there, watching. I did not quit while seeing him work at ten times my rate. My pride would not let me give up. But there came a time when I could go no further without my master�s help. Art was not possible without the ultimacy and intimacy of oral tradition. Thank God for newsgroups and the WLUG. It takes a community to raise a boy to manhood. So learning slackware, as learning unix in the old days, must require a combination of self-reliance AND guru help. In life we must settle for no false choices. Three items below. As background, I�m about ready to place an order for a stripped down machine with two IDE drives and Slackware. (Forget all that talk last week about SCSI, I don�t need bragging rights or a hardware �screamer.� Because, as you must know by now, the �screaming� I�m experiencing now has nothing whatever to do with any hardware.) 1. Partitions. I�m new to Linux, but trying to learn, so please don�t shoot me. What should my (various?) slack files look like? I have never seen any. I don�t know what to look for. Specifically, what partitioning specs can I give to the vendor who will pre-install and configure slack for me so that I have a working machine? I would like to be able to read and learn from these files BEFORE the iron arrives on my desk. I would like to split my slack partitions over two 80G disks for speed of random access. Thus, taking platter construction into account, the most frequently used partitions should be in the physical center of each disk. I would like to put slack primarily on hda, and, later on, any second distribution (Mandrake? Libranet? new Debian when it comes out?) primarily on hdb. What detailed partitioning do you recommend upfront to permit or pave the way for this control and flexibility? 2. Internet. auuggh..! Here, a problem of the chicken/egg variety. What should my slack files look like for dial-up access (to start with my current Prodigy) and DSL access (Speakeasy later when I�m ready to try downloads)? Unless I have these things up and running, I won�t be able to interface with online Linux help! 3. Printer. Anyone have a reliable model number for a Linux printer to suggest? Nothing fancy, just something to print out docs for Linux study in the woods, and an occasional letter. What should my slack files look like? (Of course I don�t know a thing yet about driver stuff..) These three are my foremost technical concerns that seem to be holding me back from my first flight. I hope to receive you hand up on these things! Biggest thing of all, the opportunity to meet you tomorrow night and chat over pizza. until then, Brian __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com