~ubuntu-branches/ubuntu/lucid/mountall/lucid-updates : changes

~ubuntu-branches/ubuntu/lucid/mountall/lucid-updates » Changes from revision 338

From Revision 338 to 319

Rev	Summary	Authors	Tags	Date
338	[ Colin Watson ] [ Colin Watson ] Fix infinite loop when one of mountall's private mount options is followed by a comma, and guard against other reasons why cut_options might end up comparing a zero-length option (LP: #649591).	Scott Moser	2.15.3	13 years ago
337	* SECURITY UPDATE: do not leave writable udev rules file aro... * SECURITY UPDATE: do not leave writable udev rules file around. - src/mountall.c: set umask correctly (LP: #591807). - debian/preinst: remove boot-time udev rules file. - CVE-2010-2961	Kees Cook	2.15.2	13 years ago
336	conf/mountall.conf: set $LANG so that messages appearing in ... conf/mountall.conf: set $LANG so that messages appearing in plymouth are translated (LP: #569365); this is a temporary workaround until upstart is fixed to pass the appropriate env vars to all init scripts	Adrien Cunin	2.15.1	13 years ago
335	[ Scott James Remnant ] [ Scott James Remnant ] * Fix an obvious thinko error that meant that the "I"gnore fsck error key for a "hard" failure was ignored. * When cancelling filesystem checks, only cancel those that are actually checking filesystems; otherwise those that are merely verifying the superblock will return an "unrecoverable error" rather than "cancelled". LP: #577331. [ Steve Langasek ] * Only send plymouth a progress update when there's actual progress to report; otherwise we flood plymouthd with redundant events, and the progress will spin for minutes after the fsck itself is finished. Thanks to Tero Mononen and Anders Kaseorg for the patch. LP: #571707.	Steve Langasek	2.15	13 years ago
334	releasing version 2.15 releasing version 2.15	Steve Langasek		13 years ago
333	document another bug closure document another bug closure	Steve Langasek		13 years ago
332	Only send plymouth a progress update when there's actual pro... Only send plymouth a progress update when there's actual progress to report; otherwise we flood plymouthd with redundant events, and the progress will spin for minutes after the fsck itself is finished. Thanks to Tero Mononen and Anders Kaseorg for the patch. LP: #571707.	Steve Langasek		13 years ago
331	mnt->error can never be 'fsck in progress' mnt->error can never be 'fsck in progress'	Scott James Remnant		13 years ago
330	When cancelling filesystem checks, only cancel those that ar... When cancelling filesystem checks, only cancel those that are actually checking filesystems; otherwise those that are merely verifying the superblock will return an "unrecoverable error" rather than "cancelled".	Scott James Remnant		13 years ago
329	Fix an obvious thinko error that meant that the "I"gnore fsc... Fix an obvious thinko error that meant that the "I"gnore fsck error key for a "hard" failure was ignored.	Scott James Remnant		13 years ago
328	Begin new release Begin new release	Scott James Remnant		13 years ago
327	releasing version 2.14 releasing version 2.14	Steve Langasek	2.14	13 years ago
326	mountall is missing a very important line of code that incre... mountall is missing a very important line of code that increases the udev buffer size; without this it's possible we may miss events during busy periods. LP: #561390.	Scott James Remnant		14 years ago
325	When cancelling in-progress fsck, don't deference the NULL m... When cancelling in-progress fsck, don't deference the NULL mount record. LP: #562811.	Scott James Remnant		14 years ago
324	Revert the previous revision. Revert the previous revision. This would result in two errors. First an fsck is not in progress just because fsck is running; this is precisely why this flag is different - we need to wait until we get the first progress indicator on the pipe. Secondly the change from > to >= would mean that the currently displayed message would change. The user might have just pressed "S" to skip one filesystem, but mountall now decides to skip a completely different one. Bad.	Scott James Remnant		14 years ago
323	When an fsck is in progress, record this properly so it's po... When an fsck is in progress, record this properly so it's possible to cancel the fsck later. LP: #562811.	Steve Langasek		14 years ago
322	better fix - instead of looking at the mountpoint, use the s... better fix - instead of looking at the mountpoint, use the same logic as in our placeholder code (type == none && device == none)	Steve Langasek		14 years ago
321	If we're not marking all nodev filesystems as virtual, we ne... If we're not marking all nodev filesystems as virtual, we need to special-case /tmp - which is already special-cased in /lib/init/fstab, so I don't feel too guilty.	Steve Langasek		14 years ago
320	Don't mark a filesystem "nodev" just because it's got "none"... Don't mark a filesystem "nodev" just because it's got "none" in the device column; this will block the "virtual-filesystems" event which is the one that can't use Plymouth to prompt. LP: #507881.	Scott James Remnant		14 years ago
319	actually start new version properly actually start new version properly	Scott James Remnant		14 years ago

Older »