Search results for "meeting" - WLUG

Fwd: Announcing the First Annual VMware User Conference

by Andy Stewart

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - ---------- Forwarded Message ---------- Subject: Announcing the First Annual VMware User Conference Date: Wednesday 28 July 2004 7:13 pm From: "VMworld Conference Committee" <VMworld(a)vmware.com> To: andystewart(a)comcast.net Announcing the First Annual VMware User Conference VMworld 2004 Join The Virtual Evolution ONE OF THE YEAR'S MOST IMPORTANT IT EVENTS **************************************************** Come hear industry leaders, technology visionaries, and VMware executives explain why virtual infrastructure is one of the hottest innovations in IT today. WHERE: Manchester Grand Hyatt in beautiful San Diego, California WHEN: Wednesday, October 27 - Friday, October 29, 2004 ========================================= Register by August 15, 2004 and save $500! REGISTER ONLINE AT <http://www.vmworld2004.com> ========================================= HERE'S WHAT YOU'LL LEARN **************************************************** * New strategies and tools for implementing virtual infrastructure technology * The latest thinking on industry developments and trends * Timesaving tips from people who know -- including VMware developers * New products & feature updates HEAR AND BE HEARD ******************** * Meet with leading experts * Network with the VMware customer and partner community * Share your views and feedback with VMware product development A UNIQUE OPPORTUNITY ********************* * Hands-on demos and labs * Keynote addresses by industry leaders * Informative breakout sessions * Exciting solutions expo * Unforgettable social events ************************* 80% OF FORTUNE 500 COMPANIES ARE SAYING THAT VIRTUAL INFRASTRUCTURE IS A CRITICAL CORE IT TECHNOLOGY. ************************** Don't wait. For more information and registration, Visit the VMworld 2004 website at www.VMworld2004.com <http://www.VMworld2004.com>. Click here <http://www.vmworld2004.com/invitation> to download a PDF overview of the conference. Conference Information ******************* Register online at: www.VMworld2004.com <http://www.VMworld2004.com> Phone Domestic: 1-866-VMWARE1 Phone International: 1-415-621-8022 VMworld 2004 Conference Committee VMworld(a)vmware.com <mailto:VMworld@vmware.com> VMware, Inc. 3145 Porter Drive Palo Alto, CA 94304 To UNSUBSCRIBE from -all- incidental VMware communications, including the VMware Newsletter, Discount Offers, Seminar invitations, etc., go to http://www.vmware.com/optout - ------------------------------------------------------- - -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBCEI7Hl0iXDssISsRAus0AKCHWkzgk4GpwEpZttrLaWQyS4V7WwCeKCoh 1/s2hr2nVAZJdI/au1zvFwo= =btgq -----END PGP SIGNATURE-----

21 years, 4 months

Re: [EXT] Framework Laptops

by John Stoffel

>>>>> "Cara" == Cara Salter via WLUG <wlug(a)lists.wlug.org> writes: > On Tue, Jan 10, 2023 at 09:52:40PM -0500, Keith Wright via WLUG wrote: >> Is that 42 days from deciding to order one until happily browsing >> the web with newly installed Debian, Xfce, Firefox? Or 42 days >> from starting to fill out the order form until finally getting >> the last required field filled in? Or what? > Hi! I'm the workstudy in question. According to the emails I > received for moving through each step in the process, it took 42 > days from me submitting my deposit and me receiving a physical > laptop that I could start using. Would you be willing to come to a WLUG meeting and show off your new toy to the rest of us? I do like the idea of that laptop, but I'd like to get my hands on it to see how the feel of it really is. > For context, I ordered the "DIY edition" which didn't come with the RAM or > storage. I ordered both on Amazon and they arrived a bit before the laptop. > I'm currently writing this from my Gentoo install on it! The only > two issues I ran into was that the wifi card (Intel AX210) firmware > wasn't in the "stable" kernel, so I had to keyword my system to > ~amd64. The other issue I ran into was that kernel 5.19.12 had a bad > display driver that caused flickering > (https://community.frame.work/t/psa-dont-upgrade-to-linux-kernel-5-19-12/231…) Did you fix the flickering with a newer kernel version? Its been years since I ran Gentoo (got tired of all the recompiles, but this was 10+ years ago for sure....) and I thought it was pretty damn bleeding edge in terms of kernels. I'm currently running kernel 6.0.8 on my main Debian Buster home NFS/KVM/etc server and it works great, but it is headless. John

2 years, 10 months

Re: [Wlug] Winter cleaning

by Eric Martin

Will do. On Wed, Feb 2, 2011 at 2:21 PM, Henrique <nican(a)wpi.edu> wrote: > Hello Eric, > > I have interest in the OpenGL book. Could you bring it to the next Wlug > meeting? > > Henrique Polido. > > On Wed, Feb 2, 2011 at 1:35 PM, Eric Martin <eric.joshua.martin(a)gmail.com>wrote: > >> I'm doing some cleaning and I have a few books / computers up for grabs. >> It's all free, please take it if you can use it. >> >> Computers: >> >> Mis-mosh of stuff, mainly >> >> >> 1. 2 CRTs (working) >> 2. Dual Pentium Pro 200MHz w/built-in SCSI and a DDS2 or DDS3 Drive >> 3. HP Proliant 1U server, questionably working but I think it's a fan >> / power supply >> 4. Intel C440 Chassis with Cabriol MB and Older Xeon processors >> 5. 2 old cases with working 300W power supplies, need MB >> 6. More to come >> >> Books: >> Interactive Computer Graphics >> >> http://www.amazon.com/Interactive-Computer-Graphics-Top-Down-Approach/dp/03… >> >> Fluency with Information Technology >> >> http://www.amazon.com/Fluency-Information-Technology-Concepts-Capabilities/… >> >> Amazon.com: Interactive Computer Graphics: A Top-Down Approach Using >> OpenGL (4th Edition) (9780321321374): Edward Angel: Books<http://www.amazon.com/Interactive-Computer-Graphics-Top-Down-Approach/dp/03…> >> >> Amazon.com: Interactive Computer Graphics: A Top-Down Approach Using >> OpenGL (4th Edition) (9780321321374): Edward Angel: Books >> C Pocket Reference >> >> http://www.amazon.com/C-Pocket-Reference-Peter-Prinz/dp/0596004362/ref=sr_1… >> -- >> Eric Martin >> >> _______________________________________________ >> Wlug mailing list >> Wlug(a)mail.wlug.org >> http://mail.wlug.org/mailman/listinfo/wlug >> >> > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > -- Eric Martin

14 years, 9 months

Re: [EXT] Improving WLUG outreach

by Anderson, Charles R

Ideas are great, but I don't think we have a lack of ideas. We need people to step up and implement ideas. What concrete steps do you propose? Who do you propose should do those steps? On Mon, Jan 13, 2020 at 10:43:30AM -0500, Joshua Stone via WLUG wrote: > Hey all, > > I thought I'd like to continue the topic about what we could do to increase > attendance meeting. > > I think working with the community at WPI would be a great thing for us, so > long as we try to understand more about the student culture. I've learned > that one of the most important things about WPI is that a sense of > community and working toward a greater goal are included as part of the > curriculum. One of the earliest classes a WPI student takes involves > thinking about the biggest problems impacting the world and makes strides > to tackling such problems head-on. > > https://www.wpi.edu/project-based-learning/wpi-plan/10-things-to-know > > I believe WPI also has a strong background in bioinformatics, and that's a > field that can surely benefit from FOSS as we want to encourage openness > and ethics when being on the forefront of scientific research that could > have sweeping societal impact. The last thing we need is more companies > like 23andMe hoarding genetic data for profit. > > Perhaps WLUG can do more to be involved in such things, emphasizing the > importance of "ethical" computing with the problems of DRM, > spying/tracking, proprietary software and data formats, software patents, > and licenses that lock away data that the community could benefit from. > Essentially we could give people more of an opportunity to think about the > social aspects and ramifications of technology, and can use that as a > framework for creating a better future. > > These are still ideas I'm throwing at the wall, hopefully something sticks! > > -Josh

5 years, 10 months

Re: DECStation 3100 on a RPi2040...

by Jon "maddog" Hall

John: That's an interesting statement. I would think it was the same case and port setup, but a different motherboard since you couldn't just slot a MIPS processor into a VAXstation processor. That is why I said "based". "Based" means that you did not have to requalify a lot of the parts, that you could use a lot of the same Bill of Materials....it does not mean you use exactly the same PCB. In the case of the VAXstation/DECstation 3100 that meant we used the same serial io chips and did not provide the hardware flow control. Yes! It's coming back to me, the 3100s were horrible for serial, > though I think they had fixed it for the 5000 series systems, since > the DECstation 5000 and the DECserver 5100 were identical, except the > DECStation had a graphics card and cost 10-20% _less_ than the > DECstation 5000. So we bought DECStations and used them as servers. The server groups were different engineers, and the 5000s were designed after the DECstation 3100/2100 series. Actually we MIGHT have caught the issue with the serial port for the DECstation 3100/2100 because I brought up the issue in a hardware meeting and was assured that it had been fixed because (and I can still hear this person's voice in my head) the DECstation was a REAL UNIX MACHINE. I should have found that person later and beaten him to death. David: > Actually, Cutler was already in trouble with management because of the > Prism project. Prism was the first try at building a RISC machine (this > was in the 1985-1986 time frame) and it was managed by Dave Cutler. > Unfortunately, Dave was not a good administrator. He was doing a very bad > job of managing the project and doing a very bad job of keeping management > up to date on what was going on. Finally, management cancelled Prism and > that is when they decided to go with the MIPS architecture. > > That is not what I experienced. I will not comment on Dave's skills as an administrator or manager of the project. I do know that he had the very ambitious project of doing the next-generation architecture and the next generation operating system. He wanted a micro-kernel based system with "personalities", one personality being VMS and the other personality being Unix. One issue he had was when there was a clash between personalities he would always favor VMS and therefore the Unix personality would not be "perfect". I felt this was a mistake, since Unix people did not tolerate things that did not smell like Unix. VMS people could have been led over to a new environment over time since DEC controlled the path with VMS. The reason I know this is that I personally interviewed with David Cutler for the position of Unix Product Manager for his new operating system. The interview was going fine until I tried to explain to Dave why his strategy was wrong and he had to make the Unix side really compatible. Then things got ugly, as David really did not like to be told he was wrong. Ken did have the bad habit of cutting off Dave's development money, then giving it back to him again. I seem to remember that Dave was still going full steam ahead while the PMAX was being developed, which is one reason why he was caught so flat-footed when PMAX was announced. It was kept REALLY SECRET. It probably did not help that Ken reportedly asked David in a gleeful tone if the new chip would be as fast as the PMAX.... "Will it be THIS FAST, Dave?" was the reported question. It is also my belief that the Alpha chip came directly from Dave's work on the PRISM, and that Windows NT came directly from David's work on the microkernel with personalities. DEC never "decided to go with MIPS" except as a stop-gap measure for Unix. If DEC had "decided to go with MIPS" they would have ported VMS to it, and since that never happened, it was obvious that DEC had not embraced MIPS. md On Sat, Jul 6, 2024 at 3:27 PM John Stoffel <john(a)stoffel.org> wrote: > >>>>> "Jon" == Jon \"maddog\" Hall via WLUG <wlug(a)lists.wlug.org> writes: > > > The DECstation 3100 (aka the PMAX) was a system based on the same > > motherboard as the VAXstation 3100, except with a MIPS processor. > > It was the first time that Digital had built a system using another > > company's chip architecture. > > That's an interesting statement. I would think it was the same case > and port setup, but a different motherboard since you couldn't just > slot a MIPS processor into a VAXstation processor. > > > We had a choice between supporting the MIPS R2000 chip as "big > > endian" or "little endian". We chose to support "little endian" to > > be compatible with PDP-11s, VAXen and Intel chips, rather than be > > compatible with other manufacturers. This, in my mind, was very > > important since it let us share data over NFS and give greater > > compatibility with programs and libraries of applications already > > running on other Unix-like systems such as Ultrix, BSD, etc. Sun > > experienced this grief when they ported Solaris off the big endian > > Motorola and SPARC chips to little endian Intel. > > > One of the few issues of the DECstation 3100 (and 2100, known as the > > "PMIN" after that) was that the serial I/O port did not support > > hardware handshaking. To save a couple of pennies per system the > > VAX hardware designers determined that having full hardware modem > > control (DECstandard 52) on the board was not needed, because "very > > few workstation users hook a modem up to their serial line". What > > they meant was that "very few VMS workstation users hooked a modem > > up to their serial line", opting for DECnet to handle their > > networking. Therefore the pins necessary to support hardware modem > > control were missing from the DECstation product lines. > > Yes! It's coming back to me, the 3100s were horrible for serial, > though I think they had fixed it for the 5000 series systems, since > the DECstation 5000 and the DECserver 5100 were identical, except the > DECStation had a graphics card and cost 10-20% _less_ than the > DECstation 5000. So we bought DECStations and used them as servers. > :-) > > I used to live and breathe the DEC options catalog, which was > something like an inch thick book in purple (maybe blue? maybe changed > each year?) with all the various options and configurations you could > get. > > > Unix users, on the other hand, often had modems hooked up to their > > workstation, to handle cu(1), uucp(1) and other serial line > > protocols. We eventually got around this by better refining > > software modem control, but it was painful. > > The EE department had Sun 1s at WPI, and they have the 9600 baud > bitnet connection running of a VAX 11/780 at the time. > > > The proposal, design and release of the DECstation 3100 was a > > top-secret project inside of DEC, kept secret from even many people > > in the Digital Unix group in Nashua, New Hampshire. The > > development of the system was done in Palo Alto's WorkStation > > Engineering group and the software engineering was done in the > > Western Software Labs in Palo Alto, albeit by taking key engineers > > from the Nashua facility and transplanting them temporarily to Palo > > Alto. > > > The implementation was kept so secret that it caught Dave Cutler, > > then working on DEC's next-generation operating system and chips, by > > surprise when it debuted at a Board Meeting in Maynard, > > Massachusetts. Shortly after that board meeting Mr. Cutler left > > Digital and moved (with some of his team) to Microsoft. > > Do you think that was just the straw that broke the camel's back? > > > The DECstations only were manufactured for a couple of years, as the > > DEC Alpha processor replaced MIPS in Digital's lineup. Although > > originally promised that OSF/1 would be ported to the DECstation > > line, this port was dropped due to realizing that there would never > > be an application base to support the customers of a DECstation > > OSF/1 port. It was better for ISVs and customers to maintain the > > Ultrix base for the DECstations than to split the base into Ultrix > > and OSF/1. > > Yeah, we had a ton of DECstations and a bunch of various early model > Alphas at WPI which we beta tested for DEC. The AS2100 with 8 DEC > StorageWorks canisters (which Netapp used on their early F220, F330, > F740 NAS systems) holding 3.5" disks, dual ported, hot-swapable. Nice > gear. > > The move from Ultrix to DEC OSF/1 was a bit painful, but not terrible > as I recall, but I'm sure I've blocked all the bad memories from then. > > Thanks for the walk down memory lane! > John >

1 year, 4 months

Re: [Wlug] Toshiba Laptop?

by Robert Condon

I am writing this on a Toshiba Tecra 8000. I have used it since Suse 7.2 but it is now 8.1. APM worked correctly with 8.0 but not with 8.1 so I will be reinstalling it with 8.0. Otherwise, I am happy with it though it gets hot and the battery only lasts about an hour. Bob Condon doug waud wrote: > Wesley Allen wrote: > >> What's your collective opinion of Toshiba laptops? Circuit City has >> got a decent machine (Satellite 1415-s173) for $999 and they actually >> let me boot Knoppix on it to check out hardware support (everything >> worked). > > > I have an old toshiba satellite ( 2595cdt ) which runs nicely for me on > SuSE 7.2. I have had it since 0ct/99. No problems. Have added memory and > put in a large hard drive. > >> The only thing I'm wondering about is the battery. > > > Battery life sucks. Like Andy I seem to get very poor running time. I > get an hour or less on battery so, for all practical purposes, I just > run it off the AC. > >> MY HP >> laptop doesn't let Linux read the battery info with either apm or acpi, >> and I think this is a function of an incredibly bad bios >> implementation. The demo models at Circuit City didn't have batteries, >> so I had no way of checking this bug out on that brand. Does anyone >> have experience with a Toshiba laptop t > > > I ran xapm and got a display which said I had 15% charge so I assume the > bios was readable. The 15% probably means little since the computer has > been sitting in its case inactive since the last WLUG meeting. > > doug > > PS while drafting this email the % came up to 21 so it seems the xapm is > working as expected. > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

22 years, 10 months

Re: [Wlug] Here I am begging again.

by John Stoffel

Ken> I have not been making the meetings. That does not mean my SUN Ken> ULTRA1 running Aurora Linux can no longer create 'interesting' Ken> problems. This time the second SUN ULTRA running Gentoo is in Ken> cahoots. Ken> I have a new SAMSUNG SyncMaster flat screen monitor. I have Ken> attached this monitor via a Belkin SUN adapter to my ULTRA1's. This is the 13W3 to VGA (HDB15) analog connector? Not the HDMI connector on the monitor? I've got a ton of Samsung 204Bs at work and they're nice to work on. Ken> It does not work!! The monitor flashes a little square window Ken> saying something about "Not optimum mode". It feels that it has Ken> not been configured correctly. The buttons on the right of the Ken> monitor, which are there to set it up, also do not work with the Ken> SUN's is attached. Ken> The monitor works fine with PC type machinery. The Belkin worked Ken> fine with a regular old tube monitor. (I have not dug out the Ken> old monitor to check whether it still works. I suspect it does.) Ken> Anybody have any ideas? Hmmm... if it was running Solaris I'd say take a look at the m64config command, but that's for Ultra 5/10 boxes. Basically, I think you need to force X to use a certain configuration. What does 'xrandr -query' say? Anything useful? Try editing your /etc/X11/xorg.conf to have a section like this, though you'll need to change the DEVICE from my old Matrox to whatever the Sun is really using. Section "Monitor" Identifier "Samsung LCD" HorizSync 60 EndSection Section "Screen" Identifier "Default Screen" Device "Matrox Graphics, Inc. MGA G400/G450" Monitor "Samsung LCD" DefaultDepth 24 SubSection "Display" Depth 1 Modes "1280x1024" EndSubSection SubSection "Display" Depth 4 Modes "1280x1024" EndSubSection SubSection "Display" Depth 8 Modes "1280x1024" EndSubSection SubSection "Display" Depth 15 Modes "1280x1024" EndSubSection SubSection "Display" Depth 16 Modes "1280x1024" EndSubSection SubSection "Display" Depth 24 Modes "1280x1024" EndSubSection EndSection

16 years, 3 months

Re: Wlug meeting on Thurs. Dec 10th 2020 @7pm.

by Frank Sweetser

It depends on the use case. If all you want is a free, reasonably stable version of RHEL, Centos stream might just be good enough. If your goal is to support software that wants RHEL, this could be hit or miss, as you'll always be running on an approximation of RHEL. You could say you should always have been just buying RHEL if it's that critical, but it's now that much less optional. I'm also really curious to see what's going to happen to the various black box appliances out there that currently run on CentOS, like Aruba Clearpass, Aruba wireless controllers, and the Juniper QFX switches. I doubt they'll want something stablish like CentOS Stream, so they most likely have three basic choices. 1. Run on CentOS 7 for as long as they can get away with it, and hope something better appears in the meantime 2. Work out a licensing deal for RHEL, and pass along the costs to the customers 3. Switch to an alternate distro like Ubuntu LTS The next year is going to be interesting for more than a few vendors... On Wed, Dec 9, 2020 at 3:59 PM Chuck Anderson <cra(a)alum.wpi.edu> wrote: > This might not be as bad as it initially sounds. Centos Stream will > consist of rolling updates that start from what will become each RHEL > point release to what will become the the next RHEL point release, so > for example from RHEL 8.1 to 8.2 to 8.3 etc. In fact, Centos 6, 7, > and 8 already is a "forced" minor upgrade every quarter or so since > they stop supporting x.y after RHEL x.y+1 comes out and your normal > system yum updates just migrate you to the newer x.y+1 anyway. This > is in contrast to how RHEL itself works, or how Scientific Linux used > to work, where you actually have to take explicit action to upgrade to > a new point release either using new install media or manual "yum" > commands. See for example: > > https://scientificlinux.org/documentation/faq/faq-releases/ > > And here is what one of my Centos 7 systems looks like: > > >cat /etc/centos-release > CentOS Linux release 7.9.2009 (Core) > >rpm -qf /etc/centos-release > centos-release-7-9.2009.1.el7.centos.x86_64 > >rpm -qi centos-release > Name : centos-release > Version : 7 > Release : 9.2009.1.el7.centos > Architecture: x86_64 > Install Date: Thu 03 Dec 2020 07:27:24 AM EST > .. > > See how the Centos 7.9.2009 release package was installed this month? > Previously, I had older versions of that package: > > >sudo grep centos-release /var/log/yum.log* > /var/log/yum.log:Nov 13 08:46:49 Updated: centos-release.x86_64 > 7-9.2009.0.el7.centos > /var/log/yum.log:Dec 03 07:27:24 Updated: centos-release.x86_64 > 7-9.2009.1.el7.centos > /var/log/yum.log-20181204:Jul 30 14:47:20 Updated: > centos-release-7-5.1804.el7.centos.2.x86_64 > /var/log/yum.log-20181204:Aug 14 12:15:35 Updated: > centos-release-7-5.1804.4.el7.centos.x86_64 > /var/log/yum.log-20181204:Oct 10 05:45:04 Updated: centos-release.x86_64 > 7-5.1804.5.el7.centos > /var/log/yum.log-20181204:Dec 04 07:19:18 Updated: centos-release.x86_64 > 7-6.1810.2.el7.centos > /var/log/yum.log-20200428:Jan 08 09:08:24 Updated: > centos-release-7-7.1908.0.el7.centos.x86_64 > /var/log/yum.log-20200428:Apr 28 07:47:22 Updated: centos-release.x86_64 > 7-8.2003.0.el7.centos > > So over the years, this server got upgraded automatically from Centos > 7.5 to 7.6 to 7.7 to 7.9. I have nightly automatic "yum updates" > turned on, so it just gets updates as they come out and I reboot the > server once every so often so the updates get fully applied (new > kernels, new shared libraries). > > The difference with Centos Stream is you'll get updates continually > /before/ RHEL releases it eventually as a "snapshot in time" called > RHEL x.y+1. Sure, they won't be as heavily tested as RHEL point > releases, but if you really need/want that, then you can either buy > RHEL or stage your Centos Stream updates from TEST-->STAGE-->PROD, > and/or stagger them across your PROD systems to minimize impact. > > On Wed, Dec 09, 2020 at 02:59:30PM -0500, Tim Keller wrote: > > I've got a fair amount of centos in production... this sucks... guess I'm > > going to Debian now... > > > > On Wed, Dec 9, 2020 at 9:10 AM Frank Sweetser via WLUG < > wlug(a)lists.wlug.org> > > wrote: > > > > > And for anyone looking to contribute to Greg's efforts: > > > > > > https://github.com/hpcng/rocky > > > > > > On Tue, Dec 8, 2020 at 11:23 PM Chuck Anderson via WLUG < > > > wlug(a)lists.wlug.org> wrote: > > > > > >> My favorite comment on that post: > > >> > > >> "Gregory Kurtzer says: > > >> December 8, 2020 at 4:27 pm > > >> > > >> I am considering creating another rebuild of RHEL and may even be able > > >> to hire some people for this effort. If you are interested in helping, > > >> please join the HPCng slack (link on the website hpcng.org) > > >> > > >> Greg > > >> (original founder of CentOS)" > > >> > > >> On Tue, Dec 08, 2020 at 10:35:24PM -0500, Frank Sweetser via WLUG > wrote: > > >> > Well, there's plenty talk about for CentOS users, like what you're > > >> going to > > >> > switch to now that CentOS is becoming something completely > different: > > >> > > > >> > https://blog.centos.org/2020/12/future-is-centos-stream/ > -- - Frank

4 years, 11 months

Re: Greetings Programs!

by Tim Keller

Lexi, I've heard of Tiny, but I've never seen it in action. That sounds really cool! Feel free to bring along the laptop to show it off! That in itself sounds like a great idea for a talk! Later, Tim. On Wed, Jan 8, 2020 at 5:16 PM Lexi Haley via WLUG <wlug(a)lists.wlug.org> wrote: > Hi, I'm Lexi! > > I've not been to a WLUG meeting since ... since a long time .... I > remember a Blender talk, and a Maddog talk - and these look like circa > 2003/2004.... So, absent a long time! > > Anyways. I am trying to find the time to come again. > > I've been a casual Linux user since 1998, when I installed Debian from a > pile of floppies (( or should I say, my friend installed it for me, and my > learning journey began )) .... and for a long time I was an exclusive user > .... and at heart I think I am still - even as I flog along a 10 year old > iMac. > > But for a couple years now, on my laptop I've been running 'Tiny Core > Linux' , which if you're unfamiliar with it, it is based on the Linux From > Scratch work, with an emphasis on a 'tiny' footprint. Needed additional > software are mounted into ram from squashfs archives, on the fly. It is > quirky, but I like it. I wondered if anyone else has used it (or uses it). > > I didn't feel right just asking blindly, without a vague reintroduction of > myself. > > So - question: Anyone else use, now or previously, the Tiny Core Linux > Distribution? [*] > > Thanks, > Lexi Haley (WPI CS 2002) > > [*] a search on the email archives yielded no hits ... > > _______________________________________________ > WLUG mailing list -- wlug(a)lists.wlug.org > To unsubscribe send an email to wlug-leave(a)lists.wlug.org > -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

5 years, 10 months

Re: [Wlug] Dec Meeting announcement / linux-raid problem

by Eric Martin

On Mon, Dec 20, 2010 at 4:52 PM, John Stoffel <john(a)stoffel.org> wrote: > >>>>> "Eric" == Eric Martin <eric.joshua.martin(a)gmail.com> writes: > > Eric> Now, the main reason for my email. My mythbox / home file > Eric> server runs linux soft-raid in RAID5 with 3 500GB disks. One > Eric> disk went bad a while ago and the array never rebuilt itself. > > So you only had two 500Gb disks left in the array? > Correct. I just received my new disk yesterday and dd_rescued the data from the bad disk onto a fresh disk. the array won't start, so here's the info you asked for > > Eric> The other day, the second disk went bad. Am I hosed? > > Possibly, it depends on how bad the second disk is. What I would do > is try to use dd_rescue to copy the 2nd bad disk onto a new disk > (possibly your original bad disk if you feel brave!) and then try to > re-assemble your raid 5 using that. You might or might not have > corruption in the filesystem, so make sure you run an fsck on it. > > Now, in the future, you should run a weekly check of the array for bad > blocks or other problems, so that you get notified if a disk dies > silently. I use the following crontab entry: > BTW, this is what I was missing. there was no warning that my disk was bad! Like I said, I have backups but the last one failed so I want something tighter > > > > Eric> I've been googling for 'rebuild bad linux software raid' but all > Eric> I get is the rebuild command. Also, I don't see any tools that > Eric> will move bad data to another spot on the disk. This is my > Eric> first time using software raid so I'm in a bit over my head. > > The first thing is to ask for help on the linux-raid mailing list, > which is hosted on vger.kernel.org. > > But somethings you can do to help is to give us more information. > Like: > > cat /proc/mdstat > Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md2 : inactive sda3[0](S) 4000064 blocks md3 : inactive sda4[0] 483315456 blocks unused devices: <none> > > mdadm -E /dev/sd... > > or /dev/hd... depending on whether your SATA or IDE drives. > Basically, use the devices you got from the /proc/mdstat output as > your basis. > > Give us this output, and we should be able to help you more. > livecd / # mdadm -E /dev/sda3 /dev/sda3: Magic : a92b4efc Version : 00.90.00 UUID : 8374ea27:6e191996:e56f6693:e45468a9 Creation Time : Sat Jul 11 17:14:31 2009 Raid Level : raid5 Used Dev Size : 4000064 (3.81 GiB 4.10 GB) Array Size : 8000128 (7.63 GiB 8.19 GB) Raid Devices : 3 Total Devices : 2 Preferred Minor : 0 Update Time : Mon Dec 13 03:59:27 2010 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 1 Spare Devices : 0 Checksum : fc28b820 - correct Events : 0.496842 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 0 8 3 0 active sync /dev/sda3 0 0 8 3 0 active sync /dev/sda3 1 1 8 19 1 active sync 2 2 0 0 2 faulty removed livecd / # mdadm -E /dev/sda4 /dev/sda4: Magic : a92b4efc Version : 00.90.00 UUID : c7b07c90:cbd50faf:bc824667:2504996b Creation Time : Sat Jul 11 16:52:52 2009 Raid Level : raid5 Used Dev Size : 483315456 (460.93 GiB 494.92 GB) Array Size : 966630912 (921.85 GiB 989.83 GB) Raid Devices : 3 Total Devices : 2 Preferred Minor : 3 Update Time : Thu Dec 9 11:13:25 2010 State : clean Active Devices : 1 Working Devices : 1 Failed Devices : 2 Spare Devices : 0 Checksum : d43b9ad8 - correct Events : 0.15550817 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 0 8 4 0 active sync /dev/sda4 0 0 8 4 0 active sync /dev/sda4 1 1 0 0 1 faulty removed 2 2 0 0 2 faulty removed livecd / # mdadm -E /dev/sdb3 mdadm: cannot open /dev/sdb3: No such file or directory livecd / # mdadm -E /dev/sdb4 mdadm: cannot open /dev/sdb4: No such file or directory livecd / # mdadm -E /dev/sdc4 /dev/sdc4: Magic : a92b4efc Version : 00.90.00 UUID : c7b07c90:cbd50faf:bc824667:2504996b Creation Time : Sat Jul 11 16:52:52 2009 Raid Level : raid5 Used Dev Size : 483315456 (460.93 GiB 494.92 GB) Array Size : 966630912 (921.85 GiB 989.83 GB) Raid Devices : 3 Total Devices : 2 Preferred Minor : 3 Update Time : Thu Dec 9 11:13:06 2010 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 1 Spare Devices : 0 Checksum : d34e516a - correct Events : 0.15550815 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 1 8 20 1 active sync 0 0 8 4 0 active sync /dev/sda4 1 1 8 20 1 active sync 2 2 0 0 2 faulty removed livecd / # mdadm -E /dev/sdc3 /dev/sdc3: Magic : a92b4efc Version : 00.90.00 UUID : 8374ea27:6e191996:e56f6693:e45468a9 Creation Time : Sat Jul 11 17:14:31 2009 Raid Level : raid5 Used Dev Size : 4000064 (3.81 GiB 4.10 GB) Array Size : 8000128 (7.63 GiB 8.19 GB) Raid Devices : 3 Total Devices : 2 Preferred Minor : 0 Update Time : Mon Dec 13 03:59:27 2010 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 1 Spare Devices : 0 Checksum : fc28b832 - correct Events : 0.496842 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 1 8 19 1 active sync 0 0 8 3 0 active sync /dev/sda3 1 1 8 19 1 active sync 2 2 0 0 2 faulty removed /dev/sda is a good disk, /dev/sdc is the bad disk and /dev/sdb is the good disk that has the clone of /dev/sdc. Curiously, mdadm -E doesn't work on /dev/sdb even though the partitions are setup correctly thanks! > > John > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > -- Eric Martin

14 years, 11 months

WLUG search results for query "meeting"