search for: int_opt

...9 insertions(+) diff --git a/usr/kinit/nfsmount/main.c b/usr/kinit/nfsmount/main.c index 36b29a5f..cca9e4ec 100644 --- a/usr/kinit/nfsmount/main.c +++ b/usr/kinit/nfsmount/main.c @@ -36,12 +36,15 @@ static struct nfs_mount_data mount_data = { }; int nfs_port; +int nfs_version; static struct int_opts { char *name; int *val; } int_opts[] = { {"port", &nfs_port}, + {"nfsvers", &nfs_version}, + {"vers", &nfs_version}, {"rsize", &mount_data.rsize}, {"wsize", &mount_data.wsize}, {"timeo", &mount_data.ti...

...19 insertions(+) diff --git a/usr/kinit/nfsmount/main.c b/usr/kinit/nfsmount/main.c index 36b29a5..cca9e4e 100644 --- a/usr/kinit/nfsmount/main.c +++ b/usr/kinit/nfsmount/main.c @@ -36,12 +36,15 @@ static struct nfs_mount_data mount_data = { }; int nfs_port; +int nfs_version; static struct int_opts { char *name; int *val; } int_opts[] = { {"port", &nfs_port}, + {"nfsvers", &nfs_version}, + {"vers", &nfs_version}, {"rsize", &mount_data.rsize}, {"wsize", &mount_data.wsize}, {"timeo", &mount_data.ti...

Hey folks; I have been happily using shorewall for quite some time so this problem _may_ not be easy to resolve but I am interested in any information regarding your experience with the same setup. I was using FC3 with shorewall 2.2.3 and two NICs setup as a bridge without any issue until I upgraded to FC4. My production system would pass traffic through the bridge but local usage would not

Various coding style fixes checkpatch warns about. The goal is not to be 100% checkpatch compliant, but to have more consistent coding style. As this is a trivial patch serie, will land in 24 hours in klibc git, unless of course ml review hits a bugger. Checked with size(3) that the generated kinit, fstype, ipconfig and nfsmount are the same. maximilian attems (4): [klibc] ipconfig: reduce