RE: cron
With not making a forward script who check you're mail to see if it's crony and let you know it. Something like the so-called vacancy demon. Fab. -- From: Al Youngwerth[SMTP:[EMAIL PROTECTED] Sent: Tuesday, August 27, 1996 8:41 AM To: 'debian-user@lists.debian.org' Subject: RE: cron That's funny, I haven't figured out how to get it to stop mailing me it results! The manpage (or some other documentation I found) says to add the line MAILTO=user_to_mail_to or if you prefer, leave it blank and it should never mail. I've found the MAILTO line doesn't seem to make any difference. If the cron job produces output to STDOUT (or maybe its STDERR), I get a friendly reminder from cron. If the cron job produces no output, I don't get a message from cron. If anyone really knows how to get cron to stop pestering me, let me know. Al Youngwerth [EMAIL PROTECTED] -- From: Miro Torrielli[SMTP:[EMAIL PROTECTED] Sent: Tuesday, August 27, 1996 5:53 AM To: debian-user@lists.debian.org Subject: cron I would be grateful if anyone can tell me how to get cron to mail me its results daily. Thanx... :-)
RE: mailing list
Humm... I think I have to complain to my news maintener... (I don't have this group on my news server though I have most of the linux groups... Is it a regional group?) Fab. -- From: Bernd Eckenfels[SMTP:[EMAIL PROTECTED] Sent: Wednesday, August 28, 1996 5:30 PM To: Ninoles, Fabien: DGSE Cc: debian-user Subject: Re: mailing list A good thing to see is some news mecanism. Aren't time to put Debian list on news groups? linux.debian.users. Go and get the Linux Hierachy. Greetings Bernd
RE: mailing list
The problem it's I can't put everything on my online account and they (administrator) don't have procmail or mh... Whatever, I did my suggestions after seeing so mush mail be reply two or three times for the same problem with the same answer. That's good for the reputation of the mail list but mush of the time, it's because we try to answer directly to the user without checking what other people already answered. (I do it myself more of the time). Results: many answers mainly identicals to a same problems. More of that, a news group is more organized. Thread are follow up and it's easy to jump over some who don't interested yourself. This will help people to got an answer more easily and more quickly, and to free a bit the traffic on this mail list (Debian-users). About the CGI-news thread... I remember to see one in a HOWTO contributions page... But where? Sorry, I was looking and don't find it. To give you an idea... it looks like a news browser on the web. You can start a thread, reply to a thread, and adding simple HTML editing you want. All the work are done by forms and CGI and a Diggest version of the threads are automaticly archive. Keeping it simple an people can see it on lynx. But I will keep the other mail lists (like announce and change) in this current form. I really that can improves the project. Thanks and sorry for this long reply, Fab. -- From: Philippe Troin[SMTP:[EMAIL PROTECTED] Sent: Wednesday, August 28, 1996 11:44 AM To: Ninoles, Fabien: DGSE Cc: debian-user Subject: Re: mailing list On Wed, 28 Aug 1996 10:20:41 EDT Ninoles, Fabien: DGSE ([EMAIL PROTECTED]) wrote: Two things I would like to see in the Debian Mailing Lists: First... An added [Debian:] tag before the suggest for those like me who receive from mush than one list. Why ? Use procmail or mh or whatever to split your incoming mail. I've goit a .maildelivery file that I can share with you. A good thing to see is some news mecanism. Aren't time to put Debian list on news groups? They aren't enought users? I think that we got so more users and be more accessible if we put almost Debian-Users on news (mostly a moderate one but we can do without). I receive near to 50 mails by day just from this list and it's not the only one I'm suscribed! News group will help to keep track of which mail was already replied and will avoid some traceback. Can you elaborate on that ? About other news mecanism, I was thinking about some web-news service such the one from O'Really. I'm not really good in doing CGI but I can try to do something (or let this to someone else) if you're interested. Where can we see this stuff ? There's already the debian mailing list archives on the Debian homepage. Phil.
RE: mailing list
Two things I would like to see in the Debian Mailing Lists: First... An added [Debian:] tag before the suggest for those like me who receive from mush than one list. A good thing to see is some news mecanism. Aren't time to put Debian list on news groups? They aren't enought users? I think that we got so more users and be more accessible if we put almost Debian-Users on news (mostly a moderate one but we can do without). I receive near to 50 mails by day just from this list and it's not the only one I'm suscribed! News group will help to keep track of which mail was already replied and will avoid some traceback. About other news mecanism, I was thinking about some web-news service such the one from O'Really. I'm not really good in doing CGI but I can try to do something (or let this to someone else) if you're interested. -- From: Mike Candy List[SMTP:[EMAIL PROTECTED] Sent: Tuesday, August 27, 1996 6:09 PM To: debian-user Subject: mailing list I don't want to complain too much, especially since group members have been so much help,but this mail is out of control.Single messages are totally acceptable although many, but multiple entries get very tiresome I'm willing to tough it out (easier than figuring out this OS for this semi literate dos user)but just my $.02 worth Mike List
RE: X11 and LaTeX minimal install
SNAP ON -- From: salwen[SMTP:[EMAIL PROTECTED] Sent: Wednesday, August 21, 1996 1:23 AM To: billy.chow Cc: debian-user Subject: Re: X11 and LaTeX minimal install A minimal X (and LaTeX) installation requires several debian packages, but most people either do not want X or want at least a minimal installation, right? So what are the justifications of splitting a minimal X and LaTeX the way it is? The developers may have their own reasons for breaking up the packages but I can suggest a couple. If people are pulling the packages over a phone line there is an advantage to limitting the size of individual packages. That way they can hang up the phone periodically. Also, if a bug shows up that needs to be fixed they only have to download the package that is broken. Nathan SNAP OFF And what about Floppy Installation like myself ! I can install most of the debian package with single floppy (1.44M although :) and only have to split few ones... It can be a good thing if you can set a more pratical multiple floppy installation scheme for those who needs space to install... But I think you already discuss about it! :)
FW: Checking version was :RE: kernel si
SNAP ON -- From: Hamish Moffatt[SMTP:[EMAIL PROTECTED] Sent: Wednesday, August 21, 1996 4:56 PM To: debian-user Subject: Re: kernel size I like your suggestion of configuring packages as a separate step. The option in dselect to 'configure remaining unconfigured packages' could handle this, instead of the 'install selected packages' option. In this scenario, the 'install' option would became 'load packages' and all configuration would be relegated to the 'configure' option. If something goes wrong during configuration, you can just re-run dselect and hit the configure option. Good Idea. One thing I find a bit annoying with dselect/dpkg is the way it checks the version of EVERY package when you pick Install. Last night I did an NFS installation (and the remote source was from CD-ROM), and this step was very slow. Can anything be done about this, eg trusting the packages list instead of looking for newer versions, or whatever? Also, how does dselect cope if it doesn't have the root debian tree? For the past few days I've been fiddling a lot and I've had the Debian CD in my CD-ROM drive all the time, but I'm about to lend it to someone. Will dselect still work with nothing but a local directory, or should I just use dpkg by hand? thanks, Hamish SNAP OFF Please, if you do so, let the check version in the available options. I find it really pratical seem I'm using msdos names package. One pratical thing would be to put the current version number side to the package name in the recurse dependancies list, so we can see it when we got some (= x.yy version) dependancies.
Please explain Motif issues (was: StarOf
SNAP ON -- From: James A. Robinson[SMTP:[EMAIL PROTECTED] Sent: Wednesday, August 21, 1996 2:48 AM To: Christopher R. Hertel Cc: debian-user Subject: Re: Please explain Motif issues (was: StarOffice under Debian) Can someone point me toward the FAQ or HOWTO that will explain the issues with Motif? Why is Motif hard to come by and what is Lesstif? Motif is a set of proprietary libraries licensed by OSF. So it costs money to get them. I've bought them for $99.00 at InfoMagic (http://www.infomagic.com), but I've heard some people quote and amazingly low price of $40.00. Normally one sees them going for $200.00 or so. Lesstif is an attempt to duplicate the API of Motif, without using the proprietary source code. They want to allow anybody to compile and run Motif programs using Lesstif. Lesstif is free, and is put out by the Hungry Programmers (http://www.hungry.com). As far as I can tell, it is still very unstable, and not usable for something like StarOffice. But others who have actually used it should speak up. Jim SNAP OFF That's the price for the shared libraries distributions from OSF Motif... You mostly got more with the Infomagic CD :) There're some really low price if you buy from OSF Direct Office but I don't understand nothing about their licences. Whatever, this is the address : http://www.osf.org/motif/ But thanks for the lesstif... it's the first time, I was really happy to find this version of LaserChess! Fab.
FW: #1, make it boot! Engage.
SNAP ON -- From: Bruce Perens[SMTP:[EMAIL PROTECTED] Sent: Tuesday, August 20, 1996 9:34 PM To: bruce; salwen; Happy Linux Users; Charles A. Schuman Subject: Re: #1, make it boot! Engage. From: Charles A. Schuman [EMAIL PROTECTED] # fdisk (then p) Device Boot Begin Start End Blocks Id System /dev/sda1 *1 1251 513891 6 DOS 16-bit =32M /dev/sda2 252252976 1484437+ 83 Linux native /dev/sda3 977977 1003 55282+ 82 Linux swap Note the * is next to the DOS partition. This will cause the DOS partition to boot, because it's marked as the Boot partition. I'm not sure what MBR (master boot record) you have. If you have the Debian one, holding the shift key down while the system boots will cause a 123FA: prompt (or something similar). Press 2 and see if Linux comes up. If you have the DOS MBR, you won't get that prompt. Use FDISK (on DOS or Linux) or activate on Linux to set /dev/sda2 to be the Boot partition. That will also set the _default_ partition booted by the Debian MBR. The drive is a SLED (Single Large Expensive Disk). Are you sure it's not an IPTMCTWTSFN? That means I Paid Too Much Compared to What They Sell For Now. I have a whole room full of those. :-) Here's the messed up lilo.conf on what now is /target/etc/lilo.conf: boot=/dev/sda2 root=/dev/sda2 install=/target/boot/boot.b vga=normal delay=20 image=/target/boot/vmlinuz label=Linux That looks like an OK lilo.conf but it's living on the sda2 partition (as it should), and you need to set that Boot designation or you'll never run it. I can't even begin to speculate on what this is all doing. At boot time, the boot ROM loads the first block of the disk. The first 446 bytes of that block contain the MBR. The next 66 bytes are the partition table. If the MBR starts with the right byte pattern, the ROM jumps into its code. The MBR looks for first partition in the table with the Boot flag set. The first block (maybe more - I don't know) of that partition is loaded, and the MBR jumps to that code. In your case that should be what LILO wrote, but the flag is on the wrong partition so you boot (or try to boot) the DOS partition instead. Bruce SNAP OFF For myself (I have a look-alike partitions table), I prefer to boot with a floppy and rerun LILO on my MBR. You will set it by replacing your boot line by boot=/dev/sda who will write on your sda MBR, in place of /dev/sda2 who would write on your partition. After that, just run lilo when you're root. the Boot flag are only use in OS/2 or MS-OSs at my knowledge. It's better to only have one set because MS-DOS doesn't support multiple boot parts. --- The contradiction is not that free software are among the best, it's that commercial software aren't the best of them. === Fabien Ninoles aka the Baggus Mage aka Baffouille [EMAIL PROTECTED] +- finger me for my PGP Public Key | Not knowing where you go | always lead you to [space must be fill to register] | a Baggus End... --- Can be reach too on [EMAIL PROTECTED] until 30/08/96 ---
Checking version was :RE: kernel size
SNAP ON -- From: Hamish Moffatt[SMTP:[EMAIL PROTECTED] Sent: Wednesday, August 21, 1996 4:56 PM To: debian-user Subject: Re: kernel size I like your suggestion of configuring packages as a separate step. The option in dselect to 'configure remaining unconfigured packages' could handle this, instead of the 'install selected packages' option. In this scenario, the 'install' option would became 'load packages' and all configuration would be relegated to the 'configure' option. If something goes wrong during configuration, you can just re-run dselect and hit the configure option. Good Idea. One thing I find a bit annoying with dselect/dpkg is the way it checks the version of EVERY package when you pick Install. Last night I did an NFS installation (and the remote source was from CD-ROM), and this step was very slow. Can anything be done about this, eg trusting the packages list instead of looking for newer versions, or whatever? Also, how does dselect cope if it doesn't have the root debian tree? For the past few days I've been fiddling a lot and I've had the Debian CD in my CD-ROM drive all the time, but I'm about to lend it to someone. Will dselect still work with nothing but a local directory, or should I just use dpkg by hand? thanks, Hamish SNAP OFF Please, if you do so, let the check version in the available options. I find it really pratical seem I'm using msdos names package. One pratical thing would be to put the current version number side to the package name in the recurse dependancies list, so we can see it when we got some (= x.yy version) dependancies.
Re: No Subject
SNAP ON -- From: Charles A. Schuman[SMTP:[EMAIL PROTECTED] Sent: Wednesday, August 21, 1996 11:52 PM To: Ninoles, Fabien: DGSE Cc: Happy Linux Users Subject: No Subject On Wed, 21 Aug 1996, Ninoles, Fabien: DGSE wrote: For myself (I have a look-alike partitions table), I prefer to boot with a floppy and rerun LILO on my MBR. You will set it by replacing your boot line by boot=/dev/sda who will write on your sda MBR, in place of /dev/sda2 who would write on your partition. After that, just run lilo when you're root. the Boot flag are only use in OS/2 or MS-OSs at my knowledge. It's better to only have one set because MS-DOS doesn't support multiple boot parts. I replaced line boot=/dev/sda2 with boot=/dev/sda and now I've an endless loop that goes: LILO Loading Linux... LILO Loading Linux... LILO Loading Linux... LILO Loading Linux... LILO Loading Linux... LILO Loading Linux... with the seven dots. Pressing shift gives me the LILO boot: What should I try next to get the hard drive to boot the kernel on the second partition? I may have ruined it by writing a boot record onto the second partition. I really don't know what I've done. I made sure to check the second partition - it is set active/bootable. I'd made a typo earlier and ommited the star (*). Missing Linux, Charles SNAP OFF Sorry about it :( I never got this problem before... and I succeed all the time with whatever partition on my HD by putting LILO on my MBR (I already succeed to make LILO run the OS/2 Boot Manager partition and an NT BOOT partition which it doesn't supposed to be.) For myself, lilo always do a good job but I suggest you to check two things : your kernel bootup (with rdev... I use it when I'm on Slackware but hope it was already in the Debian release...) and trying to clean you're boot sector on sda2 with cfdisk but be careful with it! It's easy to erase lot of stock with it. I hope you can already load from a floppy with root=/dev/sda2. And keep looking on this mail list... I'm not an expert in lilo and boot sector, I was just doing lot of weird installations as hobby :) Don't give up! You will more luv your Linux when you'll go through this! GoodLuck! Fab.
RE: Non-existent .deb's
SNAP ON -- From: Daniel Lynes[SMTP:[EMAIL PROTECTED] Sent: Wednesday, August 21, 1996 9:07 PM To: Debian Users Subject: Re: Non-existent .deb's On Thu, 22 Aug 96 00:28 BST, Ian Jackson wrote: If you delete the `Packages' files, or fail to download them, dselect will offer to scan the .deb files that are actually on your disk. But, this method does not use the descriptions, or dependency lists, either. I kind of like that information, as it allows me to see if I'm trying to install something I don't have the extra files for. SNAP OFF I use this method most of time almost because I'm take my packages in rex who change quickly. So, my own dependancies are made from the infos find in deb files. The only I don't have is the classification of some files because they're optional and let to the DM but I got all needed dependancies. Ciao! Fab.
