Linux-Development-Sys Digest #744, Volume #6     Tue, 25 May 99 21:13:57 EDT

Contents:
  Re: never reboot to upgrade ? ("G. Sumner Hayes")
  advance power management ("Paul D. Pandian")
  Re: advance power management (Moritz Franosch)
  Re: Modularizing loop device encryption filters (Jan Fredrik Leversund)
  Large CD-ROM file errors...? (Mark Tranchant)
  Re: Modularizing loop device encryption filters ("B. James Phillippe")
  [q] sg.c (Kim Tae Hyung)
  ATX auto power-off (Andreas Braun)
  Re: Problems on booting a new compiled kernel (2.2.6) (Konrad Mieredorff)
  Re: Modularizing loop device encryption filters ("G. Sumner Hayes")
  Need help about kerner sys_xxx file functions ("Yann WANWANSCAPPEL")
  Linux and Power Management ("Jeffrey Noll")
  TCP Scale window option not implemented in Linux? ([EMAIL PROTECTED])
  Re: Destructive Erase? (Eric Hegstrom)
  Re: TCP/IP Libraries ("Mathew Verdouw")
  driver needs to find another driver... how?? ("Dan Miller")
  Re: You can now use Winmodems in Linux!!!!!!! (david parsons)
  Re: [q] sg.c ("Sungmin Chun")
  Re: Modularizing loop device encryption filters (J.H.M. Dassen (Ray))

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

From: "G. Sumner Hayes" <[EMAIL PROTECTED]>
Subject: Re: never reboot to upgrade ?
Date: Tue, 25 May 1999 13:15:42 -0400

Tony Smith wrote:
> 
> "G. Sumner Hayes" wrote:
> > FWIW, a couple of years ago a lot of clustering solutions were 
> > using HIPPI at 800-1600 Mb/sec, which is 100-200 megabytes/sec.
>
> I have never heard of HIPPI though, could you elaborate?

There's lots of introductory material at:
 http://www.cern.ch/HSI/hippi/

It looks like they're up to 6400 Mb/sec, or 800 megabytes/sec. That's
pretty amazing IMO.  They're calling it GSN these days, too.  There
are some links to commercial GSN vendors from the GSN pages there.

--Sumner

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

From: "Paul D. Pandian" <[EMAIL PROTECTED]>
Subject: advance power management
Date: Wed, 26 May 1999 01:52:20 +0800

I am using RedHat 5.2 with kernel version 2.0.36. I configure it and ensure
that advance power management is selected, together with the option for
power off at shutdown selected as well. All is fine now. The system
dutifully shuts down and automatically power offs when asked to. (Saves time
hanging around waiting for all services to terminate, and then having
manually to turn the power off.)

Okay: Question. I upgraded the kernel to 2.2.0 (and tried all the rest
upwards too inlcuding the latest 2.3.3). System cannot shutdown. Even when I
selected the APM options under kernel configuration and compilation.

What do I do ?

Thanks everyone for your time.
Regards,
Paul



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

From: Moritz Franosch <[EMAIL PROTECTED]>
Subject: Re: advance power management
Date: 25 May 1999 20:39:26 +0200



> Okay: Question. I upgraded the kernel to 2.2.0 (and tried all the rest
> upwards too inlcuding the latest 2.3.3). System cannot shutdown. Even when I
> selected the APM options under kernel configuration and compilation.

By "system cannot shutdown" you probably mean "power is not switched
off during shutdown and the system ignores all apm commands too".

If you only have one processor, switch off SMP in the kernel
configuration.
APM does not work with SMP or it does not work properly with SMP
depending on your hardware and BIOS.

This also has been reported, but I have not tried it:
You could, however, try adding "apm=smp-power-off" to your kernel-cmdline.


Moritz

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

From: Jan Fredrik Leversund <[EMAIL PROTECTED]>
Subject: Re: Modularizing loop device encryption filters
Date: Tue, 25 May 1999 16:51:58 +0200
Reply-To: [EMAIL PROTECTED]

"J.H.M. Dassen (Ray)" wrote:
> Crypto patches for current kernels are actively maintained; see
> http://www.kerneli.org/ for details.

Yes, I know this.

Anyway, my point was also that it would make such maintainance efforts
unnecessary of it was possible to write crypto-filters that needed no
kernel patching (ie. a module that plugs into the loop system).

It also represents a licensing problem when you have to patch the kernel
in order to add a new encryption method. This could mean that commercial
vendors are reluctant to make encryption filters available. An inserted
module is not bound by the GPL.

--
Jan Fredrik Leversund ([EMAIL PROTECTED])
Consultant at Avenir (http://www.avenir.no)
Phone: +47-55360592, Cellular: +47-90198866
Address: Strimmelen 8, 5030 LAND�S, Norway

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

From: Mark Tranchant <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Large CD-ROM file errors...?
Date: Tue, 25 May 1999 16:05:55 +0100
Reply-To: [EMAIL PROTECTED]

I got a friend to burn the StarOffice 5.1 download onto a CD-R for me
rather than taking it home on 51 floppies. This CD-R was burned under
Windows 95, with a file name of so51_lnx_01.tar (note: a long file
name!).

On getting home, I booted up Linux (2.2.9, with full CD support
including Joliet compiled in) and tried to copy the 70.6MB file.
However, Linux could only see the first 16MB or thereabouts. The copy
succeeded and tar de-archived the file fine up to the truncation.

So I tried DOS (7.0), which saw it as many files of about 650KB each,
all with the same name. Argh!

Windows 95 read it correctly and copied it fine, although it took *ages*
(about 20 minutes on a 486DX4/120 with 24x EIDE drive).

What's going on?

Mark.

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

From: "B. James Phillippe" <[EMAIL PROTECTED]>
Subject: Re: Modularizing loop device encryption filters
Date: Tue, 25 May 1999 08:42:54 -0700

On Tue, 25 May 1999, Jan Fredrik Leversund wrote:

> I recently found myself manually patching encrytion filters from kernel
> 2.0.x into the loop device code in 2.2.x and 2.3.x kernels. It struck me
> while I was working with it that this kind of stuff would probably be
> best to modularize, that is, leave the filters out of the loop code and
> just write some generic filter interface.

Yes, I came to the same conclusion when working on the encryption methods
within our IPsec stack, particularly when trying to replace some of the
encryption with hardware driver functions.

My opinion is that encryption shouldn't be inlined into any specific kernel
driver, and instead should be a pluggable module that any part of the
kernel can use.

> Is anybody working with this right now? Is this something people would
> want, or am I the only person paranoid enough to actually encrypt my
> filesystems?
> 
> If nobody's working on it, I could take a closer look at it. Help and
> suggestions are welcome, of course.

I am working on a project called "kcipherd".  This will be completely
modular and require no kernel patching.  I do not know how successful this
project can be; I am in the U.S.

-bp
--
B. James Phillippe              . [EMAIL PROTECTED]
Software Engineer, WGT Inc.     . http://www.terran.org/~bryan



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

From: Kim Tae Hyung <[EMAIL PROTECTED]>
Subject: [q] sg.c
Date: 25 May 1999 15:16:51 GMT

        Hi.....
        
        I must analyze the sg.c source file.
        But, I can get only SCSI-programming-HOWTO document.
        I think that is only how to use it.
        
        Is there any good information about sg.c file?

-- 
############################################
Name     : Kim Tae Hyung
homepage : http://www.postech.ac.kr/~kotaeji
email    : [EMAIL PROTECTED]
############################################

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

Date: Tue, 25 May 1999 21:04:20 +0200
From: Andreas Braun <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: ATX auto power-off

Is it possible to catch the power-switch (ATX boards) and shutdown a
Linux system savely (if switched off)?

How?

Thanks

Andi

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

From: Konrad Mieredorff <[EMAIL PROTECTED]>
Subject: Re: Problems on booting a new compiled kernel (2.2.6)
Date: Tue, 25 May 1999 18:11:44 +0200

"Elias Penttil�" wrote:
> 
> Hi,
> I have this problem: when i've made my own kernel and i try to boot Linux
> with it, the LILO works, but when it tries to load Linux it hangs at
> 'Loading Linux'.
> Please help me.
> 
> Elias.

Did you run edit /etc/lilo.conf and run lilo after you compiled your
kernel?

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

From: "G. Sumner Hayes" <[EMAIL PROTECTED]>
Subject: Re: Modularizing loop device encryption filters
Date: Tue, 25 May 1999 13:04:17 -0400

"B. James Phillippe" wrote:
> I am working on a project called "kcipherd".  This will be completely
> modular and require no kernel patching.  I do not know how successful 
> this project can be; I am in the U.S.

If you make the API a general one for all kinds of streaming
transforms (e.g. compression, base64 encoding, crypto, whatever)
then you can probably export it.  EAR prohibits the export of
any crypto software or software that is "specifically designed
to work with" crypto software, which generally is interpreted to
mean that crypto-specific hooks are verboten.  Naming it something
other than kcipherd (e.g. ktransformd) would also be a good idea.

The Snuffle decision isn't too meaningful until all the appeals 
are exhausted and there's a Supreme Court ruling that extends the
decision to the whole US.

--Sumner

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

From: "Yann WANWANSCAPPEL" <[EMAIL PROTECTED]>
Subject: Need help about kerner sys_xxx file functions
Date: Tue, 25 May 1999 19:58:10 +0200

Hi !

I'm writting an Isdn4Linux low level driver for a new PCI ISDN card (not yet
available on market).

I already wrote a char mode driver for the card, and I'd like to perform
file ops such as open, close, ioctl
from the ISDN4Linux low level driver I'm writting now.

        ISDN4Linux                       ISDN4Linux Low Level Driver
Char Mode driver









                            open    ------------------------------------->
my_open

I saw  in kernel fs directory functions like sys_open, sys_close, ....  Are
these functions equivalent to user level
open, close,... functions ?

Another problem : looking in /proc/ksyms, I saw that some functions such as
sys_ioctl don't appear in the kernel public
symbol list whereas they are implemented the same way as sys_open, ... which
appear in the list. Is this normal ?


Thanks.

                                            Yann WANWANSCAPPEL











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

From: "Jeffrey Noll" <[EMAIL PROTECTED]>
Subject: Linux and Power Management
Date: Tue, 25 May 1999 06:18:50 -0400

    I'm looking to put a linux box in my trunk to to use as a radio/mp3
player and have a question
about power/hardware management. Ideally what i want is to never have to
completely shut
down the system. I really dont want to wait for the machien to reboot
whenever I turn the car
on. I'm hoping that I can do this by putting the machine in low power standy
mode.
    My question is simply, is this possible? Once i detect this can I put
both the HD and
cpu/mb into standby mode (naturally assuming the mb supports it) and then
wake it back up
when i detect the car ignition?
    Also, does anyone recommend a good board/cpu combination? I'm thinking
something around
a P200. I've looked a little bit into the Acorn, a strongarm seems it would
be ideal but they were
a bit pricy. I don't want to spend much more then I would for a cheapo P200
type setup.
    Any help or input appreciated!

    Jeff




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

From: [EMAIL PROTECTED]
Crossposted-To: 
alt.comp.linux,alt.os.linux,comp.os.linux,comp.os.linux.questions,hannet.ml.linux.kernel,alt.uu.comp.os.linux.questions
Subject: TCP Scale window option not implemented in Linux?
Date: Tue, 25 May 1999 10:46:05 -0400

Hello,
  As far as I have seen from the kernel code, the TCP window scale
option is not
implemented. That means that the maximum TCP window size can be 65536
bytes.
I would like to run some experiments with a much bigger window size.
I was wondering if anyone knows a patch to the kernel that implements
this TCP option
to scale up the window size?

Thanks in advance for your help.

Cuneyt Akinlar
[EMAIL PROTECTED]

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

From: Eric Hegstrom <[EMAIL PROTECTED]>
Subject: Re: Destructive Erase?
Date: Tue, 25 May 1999 15:53:39 -0700

I find if you can get the platters out, a microwave and a cuisanart does
a good enough job for me.

Dave Platt wrote:
> 
> In article <7hsr1s$5hp$[EMAIL PROTECTED]>,
> Graffiti  <[EMAIL PROTECTED]> wrote:
> 
> >If the original poster only wants to keep a person from finding it from the
> >command-line, then overwriting the file w/ garbage will work.  If he's
> >worried about the data being lifted from the physical media, he needs to
> >destroy the hard drive.
> 
> Right.  As I recall, "data overwrite" techniques are no longer
> considered adequate for the erasure / decommissioning of hard drives
> containing government-sensitive data (e.g. Classified or Secret).  Any
> sort of data-overwriting you can do is going to be partial, and (with
> a sufficiently sensitive magnetic detector such as a SQUID) it's
> usually possible to pick the "overwritten" data off of the edges of
> the track.
> 
> I believe that the current U.S. Government-recommended
> "decommissioning" procedure these days involves heating the entire
> hard drive to a temperature above the Curie point of the platters.
> This causes the recording medium to temporarily lose its ability to
> "remember" magnetic fields, and randomizes all of the magnetic
> domains.  Then, the drive is cooled down to room temperature, and
> physically shredded or hammered into little bits.
> 
> Moral: no computer these days should be sold without a large propane
> torch and a big hammer.
> 
> --
> Dave Platt                                           [EMAIL PROTECTED]
> Visit the Jade Warrior home page:  http://www.radagast.org/jade-warrior/
>   I do _not_ wish to receive unsolicited commercial email, and I will
>      boycott any company which has the gall to send me such ads!

-- 
Eric Hegstrom                          .~.
Senior Software Engineer               /V\  
Sonoran Scanners, Inc.                // \\          L I N U X
[EMAIL PROTECTED]        /(   )\  >don't fear the penguin<
520-617-0072 x402                     ^^-^^

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

From: "Mathew Verdouw" <[EMAIL PROTECTED]>
Subject: Re: TCP/IP Libraries
Date: Wed, 26 May 1999 08:56:49 +1000

Thanks for all the feedback,

I now remember all the Unix TCP stuff I did at uni (spent too long working
in windows since then).


Mathew Verdouw <[EMAIL PROTECTED]> wrote in message
news:NBq23.187$[EMAIL PROTECTED]...
> Hi All,
>
> I am about to change our office server from NT4 (I spit on it) to RH6.0.
> The only obstacle is that I need to write a TCP/IP server for some custom
> software.  Can anyone point me to where I can find a TCP/IP library and/or
> examples.  My C is a little rusty, so I need some tips.
>
> --
> Thanks
>
> Mathew Verdouw
> [EMAIL PROTECTED]
>
>
>
>



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

From: "Dan Miller" <[EMAIL PROTECTED]>
Subject: driver needs to find another driver... how??
Date: Tue, 25 May 1999 13:03:15 -0700

I'm writing a linkage driver that needs to hook up to another device driver
in the system.
As currently written, the major and minor numbers of the target device must
be passed
to the link driver when it is loaded, as arguments to insmod.  I find this
annoying, since
the required information is already available from the device node.
Unfortunately,
NONE of the normal functions for getting information from the device node
seem to be
valid in a device driver; stat(), open(), etc are all undefined.  When I try
to include
sys/stat.h, I get tons of duplicate definitions and other problems.

Is there some other way that I can find these values??  I only need them for
get_tty_driver(), which gives me the tty information for the target device.
It seems reallly odd that a device driver can't determine device
information...

            Dan Miller the confused




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

From: o r c @ p e l l . p o r t l a n d . o r . u s  (david parsons)
Subject: Re: You can now use Winmodems in Linux!!!!!!!
Date: 25 May 1999 16:11:53 -0700

In article <[EMAIL PROTECTED]>,
Christopher B. Browne <[EMAIL PROTECTED]> wrote:
>On 20 May 1999 01:44:07 GMT, Mark Hahn <[EMAIL PROTECTED]> posted:

>>not a big deal.  copper is way slow; I'll bet I could even drive a winmodem
>>from a RT user-space task, if the programming info were available.

>The problem is that user-space isn't good enough.  There is a need for
>whatever task services the modem to respond within strict time limits.

    Not if you're using the processor to compress and uncompress
    packets; the various compression protocols used in modems are fitted
    into an packet stream;  if you drop a packet or don't process it,
    the modem stream will grind to a stop and wait for the transform
    process to catch up to it.

    I suspect it would work out, under load, much like an ISA modem
    on a slowish dual-processor ia32 machine (I've a dual-processor
    80521/166 machine that runs 2.0.28;  when the box is rebuilding
    mastodon I lose about 500 bytes per second off the modem because
    the ISA bus is starved.)

    A Winmodem that simply passed compression and decompression up to
    the host processor would be a *wonderful* hackers tool for people
    (like me) who own both ends of the last mile.

                  ____
    david parsons \bi/ though bzip2 linux-2.0.28+logo.tar > /dev/dsp0
                   \/                     would probably be right out.

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

From: "Sungmin Chun" <[EMAIL PROTECTED]>
Subject: Re: [q] sg.c
Date: Wed, 26 May 1999 09:28:58 +0900

'Writing SCSI device driver' is available from
ftp://ftp.cs.unc.edu/pub/users/faith/papers/scsi.paper.tar.gz
This document is included in the khg(Kernel Hacker's Guide) from LDP.



Kim Tae Hyung <[EMAIL PROTECTED]>��(��) �Ʒ� �޽�����
news:7ieet3$ebu$[EMAIL PROTECTED]�� �Խ��Ͽ����ϴ�.
| Hi.....
|
| I must analyze the sg.c source file.
| But, I can get only SCSI-programming-HOWTO document.
| I think that is only how to use it.
|
| Is there any good information about sg.c file?
|
| --
| ############################################
| Name : Kim Tae Hyung
| homepage : http://www.postech.ac.kr/~kotaeji
| email : [EMAIL PROTECTED]
| ############################################



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

From: [EMAIL PROTECTED] (J.H.M. Dassen (Ray))
Subject: Re: Modularizing loop device encryption filters
Date: 25 May 1999 14:39:43 GMT

Jan Fredrik Leversund <[EMAIL PROTECTED]> wrote:
>I recently found myself manually patching encrytion filters from kernel
>2.0.x into the loop device code in 2.2.x and 2.3.x kernels.

Crypto patches for current kernels are actively maintained; see
http://www.kerneli.org/ for details.

HTH,
Ray
-- 
LEADERSHIP  A form of self-preservation exhibited by people with auto-
destructive imaginations in order to ensure that when it comes to the crunch 
it'll be someone else's bones which go crack and not their own.       
- The Hipcrime Vocab by Chad C. Mulligan    

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


** 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.development.system) 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-Development-System Digest
******************************

Reply via email to