Re: mountd: getfh failed: Operation not permitted
Stelios Parnassidis wrote: After upgrading to portmap 5-10 / 5-11 nfs mounting of some exported dirs fails while having well worked for some years now: two machines, 1. 'nero' exports some dirs; 2. 'oren' uses the same: machine 'nero' exports: # /etc/exports: the access control list for filesystems which may be exported # to NFS clients. See exports(5). # / *.localnet(sync,rw,nohide) # /ftp*.localnet(sync,rw,nohide) /ftp/deb*.localnet(sync,rw,nohide) # /ftp/cd/dvdrw *.localnet(sync,rw,nohide) # # /ftp on nero permissions: # ll -d /ftp dr-xr-xr-x 15 root root 4096 May 14 00:30 /ftp/ machine oren mounts: mount nero:/ftp/cd/dvdrw machine nero reports (syslog): May 14 00:23:56 nero mountd[639]: authenticated unmount request from oren:738 for /ftp/cd/dvdrw (/ftp/cd/dvdrw) this is ok then mount nero:/ftp machine nero reports (syslog) May 14 00:28:58 nero mountd[639]: authenticated mount request from oren:771 for /ftp (/ftp) May 14 00:28:58 nero mountd[639]: getfh failed: Operation not permitted More to this: I see a message from from exportfs: exporting oren:/ftp exporting oren:/ftp to kernel oren:/ftp: Invalid argument then after man reading i notice that due file file /var/lib/nfs/xtab has zero length, then i try manually exportfs -av and get the among normal messages for all expors again oren:/ftp: Invalid argument this time /var/lib/nfs/xtab has real content, except of course missin entry for oren:/ftp sp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
mountd: getfh failed: Operation not permitted
After upgrading to portmap 5-10 / 5-11 nfs mounting of some exported dirs fails while having well worked for some years now: two machines, 1. 'nero' exports some dirs; 2. 'oren' uses the same: machine 'nero' exports: # /etc/exports: the access control list for filesystems which may be exported # to NFS clients. See exports(5). # / *.localnet(sync,rw,nohide) # /ftp*.localnet(sync,rw,nohide) /ftp/deb*.localnet(sync,rw,nohide) # /ftp/cd/dvdrw *.localnet(sync,rw,nohide) # # /ftp on nero permissions: # ll -d /ftp dr-xr-xr-x 15 root root 4096 May 14 00:30 /ftp/ machine oren mounts: mount nero:/ftp/cd/dvdrw machine nero reports (syslog): May 14 00:23:56 nero mountd[639]: authenticated unmount request from oren:738 for /ftp/cd/dvdrw (/ftp/cd/dvdrw) this is ok then mount nero:/ftp machine nero reports (syslog) May 14 00:28:58 nero mountd[639]: authenticated mount request from oren:771 for /ftp (/ftp) May 14 00:28:58 nero mountd[639]: getfh failed: Operation not permitted Someone seeing what is wrong? thanks a lot -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: My 'h' key is unusable
Hi Daniel, I went home and had your hints ready to apply, but the, 'h' mystery DISAPPEARED, ... I keep your interesting hunting advise for the case, and thanks, I keep On Wed, 15 Jul 1998, Daniel Martin at cush wrote: > Stelios Parnassidis <[EMAIL PROTECTED]> writes: > > > Just had the base system installation of Hamm, and wanted > > to type 'which superformat'. 'h' beeps and beeps ... i have > > to type Ctrl-V h to use it. > > > > I looked into the /etc/terminfo/l/linux via ... (untic) > > could find nothing. > > > > What's wrong with my very 'h'? Heh? :( > > Could it be a missing backslash or caret in your /etc/inputrc? A > mis-quoted section of your bash initialization files? It sounds > almost as if bash is set to interpret "h" as "delete-next-character" > (something that people sometimes want the delete key to do; I can see > how on a poorly thought-out installation, one might want Control-h to > do this). See if "h" does indeed behave this way by typing some > stuff, backing up, and seeing if you can delete things with "h". > > To track down the problem, I'd suggest doing: (at the bash prompt) > bind -p | less > and inside less search for "h" (less doesn't use readline, so it > shouldn't be affected by the weird-h stuff). Then, I guess I'd look > at /etc/inputrc, ~/.inputrc, and the various bash initialization files > for anything that might be causing this. > Stelios Parnassidis | email: [EMAIL PROTECTED] -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
H Key is unusable, after base installation of hamm
Just had the base system installation of Hamm, and wanted
to type 'which superformat'. 'h' beeps and beeps ... i have
to type Ctrl-V h to use it.
I looked into the /etc/terminfo/l/linux via ... (untic)
could find nothing.
What's wrong with my very 'h'? Heh? :(
Stelios Parnassidis | email: [EMAIL PROTECTED]
MPE/IR - Garching | Giessenbachstr
85748 Garching - Germany| Tel: +49 (0)89 3299 3278
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
My 'h' key is unusable
Just had the base system installation of Hamm, and wanted to type 'which superformat'. 'h' beeps and beeps ... i have to type Ctrl-V h to use it. I looked into the /etc/terminfo/l/linux via ... (untic) could find nothing. What's wrong with my very 'h'? Heh? :( -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
posix procs: where is it gone ?
Is the old (?) ps, the one with the PS_PEERSONALITY setting, to find
under debian ?
I'm running/poerting a huge package related to my job, which rely
very heavy on the posix conform switches of 'ps'.
One of a sudden sometime ago nothing goes anymore because
in many cases system("ps -ef ... ) is used, and it must stay like
that... :(
Stelios Parnassidis
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
libstdc++ : unresolved ref... 'errno_location'
I'm boxing myself hard through same progs, written for HP and Solaris, many things in C++. I have somehow brought it to compile error-free, but then on calling the executables i get this unresolved 'errno_location'. Allthough i see it in a file, and realize it might have to do with threads, i cannot find out how it makes it in the compiled libraries - the ones i generate - why and where ... Please if it's a known problem don't blame, i need help .. Stelios Parnassidis | email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cfdisk: Cannot seek on disk drive
On Sat, 22 Mar 1997, Michael Iles wrote: [spip] referring to cfdisk w/ disks > 2G > > FATAL ERROR: Cannot seek on disk drive > After a suggestion on the BUG report system i have put the cast (ext2_loff_t) at two places in the source file. It seems to work now. Specialists please verify that this does not break anything else. diffcfdisk.c cfdisk.orig 396c396 < if (ext2_llseek(fd, (ext2_loff_t)sect_num*SECTOR_SIZE, SEEK_SET) < 0) --- > if (ext2_llseek(fd, sect_num*SECTOR_SIZE, SEEK_SET) < 0) 404c404 < if (ext2_llseek(fd, (ext2_loff_t)sect_num*SECTOR_SIZE, SEEK_SET) < 0) --- > if (ext2_llseek(fd, sect_num*SECTOR_SIZE, SEEK_SET) < 0) P.S. There is an attempt to correct this in the debian package util-linux, but it is unfortunately applied uneffectively: NIL: if (ext2_llseek(fd, (ext2_loff_t)(sect_num*SECTOR_SIZE), SEEK_SET) < 0) Stelios Parnassidis <[EMAIL PROTECTED]> Kapuzinerstr. 8, 80337 Muenchen, Germany, Tel. +49-089-7211505
how did you make it with the (still) broken cfdisk
It is my second week after having started with debian. I wanted to
taste what's it is like to have a 'stable' system running...
Anyway it's anything but stable but i'm still fighting.
I have also wondered from the very beginning, after having
carefully swallowed the install.html, how im heaven can
poeple go on with the first very important tool broken: cfdisk.
A big warning was there about my last chance to backup/ first
to sweep out my disk.
I had already partitioned the 3.1MB of the fireball, so i needed
only to change the type of a partition to swap. But the
install menu wanted then to patition the whole disk again.
Ok, i had to make it without swap.
Some days later i found my way to bug report system, for which
i can only express my respect. If only the maintainers would
do respectively serious work. I found the answer there but don't
know yet how to put it in the packaging system.
Sometime last November was a hint to repair the bug in cfdisk:
Subject: Re: Bug#5466: cfdisk is broken for disks >4GB
Solution: just as for fdisk:
On every call to ext2_llseek, cast the sector number to ext2_loff_t
And then:
Fixed in 2.5-8.
So i found the fix in util-linux_2.5-8.diff.gz and util-linux_2.5-9.diff.gz
which are what i have found to be the latest rex-fixed release.
in file cfdsik.c:
void read_sector(char *buffer, int sect_num)
{
-if (ext2_llseek(fd, sect_num*SECTOR_SIZE, SEEK_SET) < 0)
+if (ext2_llseek(fd, (ext2_loff_t)(sect_num*SECTOR_SIZE), SEEK_SET) < 0)
and
void write_sector(char *buffer, int sect_num)
{
-if (ext2_llseek(fd, sect_num*SECTOR_SIZE, SEEK_SET) < 0)
+if (ext2_llseek(fd, (ext2_loff_t)(sect_num*SECTOR_SIZE), SEEK_SET) < 0)
fatal(BAD_SEEK);
Of course for the cast it is too late:
the first suggestion was meaning : (ext2_loff_t)sect_num*SECTOR_SIZE
Well, i mean cfdisk is not a tooly. cfdisk should have been exaustively checked
before released.
Together with some other similar missings, this broke my hope i could rely on
the famous rocky solid debian.
RedHat has aldready lost my confidence. So i see i shall keep on with my own
hybrid installations (old good slackware, sigh :( ).
For the end, i have a lot of respect and thank for all the guys out there,
neverthe-
less i would like to remind that ten thousands of innocent users out there
are also a part of the process. ...
Stelios Parnassidis <[EMAIL PROTECTED]>
Kapuzinerstr. 8, 80337 Muenchen, Germany, Tel. +49-089-7211505
Re: rescue disk fails booting, cannot install ..
> > So the solution for me would be the download the compressed root image > of the rescue disk and rebuild a rescue disk using a kernel of my own. > In reply to my own question above: Thanks to a message of > From: Dale Scheetz <[EMAIL PROTECTED]> > Cc: debian-user@lists.debian.org > Subject: Re: Writing to a boot floppy. > If you mount the boot floppy that you created when you installed your > system (-t msdos) you will see that it contains various files. The file > named linux on the floppy is the kernel image file. When you rebuild your > kernel, you will find the new image file in linux/arch/i386/boot/zImage, I had not realized that the rescue disk has an msdos filesystem, so everything i need should be now clear. I should only have to put my own kernel on the floppy and go on. Sorry for the Bandwidth, cheers, stelios Stelios Parnassidis <[EMAIL PROTECTED]> Kapuzinerstr. 8, 80337 Muenchen, Germany, Tel. +49-089-7211505 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Writing to a boot floppy.
On Thu, 20 Feb 1997, Bob Clark wrote: > Make the target "zdisk" and you will have a boot floppy. > > Bubonic wrote: > > > > I recompiled my kernel today (without any major problems) to 2.027, > > however, I can't seem to figure out how to create a new boot floppy. I have > > tried: cp vmlinux /dev/fd0 to a DOS-formatted disk, but when I tried to > > reboot > > my computer, it didn't work. > > > > I assume that I am missing or forgetting something, but the books that I > > have > > and the FAQS and HOWTO's I have read have very little information on this. > > They tend to deal more with LILO, as opposed to booting off of a floppy. > > If you have access to the kernel sources, /usr/src/linux, then you may have a look at linux/Documentation/ramdisk.txt. It contains a nice, extensive story on how to build boot disks including compressed root images. Have fun Stelios Parnassidis <[EMAIL PROTECTED]> Kapuzinerstr. 8, 80337 Muenchen, Germany, Tel. +49-089-7211505 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
rescue disk fails booting, cannot install ..
I had just posted this to comp.os.linux.setup, as i found out of the debian-users list. so im sending it here too. Briefly : I concluded that to be able to install Debian on my machine i need to have a root.image file for the rescue disk which then i make up myself (with an own working kernel). Where can i get a Root Image for the installation please ? I set up the 7 installation diskettes and started with the rescue disk. It goes ok up to the point where the aix7xxx driver complains about missing BIOS32 extentions. It says that it still depends on it gives a panic not syncing message and hangs. My machine is an encient ISA/VLB motherboard w/ 486DX/2 and an adaptec 2842 scsi controller. I used to have big problems with the aic7xxx/2842, but some day in the past they stopped and since then up to my current kernel 2.0.28 it works fine. Only if i compile PCI extentions in my kernel - which i don't need of course - then it does not work. It is natural the universal boot kernel of the debian's rescue disk includes a PCI support, but this makes me very unhappy. So the solution for me would be the download the compressed root image of the rescue disk and rebuild a rescue disk using a kernel of my own. thanks for any help, stelios parnassidis -- Stelios Parnassidis <[EMAIL PROTECTED]> Kapuzinerstr. 8, 80337 Muenchen, Germany, Tel. +49-089-7211505 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
