| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
now uses the sources found there.
|
|
|
|
|
|
|
|
| |
- IP addresses are verified as being correct dotted quad format.
- Netmasks are verified as being in correct dotted quad or 0x* format,
and being consecutive 1 bits followed by consecutive 0 bits.
- The gateway is verified as being correct dotted quad format and
being reachable through the configured IP address and netmask.
|
|
|
|
|
|
| |
no as a default. Sysinstall should be both less dangerous and less
annoying as a result of this change, though that's just my opinion
(since they're the defaults which annoy ME the least :).
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Previously, you could only script these features if you said YES.
Oops. Accidentally commited to releng_4 first.
PR: 20334
Approved by: jkh
|
|
|
|
| |
Reported by: Brian J. McGovern <mcgovern@spoon.beta.com>
|
|
|
|
|
|
|
|
|
|
|
| |
IPv6 configuration is only done by rtsol. Does someone really
need manual configuration? :-)
You can specify IPv6 DNS server as well.
We have only one server ftp7.jp.freebsd.org that speaks IPv6
in this time. ftp7.jp speaks IPv4 as well and also listed as
Japan #7.
Approved by: jkh
|
|
|
|
|
|
| |
the network -> interfaces menu.
Approved by: jkh
|
|
|
|
| |
it was a feature.
|
|
|
|
| |
values set by dhcp.
|
| |
|
|
|
|
|
| |
longer to give the user something to look at while things are happening.
Change it to do so and insert the appropriate screen saves elsewhere.
|
|
|
|
|
|
|
|
|
|
|
|
| |
as redoing all the menus to have proper, or at least non-hallucinogenic,
keyboard accelerators.
This requires my recent update to libdialog to work properly and will
probably also exhibit some other "interesting" behavior while the last
few missing screen clears are found (which is why I'm not going to MFC
immediately). At least now, however, sysinstall does not gratuitously
redraw random screens at the drop of a hat and drive serial console
installers out of their minds.
|
|
|
|
|
| |
display to boot. Also fix some various warning fluff while I'm in
here cleaning up.
|
|
|
|
|
| |
PR: 14706
Submitted by: ru
|
|
|
|
|
|
| |
do its job and not override it when set.
Submitted by: Ruslan Ermilov <ru@FreeBSD.org>
|
| |
|
|
|
|
|
|
| |
to crack the K&R; I must have forgotten the C language. :)
Embarrassingly noticed by: Howard Gutch <logix@foobar.franken.de>
|
| |
|
|
|
|
|
| |
long enough (and doing it multiple times results in a dialog which waits
AGES to complete).
|
|
|
|
|
|
|
|
|
|
| |
I backed-out the changes in -current and didn't touch stable at all (I
thought I had my patch order reversed, not what actually happened).
AIEEE! I can't even blame the crack for this one since I broke my
crack pipe a few weeks ago. I think sleep deprivation gets the blame
for this one.
Medal for noticing this one goes to: Jim Bloom <bloom@acm.org>
|
|
|
|
|
|
|
| |
bringing in DHCP support. The only thing I left out were Poul-Henning's
newfs changes since I'm not sure if he's brought the rest of that support
into -stable yet. If it turns out that this is the case, I'll MFC those
changes too.
|
| |
|
|
|
|
| |
the DHCP support code.
|
|
|
|
|
| |
in GENERIC. Now a dhcp-configured system will both install and boot
initially with proper interface configuration.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ifconfig, essentially stealing the lease until the user goes and changes
it. The alternative, sadly, is total dysfunction since bpf isn't in
GENERIC and network connectivity would otherwise fail completely on first
bootup when DHCP configuration was attempted again.
The ultimate answer here is to make either bpf a loadable kernel module
(which security conscious admins will be able to simply remove from /modules)
or come up with a lighter weight mechanism just for dhcp and other apps that
need to see broadcast packets but not otherwise sniff the wire in full
bpf glory.
|
|
|
|
| |
Submitted by: obrien
|
| |
|
|
|
|
|
|
|
|
| |
in some code from C. Stone to parse the lease information. This is still
a WIP and this commit is largely intended to allow others to sync up; the
dhclient code still only works when doing dhcp configuration post-install
and requires a bit more work on the boot floppy before it will truly
work in the minimal bootstrapping role.
|
| |
|
| |
|
|
|
|
|
|
| |
for the time being) for debugging purposes.
Fix bug in options selection.
|
| |
|
|
|
|
| |
of values more than once. User might want to override them.
|
|
|
|
| |
Disable the non-working dhcp client code I just committed by mistake.
|
|
|
|
|
|
| |
which is why I didn't see this. :)
Noted by: Maxim Sobolev <sobomax@altavista.net>
|
|
|
|
|
|
|
|
| |
Now we know which variables are internal and which need to be
backed to /etc/rc.conf.site. rc.conf is not touched now.
Also kget kernel change information back properly and set up a loader.rc
file to use it.
|
|
|
|
|
|
|
|
| |
o Move fixups into extraction routine so all consumers don't have to duplicate
the right behavior.
o Make some things more orthogonal (just for asthetics sake)
o Add option to go back and do it again if XF86Setup fails (possibly with
a different setup - this one has always annoyed me).
|
| |
|
|
|
|
|
| |
of these magic knobs. This is purely cosmetic and a documentation issue
so we don't have to glop through the source code looking for gems.
|
|
|
|
|
|
| |
setup dialog from scripts is more controllable. No more biasing off of
hostname (which is now non-optional in the non-netInteractive case).
Requested by: pst
|
|
|
|
|
| |
Add and document new loadConfig function (sort of like a script #include).
Make TCP/IP setup far less chatty when it doesn't need to be.
|
|
|
|
| |
2. If hostname not set from script, bring up interactive dialog anyway.
|
| |
|
| |
|
|
|
|
| |
2. Update to XFree86 3.3
|
|
|
|
| |
puppies.
|
| |
|