* Robert Thoelen III <[EMAIL PROTECTED]> [020116 11:29] wrote:
> Sorry about the previous empty post. I am trying
> create a filesystem on a server running FreeBSD at
> work. I would like to create a floppy that would
> mount the filesystem by NFS. This way, on any given
> machine at work, I co
On Wed, Jan 16, 2002 at 11:29:25AM -0800, Robert Thoelen III wrote:
> Sorry about the previous empty post. I am trying
> create a filesystem on a server running FreeBSD at
> work. I would like to create a floppy that would
> mount the filesystem by NFS. This way, on any given
> machine at work,
Sorry about the previous empty post. I am trying
create a filesystem on a server running FreeBSD at
work. I would like to create a floppy that would
mount the filesystem by NFS. This way, on any given
machine at work, I could put the floppy in and turn it
into a BSD workstation, without manipul
> In message <[EMAIL PROTECTED]>, Doug Ambrisko writes:
> >| to the kernel's output. I had a look at the pxe code in
> >| /sys/boot/i386/libi386/pxe.c where pxeboot is built from and in
> >| /sys/i386/i386/autoconf.c which is the kernel side and it looks like
> >| they don't do anything about swap
In message <[EMAIL PROTECTED]>, Doug Ambrisko writes:
>| to the kernel's output. I had a look at the pxe code in
>| /sys/boot/i386/libi386/pxe.c where pxeboot is built from and in
>| /sys/i386/i386/autoconf.c which is the kernel side and it looks like
>| they don't do anything about swap. There is
John Hay writes:
| > | > You don't, it is done via the bootp or dhcp record option 128 for example
| > | > option option-128 "192.168.2.254:/usr/work/netboot";
| > | > You then have to make the swap file in that directory of format
| > | > swap.
| > | > Use dd to create the file by
> Yes, you are right. Putting the ip number in the root-path cures the
> pxeboot failure. But is still only configure the NFS ROOT according
> to the kernel's output. I had a look at the pxe code in
> /sys/boot/i386/libi386/pxe.c where pxeboot is built from and in
> /sys/i386/i386/autoconf.c which
> | > You don't, it is done via the bootp or dhcp record option 128 for example
> | > option option-128 "192.168.2.254:/usr/work/netboot";
> | > You then have to make the swap file in that directory of format
> | > swap.
> | > Use dd to create the file by copying /dev/zero for the
John Hay writes:
| > You don't, it is done via the bootp or dhcp record option 128 for example
| > option option-128 "192.168.2.254:/usr/work/netboot";
| > You then have to make the swap file in that directory of format
| > swap.
| > Use dd to create the file by copying /dev/zero f
In message <[EMAIL PROTECTED]>you write:
} [...]
}The option-128 confuse the pxeboot program. If I put
}
}option root-path "/export/diskless";
}option option-128 "10.1.2.3:/export/shark";
}
}in the dhcpd.conf file, pxeboot tries to mount /export/sharkM-^[^B-i=FF
}as the root filesystem. Removing t
On Nov 04, John Hay wrote:
> > John Hay writes:
> > | > > the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
> > | > > enough, so im trying to look into defining a FBSDclass ala PXEClient, and
> > | > > supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
> > |
> John Hay writes:
> | > > the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
> | > > enough, so im trying to look into defining a FBSDclass ala PXEClient, and
> | > > supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
> | >
> | > You don't need those; you c
John Hay writes:
| > > the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
| > > enough, so im trying to look into defining a FBSDclass ala PXEClient, and
| > > supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
| >
| > You don't need those; you can get them
> > the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
> > enough, so im trying to look into defining a FBSDclass ala PXEClient, and
> > supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
>
> You don't need those; you can get them out of /etc/fstab. In part
[..]
Sorry, can please anyone explain to me how the setup for etherboot is ?
Have I to boot the kernel or the loader ?
I have botting an kernel now but it asks nicely for the rootdevice;
I've setup dhcpd like explained before in this thread.
TIA
Holm
--
FreibergNet Systemhaus GbR Holm Tif
> }> what's in a name ;-)
> }> the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
> }> enough, so im trying to look into defining a FBSDclass ala PXEClient, and
> }> supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
> }
>
> ok, so now i can setenv(dhc.xxx,
Danny Braniss ([EMAIL PROTECTED]) wrote:
> In message <[EMAIL PROTECTED]>you write:
> }Danny Braniss ([EMAIL PROTECTED]) wrote:
> }> ok, so now i can setenv(dhc.xxx, val).
> }>
> }> I would very much like to make them available as sysctl dhcp.xxx, the only
> }> problem, is that the sysctl interfa
In message <[EMAIL PROTECTED]>you write:
}Danny Braniss ([EMAIL PROTECTED]) wrote:
}> ok, so now i can setenv(dhc.xxx, val).
}>
}> I would very much like to make them available as sysctl dhcp.xxx, the only
}> problem, is that the sysctl interface is prety much static, so has anybody
}> lookeed in
Danny Braniss ([EMAIL PROTECTED]) wrote:
> ok, so now i can setenv(dhc.xxx, val).
>
> I would very much like to make them available as sysctl dhcp.xxx, the only
> problem, is that the sysctl interface is prety much static, so has anybody
> lookeed into making it 'dynamic'?, ie: malloc'ing structs
In message <[EMAIL PROTECTED]>you write:
}> In message <[EMAIL PROTECTED]>you write:
}>
}> }Mostly I guess I'd really like it to simply save *all* of the DHCP
}> }response in the environment. Just "dhcp.xxx" where xxx is the parameter
}> }value would probably do it, or we can argue about names
:You can specify swap paritions with dhcpd just fine, just use
:the the numerical IP:
:
:option root-path "999.999.99.99:/";
:option option-128 "999.999.99.99:/images/swap";
:
: -Matt
You know, my written english is getting *really
:> In message <[EMAIL PROTECTED]>you write:
:>
:> }Mostly I guess I'd really like it to simply save *all* of the DHCP
:> }response in the environment. Just "dhcp.xxx" where xxx is the parameter
:> }value would probably do it, or we can argue about names for everything if
:> }there aren't esta
In message <[EMAIL PROTECTED]>you write:
}> In message <[EMAIL PROTECTED]>you write:
}>
}> }Mostly I guess I'd really like it to simply save *all* of the DHCP
}> }response in the environment. Just "dhcp.xxx" where xxx is the parameter
}> }value would probably do it, or we can argue about names
> In message <[EMAIL PROTECTED]>you write:
>
> }Mostly I guess I'd really like it to simply save *all* of the DHCP
> }response in the environment. Just "dhcp.xxx" where xxx is the parameter
> }value would probably do it, or we can argue about names for everything if
> }there aren't establishe
I think this is correct, actually. Danny, can you confirm that you're
using one of the class A address spaces (eg. 10.*.*.*?)
Actually, IMO the code around this is entirely wrong; we should always
respect the mask supplied by the server, and only use the canonical mask
if we don't get one at
> In message <[EMAIL PROTECTED]>you write:
> }
> }I think this is correct, actually. Danny, can you confirm that you're
> }using one of the class A address spaces (eg. 10.*.*.*?)
> }
> my net is class B. 132.65.0.0
Gotcha. What's your netmask? I bet it disagrees one way or the other
with the
> }> }I think this is correct, actually. Danny, can you confirm that you're
> }> }using one of the class A address spaces (eg. 10.*.*.*?)
> }> }
> }> my net is class B. 132.65.0.0
> }
> }Gotcha. What's your netmask? I bet it disagrees one way or the other
> }with the "canonical" netmask this c
> Mike Smith ([EMAIL PROTECTED]) wrote:
> >
> > I think this is correct, actually. Danny, can you confirm that you're
> > using one of the class A address spaces (eg. 10.*.*.*?)
> >
> > Actually, IMO the code around this is entirely wrong; we should always
> > respect the mask supplied by the
if i mount a fs with nfs/v3 all is fine.
loo# ls -ls /net/nafs-tmp/vol1/roots/fbsd-4.1S/dev/null
0 crw-rw-rw- 1 root wheel2, 2 Sep 20 14:33
/net/nafs-tmp/vol1/roots/fbsd-4.1S/dev/null
but if i mount the same fs with nfs/v2 all is 'almost' ok :-(
the special files have a wee-little-probl
In message <[EMAIL PROTECTED]>you write:
}Mostly I guess I'd really like it to simply save *all* of the DHCP
}response in the environment. Just "dhcp.xxx" where xxx is the parameter
}value would probably do it, or we can argue about names for everything if
}there aren't established names alre
Mike Smith ([EMAIL PROTECTED]) wrote:
>
> I think this is correct, actually. Danny, can you confirm that you're
> using one of the class A address spaces (eg. 10.*.*.*?)
>
> Actually, IMO the code around this is entirely wrong; we should always
> respect the mask supplied by the server, and on
In message <[EMAIL PROTECTED]>you write:
}> In message <[EMAIL PROTECTED]>you write:
}> }
}> }I think this is correct, actually. Danny, can you confirm that you're
}> }using one of the class A address spaces (eg. 10.*.*.*?)
}> }
}> my net is class B. 132.65.0.0
}
}Gotcha. What's your netmask? I
In message <[EMAIL PROTECTED]>you write:
}
}I think this is correct, actually. Danny, can you confirm that you're
}using one of the class A address spaces (eg. 10.*.*.*?)
}
my net is class B. 132.65.0.0
}Actually, IMO the code around this is entirely wrong; we should always
}respect the mask su
Danny Braniss ([EMAIL PROTECTED]) wrote:
> i still think that this part of code is useless. why overwride the
> info supplied by dhcp? if it's wrong then the dhcpd.conf should be
> fixed or some message printed. at the moment, bootp silently ignores
> some info it conciders wrong - wrongly :-)
T
In message <[EMAIL PROTECTED]>you write:
}Matt Dillon ([EMAIL PROTECTED]) wrote:
}> A quick review of the code seems to indicate that this is indeed a bug.
}> As far as I can tell, the IN_CLASS*() macros assume host order. e.g.
}> from /usr/include/netinet/in.h:
}>
}> #define IN_
Matt Dillon ([EMAIL PROTECTED]) wrote:
> A quick review of the code seems to indicate that this is indeed a bug.
> As far as I can tell, the IN_CLASS*() macros assume host order. e.g.
> from /usr/include/netinet/in.h:
>
> #define IN_CLASSA(i)(((u_int32_t)(i) & 0x8
A quick review of the code seems to indicate that this is indeed a bug.
As far as I can tell, the IN_CLASS*() macros assume host order. e.g.
from /usr/include/netinet/in.h:
#define IN_CLASSA(i)(((u_int32_t)(i) & 0x8000) == 0)
Since s_addr is in network byte o
Umm.. I'm using the netboot just fine here for the ports cluster and
it is using the code in the tree w/ zero modifications. It boots via
nfs and comes up with ip, netmask, and gateway.
paul
Danny Braniss ([EMAIL PROTECTED]) wrote:
> bug report:
> in lib/libstand/bootp.c:
>
> if (
bug report:
in lib/libstand/bootp.c:
if (IN_CLASSA(myip.s_addr))
nmask = htonl(IN_CLASSA_NET);
else if (IN_CLASSB(myip.s_addr))
nmask = htonl(IN_CLASSB_NET);
else
nmask = htonl(IN_CLASSC_NET);
should be:
if (
> Mike Smith wrote:
> >
> > > ok, once i compiled a kernel with options BOOTP things got better ;-)
> > > it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs)
> > > but after it re-configures the ethernet, the ethernet stops working!
> > >
> > > ponters anyone?
> >
> > You ca
Paul Saab ([EMAIL PROTECTED]) wrote:
> Chris Csanady ([EMAIL PROTECTED]) wrote:
> > Has this actually been merged to -stable yet? I can't find anything that
> > actually reads the boot.nfsroot.* loader variables.
>
> Yes.. it was done more than a week ago.
Ugh.. I could have sworn I MFC'd this
Chris Csanady ([EMAIL PROTECTED]) wrote:
> Has this actually been merged to -stable yet? I can't find anything that
> actually reads the boot.nfsroot.* loader variables.
Yes.. it was done more than a week ago.
--
Paul Saab
Technical Yahoo
[EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTE
In message <[EMAIL PROTECTED]>you write:
}Mike Smith wrote:
}>
}> > ok, once i compiled a kernel with options BOOTP things got better ;-)
}> > it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs)
}> > but after it re-configures the ethernet, the ethernet stops working!
}> >
}>
Mike Smith wrote:
>
> > ok, once i compiled a kernel with options BOOTP things got better ;-)
> > it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs)
> > but after it re-configures the ethernet, the ethernet stops working!
> >
> > ponters anyone?
>
> You can't run dhclient (
Danny Braniss ([EMAIL PROTECTED]) wrote:
> if by -stable you mean whatever i get when i do a 'cvs co -rRELENG_4' src/sys
> then there are some things missing.
> i386/i386/autoconf.c does not have the stuff for pxe.
> if i compile a kernel with the BOOTP_ stuff, then i can mount nfsroot, but
>
> if by -stable you mean whatever i get when i do a 'cvs co
> -rRELENG_4' src/sys
> then there are some things missing.
> i386/i386/autoconf.c does not have the stuff for pxe.
> if i compile a kernel with the BOOTP_ stuff, then i can mount
> nfsroot, but
> [mount_]mfs is broken, i get '
}In message <[EMAIL PROTECTED]>you write:
}}Danny Braniss ([EMAIL PROTECTED]) wrote:
}}> BTW, is someone working in passing all this stuff via dhcp? im trying to co
}m
}}e}}> up with an almost zero admin diskless ws solution.
}}
}}Yes, this has been done in current for a while and was back ported
In message <[EMAIL PROTECTED]>you write:
}If you're running -current or a very recent -stable, remove the 'BOOTP'
}options. The loader now passes all the DHCP information into the kernel.
}Then leave the interface configuration alone...
}
the 'problem' is in dhcpd, who refuses to send the host
On Sep 11, Mike Smith wrote:
> > ok, once i compiled a kernel with options BOOTP things got better ;-)
> > it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs)
> > but after it re-configures the ethernet, the ethernet stops working!
> >
> > ponters anyone?
>
> You can't run d
> ok, once i compiled a kernel with options BOOTP things got better ;-)
> it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs)
> but after it re-configures the ethernet, the ethernet stops working!
>
> ponters anyone?
You can't run dhclient (DHCP in any of the ifconfig lines
CTED]]
}}> Sent: maandag 11 september 2000 13:19
}}> To: Koster, K.J.
}}> Subject: Re: diskless workstation
}}>
}}>
}}> In message
}}> <[EMAIL PROTECTED]>you w
}}> rite:
}}> }Error message?
}}> }
}}>
}}> Interface xl0 IP-Address 132.65.80.251 Broadcast
}}
3:19
}> To: Koster, K.J.
}> Subject: Re: diskless workstation
}>
}>
}> In message
}> <[EMAIL PROTECTED]>you w
}> rite:
}> }Error message?
}> }
}>
}> Interface xl0 IP-Address 132.65.80.251 Broadcast
}> 132.65.255.255 (which is ok)
}> cp: /conf/defa
ok, once i compiled a kernel with options BOOTP things got better ;-)
it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs)
but after it re-configures the ethernet, the ethernet stops working!
ponters anyone?
danny
To Unsubscribe: send mail to [EMAIL PROTECTED]
w
The following excerpt from isc-dhcp3-3.0.b1.17's dhcpd.conf works for me:
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.193 192.168.1.208;
filename "/tftpboot/ringnet.kernel.fd0";
option root-path "192.168.1.2:/usr/n/ringrowl/root";
host ringrowl {
hardware ethernet 00:
hi,
i spent some time trying out diskless ws, using dhcp/pxe/tftp.
now im stuck after loadin the kernel - via nfs - and not finding the root
i tried putting 'host:/something/root/bar / nfs rw 0 0' in its fstab, and
the error i get is something like: bar device not found.
what magic am i missing?
Alright, so probably I'm missing something again, like in my previous
post about mounting different subdirs in a filesystem (btw thanks to
those who replied then, all replies have been most helpful).
So..
Is there a way to cleanly shutdown (or reboot) a NFS-rooted workstation?
rc.diskless2 MFS-m
This is a leftover from me trying a different Ethernet card. It does not
work without that lineI still get the same symptoms.
Thanks,
Dan Diephouse
Parag Patel wrote:
> On Sat, 12 Feb 2000 11:40:29 EST, Dan Diephouse wrote:
>
> >nebula:\
> >:tc=.default:\
> >:ha=b2
I have been trying to turn a 486 that I have into a diskless workstation
and have not gotten very far. I have compiled Etherboot, and set up the
server with tftp and bootp. I have both daemons enabled. When I boot
up the 486 machine tcpdump yields this:
[root:dragon]# tcpdump -i de0 -e
Hello
I'm trying to build new X terminals for my lab.
To do so I use FreeBSD 3.3-RELEASE.
The X terminal is a diskless PC with 64 Mo of ram. It perfectly boots
and I can launch the X server perfectly. Everything just runs fine.
Except for one little piece of thing.
As i wanted to mak
59 matches
Mail list logo
