** Branch linked: lp:ubuntu/karmic/mountall
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
I took a crack at adding a -f fake-mount option to mount.ecryptfs.c
today. I'm attaching the not-yet-functional diff, simply to store it
off somewhere until I have time to come back and take another look at
it.
The argument parsing still needs some work.
** Attachment added: "out"
http://laun
** Changed in: ecryptfs-utils (Ubuntu Karmic)
Assignee: Dustin Kirkland (kirkland) => (unassigned)
** Changed in: ecryptfs-utils (Ubuntu)
Assignee: Dustin Kirkland (kirkland) => (unassigned)
** Also affects: ecryptfs
Importance: Undecided
Status: New
** Changed in: ecryptfs
** Branch linked: lp:ubuntu/mountall
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
This bug has been fixed.
If you are still having problems, please file a new report.
** Changed in: mountall (Ubuntu Karmic)
Status: New => Fix Released
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification because yo
No whoop i face similar problem as you, I have attached my o/p or log to
the command "mountall --debug > mountall0.2.5.log 2>&1" in #73. I think
it might help kernel ppl get a better idea.
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this
Are you referring to me Rajeev? If so, I attached the log in comment #71
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
again there seems to be some problem. Please find the o/p to: sudo
mountall --debug > mountall0.2.5.log 2>&1
** Attachment added: "mountall0.2.5.log"
http://launchpadlibrarian.net/34302392/mountall0.2.5.log
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443
Thanks for the info Dustin, with new kernel upgrade. Everythings seems
so good so far..
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
** Attachment added: "sudo mountall --debug > mountall0.2.5.log 2>&1"
http://launchpadlibrarian.net/34115849/mountall0.2.5.log
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification because you are a member of Ubuntu
Bugs,
whoop: might be good to do about
$ sudo mountall --debug > mountall0.2.5.log 2>&1
and then attach the resultant file to the bug again
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification because you are a member of Ubuntu
Bu
I still get stuck at boot. This happens about once every ten boots (on
average). It gets stuck right after fsck now.. It just sits there, with a
blinking cursor and no hd activity
Please let me know if there is any (more) information I can provide to solve
this problem...
I am using mountall
I still get stuck at boot. This happens about once every ten boots (on
average). It gets stuck right after fsck now.. It just sits there, with a
blinking cursor and no hd activity
Please let me know if there is any (more) information I can provide to solve
this problem...
I am using mountall
fsck is disabled when you're on battery power, for your protection (so
that the battery doesn't die during the middle of an fsck recovery,
which would be *very* bad).
:-Dustin
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notifica
not sure if it helps, but a little trial error indicated:
Case 1: Turn on my laptop without the power cord connected.
No fsck error.
Case 2: Turn on the laptop with power cord connected.
fsck from util-linux-ng 2.16
/dev/sda5 has been mounted 34 times without being checked, check forced
A litt
This bug was fixed in the package mountall - 0.2.5
---
mountall (0.2.5) karmic; urgency=low
* Filesystem check progress reporting, including cancellation. LP: 446596.
* When we're waiting for a mountpoint, if a few seconds of inactivity
passes, report what we're waiting for a
wow. for some mysterious reason when i tried to boot my trouble
systemit went through. Can someone throw some light on this?
Also, I'm a little afraid of getting updates and installing new packages
now :)
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/4430
I've uploaded a new version of mountall (0.2.5) to the ubuntu-boot PPA,
as usual I would appreciate a little testing before I upload it to the
archive proper.
Thanks
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification becau
oops actually i did sudo apt-get upgrade ! instead of sudo apt-get update
that i mentioned in the last post.
this took a while, since it was upgrading all kind of packages.
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notificatio
Checked source.list.d files and source.list file that you specified. I
dont think I have http://ppa... or anything link with word boot enabled.
But, still your solution worked once and then, I tried to boot in safe
mode and repaired the packages. Again, I'm at the same point. unable to
boot :(
Nex
Well, my solution is applicable if you enabled the boot ppa. Those apckages
are sometimes quite experimental. In that case, you can downgrade the boot
ppa packages to the 'stable' ones from the standard karmic repo.
If that's the case, you first have to disable the boot ppa. You can edit
this by t
My system was restored and I was running Karmic for a week. Now, the
same problem arises. I again tried to follow your steps (below). Can you
please tell me what should be removed or what causes the problem that
should be removed when I'm in the problematic install (mount from disk -
Solution menti
Please close out (--> "wontfix") karmic targets for bugs that are being
deferred to lucid, don't just remove the milestone.
** Changed in: ecryptfs-utils (Ubuntu Karmic)
Status: Triaged => Won't Fix
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
Since Scott has worked around this, I won't try to fix this for Karmic.
However, I'll handle it in the upstream source and merge that into
Lucid.
Dropping the milestone, leaving assigned to me.
:-Dustin
** Changed in: ecryptfs-utils (Ubuntu Karmic)
Milestone: ubuntu-9.10 => None
** Changed
** Branch linked: lp:~ubuntu-core-dev/ubuntu/karmic/mountall/ubuntu
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Have worked around this in mountall
** Changed in: mountall (Ubuntu Karmic)
Milestone: None => ubuntu-9.10
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Dustin: in the mount manpage:
-f Causes everything to be done except for the actual system call;
if it's not obvious, this ``fakes'' mounting the file system.
This option is useful in conjunction with the -v flag to deter‐
mine what the mou
Dustin, not sure exactly, though comments #48 and #49 might be of some
use. At any rate, mountall appears to expect that you won't ask for a
password. But I'm no expert, just reading between the lines, so ...
I've resubscribed Scott James Remnant, who is responsible for mountall,
and hope that he
I also have the same problem and I still looking to fix this bug.
fsck from util-Linux-ng 2.16
/dev/sda7 has mounted 37 times without being checked, check forced
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification because
Where is the specification of -f|--fakemount that ecryptfs is supposed
to support?
:-Dustin
** Changed in: ecryptfs-utils (Ubuntu Karmic)
Status: New => Incomplete
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification
I tried it all, user login password, the password for my private folder,
an empty password, cancel and the window close button
Is the Action value: org.freedesktop.devicekit.disks.filesystem-mount-
system-internal in the
screenshot(http://launchpadlibrarian.net/33558071/gparted.png) of any
use
OK - I've updated the title and subscribed Dustin Kirkland (who looks
after ecryptfs). I guess the status should be triaged, but I don't seem
to have permission to change that.
I'm also bewildered as to why you are being asked for a password for
/dev/sda5 - have you tried just closing that window
32 matches
Mail list logo
