- WLUG - wlug.mailman3.com

OPENING - Jr SW Engineer - C, Linux kernel - direct hire in Waltham, MA

by John Spencer

Our client in Waltham, MA has a direct hire opening for a Software Engineer with 0-3 yrs of commercial design and development experience. Must be able to interview and work on-site. Our client cannot sponsor visas at this time. Jr Software Engineer Software Engineer with relevant Linux Driver experience. Responsible for design, develop and test of Linux drivers for high-speed network/communication products. Required: - BSCS/BSEE - Hands-on experience developing and interfacing with Linux drivers - Experience with Linux kernel and strong C background - Experience implementing Linux for TCP/IP Ethernet and related Please send your resume to jspencer@connectedsp (dot) com Your resume will not be sent anywhere without your prior approval Regards, John Spencer Connected Systems Partners Connecting Top Talent with Top Companies Office: 978-455-5550 x208 Cell: 978-621-9743 jspencer(a)connectedsp.com www.connectedsp.com GET CONNECTED! Unless otherwise explicitly instructed by sender, all information in this email is considered confidential and intended for the view and use of the recipient(s) only.

March 14, 2014

Re: [Wlug] HOWTO debug Ubuntu boot hang

by Randall Mason

On Fri, Mar 14, 2014 at 5:16 PM, John Stoffel <john(a)stoffel.org> wrote: > > Andy> I've got a version of Ubuntu 13.10 in my Virtualbox OSE virtual > Andy> computer. It hangs very early in the boot. GRUB runs and the > Andy> boot starts. > > I've moved to Linux Mint myself, but it's based on Ubuntu and I've > noticed that my main desktop, which NFS mounts home dirs and other > stuff, takes *forever* to actually boot not. There's something in the > setup which hangs for five minutes or so (not sure, I just walk away > right now cause I rarely reboot the box...) before it continues. > > Have you just let the boot sit there to see if it ever finishes? I've > been meaning to turn on verbose debugging to try and figure out what's > going on too, but it's a low priority. I find that fstab is also often a problem. If it's waiting for /dev/sdb1 to show up, or a specific UUID. Maybe comment out anything not required for boot. Also, if you're at the console, comment out your whole /etc/network/interfaces and see if that helps. Ubuntu often waits on block devices and network, so it could be either of those. Randall Mason clashthebunny(a)gmail.com

March 14, 2014

Re: [Wlug] HOWTO debug Ubuntu boot hang

by John Stoffel

Andy> I've got a version of Ubuntu 13.10 in my Virtualbox OSE virtual Andy> computer. It hangs very early in the boot. GRUB runs and the Andy> boot starts. I've moved to Linux Mint myself, but it's based on Ubuntu and I've noticed that my main desktop, which NFS mounts home dirs and other stuff, takes *forever* to actually boot not. There's something in the setup which hangs for five minutes or so (not sure, I just walk away right now cause I rarely reboot the box...) before it continues. Have you just let the boot sit there to see if it ever finishes? I've been meaning to turn on verbose debugging to try and figure out what's going on too, but it's a low priority. Andy> In /var/log/boot.log, I see the same messages as I see on the Andy> screen. I have to press ESC to see the text while the computer Andy> boots. There are perhaps 3 or 4 "Starting <service>....OK" Andy> messages, and that is all. I never get a chance to log in. So which services start? Or more accurately, which is the last service to start? Have you looked in /var/log/upstart as well? You might be able to also setup your system so that init (upstart) is started with the -v option to increase verbosity. Andy> The problem I have is that I don't know in which order the boot Andy> scripts are supposed to run. With the "old" initscripts, one Andy> would see Snn<script> or Knn<script> and the "nn" would be the Andy> number representing the order in which the scripts are "S"tarted Andy> or "K"illed. That isn't the case here. They're supposed to run according to events, not any particular order. The idea is that as things become ready, the next step can fire off more quickly, without the system getting stuck behind some hanging process. Good luck! John P.S. Another idea might be to try and boot a default 13.10 install in another VM and see how that looks in the console. It should be similiar at least, if not fairly identical. John

March 14, 2014

Re: [Wlug] HOWTO debug Ubuntu boot hang

by Michael C Voorhis

Andy Stewart writes: > Lots of details here: > http://upstart.ubuntu.com/cookbook > My problem seems to be something to do with networking. None of the > network related services are starting. More news later..... > Andy In FreeBSD I've run into issues with this specific problem, where DHCP runs and then netowrk dependent services start before they should. The FreeBSD folks eventually remedied the problem ("SYNCDHCP" setting for network interfaces) but my initial "fix" was to edit the network start script and add a "sleep 5" or "sleep 10" line in there allowing the networking to settle. Other cures have been to insert a ping or a dig call which must succeed, before allowing the boot process to continue. MCV.

March 14, 2014

Re: [Wlug] HOWTO debug Ubuntu boot hang

by Andy Stewart

Lots of details here: http://upstart.ubuntu.com/cookbook My problem seems to be something to do with networking. None of the network related services are starting. More news later..... Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF)

March 14, 2014

Re: [Wlug] HOWTO debug Ubuntu boot hang

by Andy Stewart

On 03/13/2014 10:18 PM, Michael C Voorhis wrote: > Andy Stewart writes: >> The problem I have is that I don't know in which order the boot scripts >> are supposed to run. With the "old" initscripts, one would see >> Snn<script> or Knn<script> and the "nn" would be the number representing >> the order in which the scripts are "S"tarted or "K"illed. That isn't >> the case here. > > The manpage for systemd(1) has this tidbit: > >> --test >> Determine startup sequence, dump it and exit. This is an option >> useful for debugging only. > > That sounds like it might be useful. > > --MCV. > I'm not sure that Ubuntu is using systemd - yet. I'm running version 13.10. http://www.zdnet.com/after-linux-civil-war-ubuntu-to-adopt-systemd-70000263… I have a feeling that I need to figure out how to debug upstart, but I'm not sure. Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF)

March 14, 2014

HOWTO debug Ubuntu boot hang

by Michael C Voorhis

Andy Stewart writes: > The problem I have is that I don't know in which order the boot scripts > are supposed to run. With the "old" initscripts, one would see > Snn<script> or Knn<script> and the "nn" would be the number representing > the order in which the scripts are "S"tarted or "K"illed. That isn't > the case here. The manpage for systemd(1) has this tidbit: > --test > Determine startup sequence, dump it and exit. This is an option > useful for debugging only. That sounds like it might be useful. --MCV.

March 14, 2014

HOWTO debug Ubuntu boot hang

by Andy Stewart

HI guys, I've got a version of Ubuntu 13.10 in my Virtualbox OSE virtual computer. It hangs very early in the boot. GRUB runs and the boot starts. In /var/log/boot.log, I see the same messages as I see on the screen. I have to press ESC to see the text while the computer boots. There are perhaps 3 or 4 "Starting <service>....OK" messages, and that is all. I never get a chance to log in. The problem I have is that I don't know in which order the boot scripts are supposed to run. With the "old" initscripts, one would see Snn<script> or Knn<script> and the "nn" would be the number representing the order in which the scripts are "S"tarted or "K"illed. That isn't the case here. I've found the boot scripts in /etc/init/*.conf so I can match boot messages to scripts. However, I'm unable to determine which script got stuck since I don't know the order of execution. My version of 13.10 is customized, not stock, so I can't compare to a known good. Any ideas would be greatly appreciated. Thanks! Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF)

March 14, 2014

Registration Reminder! LOPSA-East SysAdmin Conference, May 2-3 2014, New Brunswick, NJ

by Tom Limoncelli

Greetings! I just wanted to remind everybody about the awesome tutorials and talks we have lined up for LOPSA-East this year! Don't forget to register before the Early Bird pricing expires! LOPSA-East is a regional sysadmin conference in New Brunswick NJ, May 2-3, 2014. Two days of world-class training on a diverse range of topics plus community-selected talks on everything from DevOps to Time Management. You can find all the latest details available on our website: http://lopsa-east.org Register now at: http://lopsa-east.org/2014/register-for-lopsa-east-14 We'll see you there! Best, Tom, Evan, & the rest of the LOPSA-East 2014 Committee

March 13, 2014

Announce: WLUG Meeting Thu 3/13 7PM

by Chuck Anderson

Hi folks, The next Worcester Linux Users' Group (WLUG) meeting will be held tomorrow, Thursday, March 13 at 7PM. The location will be the WPI Campus Center, Mid-Centry Room 331. Thursday, March 13, 7:00 - 9:00 PM WPI Campus Center, Mid-Centry Room 331 Afterwards, we will go out for pizza. See you there, Chuck President, Worcester Linux Users' Group http://www.wlug.org/

March 12, 2014