| Author |
Message |
Karl Godt

Joined: 20 Jun 2010 Posts: 2689 Location: Kiel,Germany
|
Posted: Tue 21 Jun 2011, 06:02 Post subject:
|
|
Furthermost I want to add , that the mount script had not changed from pup430 to luci254 , which I think had been the third last release candidate for 525 .
|
|
Back to top
|
|
 |
Bruce B

Joined: 18 May 2005 Posts: 10818 Location: The Peoples Republic of California
|
Posted: Tue 21 Jun 2011, 08:42 Post subject:
|
|
| Karl Godt wrote: |
And of course man mount works for Puppy mount , because it uses the mount command .
But perhaps the '-n' option only works on a regular file , and not to a link to /proc/mounts . |
Puppy's mount command is a script and doesn't behave like the mount binary utility. In this particular case it passes the -n switch to ntfs-3g. The -n switch is an invalid parameter for ntfs-3g and you get the following error message.
| Quote: | | In 2009 someone reported (version unknown) that attempting to mount an NTFS partition resulted in an 'unknown option -n' error. |
If one replaces the script with the binary, no more error message and it works.
~
_________________ New! Puppy Linux Links Page
|
|
Back to top
|
|
 |
Bruce B

Joined: 18 May 2005 Posts: 10818 Location: The Peoples Republic of California
|
Posted: Tue 21 Jun 2011, 08:45 Post subject:
|
|
| Karl Godt wrote: | | Furthermost I want to add , that the mount script had not changed from pup430 to luci254 , which I think had been the third last release candidate for 525 . |
That is quite likely but apart from the problem.
The behavior is demonstrable. Did you test it?
~
_________________ New! Puppy Linux Links Page
|
|
Back to top
|
|
 |
Karl Godt

Joined: 20 Jun 2010 Posts: 2689 Location: Kiel,Germany
|
Posted: Tue 21 Jun 2011, 11:38 Post subject:
|
|
I used diff command and no output , so they are equal .
I have put some echo into the mount script and functions4puppy4 here @MacPup_F3
and
| Code: | | mount -n -t ntfs /dev/sda4 /mnt/sda4 |
returned OK : | Quote: | $@ =-n -t ntfs /dev/sda4 /mnt/sda4
$1 =-n
$2 =-t
$3 =ntfs
$4 =/dev/sda4
$5 =/mnt/sda4
$6 =
$7 =
$8 =
$9 =
home=/root
CMDPRMS=/dev/sda4 /mnt/sda4
ntfs-3g$RETVAL=0
ntfs-3g_after_check_error_code$RETVAL=0
final$RETVAL=0
$DISPLAY =:0.0
$DEVNAME =sda4
DRVNAME =sda
xDRVNAME =sda
DRVNAME =sda4
/root/.pup_event/derive_sda4 exists
dnPATTERN=/dev/sda| DRV_CATEGORY=drive
starting icon_mounted_func ...
icon_mounted_func BEGIN
1: sda4 2: drive 3:
line 100 DRVICON drive_mntd48.png
line 102 imPATTERN ^/dev/sda4
line 104 now finding the boot partition
... returned from icon mounted func
finishing now /bin/mount ...
$RETVAL=0
.../bin/mount finished |
actually there is a
| Quote: | | #screen out all the options... |
by
| Quote: | | CMDPRMS="`echo -n "$*" | tr '\t' ' ' | tr -s ' ' | tr ' ' '\n' | grep '^/' | tr '\n' ' '`" |
so everything not starting with '/' like '/dev/sda4' and '/mnt/sda4' gets eliminated
before
| Quote: | | ntfs-3g $CMDPRMS -o umask=0,no_def_opts 2>/tmp/ntfsmnterr${MYPID}.txt |
and /tmp/ntfsmnterr is empty .
So any option you pass to puppy mount script attempting to mount a ntfs fs gets lost and replaced by the standard option you find in there .
But the mount-FULL binary seems to do the job to mount ntfs also by calling directly
| Code: | | mount-FULL -n -o ro /dev/sda4 /mnt/sda4 |
and mounts also 'ro' , but of course the mount ball does not appear on the drive icon .
I don't know if mount-FULL uses ntfs-3g like ntfsmount uses mount .
The ntfs-3g -V on MacPup_F3 is "ntfs-3g 2009.4.4 integrated FUSE 27" and on 511 "ntfs-3g 2010.1.16 integrated FUSE 27" and works also on on Glibc-2.6.1 but
Puppy 52er ntfs-3g needs Glibc>=2.7 and does not work on 4series , but so I cant test this further , but mount-FULL is everywhere the same version and works on 4series .
I would try to get rid of the 52 ntfs-3g and its libs and replace it with 511 ntfs-3g .
If you are only applying frugal installs you can leave /bin/df as it is , but for full installations the `rdev` substitution for /dev/root might be necessary .
|
|
Back to top
|
|
 |
Karl Godt

Joined: 20 Jun 2010 Posts: 2689 Location: Kiel,Germany
|
Posted: Tue 21 Jun 2011, 12:29 Post subject:
|
|
another type of code might be
| Code: | mount -a -t ntfs
mount -a -t ext2
mount -a -t ext3 |
because the Puppy mount script only runs ntfs-3g if it finds the exact term 'ntfs' in "$@" , otherwise it would run mount-FULL , which works with the '-n' option but calling directly ntfs-3g -n /dev/sda4 /mnt/sda4 does not work , but the mount script takes care to delete anything else than starting with '/' from "$@"|"$*" before calling ntfs-3g .
To me it seems to be a bug of the newer ntfs-3g , might have changed the reading of the fstab file .
And googling throw up this page:
ntfs-3g does not respect fstab options
with some fstab examples for the option 'user' and setuids and correct blkid , maybe there is a problem with the LOCALE ...
|
|
Back to top
|
|
 |
Bruce B

Joined: 18 May 2005 Posts: 10818 Location: The Peoples Republic of California
|
Posted: Tue 21 Jun 2011, 14:32 Post subject:
|
|
Karl Godt,
You can theorize and speculate.
I'm doing hands on testing.
There is a huge difference in procedure. Do you want it to work in theory or in reality?
In terms of this specific bug request (turned help request), MikeF can test your theories. He can test my actual results.
If MikeF is willing to use his keyboard, and I suppose it will be, let him report results from my tests and your theories.
Unless you have a better idea
Bruce
~
_________________ New! Puppy Linux Links Page
|
|
Back to top
|
|
 |
Bruce B

Joined: 18 May 2005 Posts: 10818 Location: The Peoples Republic of California
|
Posted: Tue 21 Jun 2011, 14:43 Post subject:
|
|
Karl Godt
The code you posted below, doesn't apply to the topic title or MikeF's complaint. Or the bug I validated.
| Code: | | mount-FULL -n -o ro /dev/sda4 /mnt/sda4 |
What is in discussion is fstab mounting particular to ntfs and the bug.
Bruce
~
_________________ New! Puppy Linux Links Page
|
|
Back to top
|
|
 |
Karl Godt

Joined: 20 Jun 2010 Posts: 2689 Location: Kiel,Germany
|
Posted: Tue 21 Jun 2011, 19:13 Post subject:
|
|
The OP posted : | Quote: |
BTW I just discovered that mount from the command line will not mount NTFS partitions r/o - it ignores that option and mounts them r/w anyway. Sigh. | Can't imagine anything else than an old , dying HD .
| Quote: | | In 2009 someone reported (version unknown) that attempting to mount an NTFS partition resulted in an 'unknown option -n' error. | The link would be fine also .
Bruce posted : | Quote: |
mount is probably a script. open it and see if you can see where the odd -n option error is originating from and how it originates | The '-n' option should not do anything because it has something to do with /etc/mtab and not with /etc/fstab . "mount-FULL -n -a" should mount ntfs correctly , as "busybox mount -n -a"
FSTAB entry 1 :
/dev/sda4 /mnt/sda4 ntfs ro 0 1
mount-FULL -n -a : OK and ro
busybox mount -n -a : OK and ro
mount : OK and ro
FSTAB entry 2 :
/dev/sda4 /mnt/sda4 ntfs-3g ro 0 1
mount-FULL -n -a : ntfs-3g: Unknown option '-n'.
busybox mount -n -a : OK , but rw
mount : ntfs-3g: Unknown option '-n'.
So it seems , that mount-FULL uses the ntfs-3g binary if fs is ntfs-3g in fstab , as Bruce suggests , simply ntfs does not call for ntfs-3g by mount-FULL .
FSTAB entry 3 :
/dev/sda4 /mnt/sda4 auto ro 0 1
mount-FULL -n -a : OK , and ro
busybox mount -n -a : OK , and ro
mount : OK , and ro
Other fs=vfat|msdos gave mount error .
Mike posted : | Quote: |
/dev/sda7 /temp ntfs ro 0 0 | normally it should work , I can also imagine a typo '?/temp:/tmp' , maybe the directory /temp does not exists or should exist as /mnt/temp
| Quote: |
/dev/sr0 /cd auto ro,noauto 0 0
Also, the optical drive mount is a null action - nothing happens.
When I use pmount or the mount command line, everything works fine. | Here also : fresh install , forgotten to create the dir /cd but fixed fstab or no medium inserted .
Because I don't know where the "mount -a" command starts from ( possibilities : /etc/rc.d/rc.sysinit.local || /root/Startup ) I would suggest something like | Code: | | mount -a 2>/tmp/mount_a.err | to get more information . If you start "mount -a" from the Startup folder , take a look into /tmp/xerrs.log .
|
|
Back to top
|
|
 |
Karl Godt

Joined: 20 Jun 2010 Posts: 2689 Location: Kiel,Germany
|
Posted: Tue 21 Jun 2011, 19:43 Post subject:
|
|
And make sure , that the fuse module is loaded
It appears , that there is a 'cuse.ko' in luci_254.sfs/lib/modules/2.6.33.2/kernel/fs/fuse/ folder but no fuse.ko
CONFIG_CUSE:
This FUSE extension allows character devices to be
implemented in userspace.
CONFIG_FUSE_FS:
With FUSE it is possible to implement a fully functional filesystem
in a userspace program.
grep -i -E 'fuse|cuse|ntfs|vfat|msdos' /mnt/+mnt++mnt+sda9+ISOs+puppy5+luci-254.iso+luci_254.sfs/etc/modules/DOTconfig-k2.6.33.2-27MAY2010-LUPU-SMP-TICKLESS
CONFIG_FUSE_FS=m
CONFIG_CUSE=m
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y
CONFIG_AUFS_BR_FUSE=y
CONFIG_MSDOS_PARTITION=y
cuse.ko had not been part of the standard puppy 4series but fuse.ko is and both modules are in 511 but while trying to trim the .iso down to 128MB some "exotic" drivers had been taken out of /lib/modules in 52 .
|
|
Back to top
|
|
 |
Bruce B

Joined: 18 May 2005 Posts: 10818 Location: The Peoples Republic of California
|
Posted: Tue 21 Jun 2011, 21:24 Post subject:
|
|
Karl Godt,
Your ideas and theories serve to show your ideas and theories are silly.
You have not shown a sound testing method.
It is easy to test, why haven't you?
Bruce
~
_________________ New! Puppy Linux Links Page
|
|
Back to top
|
|
 |
Karl Godt

Joined: 20 Jun 2010 Posts: 2689 Location: Kiel,Germany
|
Posted: Wed 22 Jun 2011, 03:33 Post subject:
|
|
With all respect , but now you become kind of "to be stuck up" to say in kind words .
About the fuse module :
| Quote: |
or the FUSE kernel driver must be upgraded to a safe version which is also included in the FUSE package for Linux kernel version 2.6.9 and later. |
from the FAQ page of ntfs-3g .
| Quote: |
New: Built-in FUSE support by using a stripped down, integrated FUSE library. Linux uses this by default which means NTFS-3G doesn’t require the installation of the FUSE package, only FUSE kernel support. |
http://www.tuxera.com/community/release-history/
| Quote: |
You have not shown a sound testing method. |
No comment !
|
|
Back to top
|
|
 |
Bruce B

Joined: 18 May 2005 Posts: 10818 Location: The Peoples Republic of California
|
Posted: Wed 22 Jun 2011, 04:42 Post subject:
|
|
Karl,
| Quote: | | With all respect , but now you become kind of "to be stuck up" to say in kind words |
Not stuck up. I am no longer willing to humor you.
The bug is validated exactly as described by MikeF. I've raised the bar on you by attaching a screen shot, a picture of the bug in action. You can see it in the same post I validated the bug
Click Here For Picture
Bruce
~
_________________ New! Puppy Linux Links Page
|
|
Back to top
|
|
 |
Karl Godt

Joined: 20 Jun 2010 Posts: 2689 Location: Kiel,Germany
|
Posted: Wed 22 Jun 2011, 05:16 Post subject:
|
|
I am guessing you have ntfs-3g set as fs and not ntfs ??
Without the fstab entry the screen shot is worthless !
|
|
Back to top
|
|
 |
Bruce B

Joined: 18 May 2005 Posts: 10818 Location: The Peoples Republic of California
|
Posted: Wed 22 Jun 2011, 05:20 Post subject:
|
|
| Karl Godt wrote: | I am guessing you have ntfs-3g set as fs and not ntfs ??
Without the fstab entry the screen shot is worthless ! |
Post after post and you have not demonstrated enough technical expertise to isolate it, identify it or validate it. You haven't come close.
Why refute it?
~
_________________ New! Puppy Linux Links Page
|
|
Back to top
|
|
 |
Karl Godt

Joined: 20 Jun 2010 Posts: 2689 Location: Kiel,Germany
|
Posted: Wed 22 Jun 2011, 07:02 Post subject:
|
|
Fresch frugal install of
Lucid Puppy 254 PUPMODE=5
the fuse.ko is inside the initrd.gz and should be cp to full installs by
grep -n '/initrd' `which puppyinstaller`
1366: if [ -d /lib/modules/$KERNELVER/initrd ];then
1368: cp -af /lib/modules/$KERNELVER/initrd/* $DESTMNTPT/lib/modules/$KERNELVER/
it is loaded automatically here .
these fstab entries don't work for me :
#/dev/sda4 /mnt/sda4 ntfs ro 0 1
#/dev/sda4 /mnt/sda4 ntfs-3g ro 0 1
mount-FULL calling ntfs-3g with the -n option
busybox_v1.16.2 busybox mount -: no such device , though /dev/sda4 seems to be correct :
brw-r--r-- 1 root root 8, 4 2001-02-13 21:43 /dev/sda4
but this does :
/dev/sda4 /mnt/sda4 auto ro 0 1
to mount -n -a , mount-FULL -n -a , mount /dev/sda4 , mount /mnt/sda4 , busybox mount -n -a
sucessfully the ntfs partition .
And because of wrong '/bin/df' /tmp/xerrs.log gets spammed by 'pup_event_frontend_d' with
"ash: 713: unknown operand" , which stands for availabble tmpfs of 713MB , so
the df-script is also essential for frugal installs to reduce the output of grep '/' to only one line .
The df thing seems not to affect the mount script at all though it is used by the
'icon_mounted_func' .
At all it seems to be a simply 'auto' for the fs in fstab and perhaps delete the 'noauto' from the cd line .
|
|
Back to top
|
|
 |
|