Re: debian-user-digest Digest V2002 #716
On Thursday 01 August 2002 7:33 am,
debian-user-digest-request@lists.debian.org wrote:
> debian-user-digest Digest Volume 2002 : Issue 716
>
> Today's Topics:
> Re: Intel PRO100 [ Kirk Strauser <kirk@strauser.com>
> ] Nautilus2 freeze when connect to the [ Romel Sandoval
> <romel@prodigy.net.m ] Re: Linux at work for a corporate de [ Kirk
> Strauser <kirk@strauser.com> ] Re: How Do I download Debian from th [ Kent
> West <westk@acu.edu> ] Nautilus2 freeze [ Romel
> Sandoval <romel@prodigy.net.m ] Re: Root login in graphical envirome [
> Crispin Wellington <crispin@aeonlin ] Re: Intel PRO100
> [ John Griffiths <john@capmon.com> ] Re: Full-screen editor in /bin
> [ bob@proulx.com (Bob Proulx) ] Re: Intel PRO100 [
> Kirk Strauser <kirk@strauser.com> ] Re: Holiday arrangements [
> Gary Turner <kk5st@swbell.net> ] Re: Mutt/Tin/GNUMACS v. gnus/GNUMACS [
> bob@proulx.com (Bob Proulx) ] pdf attachments in mutt unreadable b [
> Richard Otte <otte@cats.ucsc.edu> ] Re: Mutt/Tin/GNUMACS v. gnus/GNUMACS [
> Craig Dickson <crdic@pacbell.net> ] Re: Intel PRO100 [
> bob@proulx.com (Bob Proulx) ] Re: pdf attachments in mutt unreadab [ Chris
> Kenrick <chrisk@aurema.com> ] Re: Intel PRO100 [ Chris
> Kenrick <chrisk@aurema.com> ] Re: pdf attachments in mutt unreadab [ John
> Griffiths <john@capmon.com> ] Re: Intel PRO100 [
> bob@proulx.com (Bob Proulx) ] Re: *** I BADLY WANT OUT !!!!!!!!!** [ Paul
> M Foster <paulf@quillandmouse. ] Re: Linux at work for a corporate de [
> uzoma nwosu <uzoma@audioverse.com> ] Java/Mozilla - serious failure
> [ Ben Thompson <ben_thompson@ntlworld ]
> Paul Johnson <baloo@ursine.dyndns.org> [2002-07-31 19:31:20 -0700]:
> > I realise there's a multitude of versions of both emacs and vi, but
> > another thing that's always kind of bugged me about vi is you can
> > never be quite sure what version you're going to be running, and
>
> Yes. It is really strange that things like vi are symlinked using the
> "alternatives" system in Debian. A sad thing really.
>
> I use emacs when I am doing major things. But I use vi for a quick
> point and shoot editor. The fingers have a hard time adjusting to
> different editors and so it is extremely annoying when vi is symlinked
> to vim or other similar, probably better, but certainly very different
> editors. I have been known to drop back to 'ed' at particularly
> frustrating times. When I type in vi I want vi and not vim!
>
> Since them I have learned to select vi with this.
>
> update-alternatives --config vi
>
> Then select nvi which is real vi that really should be the mandatory
> version to be called vi. Nothing against vim. But if a user wants
> vim they probably would type in vim.
>
> > whether or not it's going to be self-documenting or documented at all
> > (something that was more of a bane when I was working in the tech
> > industry). Meanwhile, you can pretty much assume that if a system has
> > emacs, it's gonna be gnumacs at this point.
>
> Unless it is xemacs, aka lucent emacs. emacs is also in the
> alternatives system so it could be anything. Sigh.
>
> Bob
> <marshal@h9.dion.ne.jp> [2002-08-01 11:42:47 +0900]:
> > >>>>> "Paul" == Paul Johnson <baloo@ursine.dyndns.org> writes:
> >
> > Paul> (Your indentation is a little bit strange...)
> >
> > eh? How so? I'm using superquote, or whatever it is in emacs. I
> > haven't adjusted the settings, so tell me what you find strange, and
> > I'll take a look at it.
>
> I agree with Paul. The quoting is not particularly bad. But usually
> quoted text will be a set of "> " at the left edge. Superquote is
> putting the persons mail name in the first part with an indention.
> That is frequently used when people are quoting several different
> people in an interspersed way as a method of identifying each. So it
> is not an unheard of quoting style. It is still seen frequently. But
> the four space indention on the front shifting everything to the right
> is an odd addition. I don't prefer it. But not a terribly big deal
> either way.
>
> And, probably the real reason it looks odd, neither mutt nor emacs-vm
> nor probably other mail readers recognizes the syntax of that quoting
> style for me and so does not syntax highlight with color differences
> the main text and the quoted text. We have to look at it in plain old
> black and white. (Or whatever your basic foreground and background
> colors happen to be.) Which is unusual compared to the common method
> of quoting which facilitates simple syntax coloring. After using ansi
> terminal color for a while you get adicted and don't want to go back
> to that vt100 in the corner. :-)
>
> > Gnus is a pain to get set up. But once it's set up, I haven't had
> > much problems with it...
>
> I never found it very difficult to set up. But I hope it is faster
> now. It used to be terribly slow. But otherwise I rather liked it.
>
> Bob
> I've been trying to send pdf files as email attachments in mutt.
> Whenever I send these to someone using windows, they are unable to open
> the files using acrobat. One of them just sent the pdf file back to me,
> and I am also now unable to open it. That makes me suspect that the
> problem is that something is happening to the files in email. Does anyone
> know why this happens, and is there a way to send pdf attachments to
> windows users with mutt. Thanks,
>
> Ric
> Bob Proulx wrote:
> > <marshal@h9.dion.ne.jp> [2002-08-01 11:42:47 +0900]:
> > > >>>>> "Paul" == Paul Johnson <baloo@ursine.dyndns.org> writes:
> > >
> > > Paul> (Your indentation is a little bit strange...)
> > >
> > > eh? How so? I'm using superquote, or whatever it is in emacs. I
> > > haven't adjusted the settings, so tell me what you find strange, and
> > > I'll take a look at it.
>
> IIRC, it's called SuperCite. It is not terribly uncommon, but it is
> infrequently seen in my experience, and some old-time email/usenet users
> regard its use as a sign of cluelessness. Back when I still bothered to
> read usenet, I more than once saw flamewars break out just because
> someone posted using SuperCite.
>
> > I agree with Paul. The quoting is not particularly bad. But usually
> > quoted text will be a set of "> " at the left edge.
>
> Yes, though sometimes people who want to be "different" use some other
> single character for quotation, such as } or | or :.
>
> > Superquote is
> > putting the persons mail name in the first part with an indention.
> > That is frequently used when people are quoting several different
> > people in an interspersed way as a method of identifying each. So it
> > is not an unheard of quoting style. It is still seen frequently. But
> > the four space indention on the front shifting everything to the right
> > is an odd addition. I don't prefer it. But not a terribly big deal
> > either way.
>
> The nastiest thing about SuperCite is that this business of putting
> people's names at the left edge shoves the quoted text so far to the
> right that it often needs reformatting, which, in the case of text that
> is not meant to be free-flowing paragraphs, can trash the formatting.
> The four-space indentation preceding the name merely adds insult to
> injury.
>
> Some people try to make SuperCite less offensive by using the previous
> poster's initials instead of their name. This, however, can have really
> ugly consequences, as the time on another mailing list that I saw a
> Jewish man's name replaced by his initials, "SS". He did not appreciate
> this in the least; I trust the reason is obvious.
>
> Craig
> > I am new to Linux. I am trying to get Intel? PRO/100 VE adapter
> > working on my newly installed box running Debian (woody) with kernel
>
> Since no one explicitly said it, you have a fine network card. It
> uses the eepro100 driver. I have used them for years at work. Pricey
> though but okay if someone else is paying. :-)
>
> I installed the driver at debian install time and it just worked. At
> the point in the b-f install where it asks you to configure kernel
> device drivers you need to specifically scroll down to some/thing/net
> and select that subpage. In that subpage scroll down to eepro100 and
> select it. Then exit out of the driver selection page and it will
> automatically walk you through the network setup. DHCP yes or no, if
> no then static IPs for DNS, etc.
>
> But frankly I don't know how you would install this later such as
> after a system is up and running. I have eepro100 in my /etc/modules
> file so I suppose that you would need to put that there and modprobe
> it as suggested by others. Then probably there is a 'dpkg-reconfigure
> something' which will walk you through that. I don't know. Can
> someone suggest the helper utility that walks the user through that?
>
> Bob
> On Wed, Jul 31, 2002 at 10:13:28PM -0700, Richard Otte wrote:
> > I've been trying to send pdf files as email attachments in mutt.
> > Whenever I send these to someone using windows, they are unable to open
> > the files using acrobat. One of them just sent the pdf file back to me,
> > and I am also now unable to open it. That makes me suspect that the
> > problem is that something is happening to the files in email. Does
> > anyone know why this happens, and is there a way to send pdf attachments
> > to windows users with mutt. Thanks,
>
> Hmm, can't see why this should be a problem.
>
> Have you tried sending a pdf file to yourself, and then verifying it
> looks OK? Try checking the md5sum of the file before sending and after
> receiving to see if it has changed.
>
> I take it you're just using the normal attachment procedure (a to attach
> file, and so on)?
>
> - Chris
>
> PS: If you want to send me a PDF file off-list to test, feel free.
> On Wed, Jul 31, 2002 at 11:16:50PM -0600, Bob Proulx wrote:
> > > I am new to Linux. I am trying to get Intel? PRO/100 VE adapter
> > > working on my newly installed box running Debian (woody) with kernel
>
> <snip>
>
> > But frankly I don't know how you would install this later such as
> > after a system is up and running. I have eepro100 in my /etc/modules
> > file so I suppose that you would need to put that there and modprobe
> > it as suggested by others. Then probably there is a 'dpkg-reconfigure
> > something' which will walk you through that. I don't know. Can
> > someone suggest the helper utility that walks the user through that?
>
> modconf.
>
> - Chris
> Chris Kenrick <chrisk@aurema.com> [2002-08-01 15:22:49 +1000]:
> > > it as suggested by others. Then probably there is a 'dpkg-reconfigure
> > > something' which will walk you through that. I don't know. Can
> > > someone suggest the helper utility that walks the user through that?
> >
> > modconf.
>
> Excellent! Thanks. But unfortunately that only does the modules and
> not the network configuration. But good enough for a start.
>
> MarkZ, ignore what I said before about /etc/modules. Instead do this
> as the root user.
>
> modconf
>
> Then scroll down to this and select it.
>
> kernel/drivers/net Drivers for network interface cards
>
> Then scroll down to this and select it.
>
> eepro100 - EtherExpress Pro/100 support
>
> It should do the modprobe itself and if it found your card you are
> good to go. Exit out of that.
>
> Now all that is needed is the network setup helper. DHCP, yes or no,
> etc.
>
> Bob
> On Wed, Jul 31, 2002 at 11:51:00PM -0400, Patrick Wiseman wrote:
> > On Wed, 31 Jul 2002, Paul M Foster wrote:
> > > So the instructions at the bottom of these emails (and the "help" email
> > > you get from the listserv, and the intro email you get when signing up)
> > > are wrong.
> >
> > Curiously, though, they work.
>
> But not for a hapless originator of this thread, apparently. Thus, he
> should try the Majordomo Way, and put his "unsubscribe" in the body of
> the email.
>
> Paul
Reply to: