From significant.bit at gmail.com Sun May 2 07:46:43 2010 From: significant.bit at gmail.com (Mike Erwin) Date: Sat, 1 May 2010 17:46:43 -0500 Subject: [ydl-gen] Sony sued over removal of Linux support from PS3 Message-ID: Normally I wish people well... but I hope Sony has to pay for their bait & switch. The PS3 has been fantastic for games and movies, but its main appeal (for geeks like me) was as a Cell programming workstation. My army of PowerMacs is no longer supported, but at least Apple didn't remotely disable them! Or turn them into iTunes Music Store kiosks. That's essentially what Sony has done. Mike Erwin musician, naturalist, pixel pusher, hacker extraordinaire > http://www.wired.com/threatlevel/2010/04/playstation-linux/ From sjh at adfa.edu.au Tue May 4 11:36:16 2010 From: sjh at adfa.edu.au (Stephen Harker) Date: Tue, 4 May 2010 12:36:16 +1000 Subject: [ydl-gen] YDL 6.2 and dri Message-ID: <20100504023616.GA29498@h42180.pems.adfa.edu.au> As some may recall there was some discussion about lack of direct rendering support on at least some Apple computers last year. An example being my iBook G4 2005 which had direct rendering under YDL 6.1 and 5.02. To exemplify, under my current kernel (2.6.32.9) from dmesg I get: dmesg | grep -e drm -e radeon [drm] Initialized drm 1.1.0 20060810 [drm] radeon defaulting to userspace modesetting. [drm] Initialized radeon 1.31.0 20080528 for 0000:00:10.0 on minor 0 [drm] Setting GART location based on new memory map [drm] Loading R300 Microcode platform radeon_cp.0: firmware: requesting radeon/R300_cp.bin [drm] Num pipes: 1 [drm] writeback test succeeded in 1 usecs While the most relevant lines from my Xorg.0.log are: grep -e drm -e radeon -e EE Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (II) Loading extension MIT-SCREEN-SAVER (II) LoadModule: "radeon" (II) Loading /usr/lib/xorg/modules/drivers//radeon_drv.so (II) Module radeon: vendor="X.Org Foundation" drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: Searching for BusID pci:0000:00:10.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: drmOpenMinor returns 8 drmOpenByBusid: drmGetBusid reports pci:0000:00:10.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: Searching for BusID pci:0000:00:10.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: drmOpenMinor returns 8 drmOpenByBusid: drmGetBusid reports pci:0000:00:10.0 (II) [drm] DRM interface version 1.3 (II) [drm] DRM open master succeeded. (II) RADEON(0): [drm] Using the DRM lock SAREA also for drawables. (II) RADEON(0): [drm] framebuffer handle = 0x98000000 (II) RADEON(0): [drm] added 1 reserved context for kernel (II) RADEON(0): [drm] installed DRM signal handler (II) RADEON(0): [drm] register handle = 0x22000000 (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers (II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers (II) RADEON(0): [drm] dma control initialized, using IRQ 48 (II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 9, (OK) drmOpenByBusid: Searching for BusID pci:0000:00:10.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 9, (OK) drmOpenByBusid: drmOpenMinor returns 9 drmOpenByBusid: drmGetBusid reports pci:0000:00:10.0 (EE) AIGLX error: dlopen of /usr/lib/dri/r300_dri.so failed (/usr/lib/dri/r300_dri.so: cannot open shared object file: No such file or directory) (EE) AIGLX: reverting to software rendering As you can see the problem appears to lie in the non-presence of /usr/lib/dri/r300_dri.so. A google search found that (for fedora, see ) this file was part of mesa-libGL. In the instant version of fedora this comprised: rpm -ql mesa-libGL /usr/lib/dri /usr/lib/dri/i810_dri.so /usr/lib/dri/i915_dri.so /usr/lib/dri/i915tex_dri.so /usr/lib/dri/i965_dri.so /usr/lib/dri/mach64_dri.so /usr/lib/dri/mga_dri.so /usr/lib/dri/r128_dri.so /usr/lib/dri/r200_dri.so /usr/lib/dri/r300_dri.so /usr/lib/dri/radeon_dri.so /usr/lib/dri/savage_dri.so /usr/lib/dri/tdfx_dri.so /usr/lib/dri/unichrome_dri.so /usr/lib/libGL.so.1 /usr/lib/libGL.so.1.2 However, for YDL 6.2 the equivalent comprises: rpm -ql mesa-libGL /usr/lib/dri /usr/lib/dri/libdricore.so /usr/lib/libGL.so /usr/lib/libGL.so.1 /usr/lib/libGL.so.1.2 This suggests we either need to rebuild Mesa or to update to a newer version. If anyone is feeling adventurous try guides such as: . -- Stephen Harker s.harker at adfa.edu.au PEMS UNSW at ADFA From wrythen at gmail.com Fri May 7 23:25:54 2010 From: wrythen at gmail.com (Mike Birlew) Date: Fri, 7 May 2010 08:25:54 -0600 Subject: [ydl-gen] Sony sued over removal of Linux support from PS3 In-Reply-To: Message-ID: I whole heartedly agree with you. I don't see how anyone on this thread could disagree, yld is why were here. If they get away with this, I fear as others do, that this will allow a wave of abuse by companies downgrading your product after they have advertised it as something else. All in the name of Intellectual Property and unconscionable EUA's. I'm seriously expecting to see a "power of attorney" clause in one of these someday. On Sat, May 1, 2010 at 4:46 PM, Mike Erwin wrote: > Normally I wish people well... but I hope Sony has to pay for their > bait & switch. The PS3 has been fantastic for games and movies, but > its main appeal (for geeks like me) was as a Cell programming > workstation. My army of PowerMacs is no longer supported, but at least > Apple didn't remotely disable them! Or turn them into iTunes Music > Store kiosks. That's essentially what Sony has done. > > Mike Erwin > musician, naturalist, pixel pusher, hacker extraordinaire > > > http://www.wired.com/threatlevel/2010/04/playstation-linux/ > _______________________________________________ > yellowdog-general mailing list - yellowdog-general at lists.fixstars.com > Unsuscribe info: > http://lists.fixstars.com/mailman/listinfo/yellowdog-general > HINT: to Google archives, try '<keywords> site:us.fixstars.com' > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sam.lummis at gmail.com Sun May 9 19:54:52 2010 From: sam.lummis at gmail.com (Sam Lummis) Date: Sun, 9 May 2010 22:54:52 +1200 Subject: [ydl-gen] Sony sued over removal of Linux support from PS3 In-Reply-To: Message-ID: I agree to an extent. However I understand from Sonys perspective their console was not made as a cheap alternative for Cell programmers to use but as a piece of consumer electronics which they sell at a loss in order to make money off software and in my opinion this allows greater control over their hardware opposed to a PC. I initially bought my launch PS3 instead of an Xbox simply because it had the OtherOS functionality and I enjoy programming and the Linux OS. Essentially I don't feel abused by Sony by the update, they'd already taken the functionality out of the new PS3's and if I you want to continue using the feature you can simply not update to the new feature and you can continue using the old firmware along with a proxy to access the PSN if you still use it. My question about YDL's continued support is if a relatively easy softmod is released at some point if they will exploit the new found hardware access? On Sat, May 8, 2010 at 2:25 AM, Mike Birlew wrote: > I whole heartedly agree with you. I don't see how anyone on this thread > could disagree, yld is why were here. If they get away with this, I fear as > others do, that this will allow a wave of abuse by companies downgrading > your product after they have advertised it as something else. All in the > name of Intellectual Property and unconscionable EUA's. I'm seriously > expecting to see a "power of attorney" clause in one of these someday. > > > On Sat, May 1, 2010 at 4:46 PM, Mike Erwin wrote: > >> Normally I wish people well... but I hope Sony has to pay for their >> bait & switch. The PS3 has been fantastic for games and movies, but >> its main appeal (for geeks like me) was as a Cell programming >> workstation. My army of PowerMacs is no longer supported, but at least >> Apple didn't remotely disable them! Or turn them into iTunes Music >> Store kiosks. That's essentially what Sony has done. >> >> Mike Erwin >> musician, naturalist, pixel pusher, hacker extraordinaire >> >> > http://www.wired.com/threatlevel/2010/04/playstation-linux/ >> _______________________________________________ >> yellowdog-general mailing list - yellowdog-general at lists.fixstars.com >> Unsuscribe info: >> http://lists.fixstars.com/mailman/listinfo/yellowdog-general >> HINT: to Google archives, try '<keywords> site:us.fixstars.com' >> > > > _______________________________________________ > yellowdog-general mailing list - yellowdog-general at lists.fixstars.com > Unsuscribe info: > http://lists.fixstars.com/mailman/listinfo/yellowdog-general > HINT: to Google archives, try '<keywords> site:us.fixstars.com' > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcenteno at ydl.net Mon May 10 06:40:45 2010 From: dcenteno at ydl.net (Derick Centeno) Date: Sun, 09 May 2010 17:40:45 -0400 Subject: [ydl-gen] Sony sued over removal of Linux support from PS3 In-Reply-To: Message-ID: <20100509174045.55ff9ca9@arakus> Dear Sam, First, I'll share a link to a thread on the YDL Board discussing this same topic: http://www.yellowdog-board.com/viewtopic.php?f=19&t=7266&p=38471#p38471 Next, I'll address the points you raised regarding the exploit created by Geohot by attempting to clarify the background issues. The problem is essentially one of perception regarding to whose "right of property" we are talking about when one creates or purchases any electronic device. First a tiny bit of history, Geohot reached fame by creating software/hardware modifications to the iPhone which allowed consumers who purchased it to use the full range of it's potential within any phone service the consumer used. This was great for the consumer as in the consumer's view s/he purchased the device to use as s/he saw fit to service the essential functions valued by the consumer. There is also behind this effort (and I'm sure Geohot is quite aware of this) the older tradition/view regarding the design purpose of Unix itself which always included the capacity to control every aspect of hardware; in that period of course these systems were owned by institutions and government agencies; it was critical for the Engineering/IT departments of that era to have and maintain full control. It was also common practice of that era, which continues today, for both manufacturers and IT departments share control of services and systems. Technology moved forward such that Linux incorporates, as we know, many, if not all the features of Unix, which allows anyone to have control over the hardware a consumer owns. However, as a society we have not exactly defined the relationship between an individual consumer and the manufacturer of the product that consumer purchased/owns. Does the consumer have the right to expect the same control and freedom to implement services the consumer finds advantageous to the consumer's interests although the manufacturer may not agree or have originally designed their product to address that task? Apple designed the iPhone to be a tool to be used exclusively with AT&T expecting consumers to abide by that restriction. Apple also years earlier also designed the first Macintosh with only a floppy drive and without an internal hard drive whose 68000 PowerPC CPU only could access 128K of RAM. What moved Apple forward then was the consumer's insistence that more was necessary to meet the consumer's vision of how to implement Apple's creation. An argument supported by the experience of other companies with their respective consumers is that this trend is not unknown and that a company's growth is related to how that company responds or addresses the demands of their consumers. Sometimes there are a convergence of ideas, services and new products -- sometimes nothing useful happens, markets change and companies die. It is not always clear what direction is best, but it is usually always the case that a series of direct interactions occur between manufacturers and consumers. There is a clear distinction and understanding of moving a product towards greater utility matching how the consumer envisions usage of the manufacturer's product versus the theft of concepts and inventions. If history is any guide of what creates a resolution usually such convergence is the result of market and technological factors, not legal maneuvering alone. Technological and market forces influence daily reality much faster as a rule. For instance, last year IBM announced that no further development on the Cell would occur and work instead had proceed ahead to a new CPU architecture which incorporates aspects of the Cell design integrated with Intel. This means that exclusively PowerPC based code programming has ended and has moved to code processed for x86 based systems. The introduction of the newer design was evidenced in the Toshiba SpursEngine which was avaiable in the Qosimo and Leadtek WinFast device which then sold for $150-$160; the current price for the Leadtek WinFast ranges between $20-$28. Access to the Leadtek WinFast requires the Leadtek SDK which is x86 based source which runs on x86 based Linux which is offered by the way by Fixstars as well. What is interesting however is that as advanced beyond the Cell as the WinFast is, newer CPU architectures will be coming to market very soon which are even better. Considering that IBM supplied the Cell to Microsoft (Xbox), Nintendo (Wii) and Sony (PS3) the new CPU architecture will be employed by these companies to replace the Cell, unless of course Sony is forced to stay with an antiquated architecture. The new CPU has more varied uses than being relegated to a game computer, so it should become more prevalent in the consumer marketplace than the Cell or any PowerPC system ever achieved. It will support however only x86 based operating systems and Linux. Regarding the question will Geohot's exploit, or any other similarly illegal violation, be supported by any commercial entity such as Fixstars - my guess is no. YDL, nor any of the related family of products were never haphazard hastily designed hacks which many exploits tend to be. Therefore any Linux (maybe Slackware or Debian or something else) which supports the exploit will not have the reliability which had been established by the YDL family produced by TSS or now Fixstars. There will be people who don't care one way or the other. However I believe Fixstars will very much care as they have a vested interest in maintaining the pristine name of YDL and related family of products as high quality product engineering which maintains dependable functionality. All the best... On Sun, 9 May 2010 22:54:52 +1200 Sam Lummis wrote: > I agree to an extent. However I understand from Sonys perspective > their console was not made as a cheap alternative for Cell > programmers to use but as a piece of consumer electronics which > they sell at a loss in order to make money off software and in my > opinion this allows greater control over their hardware opposed to > a PC. I initially bought my launch PS3 instead of an Xbox simply > because it had the OtherOS functionality and I enjoy programming > and the Linux OS. Essentially I don't feel abused by Sony by the > update, they'd already taken the functionality out of the new PS3's > and if I you want to continue using the feature you can simply not > update to the new feature and you can continue using the old > firmware along with a proxy to access the PSN if you still use it. > > My question about YDL's continued support is if a relatively easy > softmod is released at some point if they will exploit the new > found hardware access? > > > On Sat, May 8, 2010 at 2:25 AM, Mike Birlew > wrote: > > > I whole heartedly agree with you. I don't see how anyone on > > this thread could disagree, yld is why were here. If they get > > away with this, I fear as others do, that this will allow a wave > > of abuse by companies downgrading your product after they have > > advertised it as something else. All in the name of Intellectual > > Property and unconscionable EUA's. I'm seriously expecting to > > see a "power of attorney" clause in one of these someday. > > > > > > On Sat, May 1, 2010 at 4:46 PM, Mike Erwin > > wrote: > > > >> Normally I wish people well... but I hope Sony has to pay for > >> their bait & switch. The PS3 has been fantastic for games and > >> movies, but its main appeal (for geeks like me) was as a Cell > >> programming workstation. My army of PowerMacs is no longer > >> supported, but at least Apple didn't remotely disable them! Or > >> turn them into iTunes Music Store kiosks. That's essentially > >> what Sony has done. > >> > >> Mike Erwin > >> musician, naturalist, pixel pusher, hacker extraordinaire > >> > >> wrote: > >> > http://www.wired.com/threatlevel/2010/04/playstation-linux/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jamesnorred at ymail.com Sat May 15 09:07:57 2010 From: jamesnorred at ymail.com (James Norred) Date: Fri, 14 May 2010 17:07:57 -0700 (PDT) Subject: [ydl-gen] (no subject) Message-ID: <333489.75035.qm@web110812.mail.gq1.yahoo.com> jamesnorred at ymail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamesnorred at ymail.com Sat May 15 09:46:57 2010 From: jamesnorred at ymail.com (James Norred) Date: Fri, 14 May 2010 17:46:57 -0700 (PDT) Subject: [ydl-gen] (no subject) Message-ID: <285070.6598.qm@web110811.mail.gq1.yahoo.com> jamesnorred at ymail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicholas-jones at uiowa.edu Sat May 22 04:50:37 2010 From: nicholas-jones at uiowa.edu (Nick Jones) Date: Fri, 21 May 2010 14:50:37 -0500 Subject: [ydl-gen] Syslog question regarding mysterious shutdowns Message-ID: Hi, I have an xserve G5 running YDL 4.1 (I'm pretty sure, can't find a way to check this easily nor can I remember, but did a package search and that is what came up). It started gracefully shutting down on me every once in awhile for no rhyme or reason that I can see (I say graceful because I've encountered no signs of a crash, such as an inconsistent filesystem). I can't find anything in the logs regarding why it is shutting down. My conclusion is that syslogd is not saying anything about the shutdown to /var/log/messages or anything else under /var/log/* It is on a battery backup with several other pieces of hardware, all of which exhibit no problems related to power. I disconnected the USB cable from the battery backup but the problem persists. Any help would be appreciated. I hope I'm not missing something obvious. Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcenteno at ydl.net Sat May 22 11:16:44 2010 From: dcenteno at ydl.net (Derick Centeno) Date: Fri, 21 May 2010 22:16:44 -0400 Subject: [ydl-gen] Syslog question regarding mysterious shutdowns In-Reply-To: References: Message-ID: <20100521221644.59aba30f@arakus> On Fri, 21 May 2010 14:50:37 -0500 Nick Jones wrote: > Hi, > > I have an xserve G5 running YDL 4.1 (I'm pretty sure, can't > find a way to check this easily nor can I remember, but did a > package search and that is what came up). To find out what your system is running, just open a terminal and do: $ uname -r 2.6.29-3.ydl61.4 Explanation: At the $ you execute (from within YDL) the uname command with the r flag. The system will respond it did above. Here's a basic label explaining what the system is reporting: -> 2: the Kernel version -> 6: Major revision # of the kernel -> 29: Minor revision # of the kernel -> 3: revision # correcting critical bugs -> ydl61.4: YDL version # > It started gracefully shutting down on me every once in awhile > for no rhyme or reason that I can see (I say graceful because > I've encountered no signs of a crash, such as an inconsistent > filesystem). > > I can't find anything in the logs regarding why it is shutting > down. My conclusion is that syslogd is not saying anything > about the shutdown to /var/log/messages or anything else > under /var/log/* You may already be familiar with the following strategies which I'll invoke on my own system as an example: Explanation: The following checks the running of syslogd $ ps aux |grep syslogd root 3248 0.0 0.0 2036 688 ? Ss 17:09 0:00 syslogd -m 0 aguila 29234 0.0 0.0 4416 708 pts/2 S+ 19:12 0:00 grep syslogd Explanation: The following quickly checks the boot logs for outputs from syslog/d. $ dmesg |grep syslogd $ dmesg |grep syslog Explanation: The following checks for any output from anything named by "sys" just in case grep missed something. $ dmesg |grep sys SCSI subsystem initialized SGI XFS Quota Management subsystem EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs: mounted filesystem with ordered data mode. warning: process `kudzu' used the deprecated sysctl system call with 1.23. sysctl net.netfilter.nf_conntrack_acct=1 to enable it. $ > It is on a battery backup with several other pieces of > hardware, all of which exhibit no problems related to power. > I disconnected the USB cable from the battery backup but the > problem persists. > > Any help would be appreciated. I hope I'm not missing > something obvious. > > Nick Is it possible that your server is being shut down by the backup battery system you use because the power system is doing it's job and shutting down when the server demands more power than the backup power system can provide? Maybe it's time to : * check that the installed YDL version you has software monitoring the backup power supply system you use * check that your batteries on your back up system are "fresh" and don't require either upgrade or replacement as your power requirements may change or have changed depending upon the load of power your server requires as work intensifies. I see that you are running YDL 4.1. I checked the Fixstar hardware pages for YDL 6.2 looking for any description approaching what you described. I found interesting comments, but I'm not sure anything there applies to the model you have: http://www.ydl.net/support/hardware/apple-xserve.shtml Hopefully, the Fixstars webpage can help provide you enough information to suggest whether an upgrade to YDL 6.2 would be useful for you. Besides that option I thought you should check to make sure whether your version of yum is pointing to Fedora extras as software supporting apc UPS systems exist there. What follows is a search I invoked for "apc"; I've already provided yum the information it needs to search for it at Fedora Extras: $ sudo yum info "*apc*" Password: Loading "protectbase" plugin Loading "installonlyn" plugin PS3Bodega 100% |=========================| 1.9 kB 00:00 livna-stable 100% |=========================| 2.1 kB 00:00 base 100% |=========================| 1.1 kB 00:00 updates 100% |=========================| 951 B 00:00 fedora-extras 100% |=========================| 1.1 kB 00:00 dribble 100% |=========================| 951 B 00:00 Excluding Packages from Livna for Fedora Core 6 - ppc - Base Finished Excluding Packages from Fedora Extras Finished 121 packages excluded due to repository protections Available Packages Name : apcupsd Arch : ppc Version: 3.12.4 Release: 5.fc6 Size : 449 k Repo : fedora-extras Summary: APC UPS Power Control Daemon for Linux Description: Apcupsd can be used for controlling most APC UPSes. During a power failure, apcupsd will inform the users about the power failure and that a shutdown may occur. If power is not restored, a system shutdown will follow when the battery is exausted, a timeout (seconds) expires, or the battery runtime expires based on internal APC calculations determined by power consumption rates. If the power is restored before one of the above shutdown conditions is met, apcupsd will inform users about this fact. Some features depend on what UPS model you have (simple or smart). Name : apcupsd-cgi Arch : ppc Version: 3.12.4 Release: 5.fc6 Size : 150 k Repo : fedora-extras Summary: Web interface for apcupsd Description: A CGI interface to the APC UPS monitoring daemon. Name : perl-Mail-IMAPClient Arch : noarch Version: 2.2.9 Release: 3.fc6 Size : 420 k Repo : fedora-extras Summary: An IMAP Client API Description: This module provides perl routines that simplify a sockets connection to and an IMAP conversation with an IMAP server. Name : php-pecl-apc Arch : ppc Version: 3.0.12 Release: 1.fc6 Size : 77 k Repo : fedora-extras Summary: APC caches and optimizes PHP intermediate code Description: APC is a free, open, and robust framework for caching and optimizing PHP intermediate code. $ My system runs from a laptop so I don't need the ups utilities as you may. The ups utilities could provide a means for your version of YDL to manage communications with your ups better allowing the xserve to run longer. If you are interested I can share the code I use to program yum to search the livna and Fedora extras repositories (and install from them) while protecting the YDL base installation. All the best... -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From pointerleft at gmail.com Sat May 22 22:38:49 2010 From: pointerleft at gmail.com (james gray) Date: Sat, 22 May 2010 06:38:49 -0700 Subject: [ydl-gen] download package ? Message-ID: Hello I am having a psychotic moment while trying to find an actual icon, file, doc, or string of chars that would initiate a download of the YDL OS from a mirror. Question: does any one have a sane route to a YDL OS down load for the Mac G 4 PC. While at the YDL down load page i am relying on the words YDL when i go into a mirror to look for a down load, YDL is the only words that are associated with a down load at the Y D L down load page, besides ISO. Yes i can associate with the words Yellow Dog when i do see them. When they are there. The UK mirror seems to have a release for the Mac G4 PC. yet while there is was also a circle of links. And from the experience at the UK mirror and other mirrors i find it to be frustrating , i do not see any one download for a complete YDL OS . I am just chasing links in circles, it is a joke. Is there an actual download ? of a complete YDL OS, or is it pick and choose, "If" the down load is a pick and choose. where is the kernal, what abbreviated word is associated with the kernal the whole story seems to be a joke. any assistance in finding sanity would be appreciated. thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: From henry.olders at mcgill.ca Sat May 22 23:12:40 2010 From: henry.olders at mcgill.ca (Henry Olders) Date: Sat, 22 May 2010 10:12:40 -0400 Subject: [ydl-gen] download package ? In-Reply-To: References: Message-ID: What you need to download is an iso disk image, from which you burn a DVD. As the downloads page at http://www.yellowdoglinux.com/support/downloads/ says, go to the iso directory at a given mirror site. For example, at this mirror: http://ydl.oregonstate.edu/iso/ click on the file yellowdog-6.2-ppc-DVD_20090629.iso Henry On 2010-05-22, at 9:38 , james gray wrote: > > > > Hello > I am having a psychotic moment while trying to find an actual icon, file, doc, or string of chars that would initiate a download of the YDL OS from a mirror. > Question: does any one have a sane route to a YDL OS down load for the Mac G 4 PC. > > While at the YDL down load page i am relying on the words YDL when i go into a mirror to look for a down load, YDL is the only words that are associated with a down load at the Y D L down load page, besides ISO. > Yes i can associate with the words Yellow Dog when i do see them. When they are there. > > The UK mirror seems to have a release for the Mac G4 PC. > yet while there is was also a circle of links. > > And from the experience at the UK mirror and other mirrors i find it to be frustrating , i do not see any one download for a complete YDL OS . > I am just chasing links in circles, it is a joke. > Is there an actual download ? of a complete YDL OS, or is it pick and choose, > "If" the down load is a pick and choose. where is the kernal, what abbreviated word is associated with the kernal > the whole story seems to be a joke. > any assistance in finding sanity would be appreciated. > thank you > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pointerleft at gmail.com Sun May 23 03:44:35 2010 From: pointerleft at gmail.com (james gray) Date: Sat, 22 May 2010 11:44:35 -0700 Subject: [ydl-gen] thank you Message-ID: Thank you Henry Olders I was hoping to get a file map, here / here / here /. I could spend hours days weeks years looking at the plethora of Linux distro`s, trying to figure out what is what. And the People at Linux wonder why more people in the general public do not get involved. Thank you. some day if i get the time from writing code i will try to make it a mission to clarify clarity in Linux distro`s. Thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: From sjh at adfa.edu.au Mon May 24 07:58:26 2010 From: sjh at adfa.edu.au (Stephen Harker) Date: Mon, 24 May 2010 08:58:26 +1000 Subject: [ydl-gen] Syslog question regarding mysterious shutdowns In-Reply-To: <20100521221644.59aba30f@arakus> References: <20100521221644.59aba30f@arakus> Message-ID: <20100523225826.GA7545@h42156.pems.adfa.edu.au> A minor addition to Derick's comments: > > I have an xserve G5 running YDL 4.1 (I'm pretty sure, can't > > find a way to check this easily nor can I remember, but did a > > package search and that is what came up). > > To find out what your system is running, just open a terminal > and do: You can also do: cat /etc/yellowdog-release Yellow Dog Linux release 6.2 (Pyxis) The file /etc/yellowdog-release contains the release information. There is a similar file in many (most?) other releases. However, this is more system specific. Derick's suggestion is more general. > > It started gracefully shutting down on me every once in awhile > > for no rhyme or reason that I can see (I say graceful because > > I've encountered no signs of a crash, such as an inconsistent > > filesystem). > > > > I can't find anything in the logs regarding why it is shutting > > down. My conclusion is that syslogd is not saying anything > > about the shutdown to /var/log/messages or anything else > > under /var/log/* You can increase the amount of information stored in log files. I would only consider this if you don't find the problem with the suggestions given by Derick. An example of increasing/altering lot information is given in . Alternatively, although old I based my modifications on and have in /etc/syslog.conf: # Monitor all kernel messages kern.* /var/log/kernlog I don't recall what the default setting is, but if kernel messages aren't being logged it can be worth setting this even if only until you can see whether there is a problem reported in the kernel log and not in other logs. -- Stephen Harker s.harker at adfa.edu.au PEMS UNSW at ADFA From dcenteno at ydl.net Mon May 24 23:28:08 2010 From: dcenteno at ydl.net (Derick Centeno) Date: Mon, 24 May 2010 10:28:08 -0400 Subject: [ydl-gen] thank you In-Reply-To: References: Message-ID: <20100524102808.7ab9b462@arakus> Given what you posted previously I'm concerned whether you are familiar with the nuances involved in both using the SHA1SUM value and invoking the SHA1SUM test on the .iso you choose to download to burn onto a DVD. The difficulty is that if you are not familiar with it, you could easily download a defective .iso and burn an equally defective DVD - again, again, and yet again. This process ad nauseum wastes download time and burning time. Given how you already reacted, the potential frustration resulting from producing an incomplete and/or faulty DVD may be a process to avoid completely. Unfortunately without understanding the usage of the SHA1SUM value and the SHA1SUM test there is no way to determine if the .iso you downloaded before burning the DVD exactly matches the product originally released by Fixstars (or any other Linux distribution). If you determine that the information posted at the mirrors regarding the SHA1SUM are unclear I'd be happy to attempt a more effective explanation and post it here. All the best... On Sat, 22 May 2010 11:44:35 -0700 james gray wrote: > Thank you Henry Olders > I was hoping to get a file map, here / here / here /. > I could spend hours days weeks years looking at the plethora of Linux > distro`s, trying to figure out what is what. > And the People at Linux wonder why more people in the general public > do not get involved. > Thank you. > some day if i get the time from writing code i will try to make it a > mission to clarify clarity in Linux distro`s. > Thank you From pointerleft at gmail.com Wed May 26 02:56:46 2010 From: pointerleft at gmail.com (james gray) Date: Tue, 25 May 2010 10:56:46 -0700 Subject: [ydl-gen] default shell ? Message-ID: what is the default shell that Linux does use. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pointerleft at gmail.com Wed May 26 03:13:51 2010 From: pointerleft at gmail.com (james gray) Date: Tue, 25 May 2010 11:13:51 -0700 Subject: [ydl-gen] thank you In-Reply-To: <20100524102808.7ab9b462@arakus> References: <20100524102808.7ab9b462@arakus> Message-ID: Yes frustration does exist. !. I attempted sha1 in Bash and it does not work. seemingly. so i posted a question about 15 minutes ago, as to what is the default shell that Linux is built on. after all of the bs below, as i was cleaning off the desk top i did see a file with a Linux download drive inside and dragged it, the drive onto the terminal curser to get its path and tried to check it in a debug option and got nowhere. This is a small fragment of what i did try over a period of 3 hours: and several other variations from the man sha1 in BASH , i did go on line and found : openssl sha1 I then went in and did a debug option: $ openssl sha1 -d /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso BIO[00409A30]:ctrl(6) - FILE pointer BIO[00409A30]:ctrl return 0 BIO[00409A30]:ctrl(108) - FILE pointer BIO[00409A30]:ctrl return 0 /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso: No such file or directory BIO[00409A30]:Free - FILE pointer A issue of file permissions kept coming up so i did a Mac OS Disk Utility file permissions check and repair. and then did this: $ openssl sha1 -hex /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ Read Error in /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ 256:error:0200B015:system library:fread:Is a directory:bss_file.c:167: 256:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: -------------------------------------------- $ openssl sha1 -c /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ Read Error in /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ 276:error:0200B015:system library:fread:Is a directory:bss_file.c:167: 276:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: ----------------------------------------- $ open sha1 -verify /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ 2010-05-25 10:14:14.664 open[643] No such file: /Users/polymorphous/sha1 ---------------------------------- $ openssl sha1 -signature $ open sha1 -verify /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ open: No such file or directory sha1: No such file or directory -verify: No such file or directory Read Error in /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ 653:error:02001002:system library:fopen:No such file or directory:bss_file.c:278:fopen('open','r') 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: 653:error:02001002:system library:fopen:No such file or directory:bss_file.c:278:fopen('sha1','r') 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: 653:error:02001002:system library:fopen:No such file or directory:bss_file.c:278:fopen('-verify','r') 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: 653:error:0200B015:system library:fread:Is a directory:bss_file.c:167: 653:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: poly-morphous-Computer:~ polymorphous$ 2010-05-25 10:14:14.664 open[643] No such file: /Users/polymorphous/sha1 -bash: 2010-05-25: command not found On Mon, May 24, 2010 at 7:28 AM, Derick Centeno wrote: > Given what you posted previously I'm concerned whether you are familiar > with the nuances involved in both using the SHA1SUM value and > invoking the SHA1SUM test on the .iso you choose to download to burn > onto a DVD. > > The difficulty is that if you are not familiar with it, you could > easily download a defective .iso and burn an equally defective DVD - > again, again, and yet again. This process ad nauseum wastes > download time and burning time. > > Given how you already reacted, the potential frustration resulting from > producing an incomplete and/or faulty DVD may be a process to avoid > completely. Unfortunately without understanding the usage of the > SHA1SUM value and the SHA1SUM test there is no way to determine if > the .iso you downloaded before burning the DVD exactly matches the > product originally released by Fixstars (or any other Linux > distribution). > > If you determine that the information posted at the mirrors regarding > the SHA1SUM are unclear I'd be happy to attempt a more effective > explanation and post it here. > > All the best... > > On Sat, 22 May 2010 11:44:35 -0700 > james gray wrote: > > > Thank you Henry Olders > > I was hoping to get a file map, here / here / here /. > > I could spend hours days weeks years looking at the plethora of Linux > > distro`s, trying to figure out what is what. > > And the People at Linux wonder why more people in the general public > > do not get involved. > > Thank you. > > some day if i get the time from writing code i will try to make it a > > mission to clarify clarity in Linux distro`s. > > Thank you > > _______________________________________________ > yellowdog-general mailing list - yellowdog-general at lists.fixstars.com > Unsuscribe info: > http://lists.fixstars.com/mailman/listinfo/yellowdog-general > HINT: to Google archives, try '<keywords> site:us.fixstars.com' > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rarob at travelinglightfarm.net Wed May 26 03:23:07 2010 From: rarob at travelinglightfarm.net (rarob at travelinglightfarm.net) Date: Tue, 25 May 2010 14:23:07 -0400 Subject: [ydl-gen] thank you In-Reply-To: References: <20100524102808.7ab9b462@arakus> Message-ID: Sorry for the top-post, but... Have you tried 'openssl dgst -sha1 ' ? I'm not in front of my OS X box right now so I don't remember if it works the same way there, but this is how I do the checksums on my Linux box. I believe some versions of openssl equate that with the 'openssl sha1 ' command you tried below as well. -Rob Yes frustration does exist. !. > I attempted sha1 in Bash and it does not work. seemingly. so i posted a > question about 15 minutes ago, as to what is the default shell that Linux > is built on. > > after all of the bs below, as i was cleaning off the desk top i did see a > file with a Linux download drive inside and dragged it, the drive onto the > terminal curser to get its path and tried to check it in a debug option > and > got nowhere. > > This is a small fragment of what i did try over a period of 3 hours: > and several other variations from the man sha1 in BASH , i did go on line > and found : > openssl sha1 > > I then went in and did a debug option: > $ openssl sha1 -d > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso > BIO[00409A30]:ctrl(6) - FILE pointer > BIO[00409A30]:ctrl return 0 > BIO[00409A30]:ctrl(108) - FILE pointer > BIO[00409A30]:ctrl return 0 > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso: No such > file > or directory > BIO[00409A30]:Free - FILE pointer > > A issue of file permissions kept coming up so i did a Mac OS Disk Utility > file permissions check and repair. > > and then did this: > > $ openssl sha1 -hex > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > Read Error in > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > 256:error:0200B015:system library:fread:Is a directory:bss_file.c:167: > 256:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: > -------------------------------------------- > $ openssl sha1 -c > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > Read Error in > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > 276:error:0200B015:system library:fread:Is a directory:bss_file.c:167: > 276:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: > ----------------------------------------- > $ open sha1 -verify > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > 2010-05-25 10:14:14.664 open[643] No such file: /Users/polymorphous/sha1 > ---------------------------------- > $ openssl sha1 -signature $ open sha1 -verify > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > open: No such file or directory > sha1: No such file or directory > -verify: No such file or directory > Read Error in > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > 653:error:02001002:system library:fopen:No such file or > directory:bss_file.c:278:fopen('open','r') > 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: > 653:error:02001002:system library:fopen:No such file or > directory:bss_file.c:278:fopen('sha1','r') > 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: > 653:error:02001002:system library:fopen:No such file or > directory:bss_file.c:278:fopen('-verify','r') > 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: > 653:error:0200B015:system library:fread:Is a directory:bss_file.c:167: > 653:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: > poly-morphous-Computer:~ polymorphous$ 2010-05-25 10:14:14.664 open[643] > No > such file: /Users/polymorphous/sha1 > -bash: 2010-05-25: command not found > > > On Mon, May 24, 2010 at 7:28 AM, Derick Centeno wrote: > >> Given what you posted previously I'm concerned whether you are familiar >> with the nuances involved in both using the SHA1SUM value and >> invoking the SHA1SUM test on the .iso you choose to download to burn >> onto a DVD. >> >> The difficulty is that if you are not familiar with it, you could >> easily download a defective .iso and burn an equally defective DVD - >> again, again, and yet again. This process ad nauseum wastes >> download time and burning time. >> >> Given how you already reacted, the potential frustration resulting from >> producing an incomplete and/or faulty DVD may be a process to avoid >> completely. Unfortunately without understanding the usage of the >> SHA1SUM value and the SHA1SUM test there is no way to determine if >> the .iso you downloaded before burning the DVD exactly matches the >> product originally released by Fixstars (or any other Linux >> distribution). >> >> If you determine that the information posted at the mirrors regarding >> the SHA1SUM are unclear I'd be happy to attempt a more effective >> explanation and post it here. >> >> All the best... >> >> On Sat, 22 May 2010 11:44:35 -0700 >> james gray wrote: >> >> > Thank you Henry Olders >> > I was hoping to get a file map, here / here / here /. >> > I could spend hours days weeks years looking at the plethora of Linux >> > distro`s, trying to figure out what is what. >> > And the People at Linux wonder why more people in the general public >> > do not get involved. >> > Thank you. >> > some day if i get the time from writing code i will try to make it a >> > mission to clarify clarity in Linux distro`s. >> > Thank you >> >> _______________________________________________ >> yellowdog-general mailing list - yellowdog-general at lists.fixstars.com >> Unsuscribe info: >> http://lists.fixstars.com/mailman/listinfo/yellowdog-general >> HINT: to Google archives, try '<keywords> site:us.fixstars.com' >> > _______________________________________________ > yellowdog-general mailing list - yellowdog-general at lists.fixstars.com > Unsuscribe info: > http://lists.fixstars.com/mailman/listinfo/yellowdog-general > HINT: to Google archives, try '<keywords> site:us.fixstars.com' From dcenteno at ydl.net Wed May 26 04:11:06 2010 From: dcenteno at ydl.net (Derick Centeno) Date: Tue, 25 May 2010 15:11:06 -0400 Subject: [ydl-gen] default shell ? In-Reply-To: References: Message-ID: <20100525151106.563d6b82@arakus> Hi James: Linux, can use a variety shells and every Linux distribution includes the option to use/switch between 3 or more different shells. Some Linux distributions use the bash shell as the default shell; however regardless of the distribution anyone with sufficient Unix/ Linux experience/training or web based research can change the default shell to a shell they feel is more useful for their particular needs. All the best... On Tue, 25 May 2010 10:56:46 -0700 james gray wrote: > what is the default shell that Linux does use. > Thank you. From dcenteno at ydl.net Wed May 26 10:02:16 2010 From: dcenteno at ydl.net (Derick Centeno) Date: Tue, 25 May 2010 21:02:16 -0400 Subject: [ydl-gen] thank you In-Reply-To: References: <20100524102808.7ab9b462@arakus> Message-ID: <20100525210216.6019ebd9@arakus> On Tue, 25 May 2010 11:13:51 -0700 james gray wrote: > Yes frustration does exist. !. > I attempted sha1 in Bash and it does not work. seemingly. so i posted > a question about 15 minutes ago, as to what is the default shell > that Linux is built on. > > after all of the bs below, as i was cleaning off the desk top i did > see a file with a Linux download drive inside and dragged it, the > drive onto the terminal curser to get its path and tried to check it > in a debug option and got nowhere. > > This is a small fragment of what i did try over a period of 3 hours: > and several other variations from the man sha1 in BASH , i did go on > line and found : > openssl sha1 > > I then went in and did a debug option: > $ openssl sha1 -d > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso > BIO[00409A30]:ctrl(6) - FILE pointer > BIO[00409A30]:ctrl return 0 > BIO[00409A30]:ctrl(108) - FILE pointer > BIO[00409A30]:ctrl return 0 > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso: No > such file or directory > BIO[00409A30]:Free - FILE pointer > > A issue of file permissions kept coming up so i did a Mac OS Disk > Utility file permissions check and repair. > > and then did this: > > $ openssl sha1 -hex > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > Read Error in > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > 256:error:0200B015:system library:fread:Is a directory:bss_file.c:167: > 256:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: > -------------------------------------------- > $ openssl sha1 -c > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > Read Error in > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > 276:error:0200B015:system library:fread:Is a directory:bss_file.c:167: > 276:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: > ----------------------------------------- > $ open sha1 -verify > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > 2010-05-25 10:14:14.664 open[643] No such > file: /Users/polymorphous/sha1 ---------------------------------- > $ openssl sha1 -signature $ open sha1 -verify > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > open: No such file or directory > sha1: No such file or directory > -verify: No such file or directory > Read Error in > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > 653:error:02001002:system library:fopen:No such file or > directory:bss_file.c:278:fopen('open','r') > 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: > 653:error:02001002:system library:fopen:No such file or > directory:bss_file.c:278:fopen('sha1','r') > 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: > 653:error:02001002:system library:fopen:No such file or > directory:bss_file.c:278:fopen('-verify','r') > 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: > 653:error:0200B015:system library:fread:Is a directory:bss_file.c:167: > 653:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: > poly-morphous-Computer:~ polymorphous$ 2010-05-25 10:14:14.664 > open[643] No such file: /Users/polymorphous/sha1 > -bash: 2010-05-25: command not found > > > On Mon, May 24, 2010 at 7:28 AM, Derick Centeno > wrote: > > > Given what you posted previously I'm concerned whether you are > > familiar with the nuances involved in both using the SHA1SUM value > > and invoking the SHA1SUM test on the .iso you choose to download to > > burn onto a DVD. > > > > The difficulty is that if you are not familiar with it, you could > > easily download a defective .iso and burn an equally defective DVD - > > again, again, and yet again. This process ad nauseum wastes > > download time and burning time. > > > > Given how you already reacted, the potential frustration resulting > > from producing an incomplete and/or faulty DVD may be a process to > > avoid completely. Unfortunately without understanding the usage of > > the SHA1SUM value and the SHA1SUM test there is no way to determine > > if the .iso you downloaded before burning the DVD exactly matches > > the product originally released by Fixstars (or any other Linux > > distribution). > > > > If you determine that the information posted at the mirrors > > regarding the SHA1SUM are unclear I'd be happy to attempt a more > > effective explanation and post it here. > > > > All the best... I noticed your post so I'm going to explain the procedure for using the SHA1SUM command and using the SHA1SUM value step by step. It doesn't matter what shell you are in, the SHA1SUM command will work if used in the correct syntax. You already know that when the shell prompt shows $, you are in user mode; when the prompt shows #, you are in root mode. Notice: I believe that the SHA1SUM test can be executed in user mode. It's been some years since I had to download and test an .iso download myself. If you have any difficulty in using the user mode, then just execute the test and the procedures I explained below from within root mode. It is a good idea to set your browser to send all downloads to one specific directory, for me I call this directory Downloads. So what you see below is that within bash I've moved into the Downloads directory; it is this directory where a .iso would be downloaded into. What follows is my switching from bash to ksh while staying within user mode: [aguila at arakus Downloads]$ ksh $ Now regardless whether I am in bash, ksh or any other shell as long as I have moved into the same directory where the downloaded .iso file exists. I execute the SHA1SUM command exactly in the following manner: $SHA1SUM yellowdog-6.1-ppc-DVD_20081119.iso Explanation: Note that after $ the entire name SHA1SUM is typed. The command is followed by the name of the downloaded file which ends in .iso; the above is merely an example. After .iso merely press the Enter key and then a SHA1SUM value associated with the downloaded .iso file will be generated. This generated number needs to be compared against the SHA1SUM value which the vendor reports as the correct value. If the two values (the one generated by the SHA1SUM test on the file downloaded onto your computer and the value reported by the vendor) match, then you can be sure that the downloaded file was not corrupted in transmission as it was downloaded onto your computer. The matching sequence -- what to notice: The SHA1SUM test generates as many as 40 characters which include a mixture of letters and numbers in a specific sequence. Each letter and number must exactly match the sequence reported by the vendor. In our case, the vendor is Fixstars because they produced Yellowdog Linux. Therefore we need to find a file where they report the SHA1SUM value which represents a clean and working copy of Yellowdog Linux. An example of such a file is located here: http://ydl.oregonstate.edu/iso/SHA1SUM You will notice that the SHA1SUM value is on the left, and the file name of the .iso associated with that unique SHA1SUM value is on the right. The way to read this (and similar files) is that each row/line is distinct and separate from the one above. Therefore the SHA1SUM value associated with yellowdog-6.1-ppc-DVD_20081119.iso produced by Fixstars is to the immediate left. If you have followed my example up to this point where we have downloaded the above .iso, then only after the .iso has completely downloaded do I run/execute the SHA1SUM command on my computer as I explained above. My computer should then generate the SHA1SUM value for the file I downloaded -- if there is any deviation from the sequence the vendor reports; download the .iso file again. Maybe you have a "dirty" or noisy connection, there is interference or another problem. It is recommended that you download these very large files using nothing less than DSL or faster. If you still have problems choose a mirror closer to where you live. If you are in Australia, downloading from Oregon makes no sense. Find a closer mirror to you. Finding a mirror closer to where you are doesn't change the SHA1SUM values you need to compare; it does increase the chances however that the .iso you download will be cleaner and have less transmission errors as the distance to get to you is shorter. You can execute the SHA1SUM test from any shell within the user mode Please note that any Linux distribution would require use the SHA1SUM value in a similar way where the SHA1SUM command executed on the downloaded .iso file which generates a SHA1SUM value is compared against the SHA1SUM reported by the vendor. Different vendors will report different SHA1SUM values for their respective products what remains the same across vendors and distributions are the comparison procedures. If you want more references the resource below may be helpful: http://pcsupport.about.com/od/termsi/g/isofile.htm Also feel free to visit and participate on the Yellowdog Linux Board, here: http://yellowdog-board.com/ All the best... From space.time.universe at gmail.com Thu May 27 19:18:56 2010 From: space.time.universe at gmail.com (Mr. Teo En Ming (Zhang Enming)) Date: Thu, 27 May 2010 18:18:56 +0800 Subject: [ydl-gen] [URGENT] Assistance Requested in Looking for Dr Francis T. Seow, Harvard Law School Research Fellow In-Reply-To: <4BFE0A4F.7020102@bradbury.edu.hk> References: <4BFE0A4F.7020102@bradbury.edu.hk> Message-ID: <4BFE4710.1040304@gmail.com> Dear Christopher, I have sent countless emails to many governmental, non-governmental and international organizations in the world with the subject "Plea for Medical Help/Assistance". But surprisingly I get very few replies. Maybe the replies have been deleted or the emails I sent have been deleted. EDIT: I overheard my neighbours claiming to have passwords/access to my email accounts. --- Mr. Teo En Ming Hanyu Pinyin Name: Zhang Enming Facebook: Teo En Ming (Zhang Enming) Photo (1): http://img26.imageshack.us/img26/7534/enmingteodscf2511.jpg Photo (2): http://i.imgur.com/CLifZ.jpg Mobile Phone (Starhub Pre-paid): +65-8369-2618 Singapore Citizen On 05/27/2010 01:59 PM, Christopher Chan wrote: > >> Do you also know how I can contact all the justices of the Judicial >> Committee of the UK Privy Council and all the Lords of the UK House of >> Lords? According to the UK Parliament website, it says that many Peers >> do not have public email addresses. >> >> In Lucid you will find them in /etc/email/PrivyCouncil.txt and /etc/email/HouseOfLords.txt >> > Or he could just ask the Lord of Privies. In fact, I reckon he'd even be > invited for tea too. > > From pointerleft at gmail.com Thu May 27 22:22:17 2010 From: pointerleft at gmail.com (james gray) Date: Thu, 27 May 2010 06:22:17 -0700 Subject: [ydl-gen] thank you In-Reply-To: <20100525210216.6019ebd9@arakus> References: <20100524102808.7ab9b462@arakus> <20100525210216.6019ebd9@arakus> Message-ID: Thank you Derick I will look into this. I have changed into a user account and will need to go back and see what i did before. As i remember bash made a statement that sha1 was not a command etc. I could try upper case SHAW1. in any way i will go back and wrestle with the feral beast some more. Thank you On Tue, May 25, 2010 at 6:02 PM, Derick Centeno wrote: > On Tue, 25 May 2010 11:13:51 -0700 > james gray wrote: > > > Yes frustration does exist. !. > > I attempted sha1 in Bash and it does not work. seemingly. so i posted > > a question about 15 minutes ago, as to what is the default shell > > that Linux is built on. > > > > after all of the bs below, as i was cleaning off the desk top i did > > see a file with a Linux download drive inside and dragged it, the > > drive onto the terminal curser to get its path and tried to check it > > in a debug option and got nowhere. > > > > This is a small fragment of what i did try over a period of 3 hours: > > and several other variations from the man sha1 in BASH , i did go on > > line and found : > > openssl sha1 > > > > I then went in and did a debug option: > > $ openssl sha1 -d > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso > > BIO[00409A30]:ctrl(6) - FILE pointer > > BIO[00409A30]:ctrl return 0 > > BIO[00409A30]:ctrl(108) - FILE pointer > > BIO[00409A30]:ctrl return 0 > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso: No > > such file or directory > > BIO[00409A30]:Free - FILE pointer > > > > A issue of file permissions kept coming up so i did a Mac OS Disk > > Utility file permissions check and repair. > > > > and then did this: > > > > $ openssl sha1 -hex > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > Read Error in > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > 256:error:0200B015:system library:fread:Is a directory:bss_file.c:167: > > 256:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: > > -------------------------------------------- > > $ openssl sha1 -c > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > Read Error in > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > 276:error:0200B015:system library:fread:Is a directory:bss_file.c:167: > > 276:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: > > ----------------------------------------- > > $ open sha1 -verify > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > 2010-05-25 10:14:14.664 open[643] No such > > file: /Users/polymorphous/sha1 ---------------------------------- > > $ openssl sha1 -signature $ open sha1 -verify > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > open: No such file or directory > > sha1: No such file or directory > > -verify: No such file or directory > > Read Error in > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > 653:error:02001002:system library:fopen:No such file or > > directory:bss_file.c:278:fopen('open','r') > > 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: > > 653:error:02001002:system library:fopen:No such file or > > directory:bss_file.c:278:fopen('sha1','r') > > 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: > > 653:error:02001002:system library:fopen:No such file or > > directory:bss_file.c:278:fopen('-verify','r') > > 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: > > 653:error:0200B015:system library:fread:Is a directory:bss_file.c:167: > > 653:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: > > poly-morphous-Computer:~ polymorphous$ 2010-05-25 10:14:14.664 > > open[643] No such file: /Users/polymorphous/sha1 > > -bash: 2010-05-25: command not found > > > > > > On Mon, May 24, 2010 at 7:28 AM, Derick Centeno > > wrote: > > > > > Given what you posted previously I'm concerned whether you are > > > familiar with the nuances involved in both using the SHA1SUM value > > > and invoking the SHA1SUM test on the .iso you choose to download to > > > burn onto a DVD. > > > > > > The difficulty is that if you are not familiar with it, you could > > > easily download a defective .iso and burn an equally defective DVD - > > > again, again, and yet again. This process ad nauseum wastes > > > download time and burning time. > > > > > > Given how you already reacted, the potential frustration resulting > > > from producing an incomplete and/or faulty DVD may be a process to > > > avoid completely. Unfortunately without understanding the usage of > > > the SHA1SUM value and the SHA1SUM test there is no way to determine > > > if the .iso you downloaded before burning the DVD exactly matches > > > the product originally released by Fixstars (or any other Linux > > > distribution). > > > > > > If you determine that the information posted at the mirrors > > > regarding the SHA1SUM are unclear I'd be happy to attempt a more > > > effective explanation and post it here. > > > > > > All the best... > > I noticed your post so I'm going to explain the procedure for using > the SHA1SUM command and using the SHA1SUM value step by step. > > > It doesn't matter what shell you are in, the SHA1SUM command will work > if used in the correct syntax. You already know that when the shell > prompt shows $, you are in user mode; when the prompt shows #, you > are in root mode. > > Notice: I believe that the SHA1SUM test can be executed in user mode. > It's been some years since I had to download and test an .iso download > myself. If you have any difficulty in using the user mode, then just > execute the test and the procedures I explained below from within root > mode. > > It is a good idea to set your browser to send all downloads to one > specific directory, for me I call this directory Downloads. So what > you see below is that within bash I've moved into the Downloads > directory; it is this directory where a .iso would be downloaded into. > What follows is my switching from bash to ksh while staying within user > mode: > > [aguila at arakus Downloads]$ ksh > $ > > Now regardless whether I am in bash, ksh or any other shell as long as > I have moved into the same directory where the downloaded .iso file > exists. I execute the SHA1SUM command exactly in the following manner: > > $SHA1SUM yellowdog-6.1-ppc-DVD_20081119.iso > > Explanation: > Note that after $ the entire name SHA1SUM is typed. The command is > followed by the name of the downloaded file which ends in .iso; the > above is merely an example. After .iso merely press the Enter key and > then a SHA1SUM value associated with the downloaded .iso file will be > generated. > > This generated number needs to be compared against the SHA1SUM value > which the vendor reports as the correct value. If the two values (the > one generated by the SHA1SUM test on the file downloaded onto your > computer and the value reported by the vendor) match, then you can be > sure that the downloaded file was not corrupted in transmission as it > was downloaded onto your computer. > > The matching sequence -- what to notice: > The SHA1SUM test generates as many as 40 characters which include a > mixture of letters and numbers in a specific sequence. Each letter and > number must exactly match the sequence reported by the vendor. > > In our case, the vendor is Fixstars because they produced Yellowdog > Linux. Therefore we need to find a file where they report the SHA1SUM > value which represents a clean and working copy of Yellowdog Linux. An > example of such a file is located here: > > http://ydl.oregonstate.edu/iso/SHA1SUM > > You will notice that the SHA1SUM value is on the left, and the file > name of the .iso associated with that unique SHA1SUM value is on the > right. The way to read this (and similar files) is that each row/line > is distinct and separate from the one above. Therefore the SHA1SUM > value associated with yellowdog-6.1-ppc-DVD_20081119.iso produced by > Fixstars is to the immediate left. > > If you have followed my example up to this point where we have > downloaded the above .iso, then only after the .iso has completely > downloaded do I run/execute the SHA1SUM command on my computer as I > explained above. My computer should then generate the SHA1SUM value for > the file I downloaded -- if there is any deviation from the sequence > the vendor reports; download the .iso file again. Maybe you have a > "dirty" or noisy connection, there is interference or another problem. > > It is recommended that you download these very large files using > nothing less than DSL or faster. If you still have problems choose a > mirror closer to where you live. If you are in Australia, downloading > from Oregon makes no sense. Find a closer mirror to you. > > Finding a mirror closer to where you are doesn't change the SHA1SUM > values you need to compare; it does increase the chances however that > the .iso you download will be cleaner and have less transmission errors > as the distance to get to you is shorter. > > You can execute the SHA1SUM test from any shell within the user mode > Please note that any Linux distribution would require use the SHA1SUM > value in a similar way where the SHA1SUM command executed on the > downloaded .iso file which generates a SHA1SUM value is compared > against the SHA1SUM reported by the vendor. Different vendors will > report different SHA1SUM values for their respective products what > remains the same across vendors and distributions are the comparison > procedures. > > If you want more references the resource below may be helpful: > > http://pcsupport.about.com/od/termsi/g/isofile.htm > > Also feel free to visit and participate on the Yellowdog Linux Board, > here: http://yellowdog-board.com/ > > All the best... > _______________________________________________ > yellowdog-general mailing list - yellowdog-general at lists.fixstars.com > Unsuscribe info: > http://lists.fixstars.com/mailman/listinfo/yellowdog-general > HINT: to Google archives, try '<keywords> site:us.fixstars.com' > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pointerleft at gmail.com Thu May 27 23:30:30 2010 From: pointerleft at gmail.com (james gray) Date: Thu, 27 May 2010 07:30:30 -0700 Subject: [ydl-gen] thank you In-Reply-To: <20100525210216.6019ebd9@arakus> References: <20100524102808.7ab9b462@arakus> <20100525210216.6019ebd9@arakus> Message-ID: I just went back in to the admin and tried again and here are the results at more explicit, without having to remember. This is the instructions from the source: Or, you may also conduct a media check prior to burning the ISO, from the command line as follows: sha1sum /[path]/[to]/[ydl].iso [ENTER] ... which will output a SHA1SUM which you compare against the SHA1SUM in the SHA1SUM file. ---------------------------------------- And what i receive is shown below: using upper case, lower, case any case, sslsha1 or whatever, feral cat 2, does not matter. pure fecal experience. $ sha1sum /Users/polymorphous/Desktop/fire_downL/yellowdog-6.2-ppc-DVD_20090629.iso -bash: sha1sum: command not found ------------- $SHA1SUM /Users/polymorphous/Desktop/fire_downL/yellowdog-6.2-ppc-DVD_20090629.iso -bash: SHA1SUM: command not found ------------- $ SHA1 yellowdog-6.2-ppc-DVD_20090629.iso -bash: SHA1: command not found $ sha1 yellowdog-6.2-ppc-DVD_20090629.iso -bash: sha1: command not found On Tue, May 25, 2010 at 6:02 PM, Derick Centeno wrote: > On Tue, 25 May 2010 11:13:51 -0700 > james gray wrote: > > > Yes frustration does exist. !. > > I attempted sha1 in Bash and it does not work. seemingly. so i posted > > a question about 15 minutes ago, as to what is the default shell > > that Linux is built on. > > > > after all of the bs below, as i was cleaning off the desk top i did > > see a file with a Linux download drive inside and dragged it, the > > drive onto the terminal curser to get its path and tried to check it > > in a debug option and got nowhere. > > > > This is a small fragment of what i did try over a period of 3 hours: > > and several other variations from the man sha1 in BASH , i did go on > > line and found : > > openssl sha1 > > > > I then went in and did a debug option: > > $ openssl sha1 -d > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso > > BIO[00409A30]:ctrl(6) - FILE pointer > > BIO[00409A30]:ctrl return 0 > > BIO[00409A30]:ctrl(108) - FILE pointer > > BIO[00409A30]:ctrl return 0 > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso: No > > such file or directory > > BIO[00409A30]:Free - FILE pointer > > > > A issue of file permissions kept coming up so i did a Mac OS Disk > > Utility file permissions check and repair. > > > > and then did this: > > > > $ openssl sha1 -hex > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > Read Error in > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > 256:error:0200B015:system library:fread:Is a directory:bss_file.c:167: > > 256:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: > > -------------------------------------------- > > $ openssl sha1 -c > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > Read Error in > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > 276:error:0200B015:system library:fread:Is a directory:bss_file.c:167: > > 276:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: > > ----------------------------------------- > > $ open sha1 -verify > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > 2010-05-25 10:14:14.664 open[643] No such > > file: /Users/polymorphous/sha1 ---------------------------------- > > $ openssl sha1 -signature $ open sha1 -verify > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > open: No such file or directory > > sha1: No such file or directory > > -verify: No such file or directory > > Read Error in > > /Users/polymorphous/Desktop/yellowdog-6.2-ppc-DVD_20090629.iso.download/ > > 653:error:02001002:system library:fopen:No such file or > > directory:bss_file.c:278:fopen('open','r') > > 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: > > 653:error:02001002:system library:fopen:No such file or > > directory:bss_file.c:278:fopen('sha1','r') > > 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: > > 653:error:02001002:system library:fopen:No such file or > > directory:bss_file.c:278:fopen('-verify','r') > > 653:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:280: > > 653:error:0200B015:system library:fread:Is a directory:bss_file.c:167: > > 653:error:20082002:BIO routines:FILE_READ:system lib:bss_file.c:168: > > poly-morphous-Computer:~ polymorphous$ 2010-05-25 10:14:14.664 > > open[643] No such file: /Users/polymorphous/sha1 > > -bash: 2010-05-25: command not found > > > > > > On Mon, May 24, 2010 at 7:28 AM, Derick Centeno > > wrote: > > > > > Given what you posted previously I'm concerned whether you are > > > familiar with the nuances involved in both using the SHA1SUM value > > > and invoking the SHA1SUM test on the .iso you choose to download to > > > burn onto a DVD. > > > > > > The difficulty is that if you are not familiar with it, you could > > > easily download a defective .iso and burn an equally defective DVD - > > > again, again, and yet again. This process ad nauseum wastes > > > download time and burning time. > > > > > > Given how you already reacted, the potential frustration resulting > > > from producing an incomplete and/or faulty DVD may be a process to > > > avoid completely. Unfortunately without understanding the usage of > > > the SHA1SUM value and the SHA1SUM test there is no way to determine > > > if the .iso you downloaded before burning the DVD exactly matches > > > the product originally released by Fixstars (or any other Linux > > > distribution). > > > > > > If you determine that the information posted at the mirrors > > > regarding the SHA1SUM are unclear I'd be happy to attempt a more > > > effective explanation and post it here. > > > > > > All the best... > > I noticed your post so I'm going to explain the procedure for using > the SHA1SUM command and using the SHA1SUM value step by step. > > > It doesn't matter what shell you are in, the SHA1SUM command will work > if used in the correct syntax. You already know that when the shell > prompt shows $, you are in user mode; when the prompt shows #, you > are in root mode. > > Notice: I believe that the SHA1SUM test can be executed in user mode. > It's been some years since I had to download and test an .iso download > myself. If you have any difficulty in using the user mode, then just > execute the test and the procedures I explained below from within root > mode. > > It is a good idea to set your browser to send all downloads to one > specific directory, for me I call this directory Downloads. So what > you see below is that within bash I've moved into the Downloads > directory; it is this directory where a .iso would be downloaded into. > What follows is my switching from bash to ksh while staying within user > mode: > > [aguila at arakus Downloads]$ ksh > $ > > Now regardless whether I am in bash, ksh or any other shell as long as > I have moved into the same directory where the downloaded .iso file > exists. I execute the SHA1SUM command exactly in the following manner: > > $SHA1SUM yellowdog-6.1-ppc-DVD_20081119.iso > > Explanation: > Note that after $ the entire name SHA1SUM is typed. The command is > followed by the name of the downloaded file which ends in .iso; the > above is merely an example. After .iso merely press the Enter key and > then a SHA1SUM value associated with the downloaded .iso file will be > generated. > > This generated number needs to be compared against the SHA1SUM value > which the vendor reports as the correct value. If the two values (the > one generated by the SHA1SUM test on the file downloaded onto your > computer and the value reported by the vendor) match, then you can be > sure that the downloaded file was not corrupted in transmission as it > was downloaded onto your computer. > > The matching sequence -- what to notice: > The SHA1SUM test generates as many as 40 characters which include a > mixture of letters and numbers in a specific sequence. Each letter and > number must exactly match the sequence reported by the vendor. > > In our case, the vendor is Fixstars because they produced Yellowdog > Linux. Therefore we need to find a file where they report the SHA1SUM > value which represents a clean and working copy of Yellowdog Linux. An > example of such a file is located here: > > http://ydl.oregonstate.edu/iso/SHA1SUM > > You will notice that the SHA1SUM value is on the left, and the file > name of the .iso associated with that unique SHA1SUM value is on the > right. The way to read this (and similar files) is that each row/line > is distinct and separate from the one above. Therefore the SHA1SUM > value associated with yellowdog-6.1-ppc-DVD_20081119.iso produced by > Fixstars is to the immediate left. > > If you have followed my example up to this point where we have > downloaded the above .iso, then only after the .iso has completely > downloaded do I run/execute the SHA1SUM command on my computer as I > explained above. My computer should then generate the SHA1SUM value for > the file I downloaded -- if there is any deviation from the sequence > the vendor reports; download the .iso file again. Maybe you have a > "dirty" or noisy connection, there is interference or another problem. > > It is recommended that you download these very large files using > nothing less than DSL or faster. If you still have problems choose a > mirror closer to where you live. If you are in Australia, downloading > from Oregon makes no sense. Find a closer mirror to you. > > Finding a mirror closer to where you are doesn't change the SHA1SUM > values you need to compare; it does increase the chances however that > the .iso you download will be cleaner and have less transmission errors > as the distance to get to you is shorter. > > You can execute the SHA1SUM test from any shell within the user mode > Please note that any Linux distribution would require use the SHA1SUM > value in a similar way where the SHA1SUM command executed on the > downloaded .iso file which generates a SHA1SUM value is compared > against the SHA1SUM reported by the vendor. Different vendors will > report different SHA1SUM values for their respective products what > remains the same across vendors and distributions are the comparison > procedures. > > If you want more references the resource below may be helpful: > > http://pcsupport.about.com/od/termsi/g/isofile.htm > > Also feel free to visit and participate on the Yellowdog Linux Board, > here: http://yellowdog-board.com/ > > All the best... > _______________________________________________ > yellowdog-general mailing list - yellowdog-general at lists.fixstars.com > Unsuscribe info: > http://lists.fixstars.com/mailman/listinfo/yellowdog-general > HINT: to Google archives, try '<keywords> site:us.fixstars.com' > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcenteno at ydl.net Fri May 28 00:04:10 2010 From: dcenteno at ydl.net (Derick Centeno) Date: Thu, 27 May 2010 11:04:10 -0400 Subject: [ydl-gen] thank you In-Reply-To: References: <20100524102808.7ab9b462@arakus> <20100525210216.6019ebd9@arakus> Message-ID: <20100527110410.52a46a5c@arakus> On Thu, 27 May 2010 07:30:30 -0700 james gray wrote: > I just went back in to the admin and tried again and here are the > results at more explicit, without having to remember. > This is the instructions from the source: > Or, you may also conduct a media check prior to burning the ISO, from > the command line as follows: > > sha1sum /[path]/[to]/[ydl].iso [ENTER] > > ... which will output a SHA1SUM which you compare against the SHA1SUM > in the SHA1SUM file. > ---------------------------------------- > And what i receive is shown below: > using upper case, lower, case any case, sslsha1 or whatever, feral > cat 2, does not matter. pure fecal experience. > > > > $ sha1sum > /Users/polymorphous/Desktop/fire_downL/yellowdog-6.2-ppc-DVD_20090629.iso > -bash: sha1sum: command not found > ------------- > $SHA1SUM > /Users/polymorphous/Desktop/fire_downL/yellowdog-6.2-ppc-DVD_20090629.iso > -bash: SHA1SUM: command not found > > ------------- > $ SHA1 yellowdog-6.2-ppc-DVD_20090629.iso > -bash: SHA1: command not found > > $ sha1 yellowdog-6.2-ppc-DVD_20090629.iso > -bash: sha1: command not found > Ok, James, believe it or not we are a little closer to getting this done. First point, sha1 and sha1sum are different commands. You can discover that for yourself by doing: $man sha1 $info sha1 $man sha1sum $info sha1sum The above can also be executed in root. Ok. Obviously, sha1sum did not work in user mode; execute the sha1sum command in root mode. Keep in mind that in Linux, there exist a few commands which can only be executed from within the directory where their binaries exist which means you have to know where those directories are. The short-cut is to invoke the root mode using the - flag which tells root that all commands throughout the entire directory tree in Linux are available to you as though they were in the same top-level directory and available to be immediately executed. The sequence to invoke this from user mode is the following: [aguila at arakus ~]$ su - Password: [root at arakus ~]# For clarification, the user mode and root mode should have different passwords as a way of maintaining clarity for Linux and yourself which account (root or user) one is using at any one time. Once you are in root mode try executing the sha1sum again. It should work without difficulty. Make sure that the sha1sum value produced on the .iso exactly matches the sha1sum value reported by the vendor. Remember it doesn't matter which shell you are using -- bash, ksh, csh, ash -- what matters is that you execute the root mode, as you have demonstrated that sha1sum cannot be executed from within user mode. Remember the short-cut I explained above. All the best... From dcenteno at ydl.net Fri May 28 09:18:14 2010 From: dcenteno at ydl.net (Derick Centeno) Date: Thu, 27 May 2010 20:18:14 -0400 Subject: [ydl-gen] Syslog question regarding mysterious shutdowns In-Reply-To: References: Message-ID: <20100527201814.45f416ff@arakus> On Thu, 27 May 2010 13:43:19 -0500 Nick Jones wrote: > Hi Derick, > > First off thank you very much for the very thorough and prompt > response. > You're welcome. > # uname -r > Linux lcn 2.6.15-rc5.ydl.1custom #1 SMP Tue Aug 8 17:01:58 CDT 2006 > ppc64 ppc64 ppc64 GNU/Linux > I compiled the kernel with special modules, namely an LSI fiber > channel controller module. Nice. > # ps aux |grep syslogd > root 2768 0.0 0.0 1824 640 ? S May24 0:02 > syslogd -m 0 root 22311 0.0 0.0 3964 712 pts/0 S > 13:17 0:00 grep syslogd I can understand the syslogd sleeping or needing to be restarted on my system as it is a laptop; you however are running YDL as a server. I would think that you'd have lots of logs to examine from syslogd. So something is being missed. As a former System Admin myself, I don't recall all the tricks of the trade. However, I did find some references which could be useful to you. Some of these references are useful for me also as I don't like daemons sleeping when they should be telling me what is going on. Here are some references which you can explore on your own. I'll assume you've already investigated man/info as these references build upon them as well. *http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/index.jsp?topic=/com.ibm.etools.mft.doc/an04230_.htm *http://www.linuxjournal.com/article/2926 *http://www.linuxjournal.com/article/5476 *http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch05_:_Troubleshooting_Linux_with_syslog Of course, there are limits regarding what one can gather on the net which is reliable. It may be time to invest in old style System Administration tomes addressing Linux System Administration in sufficient detail to help you "drill down" to resolving the mystery quickly. > I tried running tail -f /var/log/messages >> log.txt &; so that all > messages were hopefully logged, but got nothing helpful. The references I recommend above should be more useful. > I appreciate the suggestions about the UPC, however I know for a fact > that power has never been interrupted to the battery bacukp, the > batteries are good, and that it will not shut down (it beeps loudly > until the batteries die). In the past I've observed the problem and > the batteries were all full charge minutes after I went into the > server room to check why the system went down. Recently a major power > update was performed, and the problem has gone away (I suspect that > there was "bad" power involved), so I'm waiting to see if it comes > back. > > I'll repost if I find it to be related to the version of YDL or the > packages I'm using, but for now I'm going to assume it's not that. > If you have any more suggestions regarding helpful system messages > I'd be interested, but I'm hoping the problem is gone for good. > > Thanks again > > Nick No problem Nick. However, in my previous post I also wanted to share with you the resources of two different vendors who have diverse strengths in providing technical resources (for a price, of course) which you may find useful. I didn't mention them earlier as I was pressed for time; I'll direct you to their respective webpages discussing the UPS systems they offer: *http://eshop.macsales.com/Search/Search.cfm?Ntt=apc&Ntk=Primary&N=0&Ns=P_Popularity|1 *http://www.blackbox.com/Store/Results.aspx/search-ups%60%60si_product Blackbox is a no nonsense tech shop I worked with years ago; they should be helpful in recommending more esoteric approaches should there be need. From billfink at mindspring.com Fri May 28 14:12:31 2010 From: billfink at mindspring.com (Bill Fink) Date: Fri, 28 May 2010 01:12:31 -0400 Subject: [ydl-gen] thank you In-Reply-To: <20100527110410.52a46a5c@arakus> References: <20100524102808.7ab9b462@arakus> <20100525210216.6019ebd9@arakus> <20100527110410.52a46a5c@arakus> Message-ID: <20100528011231.dd809a5b.billfink@mindspring.com> Actually, sha1sum on YDL resides in /usr/bin, which is a directory that is searched by ordinary users. It is only commands in /sbin and /usr/sbin that aren't normally available to users, and for which the "su -" trick might be helpful. It could be that you don't have coreutils installed, which sha1sum is a part of. You can check with: rpm -q coreutils If it's not already installed, you can install it via: yum install coreutils which will need to be run as root (su). -Hope this helps -Bill On Thu, 27 May 2010, Derick Centeno wrote: > On Thu, 27 May 2010 07:30:30 -0700 > james gray wrote: > > > I just went back in to the admin and tried again and here are the > > results at more explicit, without having to remember. > > This is the instructions from the source: > > Or, you may also conduct a media check prior to burning the ISO, from > > the command line as follows: > > > > sha1sum /[path]/[to]/[ydl].iso [ENTER] > > > > ... which will output a SHA1SUM which you compare against the SHA1SUM > > in the SHA1SUM file. > > ---------------------------------------- > > And what i receive is shown below: > > using upper case, lower, case any case, sslsha1 or whatever, feral > > cat 2, does not matter. pure fecal experience. > > > > > > > > $ sha1sum > > /Users/polymorphous/Desktop/fire_downL/yellowdog-6.2-ppc-DVD_20090629.iso > > -bash: sha1sum: command not found > > ------------- > > $SHA1SUM > > /Users/polymorphous/Desktop/fire_downL/yellowdog-6.2-ppc-DVD_20090629.iso > > -bash: SHA1SUM: command not found > > > > ------------- > > $ SHA1 yellowdog-6.2-ppc-DVD_20090629.iso > > -bash: SHA1: command not found > > > > $ sha1 yellowdog-6.2-ppc-DVD_20090629.iso > > -bash: sha1: command not found > > > > Ok, James, believe it or not we are a little closer to getting this > done. > > First point, sha1 and sha1sum are different commands. You can discover > that for yourself by doing: > > $man sha1 > $info sha1 > $man sha1sum > $info sha1sum > > The above can also be executed in root. > > Ok. Obviously, sha1sum did not work in user mode; execute the sha1sum > command in root mode. Keep in mind that in Linux, there exist a few > commands which can only be executed from within the directory where > their binaries exist which means you have to know where those > directories are. The short-cut is to invoke the root mode using the > - flag which tells root that all commands throughout the entire > directory tree in Linux are available to you as though they were in > the same top-level directory and available to be immediately executed. > The sequence to invoke this from user mode is the following: > > [aguila at arakus ~]$ su - > Password: > [root at arakus ~]# > > For clarification, the user mode and root mode should have different > passwords as a way of maintaining clarity for Linux and yourself which > account (root or user) one is using at any one time. > > Once you are in root mode try executing the sha1sum again. It should > work without difficulty. Make sure that the sha1sum value produced on > the .iso exactly matches the sha1sum value reported by the vendor. > > Remember it doesn't matter which shell you are using -- bash, ksh, csh, > ash -- what matters is that you execute the root mode, as you have > demonstrated that sha1sum cannot be executed from within user mode. > > Remember the short-cut I explained above. > > All the best... From pointerleft at gmail.com Mon May 31 06:41:48 2010 From: pointerleft at gmail.com (james gray) Date: Sun, 30 May 2010 14:41:48 -0700 Subject: [ydl-gen] thank you In-Reply-To: <20100527110410.52a46a5c@arakus> References: <20100524102808.7ab9b462@arakus> <20100525210216.6019ebd9@arakus> <20100527110410.52a46a5c@arakus> Message-ID: Hello and thank you. I "was" trying to install YDL on a G4 iBook. YDL or any Linux is not installed on this machine. I apologize but i think the communication and understanding that the person seeking to install YDL has any existing Linux experience, is a joke beyond my means. You could ask Julie Childs for some French Toast. Thank you for your assistance. On Thu, May 27, 2010 at 8:04 AM, Derick Centeno wrote: > On Thu, 27 May 2010 07:30:30 -0700 > james gray wrote: > > > I just went back in to the admin and tried again and here are the > > results at more explicit, without having to remember. > > This is the instructions from the source: > > Or, you may also conduct a media check prior to burning the ISO, from > > the command line as follows: > > > > sha1sum /[path]/[to]/[ydl].iso [ENTER] > > > > ... which will output a SHA1SUM which you compare against the SHA1SUM > > in the SHA1SUM file. > > ---------------------------------------- > > And what i receive is shown below: > > using upper case, lower, case any case, sslsha1 or whatever, feral > > cat 2, does not matter. pure fecal experience. > > > > > > > > $ sha1sum > > /Users/polymorphous/Desktop/fire_downL/yellowdog-6.2-ppc-DVD_20090629.iso > > -bash: sha1sum: command not found > > ------------- > > $SHA1SUM > > /Users/polymorphous/Desktop/fire_downL/yellowdog-6.2-ppc-DVD_20090629.iso > > -bash: SHA1SUM: command not found > > > > ------------- > > $ SHA1 yellowdog-6.2-ppc-DVD_20090629.iso > > -bash: SHA1: command not found > > > > $ sha1 yellowdog-6.2-ppc-DVD_20090629.iso > > -bash: sha1: command not found > > > > Ok, James, believe it or not we are a little closer to getting this > done. > > First point, sha1 and sha1sum are different commands. You can discover > that for yourself by doing: > > $man sha1 > $info sha1 > $man sha1sum > $info sha1sum > > The above can also be executed in root. > > Ok. Obviously, sha1sum did not work in user mode; execute the sha1sum > command in root mode. Keep in mind that in Linux, there exist a few > commands which can only be executed from within the directory where > their binaries exist which means you have to know where those > directories are. The short-cut is to invoke the root mode using the > - flag which tells root that all commands throughout the entire > directory tree in Linux are available to you as though they were in > the same top-level directory and available to be immediately executed. > The sequence to invoke this from user mode is the following: > > [aguila at arakus ~]$ su - > Password: > [root at arakus ~]# > > For clarification, the user mode and root mode should have different > passwords as a way of maintaining clarity for Linux and yourself which > account (root or user) one is using at any one time. > > Once you are in root mode try executing the sha1sum again. It should > work without difficulty. Make sure that the sha1sum value produced on > the .iso exactly matches the sha1sum value reported by the vendor. > > Remember it doesn't matter which shell you are using -- bash, ksh, csh, > ash -- what matters is that you execute the root mode, as you have > demonstrated that sha1sum cannot be executed from within user mode. > > Remember the short-cut I explained above. > > All the best... > > _______________________________________________ > yellowdog-general mailing list - yellowdog-general at lists.fixstars.com > Unsuscribe info: > http://lists.fixstars.com/mailman/listinfo/yellowdog-general > HINT: to Google archives, try '<keywords> site:us.fixstars.com' > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcenteno at ydl.net Mon May 31 07:27:52 2010 From: dcenteno at ydl.net (Derick Centeno) Date: Sun, 30 May 2010 18:27:52 -0400 Subject: [ydl-gen] thank you In-Reply-To: References: <20100524102808.7ab9b462@arakus> <20100525210216.6019ebd9@arakus> <20100527110410.52a46a5c@arakus> Message-ID: <20100530182752.6e5e5478@arakus> On Sun, 30 May 2010 14:41:48 -0700 james gray wrote: > Hello and thank you. > I "was" trying to install YDL on a G4 iBook. > YDL or any Linux is not installed on this machine. > I apologize but i think the communication and understanding that the > person seeking to install YDL has any existing Linux experience, is a > joke beyond my means. You could ask Julie Childs for some French > Toast. Thank you for your assistance. > You were successful then in the download of the YDL .iso, the use of sha1sum, the burning of a working DVD disc and finally the installation of YDL onto your ibook? I'm hopeful you were indeed successful. All the best...