install program cannot detect swap partition
I have just downloaded the boot floppies and am trying to install Debian. When I get to the Partition step and create a swap partition the install program cannot find it. I have used the toplevel boot floppies, the bf2.4 boot floppies, I have created the swap partition on the SCSI drive and the IDE drive, I have rebooted, I checked the type is 82 Linux Swap. Can anyone help? Thanks, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to make Alt GNU Emacs Meta?
I did "apt-get -t unstable install gnome" and it was fixed. Of course this makes sawfish use Alt as the W- modifier but that's ok with me. Thanks, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
never mind last 2 questions
I got my last two questions answered on IRC. Thanks, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC: an introduction to configuring sawfish
Here is the reply to my reply to the previously forwarded message. --- Start of forwarded message --- hi > May I post your email on my website? I wish to record contributions > and show critiques so that future reviewers can read what has been > said and express agreement or disagreement. yes, of course. you can use it as you like. i actually wanted to post it to the whole mailing list but somehow i accidently replied directly to you. > To clarify, this is not a HOWTO. It is a recipe, simple step-by-step > instructions to achieve a particular configuration of sawfish, namely > the configuration I like to use. > > As a recipe, it should be tasted first. If you don't like the results > of this recipe, you can go back and fiddle with it. You can look for > other recipies. You can eventually make up your own recipies. (I > will add a section on undoing the changes made.) ok, i agree. i've seen that you've already modified your version a bit. there's one thing i want to mention: if you say "This is a recipe, simple, step-by-step instructions to make a specific configuration of sawfish, the one I use." you should also say what kind of configuration you use, ie if it is minimalistic, eye-candy or something like that. i know, one would notice this while reading the recipe, but if i had a real recipe from you i'd like to know what i am cooking before i actually start. and the information that it is the meal that you like is nice, but still i'd want to know what it is before i try it :) > > why don't you mention both of them in 2 subsections? i also think > > they > > have both advantages and disadvantages. if you are not a programmer > > and > > do not like to fiddle around with config files, sawfish-ui is your > > friend. on the other hand it can be much faster/shorter to do it > > through > > your ~/.sawfishrc. while we are at links, why don't you offer a .sawfishrc file and two theme.jl files to download with the conents you describe in your recipe. users then would not have to copy paste & it, although they might learn less this way. so maybe only put the links to the files at the bottom? > > some links to howtos on how to configure xfree on debian/redhat etc > > might be useful here. > > ~/.Xsession and configuring xfree are beyond the scope of the > document. I think experts will either know it or be able to figure it > out, while it is too much information for novices. especially because it is beyond the scope of the recipe you should add links to other howtos/readmes where these topics are covered. after all doing it the way how it is intended on your distribution should be the prefered way to prevent possible problems in the future. the users can then decide if the follow the links or ignore them. > > the file should probably renamed first to custom.save or something > > before deleting it at once. after the custom files has been renamed, > > sawfish has to be restarted. > > I don't think it will help to save the file if sawfish always has > problems starting up with it. it doesnt help but you're on the save side not deleting any configuration files. after all you have a problem and you _try_ to delete the custom file to see if it works then. maybe the problem is caused by other things and deleting it was in vain. you lose all configurations done through sawfish-ui if you delete the custom file. especially if you're a novice you should save old config files. you never know when you need them again. btw, you can save your current gnome session with a program called "gnome-session-save". (should be included in gnome by default, try "man gnome-session-save") besides, killall metacity && sleep 2 && nohup sawfish might be better.. sleep prevents sawfish from starting too early and nuhop detaches sawfish from the xterminal so one can close it. (and use gnome-session-save afterwards [but before closing the terminal of course]) greets, CAiRO --- End of forwarded message --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC: an introduction to configuring sawfish
Here is my reply to the previously forwarded email feedback. --- Start of forwarded message --- Thank you for your email. May I post your email on my website? I wish to record contributions and show critiques so that future reviewers can read what has been said and express agreement or disagreement. To clarify, this is not a HOWTO. It is a recipe, simple step-by-step instructions to achieve a particular configuration of sawfish, namely the configuration I like to use. As a recipe, it should be tasted first. If you don't like the results of this recipe, you can go back and fiddle with it. You can look for other recipies. You can eventually make up your own recipies. (I will add a section on undoing the changes made.) Novice users like my mom get confused if you offer them many options at the beginning. They do not know enough to know what they want and become afraid of making the wrong choice. That is why the recipe is a simple linear sequence. (Although I will add links to optional steps for experts.) (You could argue that users that inexperienced would not use Linux and I am targeting the wrong audience, to which I have no reply. The only way to find out is to put it out there and see if people find it useful.) An observant user following the instructions will notice that things can be done differently. For example, someone who does not want sound probably does not need to be told he can turn it off by unchecking the checkbox labelled "Play sound effects for window events.". (I will put [Optional] in front of some of the steps.) I wrote this recipe because: 1. The existing sawfish documentation is scattered, sparse, and outdated. I had to Google, read pages closely, and read functioning examples (that were more complex than I needed) to figure out what to do. 2. It is simple enough for novices. It is an excellent teaching example because it doesn't do much (thus the name "How to make sawfish do nothing"). There are few steps, the files to be created are short. 3. It is powerful enough for experts. I am an expert. I spend much time fighting software that does things for me when I know exactly what I want to do. I prefer software that does nothing. This recipe touches on all the ways to configure and extend sawfish short of modifying the source. After reading it an expert will be able to use any theme or Lisp package and create his own, hopefully saving him the hours of web browsing I spent. I also believe that because sawfish is so easy to configure and the results are so immediate, configuring sawfish can provide a gentle introduction to programming for the non-programmer. Responses to individual points: > maybe you should include a table of contents and the possibility to > download the raw, text and html version. It is too short for a table of contents, and it is intended to be read linearly, not as a reference. I see no reason to provide a download when you can simply save the html to a file. I do not expect anyone will need to read it more than once. > besides i think a chapter with links where to get further information > would be nice. i know, there is a misc chapter already. maybe add > more > links to themes repository etc. there? There is a link to a themes repository under 4. More themes. > why don't you mention both of them in 2 subsections? i also think > they > have both advantages and disadvantages. if you are not a programmer > and > do not like to fiddle around with config files, sawfish-ui is your > friend. on the other hand it can be much faster/shorter to do it > through > your ~/.sawfishrc. This could be handled with an optional link as I mentioned above. > besides i wonder if everybody who is reading the howto is aware of > the > fact that the graphical configuration through sawfish-ui has it's own > config file (~/.sawfish/custom) while the user config file is > ~/.sawfishrc. This is mentioned at the end of 1. Root menu and Configurator. > especially if you are using debian you should use > $ update-alternatives --config x-window-manager > to set your default window manager. Thank you, I will look into this. > if you've allowed user-x-sessions users might be able to start > sawfish > from ~/.Xsession. > some links to howtos on how to configure xfree on debian/redhat etc > might be useful here. ~/.Xsession and configuring xfree are beyond the scope of the document. I think experts will either know it or be able to figure it out, while it is too much information for novices. > these points above should maybe more sound like recommendations than > commands :) > besides, even if your readers are novices, they're not stupid. you > should explain why setting a certain option this way is recommended. > (eg. i doubt that everybody likes to have sound effects turned on) See general comments above. I will add [Optional} before these steps. > point out more that ~/.sawfish/custom is the config file from > sawfish-ui.
GNU Emacs tutorial?
When I learned Emacs (almost 20 years ago) there was a nifty tutorial. Now I can't find it in the info hierarchy. Has it been retired? How should a novice start learning Emacs? Thanks, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to set colors of ls listings?
Someone on IRC pointed me at dircolors. But since my problem is that the primary colors are too strong and clash with the background, I ended up editing the profile in gnome-terminal and assigning a pastel RGB value to each primary color in the Color palette provided to the terminal applications. Thus ls thinks it is using Red but it comes out pink. Works great. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: GNU Emacs tutorial?
Thank you for your help. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC: an introduction to configuring sawfish
> May I post your email on my website? I wish to record contributions > and show critiques so that future reviewers can read what has been > said and express agreement or disagreement. yes, of course. you can use it as you like. i actually wanted to post it to the whole mailing list but somehow i accidently replied directly to you. Is there some name you would prefer to be known as on the website or is CAiRO fine? I hope you don't mind that I have forwarded our correspondence to debian-user. there's one thing i want to mention: if you say "This is a recipe, simple, step-by-step instructions to make a specific configuration of sawfish, the one I use." you should also say what kind of configuration you use, ie if it is minimalistic, eye-candy or something like that. i know, one would notice this while reading the recipe, but if i had a real recipe from you i'd like to know what i am cooking before i actually start. and the information that it is the meal that you like is nice, but still i'd want to know what it is before i try it :) I have added some explanation in the Motivation section. Let me know if you think this should be more explicit or up front. while we are at links, why don't you offer a .sawfishrc file and two theme.jl files to download with the conents you describe in your recipe. users then would not have to copy paste & it, although they might learn less this way. so maybe only put the links to the files at the bottom? Done. > ~/.Xsession and configuring xfree are beyond the scope of the > document. I think experts will either know it or be able to figure it > out, while it is too much information for novices. especially because it is beyond the scope of the recipe you should add links to other howtos/readmes where these topics are covered. after all doing it the way how it is intended on your distribution should be the prefered way to prevent possible problems in the future. the users can then decide if the follow the links or ignore them. Let me think about this, and see if other people agree with you. > > the file should probably renamed first to custom.save or something > > before deleting it at once. after the custom files has been renamed, > > sawfish has to be restarted. > > I don't think it will help to save the file if sawfish always has > problems starting up with it. it doesnt help but you're on the save side not deleting any configuration files. after all you have a problem and you _try_ to delete the custom file to see if it works then. maybe the problem is caused by other things and deleting it was in vain. you lose all configurations done through sawfish-ui if you delete the custom file. especially if you're a novice you should save old config files. you never know when you need them again. Ok, done. btw, you can save your current gnome session with a program called "gnome-session-save". (should be included in gnome by default, try "man gnome-session-save") Thanks, I will try it. killall metacity && sleep 2 && nohup sawfish might be better.. sleep prevents sawfish from starting too early and nuhop detaches sawfish from the xterminal so one can close it. (and use gnome-session-save afterwards [but before closing the terminal of course]) I will do a clean install on an old system and try all the variations to see which works best. At this point I have so many unstable packages on my system I wouldn't know what to conclude if somethng didn't work. Thank you again for your help. Please do not hesitate to continue sharing your thoughts. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to set colors of ls listings?
Can you be more explicit about what you did? Where is the profile for gnome-terminal, etc? , gnome2? I am using GNOME 2. To edit the profile in gnome-terminal, you can right click on the gnome-terminal window, select "Edit Current Profile", in the dialog click the Colors tab, click on one of the bottom row of colors next to "Color palette" and then enter HSV or RGB values (or click and drag on the way cool color wheel widget). Adam - Original Message ----- From: "Adam Kao" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 16, 2003 5:33 AM Subject: Re: How to set colors of ls listings? > > Someone on IRC pointed me at dircolors. But since my problem is that > the primary colors are too strong and clash with the background, I > ended up editing the profile in gnome-terminal and assigning a pastel > RGB value to each primary color in the Color palette provided to the > terminal applications. Thus ls thinks it is using Red but it comes > out pink. Works great. > > Adam > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Adding ethernet driver to install??
I am installing Linux to a machine with a new and obscure ethernet card. I could not find it in the Install Kernel and Driver Modules section. However I went to the manufacturer website and downloaded a linux driver (it is a .tar.gz file). How do I put this on the driver diskettes or get it into the Install Kernel and Driver Modules section? Thanks, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't start X with Nvidia
I don't know if this is relevant, but when I installed X on my system I had to remove the "UseFBDev" option from the "Device" section. My system is much older and the video card is an old nVidia card that uses the "nv" driver but it's something to try and can't hurt. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
