pablolie;497473 Wrote:
> At this point in time you are trolling, your argument consists of
> putting words in my mouth I have never remotely used, and absolutes
> ("root" "everyone") that sadky reveal a confrontational instinct, and
> your confidence coming from your conviction you are smarter than the
> entire Ubuntu community put together. Good for you and I hope you are
> right, you'll do well indeed then.
Righto. The "entire Ubuntu community"? And you're not talking about
everyone?
>
> Since I have no idea what your point is I'll move to ignoring you now.
> Which is a shame because I think there is technical merit to some of
> your arrogance, but at this point in time you've dug your grave in this
> argument with it.
>
There is a ton of technical merit: you seem to miss it... You also
contradict yourself.
>
> That is because the start sequence is all screwed up in Linux with
> 7.4.1.
>
Wrong: it IS correct... Explain why it is "all screwed up in Linux".
(Again, this is ALL versions of Linux? Not just your install and usage
in Ubuntu?)
[qoute]
You have to restart SBS every time you restart you system, or edit a
startup script that delays SBS start. Try..
sudo /etc/init.d/squeezeboxserver stop
and
sudo /etc/init.d/squeezeboxserver start
I do not have to manuallyt start SBS. So "You" is wrong there. I have
not edited any startup script or even changed the order of rc2.d
executions.
After a little while, SBS should then run as OK as it every will under
7.4.1. I do that on the rare occasions that I restart this system.
I thought this didn't affect you.. but here you say it does...
As to permissions, and package that is installed by the admin id ought
to be smart enough to make sure that sufficient resource permissions are
awarded to it for system wide operation. Otherwise the installation
procedure can only be regarded as buggy.
So it is "buggy" that a process installed can not access files that it
does not have permission to access? The only way an arbitrary process
may access files is if it either has explicit permission granted by the
filesystem based on UID and GID of the process, or it is root and can
access whatever it wants.
I've asked you what your fix for this "buggy" behavior is several times,
yet you ignore and sidestep the issue.
The catch is that there is no such fix. You must either fix the file
permissions or run the server as root.
Neither should be done at package install: the admin can change
pemissions as needed and root is a bad idea.
This is NOT a hypothetical issue: you yourself raised it and called the
behavior buggy.
Stand by your own words.
--
snarlydwarf
------------------------------------------------------------------------
snarlydwarf's Profile: http://forums.slimdevices.com/member.php?userid=1179
View this thread: http://forums.slimdevices.com/showthread.php?t=71700
_______________________________________________
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
