Linux-Misc Digest #794, Volume #25               Sun, 17 Sep 00 21:13:03 EDT

Contents:
  Re: The Truth About the Kursk Disaster (zorba)
  Re: ps always return 0 (Floyd Davidson)
  Re: Wish for a writable ISO-9660 compatible filsystem (Otto Wyss)
  Re: Goddamnit!  Can't download files (Praedor Tempus)
  Creating a SUSE rescue CD ([EMAIL PROTECTED])
  Re: Problem With Fdisk Utility (Bjarne Nygaard)
  Re: Linux & SCSI tools (nobody)
  Re: aic7xxx 2.4.0 kernel module...gone (Michael Meding)
  Re: The Truth About the Kursk Disaster (Robert Jones)
  Re: The Truth About the Kursk Disaster ("Tomas Kroown")
  Bru and cdrw (Brian Goodyear)
  Re: Newer versions of CDRECORD no longer work... (MH)
  circuit layout program (Glitch)

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

From: zorba <[EMAIL PROTECTED]>
Subject: Re: The Truth About the Kursk Disaster
Date: Sun, 17 Sep 2000 22:03:07 GMT

In article <[EMAIL PROTECTED]>,
  Brian Goodyear <[EMAIL PROTECTED]> wrote:
> "David .." wrote:
> >
> > Some new information has come to light over the Kursk disaster. For
>
> If it wasn't for the fact that quite a few real people drowned in that
> submarine incident, I might have found your parody amusing
-
I figured he was going to tellus about how the sub got attacked by
penquins and sank because of currently installed MS software onthe
ships navigations.
-
HTTP://www.inlink.com/~macstl/vault.htm


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

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

From: Floyd Davidson <[EMAIL PROTECTED]>
Subject: Re: ps always return 0
Date: 17 Sep 2000 13:31:59 -0800

Rafael <[EMAIL PROTECTED]> wrote:
>When I run "ps h pid" it always return 0, it does matter if the pid
>exist or not. What the problem it is. How it should be solved.
>Where to look for solution?
>
>Rafael

Try this:

  ps h _pid_ | grep _pid_

which will return 0 if ps reports a process with that pid, or 1
otherwise.

-- 
Floyd L. Davidson                          [EMAIL PROTECTED]
Ukpeagvik (Barrow, Alaska)

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

From: [EMAIL PROTECTED] (Otto Wyss)
Crossposted-To: comp.os.linux.development.system
Subject: Re: Wish for a writable ISO-9660 compatible filsystem
Date: Mon, 18 Sep 2000 00:14:24 +0200

Seems there is no enthusiasm for a writable ISO-9660 solution, so I
won't do anything.

O. Wyss

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

From: Praedor Tempus <[EMAIL PROTECTED]>
Subject: Re: Goddamnit!  Can't download files
Date: Sun, 17 Sep 2000 16:30:16 -0600

Paul Lew wrote:
> 
> On Sat, 16 Sep 2000 22:18:00 -0700, MH <[EMAIL PROTECTED]> wrote:
> >Praedor Tempus wrote:
[...]
> >> Lately I have been unable to download files.  I have
> >> tried with ncftp and plain old ftp.  Neither works.
> >>
> >> What happens is that it appears to download fine, all
> >> the way to the end, but at the end, the connection
> >> doesn't terminate and just doesn't complete.
> >>
> >> Using Netscape, I tried downloading a couple of
> >> RPMs from rufus.rpmfind.  Both rpms downloaded 100%
> >> but the download window will NOT close.  I cannot
> >> install the rpms because of this.
[...]
> >I have the exact same problem with RH 6.0 (2.2.16 kernel). It appears to
> >occur only with large files.  Still, I thought Linux was "one with the
> >Internet"...
> >So much for downloading distribution ISOs!!!
> >
> 
> I've used netscape 4.7x to download the oracle 8.1 distr of 384 megs that
> is just 1 file; so, large file download is ok.  Also have just downloaded
[...]
> Your "problem" may be just the max users for the site or when "everyone"
> is downloading the everything.  What "speed" is your access...

It is not simply based on file size.  I thought this initially as well
but have found it is not tenable.  I CAN download relatively small files
without difficulty and I can download SOME large files.  There are some
that are CONSISTENTLY troublesome for me (kernels, XFree86 src).  

I have found that if I am using Netscape (4.73...always 4.73.  Every 
version since that one that I try is unstable and give NUMEROUS bus
errors) I need to wait until the download indicator says that 100% of
the file is downloaded (and the transfer speed begins ticking downward).
At that point, I hit "Cancel" and then immediately reselect the file
for download.  This second time, the download indicator QUICKLY runs
up to 100% and the download actually completes successfully.  I have 
to do this semi-regularly.  There are some rpms, src tarballs or bzip
files that are ALWAYS a problem along this line.

My connection speed is ~600kbps.  I average about 500kbps.  This
happens regardless of the time of day or site.  Its like the final 
little negotiation that is required to terminate the download and
call it successful and finished doesn't occur.  

praedor

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

From: [EMAIL PROTECTED]
Subject: Creating a SUSE rescue CD
Date: Sun, 17 Sep 2000 23:24:36 GMT

I'm trying to create a rescue CD.  Actually, I'm using backuponcd and
have my toast.sh creating a few extra files and directories.   I have
it properly booting the SUSE 6.4 boot image, but when the process
completes, I want to run the rescue system, but it claims it can't find
it.  i've tried butting the rescue image in the root directory, I've
tried putting it in the disks subdirectory.  I'd like to know how to
get the SUSE boot disk to recognize the 'rescue' image to mount it and
continue for a quick emergency repair disk.

[I'm writing these on 'backup' CD's I want the units to be self
contained, this is why using the original CDs is not feasible]

Please e-mail a reply


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

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

From: Bjarne Nygaard <[EMAIL PROTECTED]>
Subject: Re: Problem With Fdisk Utility
Date: Mon, 18 Sep 2000 01:43:25 +0200

Frank the root wrote:
> 
> Hi, everybody
> 
> I'm presently trying to organize a particular partition order on a 20GB
> hard drive (/dev/hdb). Here is what it looks like (fdisk output):
> 
>    Device Boot   Begin    Start      End   Blocks   Id  System
> /dev/hdb1          1        1        7      56196   83  Linux native
> /dev/hdb2          8        8       1027  8193150    5  Extended
> /dev/hdb3         1024     1028     1792  6144862+  83  Linux native
> /dev/hdb4         1024     1793     1799    56227+  82  Linux swap
> /dev/hdb5          8        8        772  6144831    b  Win95 FAT32
> /dev/hdb6         773      773      1027  2048256    b  Win95 FAT32
> 
> Command (m for help): v
> Warning: partition 3 overlaps partition 4.
> Warning: partition 3 overlaps partition 6.
> Warning: partition 4 overlaps partition 6.
> 11229619 unallocated sectors
> 
> I don't know how to force the partitions 3 and 4 to start at another
> cylinder than 1024. Why that? Anyone has a solution?
> 
> Thank for sharing to knowledge.
> 
> Frank
> 
> --
> Ceux qui r�vent le jour, savent des choses qu'ignorent ceux qui
> r�vent la nuit.

You may have 4 primary partitions. Then if you want more partitions
you then have to do an extended partition. This is then declared as
the 4' primary.
The extended partion the has to fit the rest your harddisk if you want
to use it all. :)
In this extended partition you declare the rest of your logical
partitions.

That's it...

cu
Bjarne

-- 
+----------------------------------------------------------------------+
|             Bjarne Nygaard at home: [EMAIL PROTECTED]                |
|          ---this space is not intentionally left blank---            |
+----------------------------------------------------------------------+

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

From: nobody <[EMAIL PROTECTED]>
Subject: Re: Linux & SCSI tools
Date: 18 Sep 2000 07:57:02 -0700

[EMAIL PROTECTED] (Neil Cherry) writes:

> I have 2 Seagate drives and they are acting up on me. The first gets
> errors when reading or writting. I honestly think it's shot (barely
> used too!). The other is a 9G SCSI2 drive, I keep getting:
> 
> kernel:   Vendor: SEAGATE   Model: SX910800N         Rev: 8513 
> kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02 
> kernel: Detected scsi disk sda at scsi0, channel 0, id 5, lun 0 
> kernel: sda : READ CAPACITY failed. 
> kernel: sda : status = 1, message = 00, host = 0, driver = 28  
> kernel: sda : extended sense code = 3  
> kernel: sda : block size assumed to be 512 bytes, disk size 1GB.   
> kernel:  sda:scsi0: MEDIUM ERROR on channel 0, id 5, lun 0, CDB: Read
>          (6) 00 00 00 02 00  
> kernel: [valid=0] Info fld=0x0, Current sd08:00: sense key Medium Error 
> kernel: Additional sense indicates Medium format corrupted 
> kernel: scsidisk I/O error: dev 08:00, sector 0 
> kernel:  unable to read partition table 
> 
> This looks like it was dead from the start or I need to do a low level
> format. Any idea how I can attempt such a thing? Are there any
> addition SCSI tools for Linux?
> 
> -- 
> Linux Home Automation           Neil Cherry             [EMAIL PROTECTED]
> http://members.home.net/ncherry                         (Text only)
> http://meltingpot.fortunecity.com/lightsey/52           (Graphics)
> http://linuxha.sourceforge.net/                               (SourceForge)

My first rule with SCSI is CHECK THE CABLES!  Having said that, I just
sprung for a new Athlon Thunderbird system and am going through the pains
of getting it up and running.  This morning it started crashing on me
right and left.  I tried substituting different things, but I only have
one working SCSI cable at the moment. I do, however, have 2 SCSI controllers,
a Buslogic and a Tekram DC390F.  I was using the Buslogic so I swapped in
the Tekram, what a pain, I have to get the linux boot disk image and
color.gz disk image from their website (already had 'em fortunately), and
boot in and install and patch the kernel and rebuild.  Why can't Tekram
just be automatically included in new kernel versions the way Buslogic is?
Anyway, since putting in the Tekram, the system has behaved, so I'm sad to
say the Buslogic controller is suspect.  It could still be the cable though,
reconnecting it may have removed a kink in it or something.

  --------- Remove "UhUh" and "Spam" to get my real email address -----

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

From: Michael Meding <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.development.system,comp.os.linux.setup
Subject: Re: aic7xxx 2.4.0 kernel module...gone
Date: Mon, 18 Sep 2000 02:20:51 +0200
Reply-To: [EMAIL PROTECTED]

Hi Jeremy,

> I am using the 2.4.0-test7 kernel and I amusing the aic7xxx drivers with
> no problem. However, I have the drivers compile into the kernel, not
> loaded as a module. I made that mistake once and my machine would not
> boot. After reading the docs in the Documentation tree of the new kernel
> it clearly states **NOT** to load any of the SCSI stuff as a module if
> that is where you boot from. 

That is not true. You can use for example the aic7x module with an
initial ramdisk (you have to mkinitrd and specify it in lilo.conf) and
then boot up the system through a aic7x based controller without hassle.

RedHat uses this as standard on (all?) their distros.

For myself I do not see advantages in this behaviour so I use compiled
in support also, but this is a question of gusto.


Greetings

Michael


That was a X-post, wasn't it ?

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

From: Robert Jones <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,redhat.general,alt.linux
Subject: Re: The Truth About the Kursk Disaster
Date: Sun, 17 Sep 2000 19:05:41 -0500

Jerry L Kreps wrote:

> On Sun, 17 Sep 2000, David .. wrote:
> >Some new information has come to light over the Kursk disaster. For
>
> What's really scarey is that W2K is going to be used to control the new
> warships coming from the Newport News Inc. ship building facility, of which
> Gates is a large shareholder.

Some folks live and learn; others just live...

I remember very well that about the time that Gates was appropriating DOS, one
could walk into his neighborhood Radio Shack store and see RS calculators *in*
the showcase for sale to customers and TI calculators *on* the showcase for
totalling the customers' bills.  I might have made a comment or two about
that, too  :-)

--

  6:57pm  up  2:19,  1 user,  load average: 0.01, 0.05, 0.07



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

From: "Tomas Kroown" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,redhat.general,alt.linux
Subject: Re: The Truth About the Kursk Disaster
Date: Mon, 18 Sep 2000 11:21:09 +1100


Best bloody satirical story I have read for a long time.

Check out www.chaser.com.au  for more...

"David .." <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Some new information has come to light over the Kursk disaster. For
> those with short attention spans, the Kursk was the submarine that blew
> up and sank in the Artic Ocean killing all 118 on board. The Russians
> tried to blame the incident on a collision with an unidentified object.
> However, sonar tapes which recorded the blasts (a small one at first,
> then a much larger one two minutes later) cast doubt on these claims. A
> whistle blower within the Russian military has leaked that the crew of
> the Kursk was testing a new type of torpedo when the accident occured.
> It seemed very likely that the test didn't go quite as planned.
>
>  While rescue efforts to save the survivors of the Kursk failed, salvage
> crews were able to recover a 'Black Box' from the submarine which
> contained detailed accounts of the events leading up to the explosion.
> As luck would have it, we got a copy of those tapes.
>
>  It turns out that the submarine crew was trying to load Microsoft
> Windows on their fire control computer. Their intent was to replace the
> aging CP/M operating system with the flashier Windows OS. Apparently,
> the Russians didn't know about the legendary stability problems
> exhibited by Windows. The log tapes make this painfully obvious:
>
>  Captain: Is the new fire control Windows OS installed yet Comrade?
>
>  Seaman: Almost Sir. We just need to finish filling out the registration
> card.
>
>  Captain: Excellent. Soon we will be able to point and click our enemies
> into oblivian.
>
>  [evil laughter in background]
>
>  Seaman: Comrade Captain! It is booting! Look, it says "Preparing to run
> Windows for the first time".
>
>  [long pause]
>
>  Seaman: Arrgh! Sir, it wants me to reboot again. That makes the 27th
> time.
>
>  Captain: Hmmm. This is not encouraging. Go ahead and reboot again.
>
>  Seaman: Aye Sir.
>
>  [another long pause]
>
>  Seaman: Captain, it is up again. It says it found new hardware ... A
> CD-ROM drive and that it needs drivers.
>
>  Captain: Where are the drivers?
>
>  Seaman: On the CD-ROM.
>
>  Captain: You are joking, right?
>
>  Seaman: No Sir.
>
>  Captain: Reboot the damn thing again. I am starting not to like this
> Windows.
>
>  [another long pause]
>
>  Seaman: Sir! It is back! It says it found the Gorby2000 Torpedo and is
> looking for the device drivers. Do we have a driver disk?
>
>  Captain: I do not think so.
>
>  Seaman: I will tell it to use the default drivers.
>
>  [another long pause]
>
>  Seaman: Crap. It wants to reboot again.
>
>  Captain: How many times are we going to reboot today? This is taking
> forever. Our hull is going to rust out before this works.
>
>  [another long pause]
>
>  Seaman: Sir! It is up and this time it is not asking for anything!
>
>  Captain: Really? No device drivers? No registration cards? No user
> profiles?
>
>  Seaman: No Sir. I think it is ready.
>
>  Captain: Good work comrade. Now click on the fire control icon and let
> us see how this works.
>
>  Seaman: Clicking now, Sir.
>
>  [another long pause]
>
>  Captain: Why does the fire control screen have a dancing paper clip on
> it?
>
>  Seaman: I have no idea Sir.
>
>  Captain: Hmmm, well try clicking on the menu.
>
>  Seaman: Aye Sir. Let us see; Open E-mail, Spam a friend, Mail a Virus,
> Fire a Torpedo.
>
>  Captain: We will spam a friend later. Let us fire a torpedo.
>
>  Seaman: Aye Sir.
>
>  [another long pause]
>
>  Seaman: It is asking us to load the torpedo and to click when ready.
>
>  Captain: Torpedo room, load a torpedo in tube number 1!
>
>  [intercom:] This is the Torpedo room. The torpedo is loaded Sir.
>
>  Captain: Click on the continue button.
>
>  Seaman: Aye Sir.
>
>  [another long pause]
>
>  Seaman: It is asking for a target Sir.
>
>  Captain: Hmmm, target the Rainbow Warrior.
>
>  Seaman: Aye Sir. Damn! It says the torpedo is low on ink.
>
>  Captain: Click ignore. We will get some ink when we return to base.
>
>  Seaman: Aye Sir. We are ready to fire.
>
>  Captain: Very good. You may fire when ready comrade.
>
>  Seaman: Firing torpedo Sir.
>
>  [another really long pause]
>
>  Captain: Well?
>
>  Seaman: I am trying Sir. Nothing is happening. Wait a minute....
>
>  [a loud explosion is heard in the background followed by screaming on
> intercom]
>
>  Captain: WTF was that?!?!?
>
>  Seaman: Captain! A new screen has appeared!
>
>
>  Outlook Express Fire Control has performed an illegal operation and
> will be shut down.
>
>  Click 'OK' to continue.
>
>
>  Seaman: Oh my God! The paper clip has died! What should I do?
>
>  Captain: Shut it down! Shut it down!
>
>  Seaman: It is not responding Sir!
>
>  Captain: Try 'CTRL-ALT-DELETE'!
>
>  Seaman: Aye Sir. We are in luck! The task manager is still operating. I
> am instructing the task manager to shut down Outlook Fire Control.
>
>  [another long pause]
>
>  Seaman: The task manager says that Outlook Fire Control is not
> responding.
>
>  Captain: Well no shit. Tell it to 'end task'.
>
>  Seaman: Nothing is happening Sir.
>
>  Captain: Try 'CTRL-ALT-DELETE' again.
>
>  Seaman: Aye Sir.
>
>  [sounds of frantic pecking on keyboard.]
>
>  Seaman: Oooh! What a pretty blue screen!
>
>  Captain: Holy Shit! Not the blue screen of dea....
>
>  [ KABLAM! A really big explosion. More screaming and the sound of
> rushing water.]
>
> --------------------------------------------------------
>
>  The tape ends at this point.
>
>  During the week long rescue effort, divers reported hearing tapping in
> the form of morse code coming from survivors inside the damaged sub. The
> rescuers couldn't understand why a group of men would spend the last of
> their strength tapping out "windows sucks" in morse code. The tapes of
> the last moments of the Kursk may offer some insight into this.
>
> --
> Where do you want to go today?



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

Date: Sun, 17 Sep 2000 20:43:49 -0400
From: Brian Goodyear <[EMAIL PROTECTED]>
Subject: Bru and cdrw

I am using the version of Bru that came with Corel linux.  It works fine
except in one situation.

If I use this command line:

        bru -cvvvv -s 640M -f - /home/* | cdrecord dev=3,0 speed=4 -eject -

it winds it's way though till it gets around the 650 mark and then bru
says something to the effect that "-" is not a directory, shall we
backup "-" y/n

If I press n, it just asks the question again, if I press y cdrecord
aborts and ejects cause the disk is full.

I am under the impression that I should be able to feed it another one
but the script or whatever it is bumps me back to the command line.  Any
ideas?
Brian

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

From: MH <[EMAIL PROTECTED]>
Subject: Re: Newer versions of CDRECORD no longer work...
Date: Sun, 17 Sep 2000 18:03:35 -0700
Reply-To: [EMAIL PROTECTED]

Dances With Crows wrote:
> 
> OK, great... but:  What type of CD-RW are you trying to access
> (IDE/ATAPI, external parport, SCSI) and what did "cdrecord -scanbus"
> tell you?  If cdrecord -scanbus doesn't show your CD-RW as being listed,
> then there's no chance that cdrecord will work.  /dev/pg6 is the 6th
> device on the virtual SCSI bus used for parport-connected devices, and
> it's extremely unlikely that you have 6 devices connected to your
> parallel port.  If you have something like a ZIP drive stuck to your
> parallel port, and an internal IDE CD-RW, there's an excellent chance
> that your ZIP is on SCSI controller 0 and your CD-RW is on SCSI
> controller 1.
> 

If what you say is true about /dev/pg6, then evidently cdrecord is
trying to access my IDE CD-ROM, which is *read-only*, and is ignoring my
SCSI CD-ROM, which is RW--in spite of the fact that I am *telling* it
which device to use. Nice.

I did not have this problem using an early version of cdrecord on this
system.

BTW--This is what I get with cdrecord -scanbus:

Cdrecord 1.8 (i686-pc-linux-gnu) Copyright (C) 1995-2000 J�rg Schilling
cdrecord: No such file or directory. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you
are root.

Note THAT I AM logged on as root.


> 
> BTW, since you do actually understand SCSI terminology/settings, do you
> reccommend black or white goats for use in consecrating HVD equipment?
> :-]
> 

You never sacrifice goats--you sacrifice pigs.

-- 
Don't waste your vote.  Vote Green, or don't vote at all.

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

Date: Sun, 17 Sep 2000 21:14:13 -0400
From: Glitch <[EMAIL PROTECTED]>
Subject: circuit layout program

Can anyone recommend a good circuit layout program?  I am taking my
first 2 electronics classes and would
like to make some 'virtual' circuits in class with my laptop. I tried
klogic but I don't like it much (but maybe that was because it was
before I actually started to take my classes and knew what I was doing).

Can anyone point me to some good ones out there?

Thanks

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


** 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