Text 3709, 119 rader
Skriven 2005-10-08 01:21:00 av CHARLES ANGELICH (1:123/140)
     Kommentar till en text av MAURICE KINAL
Ärende: software for linspire
=============================

123c7d35bf58
linux



Hello Maurice - 

CA>> Half of them are snobs, the other half are followers of
CA>> the snobs. We didn't get along very well at all. 

MK> More reason for me to say, 'They can keep it.' :-) 

True. I only mention OBERON because it is quite unique, has
Wirth in it's lineage, and I really did rewrite parts of it to
get it onto the www. I also rewrote the dispalys to fit my
640x480 monitor I was using at the time and rewrote the
filemanager display to line up the columns. Simple stuff but
helpful (to me). OBERON is my 'running gag' but it is a real OS
regardless. 

--8<--cut 

CA>> Ah yes, wasn't thinking about informing the kernel that a
CA>> device was no longer available. :-) 

MK> I was. I used to have a problem with plugging and
MK> unplugging usb flash disks and to 'fix' that I would simply
MK> unload the usb-storage module before plugging in a
MK> different one so that it would reinintialize the module
MK> with the new parameters. 

I vaguely recall your discussions about putting a full linux
install onto a usb storage device. 

MK> I wrote a script for it but no longer require it since
MK> things started working as advertised. I guess I was a tad
MK> ahead of the times. 

Your attempts were the first I heard of anyone trying to use a
usb drive for a portable linux. 

MK> I think the same could be done with a pci scsi and/or ide
MK> card as long as the controller is modularized and the
MK> drives are powered seperately, as in the case of the
MK> external scsi array. As long as none of them are mounted,
MK> or unmounted if need be, then simply removing the module
MK> for that device and then probing it once whatever changes
MK> are made in the array ought to renew what is available to
MK> the system to later mount if indeed simply restarting the
MK> hotplug script doesn't catch that without the need to
MK> remove the module for that device. The problem with this
MK> particular scheme is that you wouldn't be able to boot any
MK> of these devices unless it is available on bootup with the
MK> proper controller built in rather then modular. For my plan
MK> this isn't an issue since I don't require them to be
MK> bootable but rather swappable on the fly, not unlike
MK> changing CDs, except with harddrives. I've got a good
MK> reason for wanting such a scheme, believe it or not, but am
MK> in no rush to get it working. Finding the scsi array with
MK> drives for $10 helped prompt this experiment though. :-) 

Sounds doable but based on my past experience with hardware
there is always a 'gotcha' or two to overcome first. 

CA>> Yes, AMOF I think the GNU support for basic linux
CA>> functions has been exceptional. Linus and those who work
CA>> with the kernel seem to get all the attention but I
CA>> personally feel the GNU support is equally or even _more_
CA>> important and worthy of some recognition. 

MK> For sure. Definetly some good stuff coming from that
MK> direction. 

I do admire some of the thinking and coding that has gone into
the GNU portion of linux. I don't know enough about the kernel
to really appreciate what has been done with it. That may
change one day but for now I just observe and say "Hmmmm ....". 

--8<--cut 

CA>> I haven't scrounged around in the source code as yet but I
CA>> do have the impression that SlackWare (in general) follows
CA>> the "keep it simple" philosophy which makes
CA>> adding/removing modules and recoding a much easier thing
CA>> to do. 

MK> Not really easier then the rest, but you end up breaking
MK> less since there are few, if any, utilities that require
MK> the kernel to be the same as the one installed. I used to
MK> have to recomile things like pcmcia_cs every time I changed
MK> the kernel but that seems to have changed recently so
MK> things have gotten easier in that regard. 

Good. 

CA>> I was a huge fan of small/tight coding probably because I
CA>> learned ASM first before any other languages. 

MK> Fortran here but after the move to Solaris C became the
MK> most used language for me. I started appreciating scripting
MK> more as time went on but even there the most used ones are
MK> C-like. 

I was very fond of AWK for that reason. The similarity with C
code made it easy for me to adapt to. Haven't done much with
AWK lately but I do have it here and use previously written AWK
routines. 

>
>        ,                          ,
>      o/      Charles.Angelich      \o       ,
>     <|                              |>  __o/
>     / >          USA, MI           < \   __\__
 

--- * ATP/16bit 2.31 * 
... DOS the Ghost in the Machine! http://www.devedia.com/dosghost/
 * Origin: Try Our Web Based QWK: DOCSPLACE.ORG (1:123/140)