Linux-Misc Digest #568, Volume #25               Sat, 26 Aug 00 10:13:02 EDT

Contents:
  Re: Reading vi files in windows (Fabian Gebhardt)
  Changing the keyboard language (Josef)
  Re: Linux, XML, and assalting Windows ("paul snow")
  Re: KPPP and PPPd Question (Timothy Murphy)
  Re: splitting files compatible to linux and winnt ([EMAIL PROTECTED])
  Re: security at university ([EMAIL PROTECTED])
  Re: NEWBIE-Shell scripting - When to use script variable vs. create tmp  file??? 
([EMAIL PROTECTED])
  Re: Linux, XML, and assalting Windows ("paul snow")
  Re: Reading vi files in windows (Andres Soolo)
  Re: NEWBIE-Shell scripting - When to use script variable vs. create tmp file??? 
([EMAIL PROTECTED])
  NFS or SAMBA with DHCP Server (SDI \"Semiconductor Instruments\")
  Re: NEWBIE-Shell scripting - When to use script variable vs. create tmp file??? 
(Martien Verbruggen)
  Re: Help for newbie stuck with linux boot floppy ([EMAIL PROTECTED])

----------------------------------------------------------------------------

From: Fabian Gebhardt <[EMAIL PROTECTED]>
Subject: Re: Reading vi files in windows
Date: Sat, 26 Aug 2000 14:25:00 +0200

There is also a little trick: Notepad doesn't understand the UNIX files, but the
old DOS 'edit' does!
So just open them in DOS 'edit' and save them. Or use some of the convert progs:
duconv, unix2dos, dos2unix...

-- 
CU, Fabian Gebhardt 
   
   E-Mail:      [EMAIL PROTECTED]
   ICQ#:        77948091
   Homepage:    http://www.ki.tng.de/~gebhardt
   Schul-Seite: http://www.ebg.org

------------------------------

Date: Sat, 26 Aug 2000 14:35:37 +0200
From: Josef <[EMAIL PROTECTED]>
Subject: Changing the keyboard language

Hi all!
How can I change the keyboard language for my linux system?
TIA

------------------------------

From: "paul snow" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.text.xml,comp.os.linux.setup,comp.os.linux.advocacy
Subject: Re: Linux, XML, and assalting Windows
Date: Sat, 26 Aug 2000 12:52:59 GMT


> > Let's reexamine the long suffering example again.  You are using an
office
> > productivity application.  You are working on a document that consumes 5
Meg
> > stored in a non-XML file.  You are given the option of saving it in
either
> > XML or the program's native format.  You choose the XML file format.
When
> > you examine the file you have just saved you find the XML the following
XML
> > "tokens" the the start of the file.
> >
> > <?xml version="1.0" encoding="iso-8859-1" ?>
> > <!DOCTYPE RST "http://localhost/fubar.dtd>
> > <RST>
> >     <R ID="0" >
> >     <F0>
> >
> > Followed by 6.5Meg of data of the follow kind
> >
> > alahasdfnaxvc9qweafva8712345lkf0asdf
> >
> > Followed by the closing tags:
> >
> >    </F0>
> >    </R>
> > </RST>
> >
> > What have you gained?
>
> Who's me?  The casual web browser, the company vice president, the
> programmer?
> Answer: nothing unless you know what the hell it is.
> If two companies wanted to share the data then they would agree on a
> method of encryption.  If someone wanted to share it with the whole world
> then they would make it nice simple english (swahili whatever).
>
> IanP

This is really getting close to what the origional post was all about!  Only
it is isn't what is in the document that I want to know, but the information
that is typically "encrypted" into the installation program!  I want to know
what files, directories, configuration settings, etc. that a program relies
on in order to be operational.  I know this information is in the install
program the developer provided.  Thus I often uninstall and reinstall the
program to try to fix the program (success rate: 20 percent).

The problem is that every software component is handed to me in the same,
encrypted format (a pile of installs from various venders).  No meta
information about how these structures are supposed to be interrelated.  No
single and separate "installation" facility (or what I would call a
"Software Rendering Facility") for collecting and tracking this information.

Perhaps the developer doesn't WANT me to know what they are going to do to
my computer's storage in order to install their program.  Well, in that
case, I don't want their product.  I am sick and tired of having a dead
machine because some stinking DLL or registry setting is screwed up, and I
haven't got any reasonable way of figuring it out.  In fact, I have such a
laptop (a four week old, top of the line Dell with a dead Windows 98)
sitting right over there in the corner.

My point is we have gotten past the idea that the writer is responsible for
laying out each page in a document.  Let's get over the idea that each
developer has the responsibility for laying out my storage.

There is little to hide when it comes to how to install software.  So why
don't developers just lay out what they need done in plain English (or
swahili whatever) already!






------------------------------

From: [EMAIL PROTECTED] (Timothy Murphy)
Subject: Re: KPPP and PPPd Question
Date: 26 Aug 2000 13:55:11 +0100

"Rinaldi J. Montessi" <[EMAIL PROTECTED]> writes:

>> >Is kppp SUID root?  The documentation for kppp (read it!)
>> 
>> Where exactly is this documentation?

>At the end of the locate rainbow?

Isn't that a slightly crazy place to put documentation?
Why not in /usr/doc/ with everything else?

>~]# locate kppp | grep doc | grep html

>Point your browser at the results, start with index.html, probably.

Thanks very much for the pointer.
Actually what I get is

/usr/share/doc/HTML/de/kppp/hayes.html
/usr/share/doc/HTML/en/kppp/hayes.html
/usr/share/doc/HTML/en/kpppload/gpl.html
/usr/share/doc/HTML/en/kpppload/index.html

But I'll see if I can find anything there.

I must admit that I'm completely baffled
by the KDE attitude to documentation.
It seems that a huge effort is going into this --
yet the simplest things,
like leaving the documentation in the normal place,
seem to be ignored.

I'm probably rather old fashioned,
but I think there is a lot to be said
for a 1 page man-page,
if only to point at other documentation.

I should say that I am (probably foolishly)
running KDE-1.92 under pinstripe.


-- 
Timothy Murphy  
e-mail: [EMAIL PROTECTED]
tel: 086-233 6090
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

------------------------------

From: [EMAIL PROTECTED]
Subject: Re: splitting files compatible to linux and winnt
Date: Sat, 26 Aug 2000 12:33:38 +0100

Garry Knight <[EMAIL PROTECTED]> did eloquently scribble:
> Christian Verbeek <[EMAIL PROTECTED]> wrote:
>>dear newsgroup,
>>
>>i am doing my everyday backup on my laptop running winnt4 using gnu-tar. 
>>the file is about 200megs big, so it does not fit on my zip-disks. i am 
>>looking for a way to split up the tar file to fit on multiple zip-disks 
>>and being able to merge the splitted files on my linux-computer.

> $ man split

Or indeed man tar
(tar has multi-volume support)

-- 
______________________________________________________________________________
|   [EMAIL PROTECTED]   | "Are you pondering what I'm pondering Pinky?"   |
|Andrew Halliwell BSc(hons)|                                                 |
|            in            | "I think so brain, but this time, you control   |
|     Computer Science     |  the Encounter suit, and I'll do the voice..."  |
==============================================================================

------------------------------

From: [EMAIL PROTECTED]
Subject: Re: security at university
Date: Sat, 26 Aug 2000 12:51:42 +0100

Damir Jurica <[EMAIL PROTECTED]> did eloquently scribble:
> Im building computer network at my uni with few computers. Im going to have
> one server computer that runs linux and I have few questions concerning
> security.How can I be sure that someone wouldnt crash system or erase some
> important files,just by getting rescue disk, mounting my disk to lets say 
> /mnt ,and doing there anything he likes. 

1: Diasable floppy booting in the BIOS
2: Passowrd protect the BIOS
3: Password protect LILO
4: Padlock the case.

Apart from locking the box in a room, that's the best you can do.

> I dont know how to solve this or prevent this.I cant spend my all day
> sitting at computer there..  So is there any way to prevent access to
> total system with rescue disk? Ideas,suggestions,anything?

Yes, see above.

-- 
______________________________________________________________________________
|   [EMAIL PROTECTED]   |                                                 |
|Andrew Halliwell BSc(hons)| "ARSE! GERLS!! DRINK! DRINK! DRINK!!!"          |
|            in            | "THAT WOULD BE AN ECUMENICAL MATTER!...FECK!!!! |
|     Computer Science     | - Father Jack in "Father Ted"                   |
==============================================================================

------------------------------

From: [EMAIL PROTECTED]
Subject: Re: NEWBIE-Shell scripting - When to use script variable vs. create tmp  
file???
Crossposted-To: comp.unix.aix,comp.unix.misc,comp.unix.shell
Date: Sat, 26 Aug 2000 13:25:22 +0100

Christopher Browne <[EMAIL PROTECTED]> did eloquently scribble:
> Linux does not have an exact equivalent to tmpfs, and thus while
> operations on files in /tmp do get cached for _read_ purposes, there is
> some degree of "write-thru" on output.

> In other words, the data does get shoved out to disk.

There's no reason why linux shouldn't mimic this though.
Linux does have Ramdisk capabilities, after all...
-- 
______________________________________________________________________________
|   [EMAIL PROTECTED]   |                                                 |
|Andrew Halliwell BSc(hons)| "The day Microsoft makes something that doesn't |
|            in            |  suck is probably the day they start making     |
|     Computer science     |  vacuum cleaners" - Ernst Jan Plugge            |
==============================================================================

------------------------------

From: "paul snow" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.text.xml,comp.os.linux.setup
Subject: Re: Linux, XML, and assalting Windows
Date: Sat, 26 Aug 2000 13:12:53 GMT

Let me get this straight.  I have posted a fairly long document that claims
that installation of software is nothing more than properly rendering
storage.  I also claim that this can be done automatically by a third party
so long as the developer exposes enough information (i.e. what must exist in
storage in terms of files, directories, and configuration settings) for a
third party to construct such a rendering.  Assuming we can do that, I go on
to lay out the associated benefits of the approach.

It would seem that you believe file system defining a computer system's
configuration is something more than just another structured data format.
It must be magic, then?

I am not the one that believes in Witchcraft.

Bob Hauck <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> On Fri, 25 Aug 2000 22:40:10 GMT, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
>
> [snip miracle-working]
>
> >Let's try to discuss what it is going to take to make the above
> >happen.
>
> Oh, you'll be having a talk about witchcraft then?
>
> [snip a few hundred lines of handwaving]
>
>
> --
>  -| Bob Hauck
>  -| To Whom You Are Speaking
>  -| http://www.haucks.org/



------------------------------

From: Andres Soolo <[EMAIL PROTECTED]>
Subject: Re: Reading vi files in windows
Date: 26 Aug 2000 13:13:00 GMT

Dances With Crows <[EMAIL PROTECTED]> wrote:

> ITYM "text conventions differing between DOS and Unix."  vi (and vim,
> and emacs, and joe, and nedit...) use '\n' as the line-ending character
> within text files.  DOS uses '\n\r' as the line-ending sequence.
To be exact, the DOS conventional newline consists of ASCII-chars 0x0D 0x0A
(or 13 10) that's ordinarily represented by '\r\n'.

> MacOS uses '\r'.
Since what '\n' exactly is is subject to local conventions, MacOS uses
'\n' too, but '\n' on MacOS is ASCII-10 that happens to be '\r' on most
other ASCII-based systems.  (This can be confusing, especially when writing
network protocols or file formats that are supposed to be OS-independent.)

ASCII defines 0x0D as CR (Carriage Return) and 0x0A LF (Line Feed).
Historically, typewriters, teletypes and then printers required separate
commands to return carriage to the left end of paper and to scroll the
main roll even though they're intuitively a single operation.  Since it's
much easier to handle newline as a single char than if it'd be a token
of multiple chars, it's been modified by different systems for simplification
purposes but different systems have done it in different ways and thusly
created incompatibilities.

-- 
Andres Soolo   <[EMAIL PROTECTED]>

Most general statements are false, including this one.
                -- Alexander Dumas

------------------------------

From: [EMAIL PROTECTED]
Crossposted-To: comp.unix.aix,comp.unix.misc,comp.unix.shell
Subject: Re: NEWBIE-Shell scripting - When to use script variable vs. create tmp 
file???
Date: Sat, 26 Aug 2000 13:21:09 GMT

Some consider Perl a shell scripting language of sorts.  If you use
Perl you can open a file and operate on it line by line, or character by
character, or whatever.  You can also forget sed and grep, and use the
Perl functionality.  THIS is the way that I would go.

Already the $$ has been pointed out, so no need to rehash that.

You can try some clever combinations of "cat" and "|" and ">" to read
the file and write back out to it:  e.g.

   cat bob.txt | sort -r > bob.txt

mtc

In article <8o3pe3$fcg$[EMAIL PROTECTED]>,
  "Ken Abrahamsen" <[EMAIL PROTECTED]> wrote:
> When doing shell scripting and needing to manipulate (sed, grep, etc)
file
> contents, what are generally accepted good shell programming practices
> determining when to assign the contents of a file to a shell variable
versus
> creating a tmp file and using the tmp to do all the work in?
>
> Avoiding tmp files means avoiding duplicate tmp file naming problems,
and
> the cleanup of these tmp files but what type of problems would be
created by
> using shell variables, especially if the contents of these shell
variables
> were loaded from a 'large' file. If there are size thresholds (i.e.,
it's a
> bad idea to use a shell variable if the data is over xxxx kilobytes,
but OK
> if under this), what do people find these thresholds to be? Any other
> pointers / recommendations would be appreciated.
>
> I'm trying to do better scripting, but find no information on these
type of
> 'style' guidelines.
>
> Thanks for your comments!
> ken
>
>


Sent via Deja.com http://www.deja.com/
Before you buy.

------------------------------

From: SDI \"Semiconductor Instruments\" <[EMAIL PROTECTED]>
Subject: NFS or SAMBA with DHCP Server
Date: Sat, 26 Aug 2000 15:45:25 +0200

This is a multi-part message in MIME format.
==============84E77F54B2407219CE97F698
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear Everyone,

I have sucessfully set up a DHCP server between Liux systems with the
eventual intention of also networking a windoze system with samba and a
mac all on the same network.
I chose DHCP because I found a really good book by coriolis (Setting up
a Linux Intranet Srver , www.coriolis.com) which explains how to do
this.
The only problem is that this wonderful book doesn't explain how you
should interface 2 systems together running linux.

I understand I have 2 possibilities:
1. Use NFS
2. Use smbfs, seeing as I already have to set up samba to interface the
mac and the windows system on the network anyway.

I have 2 questions:-

1. Should I use NFS to communicate between linux systems ?
If so, how do I  install NFS on my redhat 6.1 linux box and set it up as
a client under dhcp ?

2. Is it possible to use samba to run file transfers between my linux
boxes ?
Is this preferrable in terms of security considerations to running NFS ?

Also , How do I install samba on a linux 6.1 redhat system as a client
under a dhcp protocol ?



==============84E77F54B2407219CE97F698
Content-Type: text/x-vcard; charset=us-ascii;
 name="showe.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for SDI "Semiconductor Instruments"
Content-Disposition: attachment;
 filename="showe.vcf"

begin:vcard 
n:Howe;Stephen
tel;pager:none
tel;cell:Italy(39) 335 710 7756
tel;fax:Italy(39) 081 575 5835
tel;home:Italy(39) 081 598 3133
tel;work:Italy(39) 081 598 3133
x-mozilla-html:FALSE
org:SDI (Tel: Italy (39) 081 598 3133 Fax:Italy(39)081 575 5835)
adr:;;Via F. Russo,19;NAPOLI;;80123;ITALY
version:2.1
email;internet:[EMAIL PROTECTED]
title:Principal
x-mozilla-cpt:;32480
fn:Stephen Howe
end:vcard

==============84E77F54B2407219CE97F698==


------------------------------

From: [EMAIL PROTECTED] (Martien Verbruggen)
Crossposted-To: comp.unix.aix,comp.unix.misc,comp.unix.shell
Subject: Re: NEWBIE-Shell scripting - When to use script variable vs. create tmp 
file???
Date: Sat, 26 Aug 2000 23:46:31 +1000
Reply-To: [EMAIL PROTECTED]

On Sat, 26 Aug 2000 13:21:09 GMT,
        [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Some consider Perl a shell scripting language of sorts.  If you use

I don't think you're quite right here. 

Some people do consider Perl to be a scripting language, but I don't
think I've ever heard anyone call it a _shell_ scripting language before
now. Many discussions go on regularly about whether it is a scripting
language or a programming language, and people get in knots trying to
find out what the difference betweenthose two is. However, a shell is a
shell, and perl ain't one of those.

Maybe you know another 'some' than I do, and in that case you are right,
but they are still wrong.

> Perl you can open a file and operate on it line by line, or character by
> character, or whatever.  You can also forget sed and grep, and use the
> Perl functionality.  THIS is the way that I would go.

Perl is a good language for many system administration tasks, and often
you'll find that shell scripts that use a lot of sed, grep and awk will
benefit considerably from a rewrite in Perl. However, don't make the
mistake of using Perl when you need to call large numbers of external
programs. While perl can easily do tat, shells are normally better at
it.

Some things work well in shells, some in Perl, and some in C.  I believe
that that was more or less your point as well, but I couldn't just let
you call Perl a shell scripting language, now, could I? :)

Martien
-- 
Martien Verbruggen              | Since light travels faster than
Interactive Media Division      | sound, isn't that why some people
Commercial Dynamics Pty. Ltd.   | appear bright until you hear them
NSW, Australia                  | speak?

------------------------------

From: [EMAIL PROTECTED]
Crossposted-To: alt.os.linux,comp.os.linux.setup
Subject: Re: Help for newbie stuck with linux boot floppy
Date: Sat, 26 Aug 2000 21:53:26 +0800

Thank you,....i will tried it!!

TongEng Chiah wrote:

> i think ur hardisk is bigger than 8.4Mb, and linux may have problem
> accessing beyond 1024 cylinders.
>
> to solve the problem, boot up using ur floppy
>     edit the file /etc/lilo.conf
>
> there should be a option linear in the file, change it to lba32
> if not, just added lba32 in
> after that, do a
>     /sbin/lilo
>
> reboot after that.
>
> <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> > Hi, any help appreciated.......
> >
> > I'm currently using Gentus Linux GPL v3.0 with a dual Celeron ABIT BP-6
> > motherboard. I am using a boot floppy to boot into the system. My
> > regular LILO gets stuck at LI....and died. I'm using ATA66 harddisks
> > (and they are detected properly once we pass the initial boot sequence),
> > and i believe the kernel is already specially compiled in the CD to run
> > with ATA66.
> >
> > Am I missing something? There is also a problem when i use upgrade
> > option in the Gentus CD to upgrade to a higher version Linux(such as
> > from Gentus v1.0 to Gentus v3.0). It always get stuck, i suspect the
> > installer was unable to properly read the harddisk geometry.....and i
> > have to install as fresh.    :-(
> >
> > Thank you for any help.
> >
> > Regards
> > Damon
> >
> > P.S. - Gentus distro is very similar  to RedHat distro(actually i
> > believe it's exactly alike except with kernel compiled to handle UDMA
> > and some other special drivers).


------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.misc) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Misc Digest
******************************

Reply via email to