Slashdot Mirror

systemd is modular.

Yes, so modular.

I take it that you have not looked at the actual code, afaik there is no nasty web of dependencies. Where there are dependencies they are on a documented DBUS service and not on a specific pid 1 and afaik there are no inter-project dependency either.

Yeah, so a fork that tries to split the "applications" in systemd must be quite easy to produce. Or is it?

It's always nice to have alternatives. How fast or slow is it for a typical desktop?

I did find an interesting write up of experimenting with epoch as an init/systemd replacement.

Glad that you finally realise something running well and continues to run well cannot be "just broken". And in case you need demonstrably better alternatives to systemd, there are already quite a few.

The Devuan developers don't think they can do it in Debian for two reasons:

One, most of them never contributed to Debian before, they only use it.

Which makes the false assumption that Debian is only contributed to by developers. Nice distro that does not need users!

Two, they have a "burn it with fire" attitude instead of actually understanding how to support both systemd and sysvinit in the same distro.

.. or instead because systemd is such crapware, does not play well with other software (eg. NFS mount), and has excellent alternatives?

Captcha: dispute

Keyword: propaganda.

You ean you can't do this, or this? Interesting.

I know what you're trying to get at - doing those things in PowerShell is possibly more convenient if it's been designed from the ground up for a networked environment - but you shouldn't make the mistake of assuming that you can't do something in Linux just because you yourself do not know how. That's rather hypocritical after what you just said about Slashdotters not knowing how to use Windows.

In fact, you can take the bootable floppy image and burn it straight to abootable CD using this process. I've used this successfully to upgrade the BIOS of a machine with no floppy drive.

The most common version of this issue has to do with when a new kernel update occurs during a NORMAL ubuntu update. You click the orange star, choose update, let it download and install, then reboot and voila...no more access to any hard drive. It happens to my machine every single time.

I agree that it is annoying when a kernel updates swacks your menu.lst.

I have to get out my liveCD boot with it, mount the main HDD partition, go into the /boot/grub and edit the menu.lst to change everything back.

Wow, talk about doing it the hard way!

The thing I like about grub is that you can alter your boot parameters on the fly, so you can work your way out of this situation without having to resort to the liveCD method. You can give grub commands from the grub prompt and get running so that you can at least boot up normally and edit your menu.lst.

I have found this to be an excellent resource for demystifying how grub works.

So much better than the bad old LILO days...

I've been playing with the math myself for primes, but what library or technique do they use to get past 32bits? It's probably simple, but I'd appreciate some help.

You'll probably find this article interesting - it covers prime finding (in C) from naive algorithms to complexe ones involving paging bit arrays in and out of memory: "Fun With Prime Numbers"

1. Get the Attitude
2. Get a complete and accurate symptom description
3. Make damage control plan
4. Reproduce the symptom
5. Do the appropriate general maintenance
6. Narrow it down to the root cause
7. Repair or replace the defective component
8. Test
9. Take pride in your solution
10. Prevent future occurrence of this problem

1. Get the Attitude
2. Get a complete and accurate symptom description
3. Make damage control plan
4. Reproduce the symptom
5. Do the appropriate general maintenance
6. Narrow it down to the root cause
7. Repair or replace the defective component
8. Test
9. Take pride in your solution
10. Prevent future occurrence of this problem

1. Get the Attitude
2. Get a complete and accurate symptom description
3. Make damage control plan
4. Reproduce the symptom
5. Do the appropriate general maintenance
6. Narrow it down to the root cause
7. Repair or replace the defective component
8. Test
9. Take pride in your solution
10. Prevent future occurrence of this problem

1. Get the Attitude
2. Get a complete and accurate symptom description
3. Make damage control plan
4. Reproduce the symptom
5. Do the appropriate general maintenance
6. Narrow it down to the root cause
7. Repair or replace the defective component
8. Test
9. Take pride in your solution
10. Prevent future occurrence of this problem

1. Get the Attitude
2. Get a complete and accurate symptom description
3. Make damage control plan
4. Reproduce the symptom
5. Do the appropriate general maintenance
6. Narrow it down to the root cause
7. Repair or replace the defective component
8. Test
9. Take pride in your solution
10. Prevent future occurrence of this problem

1. Get the Attitude
2. Get a complete and accurate symptom description
3. Make damage control plan
4. Reproduce the symptom
5. Do the appropriate general maintenance
6. Narrow it down to the root cause
7. Repair or replace the defective component
8. Test
9. Take pride in your solution
10. Prevent future occurrence of this problem

1. Get the Attitude
2. Get a complete and accurate symptom description
3. Make damage control plan
4. Reproduce the symptom
5. Do the appropriate general maintenance
6. Narrow it down to the root cause
7. Repair or replace the defective component
8. Test
9. Take pride in your solution
10. Prevent future occurrence of this problem

1. Get the Attitude
2. Get a complete and accurate symptom description
3. Make damage control plan
4. Reproduce the symptom
5. Do the appropriate general maintenance
6. Narrow it down to the root cause
7. Repair or replace the defective component
8. Test
9. Take pride in your solution
10. Prevent future occurrence of this problem

1. Get the Attitude
2. Get a complete and accurate symptom description
3. Make damage control plan
4. Reproduce the symptom
5. Do the appropriate general maintenance
6. Narrow it down to the root cause
7. Repair or replace the defective component
8. Test
9. Take pride in your solution
10. Prevent future occurrence of this problem

1. Get the Attitude
2. Get a complete and accurate symptom description
3. Make damage control plan
4. Reproduce the symptom
5. Do the appropriate general maintenance
6. Narrow it down to the root cause
7. Repair or replace the defective component
8. Test
9. Take pride in your solution
10. Prevent future occurrence of this problem

Randal Schwartz's Perls of Wisdom will never take the place in my heart that is forever occupied by Steve Litt's PERLS of Wisdom!

Replace step 5 with Microsoft will fund a bill in congress to make open source GPL illegal.

Several posters have pointed out useful rules that didn't make the book authors list, such as comparison with a known good example or explaining the problem to someone else.

It's also worth noting that some of this terrain has also been codified into the "Universal Troubleshooting Process" here.

Tyler

Google found a great article called Windows to Linux Migration Case Histories

And as a nice sideeffect everyone is forced to upgrade his Browser. Even if the upgrade is free this has some implications. My major concern would be changes in the Licensing terms, i.e. what you are allowed to do with that browser and the files with your data it is managing. See here why this might be a concern. As an example, if it manages your email, and that updated browser is using a proprietary format to save it you're suddenly tied to that productline if you want to keep that e-mail. Extend that to address-lists, bookmarks, etc.

So i think there are valid reasons not to want a free update, but security-holes that large are plain unbearable.

I asked Hadar how they planned to make money now that they'd given away the tools. He smiled and ticked off the three prong plan:

1.Tech support on Zope projects
2.Contract Zope development
3.Zope derived vertical apps

such as this - if a company knows of a material defect in their product and conceals such to the consumer, resulting in losses to the consumer - said greedheads are liable under the higher standards of gross-negligence, recklessness, or even intentional tort, resulting in statutory treble damages or unlimited punitive damages in some cicumstances.

The greedheads are already well on their way to taking care of that little problem. Go read up on UCITA.

http://www.troubleshooters.com/ucita/

http://www.2bguide.com/nccusl.html

Here's a list of Infoworld articles on UCITA

You can find a whole lot more besides these by doing a Google search.

This sounds like a job for

http://www.troubleshooters.com
Troubleshooting follows a general
problem solving process, which makes any
intractible problem look like debugging
a program. There is always a place to
start. You never have to feel overwhelmed.
And basically you know that there are a
million other troubleshooters out there who
are on your side all the way.

If you are looking for more specific
references on wiring computers for kids and
schools,
there is a new initiative directed at
getting better software into schools
called.

http://www.openclassroom.com


This is really a worthwhile ambition.
Good luck! (and remember, the computer
is your friend...)