Slashdot Mirror
Shuttleworth Says Snappy Won't Replace .deb Linux Package Files In Ubuntu 15.10
darthcamaro writes: Mark Shuttleworth, BDFL of Ubuntu is clearing the air about how Ubuntu will make use of .deb packages even in an era where it is moving to its own Snappy ('snaps') format of rapid updates. Fundamentally it's a chicken and egg issue. From the serverwatch article: "'We build Snappy out of the built deb, so we can't build Snappy unless we first build the deb,' Shuttleworth said. Going forward, Shuttleworth said that Ubuntu users will still get access to an archive of .deb packages. That said, for users of a Snappy Ubuntu-based system, the apt-get command no longer applies. However, Shuttleworth explained that on a Snappy-based system there will be a container that contains all the deb packages. 'The nice thing about Snappy is that it's completely worry-free updates,' Shuttleworth said."
why is this modded troll?
Lennart the great mastermind has announced it on his blog: http://0pointer.net/blog/revis...
When they F*sk my system with an update that fails and it loses my data or prevents me from working, just once, it can be a huge disaster for me.
But isn't that exactly what these Snappy - packages are meant to address? All the current data for the application is backed up, the update is applied, if something goes wrong the system rolls back to the state the package and its data was before the update was attempted. At least that's what it says on Ubuntu's website, I don't know anything else about this thing.
What are you on about?
There's your stdout and stderr.
Actually no, it hasn't. sysv init has long been a pile of hacks on top of a pile of hacks. Ever tried to write a sysv service? It's really wonderful when a service refuses to come up because the pid file was left around for whatever reason, and some other program happens to be running under that pid.
For instance, the stderr thing this guy is complaining about was long a "feature" of sysv systems, where stderr could actually disappear into the void. Systemd actually makes things much better by ensuring stderr always gets saved.
As to why change logging, under systemd you can trivially ask for the messages for a particular service, or the messages from last boot, without having to figure out what to grep for, or having to setup syslogd beforehand to sort out your messages into separate files.