8th July snapshot: bsdinstall not creating homedir
I've installed FreeBSD snapshots a couple of times this week. With Virtualbox 4.1 on both Windows and OS X with a 20GB disk I've found the installer forgets to create the homedir - /home doesn't exist, so when you get placed at / when logging in. Unfortunately pub.allbsd.org seems to be queued up so I've not been able to try any more recent snapshots (should the snapshot ISOs be labelled with -release.iso)? -- Bruce Cran___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 8th July snapshot: bsdinstall not creating homedir
Bruce Cran br...@cran.org.uk wrote in a23d9339-458e-4a2d-8bdc-4ef1d283f...@cran.org.uk: br I've installed FreeBSD snapshots a couple of times this week. With br Virtualbox 4.1 on both Windows and OS X with a 20GB disk I've found br the installer forgets to create the homedir - /home doesn't exist, so br when you get placed at / when logging in. Unfortunately br pub.allbsd.org seems to be queued up so I've not been able to try any br more recent snapshots (should the snapshot ISOs be labelled with br -release.iso)? Sorry, due to a hardware trouble on Saturday some of the snapshots had to be removed. It recovered already and generating ones as of July 21-24 now, FYI. -- Hiroki pgpY7YAUqjneU.pgp Description: PGP signature
No disks usable on a P5NE MB
Hi, Trying to upgrade one of my box from 8-stable to 9-current lead be to some important problems. I'm have tried both from sources (svn buildworld etc.) and from memdisk provided by allbsd.org. The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901 more informations here : http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and http://people.freebsd.org/~bapt/P5N-E.pciconv.txt Both memstick and install current stopped claiming they can mount the root filesystem. when trying to list disks in the mountroot prompt it doesn't list anythings. before failing in the boot process, there are some warning : run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config I have no way to netboot this box. regards, Bapt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
chromium port causing massive I/O faults
hi there, i noticed that chromium, expecially in combination with nspluginwrapper and flash, is causing a lot of I/O faults. i ran 'top -mio -I -n 99' and after only ~ 4 hours of running chromium (most of the time not loading any new pages), i got the following data: last pid: 39976; load averages: 0.37, 0.26, 0.19 up 3+02:38:3023:15:26 72 processes: 2 running, 70 sleeping Mem: 755M Active, 662M Inact, 447M Wired, 51M Cache, 212M Buf, 45M Free Swap: 10G Total, 159M Used, 10G Free, 1% Inuse PIDUID VCSW IVCSW READ WRITE FAULT TOTAL PERCENT COMMAND 39908 1001 7409 51112 0 0 4 4 0.00% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi 39605 1001 598315 233115 11 0 3 14 0.01% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi 1752 1001 22292378 29644471138 0696834 0.38% /usr/local/bin/Xorg -nolisten inet6 1756 1001 1551733 2002630480 0455935 0.43% /usr/local/bin/awesome 39140 1001 10672291 1240670 0 0 6522 6522 2.97% chrome: --type=zygote (chrome) 39116 1001 5967965 3237798 8249 20401 136394 165044 75.14% chromium-browser: (chrome) 39138 1001 6436642 994546 0 0 1785 1785 0.81% chrome: --type=zygote (chrome) 39135 1001 4334272 169320 0 0 1723 1723 0.78% chrome: --type=zygote (chrome) 39133 1001 4321593 169574 1 0 1717 1718 0.78% chrome: --type=zygote (chrome) 39132 1001 4292029 164913 6 0 1766 1772 0.81% chrome: --type=zygote (chrome) 39137 1001 4152284 139225 1 0 1762 1763 0.80% chrome: --type=zygote (chrome) 1629560 356784 70399 25 0 40 65 0.03% /usr/local/sbin/hald 1767 1001 355603 87998 32 0 0 32 0.01% /usr/local/libexec/gam_server 39144 1001 2659919 409841 0 0 3578 3578 1.63% chrome: --type=plugin --plugin-path=/usr/home/arundel/.mozill 10217 1001 472898 258689601 1 8610 0.28% /usr/local/bin/musicpd /usr/local/etc/musicpd.conf 39121 1001 552140 44286 1 0181182 0.08% chrome: --type=zygote (chrome) 39358 1001 103237 20357223 1479211 1913 0.87% /usr/local/bin/sakura 39119 100191173 58899 2 0 14795 14797 6.74% chrome: --type=zygote (chrome) 39846 1001 275524 51575 0 0 7085 7085 3.23% chrome: --type=zygote (chrome) 39120 100160470 18204 0 0 22 22 0.01% chrome: --type=zygote (chrome) 1538 053910 6390 0 0 1 1 0.00% sendmail: accepting connections (sendmail) 39363 100133822 9157 1 1113 3 1117 0.51% /usr/local/bin/sakura 39805 100155542 43060 0 0 2787 2787 1.27% chrome: --type=zygote (chrome) 39117 1001 2935 13041156 0155311 0.14% chromium-browser: (chrome) 39902 100143829 31005 0 0 4477 4477 2.04% chrome: --type=zygote (chrome) 362 028923 1878 1 0 5 6 0.00% /usr/sbin/wpa_supplicant -s -B -i wlan0 -c /etc/wpa_supplicant 1548 0 5122672 11 0 0 11 0.01% /usr/sbin/cron -s 1217 013118676 21 39 0 60 0.03% /usr/sbin/syslogd -s 39907 100116179 6366 0 0 2 2 0.00% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi 39118 1001 976716 90 0 81171 0.08% chrome: --type=zygote (chrome) 1345 0 1362201 1 0 2 3 0.00% /usr/local/sbin/smartd -p /var/run/smartd.pid -c /usr/local/et 1685 1001 180 22 52 0 30 82 0.04% -zsh (zsh) 1458 65534 512 62 2 0 0 2 0.00% /usr/local/bin/mpdscribble --daemon-user nobody 39360 1001 394287 14 0 5 19 0.01% /usr/local/bin/zsh 1636 0 184181 8 0 0 8 0.00% hald-runner 39365 1001 98113 18 0 0 18 0.01% /usr/local/bin/zsh 1633 0 648133 29 0 5 34 0.02% /usr/local/libexec/polkitd 1631 0 608 71 15 0 24 39 0.02% /usr/local/sbin/console-kit-daemon --no-daemon 39931 1001 53 81 1 0 1 2 0.00% /usr/local/bin/zsh 1713 1001 21 16 0 0 2 2 0.00% ssh-agent 1352556 176125 2 0 0 2 0.00% /usr/local/bin/dbus-daemon --system 1494 0 62 17 45 0 14 59 0.03% /usr/local/sbin/cupsd -C /usr/local/etc/cups/cupsd.conf 1733 1001 20 0 1 0 0 1 0.00% /bin/sh /usr/local/bin/startx 1617 0 33 15 7 0 0 7 0.00% login [pam] (login) 1751 1001
Trying to install current from a memory stick and then a DVD and got a new and strange installer.
I have been hearing about a new installer but I obviously have not payed enough attention, I am afraid. I started running freebsd at 2.0 and never really had a problem with understanding the installation program. There is always a first time, I guess. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ When booting I seem to get a screen that makes me remember installer screens of the 1980s. (They were not exactly intuitive.) I somehow got the idea that the new installer was graphic. Maybe something like PCBsd that is not bad at all. I use it on all our employees computers. Actually, after seeing this, I would love to have the old installer back. Is their an option for that? Does this new ASCII installer have a how to with a bit of information on the flow of the installation. Thanks, ed P.D. The handbook does not seem to cover the installer I am seeing because it is 8.2. It shows what I would love to see. Maybe I need to install 8.2 and upgrade? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
On 07/24/11 16:29, eculp wrote: I have been hearing about a new installer but I obviously have not payed enough attention, I am afraid. I started running freebsd at 2.0 and never really had a problem with understanding the installation program. There is always a first time, I guess. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ When booting I seem to get a screen that makes me remember installer screens of the 1980s. (They were not exactly intuitive.) I somehow got the idea that the new installer was graphic. Maybe something like PCBsd that is not bad at all. I use it on all our employees computers. Actually, after seeing this, I would love to have the old installer back. Is their an option for that? Does this new ASCII installer have a how to with a bit of information on the flow of the installation. Thanks, Can you please describe what you didn't like about it, and what you would prefer be changed? Reminiscent of the 1980s is not really helpful, especially given that the new installer in fact looks very much like sysinstall, which you seemed to like. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
Quoting Nathan Whitehorn nwhiteh...@freebsd.org: On 07/24/11 16:29, eculp wrote: I have been hearing about a new installer but I obviously have not payed enough attention, I am afraid. I started running freebsd at 2.0 and never really had a problem with understanding the installation program. There is always a first time, I guess. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ When booting I seem to get a screen that makes me remember installer screens of the 1980s. (They were not exactly intuitive.) I somehow got the idea that the new installer was graphic. Maybe something like PCBsd that is not bad at all. I use it on all our employees computers. Actually, after seeing this, I would love to have the old installer back. Is their an option for that? Does this new ASCII installer have a how to with a bit of information on the flow of the installation. Thanks, Can you please describe what you didn't like about it, and what you would prefer be changed? Reminiscent of the 1980s is not really helpful, especially given that the new installer in fact looks very much like sysinstall, which you seemed to like. -Nathan I do not get a menu that I can understand or relate to any of the installations that I have done previously. I will give it another try and try to explain what I don't understand. Thanks, ed P.S. Is their no documentation on what to expect? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
Nathan Whitehorn wrote: On 07/24/11 16:29, eculp wrote: I have been hearing about a new installer but I obviously have not payed enough attention, I am afraid. I started running freebsd at 2.0 and never really had a problem with understanding the installation program. There is always a first time, I guess. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ When booting I seem to get a screen that makes me remember installer screens of the 1980s. (They were not exactly intuitive.) I somehow got the idea that the new installer was graphic. Maybe something like PCBsd that is not bad at all. I use it on all our employees computers. Actually, after seeing this, I would love to have the old installer back. Is their an option for that? Does this new ASCII installer have a how to with a bit of information on the flow of the installation. Thanks, Can you please describe what you didn't like about it, and what you would prefer be changed? Reminiscent of the 1980s is not really helpful, especially given that the new installer in fact looks very much like sysinstall, which you seemed to like. -Nathan I'll have to agree with the original poster. I have no problem with the look and feel of the new installer, but when functionality that WAS there is now gone, that's a problem. My two, make that three, biggest gripes are: 1) no back button/selection/mechanism on each screen. Rebooting because I fat-fingered something on the previous screen is, well, unacceptable. 2) no minimal install. Most of my installs are single- or few-task servers where I need a base os and a couple ports. 3) I see no post-install uses on the new one. Sysinstall could be used on an up-and-running system to do everything from adding a user to changing a nameserver and more. -- Ron McDowell San Antonio TX ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: chromium port causing massive I/O faults
Same here. I have no way of sending my dump as I'm leaving for OScon and have no access to my desktop, but I did see this behavior. I'm also running HEAD on amd64. Cheers, Norberto On Jul 24, 2011, at 2:25 PM, Alexander Best wrote: hi there, i noticed that chromium, expecially in combination with nspluginwrapper and flash, is causing a lot of I/O faults. i ran 'top -mio -I -n 99' and after only ~ 4 hours of running chromium (most of the time not loading any new pages), i got the following data: last pid: 39976; load averages: 0.37, 0.26, 0.19 up 3+02:38:30 23:15:26 72 processes: 2 running, 70 sleeping Mem: 755M Active, 662M Inact, 447M Wired, 51M Cache, 212M Buf, 45M Free Swap: 10G Total, 159M Used, 10G Free, 1% Inuse PIDUID VCSW IVCSW READ WRITE FAULT TOTAL PERCENT COMMAND 39908 1001 7409 51112 0 0 4 4 0.00% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi 39605 1001 598315 233115 11 0 3 14 0.01% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi 1752 1001 22292378 29644471138 0696834 0.38% /usr/local/bin/Xorg -nolisten inet6 1756 1001 1551733 2002630480 0455935 0.43% /usr/local/bin/awesome 39140 1001 10672291 1240670 0 0 6522 6522 2.97% chrome: --type=zygote (chrome) 39116 1001 5967965 3237798 8249 20401 136394 165044 75.14% chromium-browser: (chrome) 39138 1001 6436642 994546 0 0 1785 1785 0.81% chrome: --type=zygote (chrome) 39135 1001 4334272 169320 0 0 1723 1723 0.78% chrome: --type=zygote (chrome) 39133 1001 4321593 169574 1 0 1717 1718 0.78% chrome: --type=zygote (chrome) 39132 1001 4292029 164913 6 0 1766 1772 0.81% chrome: --type=zygote (chrome) 39137 1001 4152284 139225 1 0 1762 1763 0.80% chrome: --type=zygote (chrome) 1629560 356784 70399 25 0 40 65 0.03% /usr/local/sbin/hald 1767 1001 355603 87998 32 0 0 32 0.01% /usr/local/libexec/gam_server 39144 1001 2659919 409841 0 0 3578 3578 1.63% chrome: --type=plugin --plugin-path=/usr/home/arundel/.mozill 10217 1001 472898 258689601 1 8610 0.28% /usr/local/bin/musicpd /usr/local/etc/musicpd.conf 39121 1001 552140 44286 1 0181182 0.08% chrome: --type=zygote (chrome) 39358 1001 103237 20357223 1479211 1913 0.87% /usr/local/bin/sakura 39119 100191173 58899 2 0 14795 14797 6.74% chrome: --type=zygote (chrome) 39846 1001 275524 51575 0 0 7085 7085 3.23% chrome: --type=zygote (chrome) 39120 100160470 18204 0 0 22 22 0.01% chrome: --type=zygote (chrome) 1538 053910 6390 0 0 1 1 0.00% sendmail: accepting connections (sendmail) 39363 100133822 9157 1 1113 3 1117 0.51% /usr/local/bin/sakura 39805 100155542 43060 0 0 2787 2787 1.27% chrome: --type=zygote (chrome) 39117 1001 2935 13041156 0155311 0.14% chromium-browser: (chrome) 39902 100143829 31005 0 0 4477 4477 2.04% chrome: --type=zygote (chrome) 362 028923 1878 1 0 5 6 0.00% /usr/sbin/wpa_supplicant -s -B -i wlan0 -c /etc/wpa_supplicant 1548 0 5122672 11 0 0 11 0.01% /usr/sbin/cron -s 1217 013118676 21 39 0 60 0.03% /usr/sbin/syslogd -s 39907 100116179 6366 0 0 2 2 0.00% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi 39118 1001 976716 90 0 81171 0.08% chrome: --type=zygote (chrome) 1345 0 1362201 1 0 2 3 0.00% /usr/local/sbin/smartd -p /var/run/smartd.pid -c /usr/local/et 1685 1001 180 22 52 0 30 82 0.04% -zsh (zsh) 1458 65534 512 62 2 0 0 2 0.00% /usr/local/bin/mpdscribble --daemon-user nobody 39360 1001 394287 14 0 5 19 0.01% /usr/local/bin/zsh 1636 0 184181 8 0 0 8 0.00% hald-runner 39365 1001 98113 18 0 0 18 0.01% /usr/local/bin/zsh 1633 0 648133 29 0 5 34 0.02% /usr/local/libexec/polkitd 1631 0 608 71 15 0 24 39 0.02% /usr/local/sbin/console-kit-daemon --no-daemon 39931 1001 53 81 1 0 1 2 0.00% /usr/local/bin/zsh 1713 1001 21 16 0 0 2 2 0.00% ssh-agent 1352556 176125 2 0 0 2 0.00% /usr/local/bin/dbus-daemon --system
Re: chromium port causing massive I/O faults
Am 24.07.2011 23:25, schrieb Alexander Best: hi there, i noticed that chromium, expecially in combination with nspluginwrapper and flash, is causing a lot of I/O faults. i ran 'top -mio -I -n 99' and after It's causing page faults, which is a massive difference. only ~ 4 hours of running chromium (most of the time not loading any new pages), i got the following data: last pid: 39976; load averages: 0.37, 0.26, 0.19 up 3+02:38:30 23:15:26 72 processes: 2 running, 70 sleeping Mem: 755M Active, 662M Inact, 447M Wired, 51M Cache, 212M Buf, 45M Free Swap: 10G Total, 159M Used, 10G Free, 1% Inuse ... is anybody else experiencing the same behavior? i also noticed a massive fault burst (~ 1500/sec), when closing chromium. Is that special to Chrome or -CURRENT? Or does it also happen with Firefox, for instance, or on -STABLE? I suppose FF might cause even more, it readily consumes 1.5 GB on my Linux computer after some time running. A page fault affecting 1500 pages/s (note it's s NOT sec!) amounts to 6 MB/s which appears to be on the comfortable side for any halfway modern system. Page in/page out is quite normal behaviour for any system that has swap space available and is running (especially idle) applications with nontrivial memory requirements and ultimately filling up its ram. At some point in time, when applications have been idle for long enough, it's more useful to page out unused pages and use them as cache instead. Why would a swap usage of 8% of physical RAM size be a reason for concern on a 2 GB RAM 64-bit computer? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
On 07/24/2011 23:33, Nathan Whitehorn wrote: On 07/24/11 16:29, eculp wrote: I have been hearing about a new installer but I obviously have not payed enough attention, I am afraid. I started running freebsd at 2.0 and never really had a problem with understanding the installation program. There is always a first time, I guess. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ When booting I seem to get a screen that makes me remember installer screens of the 1980s. (They were not exactly intuitive.) I somehow got the idea that the new installer was graphic. Maybe something like PCBsd that is not bad at all. I use it on all our employees computers. Actually, after seeing this, I would love to have the old installer back. Is their an option for that? Does this new ASCII installer have a how to with a bit of information on the flow of the installation. Thanks, Can you please describe what you didn't like about it, and what you would prefer be changed? Reminiscent of the 1980s is not really helpful, especially given that the new installer in fact looks very much like sysinstall, which you seemed to like. -Nathan Recently I installed a system from the official memory stick May snapshot (FreeBSD-9.0-CURRENT-201105-amd64-memstick.img). here are a few remarks: - the 1st thing I need to do is to configure the keyboard, as I am not in the US. This is needed for an install, but also for using it as a live system. And the keyboard configuration dialog is only a part of the installation procedure. - the partition tool is too simple/rudimentary, compared to the old sysinstall dialog. I always want to have a total control of the partitions e.g. to have a proper alignement. So one must use the shell escape or the live system, which is a regression. - extracting the tarballs lead to (cryptic) errors: I discovered the hard way that I needed to execute a newfs. - I followed a succession of screens asking me to do the usual configuration steps (hostname, clock, network - IPv4 only ?? -, users) and at the end I get back a screen asking me if a wanted to do the steps I had done just before... - booting the installed system, I found that the hostname disappeared, the keyboard was not configured, nor the network, and so on - during the whole process the screen was scrambled by the occurence of a number of LORs displayed on top of the dialogs/messages of the installer. - the file system of the installer/live system seems to be too small, leading to a number of system full messages as soon a few files are written to it. So the sole value added of the installer was the extraction of the tarballs.. It seems that (on a memory stick which is writable) that every aborted attempt to do a configuration step leaves a trace in some files used by the installer, which is able to show it (e.g. the hostname) at the following attempts, but without garantee that it will effectively be used. (On the other hand, the advantage of the memory stick is that the system on it can be configured at will) Referring to a thread I found recently a propos the documentation on the install media, I also want to say that a proper installer must be able to do its work without any Internet connectivity. There exist systems which are not connected, and networks without any communication with the Internet. Claude Buisson ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
.. wait, the install-off-USB doesn't default to a read-only boot? Adrian On 25 July 2011 08:11, Claude Buisson clbuis...@orange.fr wrote: On 07/24/2011 23:33, Nathan Whitehorn wrote: On 07/24/11 16:29, eculp wrote: I have been hearing about a new installer but I obviously have not payed enough attention, I am afraid. I started running freebsd at 2.0 and never really had a problem with understanding the installation program. There is always a first time, I guess. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ When booting I seem to get a screen that makes me remember installer screens of the 1980s. (They were not exactly intuitive.) I somehow got the idea that the new installer was graphic. Maybe something like PCBsd that is not bad at all. I use it on all our employees computers. Actually, after seeing this, I would love to have the old installer back. Is their an option for that? Does this new ASCII installer have a how to with a bit of information on the flow of the installation. Thanks, Can you please describe what you didn't like about it, and what you would prefer be changed? Reminiscent of the 1980s is not really helpful, especially given that the new installer in fact looks very much like sysinstall, which you seemed to like. -Nathan Recently I installed a system from the official memory stick May snapshot (FreeBSD-9.0-CURRENT-201105-amd64-memstick.img). here are a few remarks: - the 1st thing I need to do is to configure the keyboard, as I am not in the US. This is needed for an install, but also for using it as a live system. And the keyboard configuration dialog is only a part of the installation procedure. - the partition tool is too simple/rudimentary, compared to the old sysinstall dialog. I always want to have a total control of the partitions e.g. to have a proper alignement. So one must use the shell escape or the live system, which is a regression. - extracting the tarballs lead to (cryptic) errors: I discovered the hard way that I needed to execute a newfs. - I followed a succession of screens asking me to do the usual configuration steps (hostname, clock, network - IPv4 only ?? -, users) and at the end I get back a screen asking me if a wanted to do the steps I had done just before... - booting the installed system, I found that the hostname disappeared, the keyboard was not configured, nor the network, and so on - during the whole process the screen was scrambled by the occurence of a number of LORs displayed on top of the dialogs/messages of the installer. - the file system of the installer/live system seems to be too small, leading to a number of system full messages as soon a few files are written to it. So the sole value added of the installer was the extraction of the tarballs.. It seems that (on a memory stick which is writable) that every aborted attempt to do a configuration step leaves a trace in some files used by the installer, which is able to show it (e.g. the hostname) at the following attempts, but without garantee that it will effectively be used. (On the other hand, the advantage of the memory stick is that the system on it can be configured at will) Referring to a thread I found recently a propos the documentation on the install media, I also want to say that a proper installer must be able to do its work without any Internet connectivity. There exist systems which are not connected, and networks without any communication with the Internet. Claude Buisson ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
On 07/24/11 19:11, Claude Buisson wrote: On 07/24/2011 23:33, Nathan Whitehorn wrote: On 07/24/11 16:29, eculp wrote: I have been hearing about a new installer but I obviously have not payed enough attention, I am afraid. I started running freebsd at 2.0 and never really had a problem with understanding the installation program. There is always a first time, I guess. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ When booting I seem to get a screen that makes me remember installer screens of the 1980s. (They were not exactly intuitive.) I somehow got the idea that the new installer was graphic. Maybe something like PCBsd that is not bad at all. I use it on all our employees computers. Actually, after seeing this, I would love to have the old installer back. Is their an option for that? Does this new ASCII installer have a how to with a bit of information on the flow of the installation. Thanks, Can you please describe what you didn't like about it, and what you would prefer be changed? Reminiscent of the 1980s is not really helpful, especially given that the new installer in fact looks very much like sysinstall, which you seemed to like. -Nathan Recently I installed a system from the official memory stick May snapshot (FreeBSD-9.0-CURRENT-201105-amd64-memstick.img). here are a few remarks: Thank you for testing! - the 1st thing I need to do is to configure the keyboard, as I am not in the US. This is needed for an install, but also for using it as a live system. And the keyboard configuration dialog is only a part of the installation procedure. Which is why this is the very first screen of the installer? - the partition tool is too simple/rudimentary, compared to the old sysinstall dialog. I always want to have a total control of the partitions e.g. to have a proper alignement. So one must use the shell escape or the live system, which is a regression. The alignment is done to match the disk stripe size automatically, and the partition editor has many, many more features than the sysinstall one. Is there something in particular you wanted? - extracting the tarballs lead to (cryptic) errors: I discovered the hard way that I needed to execute a newfs. This is what the directions at the top of the partitioning shell say. - I followed a succession of screens asking me to do the usual configuration steps (hostname, clock, network - IPv4 only ?? -, users) and at the end I get back a screen asking me if a wanted to do the steps I had done just before... The network configuration also allows IPv6 in newer versions -- that snapshot is 2 months out of date. The final screen says at the top that is there to modify earlier choices. Can you suggest a clearer wording? - booting the installed system, I found that the hostname disappeared, the keyboard was not configured, nor the network, and so on This is inexplicable. This has worked perfectly for everyone else -- it's possible you made a mistake in the partitioning, but I can't imagine how it would have caused this. Are you able to reproduce the problem? - during the whole process the screen was scrambled by the occurence of a number of LORs displayed on top of the dialogs/messages of the installer. The actual 9.0 CDs will not have WITNESS enabled. It would be nice if the LORs in question were actually fixed, however. - the file system of the installer/live system seems to be too small, leading to a number of system full messages as soon a few files are written to it. The live system is designed more as a fixit medium. What were you trying to do with it? Referring to a thread I found recently a propos the documentation on the install media, I also want to say that a proper installer must be able to do its work without any Internet connectivity. There exist systems which are not connected, and networks without any communication with the Internet. Which is why it behaves in exactly the way you suggest. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
It does not. I had tried to match the behavior of the 8.x memsticks. It's an easy change in /usr/src/release/ARCH/make-memstick.sh to change it, however. -Nathan On 07/24/11 19:54, Adrian Chadd wrote: .. wait, the install-off-USB doesn't default to a read-only boot? Adrian On 25 July 2011 08:11, Claude Buissonclbuis...@orange.fr wrote: On 07/24/2011 23:33, Nathan Whitehorn wrote: On 07/24/11 16:29, eculp wrote: I have been hearing about a new installer but I obviously have not payed enough attention, I am afraid. I started running freebsd at 2.0 and never really had a problem with understanding the installation program. There is always a first time, I guess. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ When booting I seem to get a screen that makes me remember installer screens of the 1980s. (They were not exactly intuitive.) I somehow got the idea that the new installer was graphic. Maybe something like PCBsd that is not bad at all. I use it on all our employees computers. Actually, after seeing this, I would love to have the old installer back. Is their an option for that? Does this new ASCII installer have a how to with a bit of information on the flow of the installation. Thanks, Can you please describe what you didn't like about it, and what you would prefer be changed? Reminiscent of the 1980s is not really helpful, especially given that the new installer in fact looks very much like sysinstall, which you seemed to like. -Nathan Recently I installed a system from the official memory stick May snapshot (FreeBSD-9.0-CURRENT-201105-amd64-memstick.img). here are a few remarks: - the 1st thing I need to do is to configure the keyboard, as I am not in the US. This is needed for an install, but also for using it as a live system. And the keyboard configuration dialog is only a part of the installation procedure. - the partition tool is too simple/rudimentary, compared to the old sysinstall dialog. I always want to have a total control of the partitions e.g. to have a proper alignement. So one must use the shell escape or the live system, which is a regression. - extracting the tarballs lead to (cryptic) errors: I discovered the hard way that I needed to execute a newfs. - I followed a succession of screens asking me to do the usual configuration steps (hostname, clock, network - IPv4 only ?? -, users) and at the end I get back a screen asking me if a wanted to do the steps I had done just before... - booting the installed system, I found that the hostname disappeared, the keyboard was not configured, nor the network, and so on - during the whole process the screen was scrambled by the occurence of a number of LORs displayed on top of the dialogs/messages of the installer. - the file system of the installer/live system seems to be too small, leading to a number of system full messages as soon a few files are written to it. So the sole value added of the installer was the extraction of the tarballs.. It seems that (on a memory stick which is writable) that every aborted attempt to do a configuration step leaves a trace in some files used by the installer, which is able to show it (e.g. the hostname) at the following attempts, but without garantee that it will effectively be used. (On the other hand, the advantage of the memory stick is that the system on it can be configured at will) Referring to a thread I found recently a propos the documentation on the install media, I also want to say that a proper installer must be able to do its work without any Internet connectivity. There exist systems which are not connected, and networks without any communication with the Internet. Claude Buisson ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: chromium port causing massive I/O faults
Is it perhaps doing disk IO using mmap? adrian On 25 July 2011 05:25, Alexander Best arun...@freebsd.org wrote: hi there, i noticed that chromium, expecially in combination with nspluginwrapper and flash, is causing a lot of I/O faults. i ran 'top -mio -I -n 99' and after only ~ 4 hours of running chromium (most of the time not loading any new pages), i got the following data: last pid: 39976; load averages: 0.37, 0.26, 0.19 up 3+02:38:30 23:15:26 72 processes: 2 running, 70 sleeping Mem: 755M Active, 662M Inact, 447M Wired, 51M Cache, 212M Buf, 45M Free Swap: 10G Total, 159M Used, 10G Free, 1% Inuse PID UID VCSW IVCSW READ WRITE FAULT TOTAL PERCENT COMMAND 39908 1001 7409 51112 0 0 4 4 0.00% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi 39605 1001 598315 233115 11 0 3 14 0.01% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi 1752 1001 22292378 29644471 138 0 696 834 0.38% /usr/local/bin/Xorg -nolisten inet6 1756 1001 1551733 2002630 480 0 455 935 0.43% /usr/local/bin/awesome 39140 1001 10672291 1240670 0 0 6522 6522 2.97% chrome: --type=zygote (chrome) 39116 1001 5967965 3237798 8249 20401 136394 165044 75.14% chromium-browser: (chrome) 39138 1001 6436642 994546 0 0 1785 1785 0.81% chrome: --type=zygote (chrome) 39135 1001 4334272 169320 0 0 1723 1723 0.78% chrome: --type=zygote (chrome) 39133 1001 4321593 169574 1 0 1717 1718 0.78% chrome: --type=zygote (chrome) 39132 1001 4292029 164913 6 0 1766 1772 0.81% chrome: --type=zygote (chrome) 39137 1001 4152284 139225 1 0 1762 1763 0.80% chrome: --type=zygote (chrome) 1629 560 356784 70399 25 0 40 65 0.03% /usr/local/sbin/hald 1767 1001 355603 87998 32 0 0 32 0.01% /usr/local/libexec/gam_server 39144 1001 2659919 409841 0 0 3578 3578 1.63% chrome: --type=plugin --plugin-path=/usr/home/arundel/.mozill 10217 1001 472898 258689 601 1 8 610 0.28% /usr/local/bin/musicpd /usr/local/etc/musicpd.conf 39121 1001 552140 44286 1 0 181 182 0.08% chrome: --type=zygote (chrome) 39358 1001 103237 20357 223 1479 211 1913 0.87% /usr/local/bin/sakura 39119 1001 91173 58899 2 0 14795 14797 6.74% chrome: --type=zygote (chrome) 39846 1001 275524 51575 0 0 7085 7085 3.23% chrome: --type=zygote (chrome) 39120 1001 60470 18204 0 0 22 22 0.01% chrome: --type=zygote (chrome) 1538 0 53910 6390 0 0 1 1 0.00% sendmail: accepting connections (sendmail) 39363 1001 33822 9157 1 1113 3 1117 0.51% /usr/local/bin/sakura 39805 1001 55542 43060 0 0 2787 2787 1.27% chrome: --type=zygote (chrome) 39117 1001 2935 13041 156 0 155 311 0.14% chromium-browser: (chrome) 39902 1001 43829 31005 0 0 4477 4477 2.04% chrome: --type=zygote (chrome) 362 0 28923 1878 1 0 5 6 0.00% /usr/sbin/wpa_supplicant -s -B -i wlan0 -c /etc/wpa_supplicant 1548 0 5122 672 11 0 0 11 0.01% /usr/sbin/cron -s 1217 0 13118 676 21 39 0 60 0.03% /usr/sbin/syslogd -s 39907 1001 16179 6366 0 0 2 2 0.00% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi 39118 1001 976 716 90 0 81 171 0.08% chrome: --type=zygote (chrome) 1345 0 1362 201 1 0 2 3 0.00% /usr/local/sbin/smartd -p /var/run/smartd.pid -c /usr/local/et 1685 1001 180 22 52 0 30 82 0.04% -zsh (zsh) 1458 65534 512 62 2 0 0 2 0.00% /usr/local/bin/mpdscribble --daemon-user nobody 39360 1001 394 287 14 0 5 19 0.01% /usr/local/bin/zsh 1636 0 184 181 8 0 0 8 0.00% hald-runner 39365 1001 98 113 18 0 0 18 0.01% /usr/local/bin/zsh 1633 0 648 133 29 0 5 34 0.02% /usr/local/libexec/polkitd 1631 0 608 71 15 0 24 39 0.02% /usr/local/sbin/console-kit-daemon --no-daemon 39931 1001 53 81 1 0 1 2 0.00% /usr/local/bin/zsh 1713 1001 21 16 0 0 2 2 0.00% ssh-agent 1352 556 176 125 2 0 0 2 0.00% /usr/local/bin/dbus-daemon --system 1494 0 62 17 45 0 14 59 0.03% /usr/local/sbin/cupsd -C
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
Something tells me that's a disaster waiting to happen. Eg, if something happens, and the installer disk gets corrupted, people may blame freebsd for being unstable, email questions to freebsd-* mailing lists asking why X doesn't work (only for it to work when the image is written out again), etc, etc. If it's going to double as a live image versus an installer than maybe have a boot option that mounts the root filesystem read-write (complete with some fingerprint that says that the image has been booted read-write at least once?) Adrian On 25 July 2011 08:57, Nathan Whitehorn nwhiteh...@freebsd.org wrote: It does not. I had tried to match the behavior of the 8.x memsticks. It's an easy change in /usr/src/release/ARCH/make-memstick.sh to change it, however. -Nathan On 07/24/11 19:54, Adrian Chadd wrote: .. wait, the install-off-USB doesn't default to a read-only boot? Adrian On 25 July 2011 08:11, Claude Buissonclbuis...@orange.fr wrote: On 07/24/2011 23:33, Nathan Whitehorn wrote: On 07/24/11 16:29, eculp wrote: I have been hearing about a new installer but I obviously have not payed enough attention, I am afraid. I started running freebsd at 2.0 and never really had a problem with understanding the installation program. There is always a first time, I guess. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ When booting I seem to get a screen that makes me remember installer screens of the 1980s. (They were not exactly intuitive.) I somehow got the idea that the new installer was graphic. Maybe something like PCBsd that is not bad at all. I use it on all our employees computers. Actually, after seeing this, I would love to have the old installer back. Is their an option for that? Does this new ASCII installer have a how to with a bit of information on the flow of the installation. Thanks, Can you please describe what you didn't like about it, and what you would prefer be changed? Reminiscent of the 1980s is not really helpful, especially given that the new installer in fact looks very much like sysinstall, which you seemed to like. -Nathan Recently I installed a system from the official memory stick May snapshot (FreeBSD-9.0-CURRENT-201105-amd64-memstick.img). here are a few remarks: - the 1st thing I need to do is to configure the keyboard, as I am not in the US. This is needed for an install, but also for using it as a live system. And the keyboard configuration dialog is only a part of the installation procedure. - the partition tool is too simple/rudimentary, compared to the old sysinstall dialog. I always want to have a total control of the partitions e.g. to have a proper alignement. So one must use the shell escape or the live system, which is a regression. - extracting the tarballs lead to (cryptic) errors: I discovered the hard way that I needed to execute a newfs. - I followed a succession of screens asking me to do the usual configuration steps (hostname, clock, network - IPv4 only ?? -, users) and at the end I get back a screen asking me if a wanted to do the steps I had done just before... - booting the installed system, I found that the hostname disappeared, the keyboard was not configured, nor the network, and so on - during the whole process the screen was scrambled by the occurence of a number of LORs displayed on top of the dialogs/messages of the installer. - the file system of the installer/live system seems to be too small, leading to a number of system full messages as soon a few files are written to it. So the sole value added of the installer was the extraction of the tarballs.. It seems that (on a memory stick which is writable) that every aborted attempt to do a configuration step leaves a trace in some files used by the installer, which is able to show it (e.g. the hostname) at the following attempts, but without garantee that it will effectively be used. (On the other hand, the advantage of the memory stick is that the system on it can be configured at will) Referring to a thread I found recently a propos the documentation on the install media, I also want to say that a proper installer must be able to do its work without any Internet connectivity. There exist systems which are not connected, and networks without any communication with the Internet. Claude Buisson ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
On 25/07/2011 00:03, Ron McDowell wrote: 1) no back button/selection/mechanism on each screen. Rebooting because I fat-fingered something on the previous screen is, well, unacceptable. 2) no minimal install. Most of my installs are single- or few-task servers where I need a base os and a couple ports. 3) I see no post-install uses on the new one. Sysinstall could be used on an up-and-running system to do everything from adding a user to changing a nameserver and more. Another potential problem is that the new version of libdialog that the new installer uses changes the way navigation is done: on Linux and in the previous version on FreeBSD it's possible to press Tab to change focus to the buttons and different UI elements. That doesn't work any more. -- Bruce Cran ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
On 07/24/11 18:03, Ron McDowell wrote: Nathan Whitehorn wrote: On 07/24/11 16:29, eculp wrote: I have been hearing about a new installer but I obviously have not payed enough attention, I am afraid. I started running freebsd at 2.0 and never really had a problem with understanding the installation program. There is always a first time, I guess. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ When booting I seem to get a screen that makes me remember installer screens of the 1980s. (They were not exactly intuitive.) I somehow got the idea that the new installer was graphic. Maybe something like PCBsd that is not bad at all. I use it on all our employees computers. Actually, after seeing this, I would love to have the old installer back. Is their an option for that? Does this new ASCII installer have a how to with a bit of information on the flow of the installation. Thanks, Can you please describe what you didn't like about it, and what you would prefer be changed? Reminiscent of the 1980s is not really helpful, especially given that the new installer in fact looks very much like sysinstall, which you seemed to like. -Nathan I'll have to agree with the original poster. I have no problem with the look and feel of the new installer, but when functionality that WAS there is now gone, that's a problem. My two, make that three, biggest gripes are: 1) no back button/selection/mechanism on each screen. Rebooting because I fat-fingered something on the previous screen is, well, unacceptable. This is why almost all screens have a cancel button. You can also restart the installer by control-C at any time without rebooting. Providing an actual back button is quite tricky and not necessarily always well defined in behavior, since the installed system will then be in an inconsistent state at which previous steps cannot necessarily be repeated. For those steps where that is not true, they can be reentered from the menu at the end in case of fat-fingering. 2) no minimal install. Most of my installs are single- or few-task servers where I need a base os and a couple ports. I'm not sure what you mean by this. You can install just a kernel and the base system by deselecting the ports tree, games, and docs when you select which system components to install. 3) I see no post-install uses on the new one. Sysinstall could be used on an up-and-running system to do everything from adding a user to changing a nameserver and more. This is deliberate. This particular feature of sysinstall made it almost unmaintainable, especially as those features slowly bitrotted. We have very good system configuration utilities already -- there is no need to duplicate them in the installer, especially when it makes maintaining and improving that installer more difficult. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
Yes, I agree. I'll ask re@ to change it. -Nathan On 07/24/11 20:02, Adrian Chadd wrote: Something tells me that's a disaster waiting to happen. Eg, if something happens, and the installer disk gets corrupted, people may blame freebsd for being unstable, email questions to freebsd-* mailing lists asking why X doesn't work (only for it to work when the image is written out again), etc, etc. If it's going to double as a live image versus an installer than maybe have a boot option that mounts the root filesystem read-write (complete with some fingerprint that says that the image has been booted read-write at least once?) Adrian On 25 July 2011 08:57, Nathan Whitehornnwhiteh...@freebsd.org wrote: It does not. I had tried to match the behavior of the 8.x memsticks. It's an easy change in /usr/src/release/ARCH/make-memstick.sh to change it, however. -Nathan On 07/24/11 19:54, Adrian Chadd wrote: .. wait, the install-off-USB doesn't default to a read-only boot? Adrian On 25 July 2011 08:11, Claude Buissonclbuis...@orange.frwrote: On 07/24/2011 23:33, Nathan Whitehorn wrote: On 07/24/11 16:29, eculp wrote: I have been hearing about a new installer but I obviously have not payed enough attention, I am afraid. I started running freebsd at 2.0 and never really had a problem with understanding the installation program. There is always a first time, I guess. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ When booting I seem to get a screen that makes me remember installer screens of the 1980s. (They were not exactly intuitive.) I somehow got the idea that the new installer was graphic. Maybe something like PCBsd that is not bad at all. I use it on all our employees computers. Actually, after seeing this, I would love to have the old installer back. Is their an option for that? Does this new ASCII installer have a how to with a bit of information on the flow of the installation. Thanks, Can you please describe what you didn't like about it, and what you would prefer be changed? Reminiscent of the 1980s is not really helpful, especially given that the new installer in fact looks very much like sysinstall, which you seemed to like. -Nathan Recently I installed a system from the official memory stick May snapshot (FreeBSD-9.0-CURRENT-201105-amd64-memstick.img). here are a few remarks: - the 1st thing I need to do is to configure the keyboard, as I am not in the US. This is needed for an install, but also for using it as a live system. And the keyboard configuration dialog is only a part of the installation procedure. - the partition tool is too simple/rudimentary, compared to the old sysinstall dialog. I always want to have a total control of the partitions e.g. to have a proper alignement. So one must use the shell escape or the live system, which is a regression. - extracting the tarballs lead to (cryptic) errors: I discovered the hard way that I needed to execute a newfs. - I followed a succession of screens asking me to do the usual configuration steps (hostname, clock, network - IPv4 only ?? -, users) and at the end I get back a screen asking me if a wanted to do the steps I had done just before... - booting the installed system, I found that the hostname disappeared, the keyboard was not configured, nor the network, and so on - during the whole process the screen was scrambled by the occurence of a number of LORs displayed on top of the dialogs/messages of the installer. - the file system of the installer/live system seems to be too small, leading to a number of system full messages as soon a few files are written to it. So the sole value added of the installer was the extraction of the tarballs.. It seems that (on a memory stick which is writable) that every aborted attempt to do a configuration step leaves a trace in some files used by the installer, which is able to show it (e.g. the hostname) at the following attempts, but without garantee that it will effectively be used. (On the other hand, the advantage of the memory stick is that the system on it can be configured at will) Referring to a thread I found recently a propos the documentation on the install media, I also want to say that a proper installer must be able to do its work without any Internet connectivity. There exist systems which are not connected, and networks without any communication with the Internet. Claude Buisson ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
On 07/24/11 20:03, Bruce Cran wrote: On 25/07/2011 00:03, Ron McDowell wrote: 1) no back button/selection/mechanism on each screen. Rebooting because I fat-fingered something on the previous screen is, well, unacceptable. 2) no minimal install. Most of my installs are single- or few-task servers where I need a base os and a couple ports. 3) I see no post-install uses on the new one. Sysinstall could be used on an up-and-running system to do everything from adding a user to changing a nameserver and more. Another potential problem is that the new version of libdialog that the new installer uses changes the way navigation is done: on Linux and in the previous version on FreeBSD it's possible to press Tab to change focus to the buttons and different UI elements. That doesn't work any more. It's a change from before, but a normalization with respect to most Linux distributions, since we are now using the same dialog as, e.g., Debian and Ubuntu. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
On 25/07/2011 02:08, Nathan Whitehorn wrote: On 07/24/11 20:03, Bruce Cran wrote: On 25/07/2011 00:03, Ron McDowell wrote: 1) no back button/selection/mechanism on each screen. Rebooting because I fat-fingered something on the previous screen is, well, unacceptable. 2) no minimal install. Most of my installs are single- or few-task servers where I need a base os and a couple ports. 3) I see no post-install uses on the new one. Sysinstall could be used on an up-and-running system to do everything from adding a user to changing a nameserver and more. Another potential problem is that the new version of libdialog that the new installer uses changes the way navigation is done: on Linux and in the previous version on FreeBSD it's possible to press Tab to change focus to the buttons and different UI elements. That doesn't work any more. It's a change from before, but a normalization with respect to most Linux distributions, since we are now using the same dialog as, e.g., Debian and Ubuntu. The Debian 6.0.2.1 installer appears to use the old navigation method, and SuSE 11.4 seems to too. -- Bruce Cran ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
On Sunday, July 24, 2011, Ron McDowell r...@fuzzwad.org wrote: I'll have to agree with the original poster. I have no problem with the look and feel of the new installer, but when functionality that WAS there is now gone, that's a problem. My two, make that three, biggest gripes are: 1) no back button/selection/mechanism on each screen. Rebooting because I fat-fingered something on the previous screen is, well, unacceptable. 2) no minimal install. Most of my installs are single- or few-task servers where I need a base os and a couple ports. The nice thing about bsdinstall is that every install is identical. It's basically just dumping an image file to disk. 3) I see no post-install uses on the new one. Sysinstall could be used on an up-and-running system to do everything from adding a user to changing a nameserver and more. Thank goodness. The worst thing about sysinstall was that it tried to be a Swiss Army knife doing everything, yet not doing any one thing well. It made a royal mess of rc.conf if you tried to use it to configure a system. Usually the first time someone mentions they use it for post-install configuration, the recommendation is to stop doing that! An os installer should do just that: install the os and nothing else. -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
On Sun, 24 Jul 2011, Nathan Whitehorn wrote: Can you please describe what you didn't like about it, and what you would prefer be changed? Reminiscent of the 1980s is not really helpful, especially given that the new installer in fact looks very much like sysinstall, which you seemed to like. For myself, two things jumped out: 1. The use of tab and enter in the dialogs is different enough to be a problem, particularly when other dialogs like port options still work as before. 2. The disk setup screen is unclear, or unintuitive, at least for me. For reference, here's a copy: Please review the disk setup. When complete, press the Exit button. ad0 8.7 GBGPT ad0p1 64 KB freebsd-boot ad0p2 8.3 GBfreebsd-ufs/ ad0p3 446 MBfreebsd-swap none Create Delete Modify Revert Auto Exit 1. Extending the highlight bar the whole width of the window would help to show what is being operated on. 2. The options don't always really apply. Create when ad0 is highlighted leads the user to think they can create a new device, like ad1. But it will really create another partition. Delete on ad0 deletes all the partitions, not ad0. No warning, either. 3. Tab in the Modify partition window doesn't go to the next field, but to the OK button. Backtab closes the window instead of going back a field. 4. The partition scheme requires a boot partition. But there's one already there. Possibly this is a bug. ad0 8.7 GBGPT ad0p1 64 KB freebsd-boot ad0p2 8.3 GBfreebsd-ufs/ ad0p3 446 MBfreebsd-swap none ad0p4 64 KB freebsd-boot ad0p5 926 KBfreebsd-ufs/ 5. This one's about method rather than user interface... Auto creation should probably follow the standard of separate partitions for /, swap, /var, /tmp, and /usr. Swap at the end of the disk will be slower, and combining all the filesystems is a big change. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
