Bug#1071652: As a matter of fact
As a matter of fact, the solution I posted doesn't work either. Therefore, be sure on the man page, to mention the true sequence needed: # debootstrap (missing step goes here) # debootstrap --second-stage
Bug#927987: Don't tell users to use ext3
Maybe the document should say "don't worry, the installer process will walk you through this. /tmp: well I just use tmpfs. Also the worst thing is if one searches on Google for /var /home vs. just / Debian articles, he will find ../jessie/.. and has to put in the word ../stretch/.. in the URL to get the newer version. So even if he knew which name is newer, Google doesn't so gives them all the same priority for search results... in fact backward priority. So even if you make a spanking new version, people will still find the older version. Anyway you might want to just merge the document with the installer documents.
Bug#927045: ^C doesn't work when booting into recovery mode
Package: installation-reports Severity: minor Just want to let you know after a fresh install, when booting into "(recovery mode)" from the grub menu, and typing the root passwd, # cat ^C doesn't interrupt cat, etc. One needs ^Z, then "kill %" to stop it. Yes, these just reported the same as on a normal fully working terminal: # stty -a speed 38400 baud; rows 48; columns 128; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ; eol2 = ; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; discard = ^O; min = 1; time = 0; -parenb -parodd -cmspar cs8 hupcl -cstopb cread -clocal -crtscts -ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany imaxbel iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke -flusho -extproc # stty -g 6502:5:4bf:8a3b:3:1c:7f:15:4:0:1:0:11:13:1a:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0 So I don't know what the problem is. Note I had only installed the packages contained on Debian GNU/Linux 9.8.0 _Stretch_ - Official amd64 NETINST 20190216-11:59"; with no internet connection. Sure, after adding more packages and rebooting, the problem went away. So do try it with the bare bones install from just http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/ with no network connection to download extra packages. The only other odd thing I did was add nomodeset to linux /boot/vmlinuz-4.9.0-8-amd64 ... in grub.
Bug#927037: Message didn't fully fit inside its window
Package: debian-installer
Severity: minor
I recall when the graphical installer got to this message,
Name: partman-crypto/progress/plain_erase_text
Type: text
Description: The installer is now overwriting ${DEVICE} with zeroes to delete
its previous contents. This step may be skipped by cancelling this action.
it didn't fully fit in its window, so people couldn't see the last part
of the sentence.
Bug#849509: Logs show popularity-contest installation indeed occurs after user says no
OK. The package is actually installed. It is just the message about that being buffered until the next interaction probably.
Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen
All I know is I researched what ISO I could put on a USB stick and take to my mountain for a minimal install with no network. It worked fine, after I added that nomodeset line. It is a shame if officially debian no longer can be installed without a network.
Bug#849509: Logs show popularity-contest installation indeed occurs after user says no
Actually try this: When you get to the popularity-contest question, wait a few moments, then answer "no". Later examine the logs. You will see actual installation (and then removal) indeed occurs *after* the user has answered "no". So the user's eyes didn't fool him after all.
Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen
I'll be very happy to help you test this week. Next week I wish to proceed with final installation though. BH> Was the firmware (firmware-amd-graphics package) installed on your test BH> system? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925556#25 mentions what ISO I used, and all logs are attached to that bug report. Note I do all my installs offline with just the ISO. I recall having worked around the /dev/sdX issue, one can get as far as (Staring at the stuck screen with one of the last messages being amdgpudrmfb ...) I recall with nomodeset in effect, logs will contain [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. but at least one can still use the computer.
Bug#925556: use UUIDs 100% in grub, not /dev/sdX
retitle 925556 Use UUID, not sdX on grub linux lines
thanks
The problem simply turns out to be:
grub lines like
linux /boot/vmlinuz-4.9.0-8-amd64 root=/dev/sdb2 ro quiet
are simply bound to fail:
When the computer boots, no matter when for the installer, or later, the
installed system, /dev/sdX could refer to something different.
So let's say there are two items plugged in when the grub.cfg is
created. And two items plugged in when the newly installed system is
booted. Well there is a 50% chance that the system won't boot.
With three items, only a 33% chance the system will boot.
https://www.gnu.org/software/grub/manual/grub/html_node/Device-map.html
Let's examine a proper linux line:
linux /boot/vmlinuz-4.19.0-4-amd64
root=UUID=f19dae4b-fcb8-49eb-b43b-6f99597db52d ro quiet
I don't know why in the world your installer is still producing such bad
linux lines. Maybe it is because I did the install totally offline and
that's not what you test with.
Anyway, you need to find out why
GRUB_DISABLE_LINUX_UUID=true
is somehow apparently sadly in effect.
Actually it is only half in effect, as you see UUID entries, just not on
the linux line:
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu
--class os $menuentry_id_option
'gnulinux-simple-ee7dd9c6-9f5b-45bc-bf31-36123bd61588' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2
--hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2
ee7dd9c6-9f5b-45bc-bf31-36123bd61588
else
search --no-floppy --fs-uuid --set=root
ee7dd9c6-9f5b-45bc-bf31-36123bd61588
fi
echo'Loading Linux 4.9.0-8-amd64 ...'
linux /boot/vmlinuz-4.9.0-8-amd64 root=/dev/sdb2 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.9.0-8-amd64
}
For users reading this bug: use "e" from the grub boot screen to fix
e.g., sda2 to sdb2 or sdb2 to sda2, etc.
(The only other problem I had was the unrelated
Bug#926149: (AMD: Add nomodeset kernel parameter to avoid black screen))
Anyway this week I will delay final installation so I can assist further
if needed.
Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen
Package: installation-reports With the latest AMD CPUs the kernel will attempt to use the AMDGPU kernel driver. Alas this will result in a black screen on the minimal system installed by the installer. Therefore on all three of these lines in /boot/grub/grub.cfg linux /boot/vmlinuz-... root=... the parameter "nomodeset" needs to occur. Yes, even for the "recovery mode entry". (Users reading this bug would want to add it by using "e" when looking at the grub boot screen, to get their system booted. Then put it in GRUB_CMDLINE_LINUX= in /etc/default/grub and then run grub-install. For full logs please see #925556.
Bug#849509: Can't blame the user for trying to read the messages
I suppose in the logs, of Mar 27 23:38:24 in-target: Preparing to unpack .../popularity-contest_1.64_all.deb ... Mar 27 23:38:24 in-target: Unpacking popularity-contest (1.64) ... Mar 27 23:38:24 in-target: Setting up popularity-contest (1.64) ... Mar 27 23:38:24 in-target: Removing popularity-contest (1.64) ... Mar 27 23:38:24 in-target: Purging configuration files for popularity-contest (1.64) ... what one is seeing go by so fast in the little window is the latter part. So the only thing the user has time to notice is the package name. So he thinks you must be installing it, along with the other names he sees fly by. But in fact you are removing it. Anyway if it said "transfer 5 euros?" and you hit "no", would you still be happy if what you saw was something about 5 go by below, looking like the same message the last time when you said "yes". In fact it is putting the money back into your account, from a temporary holding area, instead of forwarding it elsewhere. All very odd.
Bug#925556: UEFI or not, can't mount /dev
Trying again with expert install and some different choices, and putting nomodeset in the grub finally booted it. I'll send new logs soon.
Bug#925991: Show version on splash screen
Package: debian-installer Severity: minor The Installer splash screen should show the version number.
Bug#925887: Users fooled by Busybox boilerplate
Maybe just have a message: "press TAB to see all available commands." That would show both built-ins and non builtins. (Hope TAB works.)
Bug#925897: Always also offer UTC when asking timezone
Package: debian-installer Severity: minor Let's say you are asking the user what time zone he is in for some country: Eastern Time Zone Plains Time Zone Mountain Time Zone Other Well I recall in expert mode installation, UTC is also always present: Eastern Time Zone Plains Time Zone Mountain Time Zone UTC Other Please also make it always present in non-expert mode too. Some people would just like to give a neutral choice, and save the real configuration for later after actual booting success.
Bug#925896: tasksel_first: Give examples of "Standard system utilities" when asking
Package: debian-installer Severity: minor In tasksel_first_0.png the user is totally helpless trying to figure out what you mean by "Standard system utilities" So give some examples. Say "Standard system utilities (cat, ls...)" or "Standard system utilities (gnome, kde...)" or something, anything! We are at the nuclear test site and can't drive all the way back and Google what you mean. "Don't worry, you'll see their names fly by on the next screen as they are installed." Yeah, but that's is *after* we've made the choice. "They are simply the ones with Priority: standard etc. in their dpkg fields." Yes great but the user cannot look them all up there staring at the question.
Bug#925895: partman_choose_partition: mention that there will be one more screen with a list of proposed changes
Package: debian-installer Severity: wishlist Here on partman_choose_partition_0.png we see both things that are about to be changed, and things that will stay the same, but we can't tell which are which. So right after the words "write changes to disk" you need to add "(You will be first shown a confirmation screen with a list of which of these items are proposed to be changed.)"
Bug#925893: Also ask "Do not configure the network at this time" *before* trying to configure the network
Package: debian-installer Severity: minor Please also ask "Do not configure the network at this time" *before* trying to configure the network. Not only after, and failing. That way users installing offline wouldn't need to answer several futile questions and have futile DHCP packets sent to them. And then no point in asking them apt-setup_no_mirror questions:
Bug#925892: Add version name next to number
Package: debian-installer Users often hear "Stretch", "Buster", but on the installer, they see just "Debian 9". Therefore please make it say "Debian 9 (Stretch)" or "Debian 9 Stretch". In fact much wiser would be to do what iOS does, and keep them a top secret. https://medium.com/@viswa127/apples-secret-code-names-for-ios-versions-22e44ac72355
Bug#925891: Debian Black Screen of Death worse than Microsoft's Blue Screen of Death
Package: debian-installer Severity: wishlist In bug #925556, I showed you what a failed install looks like to a user who has booted via grub's "(recovery mode)" entries. If the user hadn't touched the keyboard, a normal boot would instead proceed, whereupon the user would just end up on a black screen. They might say 'I tried Debian. Black screen! Not even "BSOD" with a few words on it. Forget it!' "One can't just hack X Windows to do that" you might say... Well please do something.
Bug#925889: Add "exit" or "Reboot" to the menus
Package: debian-installer Severity: wishlist The menus are great, But you forgot one item. "Reboot". You see, no matter how the user scours the menus, he cannot find the proper way to exit (reboot). "Well he is supposed to know how to do that himself!" Yes, but he wants the "proper" way to get out of your menus. He is worried that just guessing some way, or hitting the power button, might mess things up. Plus he is offline at the remote N. Korean nuke site so he can't just Google the answer. You do intend him to have a proper way to get out right? OK, the only proper way is to follow through to the end: install a debian operating system, after which the menus finally say the next step will reboot your computer.
Bug#925888: Add Quick rescue mode
Package: debian-installer Today let's discuss Rescue Mode. I think you should offer a second rescue mode choice. Call it "Quick Rescue Mode". List it right after Rescue Mode. Quick Rescue Mode would drop the user into a shell right away. No questions about languages. Yup, unfair. Sorry. No questions about time zones. Yup, no time to ask about time zones. We are trying to rescue the patient, remember? No million other questions that I already forgot. I don't even recall if it even tried to configure the network, there were so many questions. Only one screen needed: Indeed you don't even need to try help him mount a disk! Just say "use mkdir /mnt/zz; mount /dev/sdX8 /mnt/zz to mount disks". Anyway this Quick Rescue Mode would start in one second. Long before our classmates using plain Rescue Mode have even answered their first question.
Bug#925886: Rescue mode: When asking device to use as root file system, give more detailed choices
Package: debian-installer Severity: minor Here there is a high chance the user will chose the wrong item, because he does not recall which of his disks are which. Therefore you need to present more details, which yes, can fit on the same line. Add sizes and partition types and disk label stuff etc.
Bug#925556: UEFI or not, can't mount /dev
logs.gz Description: application/gzip
Bug#925556: UEFI or not, can't mount /dev
I tried installing again. (This time with no network.) The normal
graphical install. All goes fine, but in the logs there is one "Failed
to get":
$ grep -A 2 'Failed to get' syslog |cut -c 17-
base-installer: warning: Failed to get debconf answer
'base-installer/kernel/linux/initrd'.
base-installer: info: Setting do_initrd='yes'.
base-installer: info: Setting link_in_boot='no'.
Anyway, then from BIOS boot list
choosing the first item, booting stops at
choosing the last item, booting stops at
By the way, it might not be a good idea to hardwire the names /sda when
making grub stuff, as that might not always be where it is... maybe I
should try editing ("e" at the grub menu) and replace the a with b, c,
etc. until I hit a winner... and can boot(?) But then how would I go
about making sure it would boot the next time by itself.
P.S., a few days ago I tried and expert install, and recall a question,
Name: base-installer/initramfs-tools/driver-policy
Type: select
Choices: generic: include all available drivers, targeted: only include
drivers needed for this system
Description: Drivers to include in the initrd:
Extended_description: The primary function of an initrd is to allow the..
But I recall no matter how I answer it, it didn't make a bootable
system.
Bug#925556: UEFI or not, can't mount /dev
> "SM" == Steve McIntyre writes: SM> Please attach the installer syslog so we have a chance to see what SM> happened. On the installed system, that's in /var/log/installer/syslog What should I give at that initramfs prompt you see that would put it on the screen? Then I could take a photograph of it.
Bug#925582: Allow telling installer about local deb and Package list locations
Package: debian-installer User has a USB drive, loaded with $ mount /dev/sdg2 on /var/cache/apt/archives type ext4 /dev/sdg1 on /var/lib/apt/lists type ext4 He takes this drive, along with another drive, containing a Debian installation ISO, to a remote mountain (offline) computer, intending to install Debian on it. Alas, while running the ISO there is no way to tell it about the other stick where those the .debs are. Thus making an offline https://haydenjames.io/direct-install-debian-sid-rolling-release-using-mini-iso-w-screenshots/ not possible. See also https://wiki.debian.org/SourcesList#CD-ROM https://www.debian.org/releases/stretch/amd64/ch06s03.html.en#di-install-software "/etc/apt/sources.list. You can examine and edit this file to your liking **after** the installation is complete." Anyway the user would like to offline, have a way to say to the installer: This is the location of a lot of *.debs. and This ... is a Packages file I made from them. and This ... is a list of packages I want you to install from it. Sure, "just do that all later after you get Debain installed". But that is very wasteful.
Bug#925556: UEFI or not, can't mount /dev
LS> Clearly the initramfs was able to mount /dev and run fsck, but mounting LS> it to /root/dev to transfer to the real rootfs failed due to a missing LS> directory. So it booted, meaning it is not a https://www.debian.org/releases/stretch/amd64/ch03s06.html.en#UEFI problem...
Bug#925580: Never leave the user staring at an empty screen, even for a second
Package: debian-installer Here the user is left staring at an empty screen. (Many look that way for a while at the beginning. Even with the latest fastest hardware.) Not for long you might say. But long enough for the user to scratch his head, and then casually get out his cellphone and take a picture, then wonder some more. Please for every screen, add a "Please wait..." first.
Bug#925579: User could have just as easily clicked the UEFI or non-UEFI...
Package: debian-installer In https://wiki.debian.org/UEFI We read "debian-installer's support for UEFI is mostly contained in two modules. First comes the partman-efi module, and this will be loaded automatically if d-i recognises it has been booted in UEFI mode." The problem here is that on e.g., ASUS, there is a 50% chance that a user could have picked the plain JetFlash (where the d-i ISO is), or the same ISO, but with the UEFI: prefix... (Don't worry about the highlighted line in that photo.)
Bug#857459: cannot scroll to bottom of help on partitioning screen
Package: d-i.debian.org Severity: wishlist Cannot scroll to bottom of 'help on partitioning' screen... too long... no way to read all the way to the bottom.
Bug#852670: dpkg: warning: while removing console-setup-linux, directory '/etc/console-setup' not empty so not removed
Package: console-setup-linux Version: 1.158 dpkg: warning: while removing console-setup-linux, directory '/etc/console-setup' not empty so not removed OK I'll remove by hand -rw-r--r-- 1 root root 4147 2014-02-24 /etc/console-setup/Uni2-Fixed16.psf.gz
Bug#849509: popularity-contest installed momentarily even if user says No
Well just as if one's country must install a missle defense system just to ask the question if they should install the missle defense system... and then remove the missle defense system... But OK maybe there are some translation strings unavailable from e.g., $ for package in popularity-contest; do grep-aptavail -PX -d $package; echo should we install...; read answer; ... done
Bug#849509: popularity-contest installed momentarily even if user says No
Package: installation-reports Using DISTRIB_RELEASE="9 (stretch) - installer build 20161212-00:04" the user chooses "No", the default, to the popularity-contest question. He notices through the corner of his eye, something about the package flashing by on the screen anyway! Indeed the logs expose the fact that the package is installed then removed right away. One big no-op! Please don't install it in the first place if the user has said No. Dec 25 23:38:10 in-target: The following NEW packages will be installed: Dec 25 23:38:10 in-target: popularity-contest Dec 25 23:38:10 in-target: 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Dec 25 23:38:10 in-target: Need to get 0 B/70.6 kB of archives. Dec 25 23:38:10 in-target: After this operation, 179 kB of additional disk space will be used. Dec 25 23:38:10 in-target: Get:1 cdrom://[Debian GNU/Linux testing _Stretch_ - Official Snapshot amd64 NETINST Binary-1 20161212-05:24] stretch/main amd64 popularity-contest all 1.64 [70.6 kB] Dec 25 23:38:10 in-target: Preconfiguring packages ... Dec 25 23:38:14 in-target: Selecting previously unselected package popularity-contest. Dec 25 23:38:14 in-target: ^M Dec 25 23:38:14 in-target: (Reading database ... Dec 25 23:38:14 in-target: 15048 files and directories currently installed.) Dec 25 23:38:14 in-target: Preparing to unpack .../popularity-contest_1.64_all.deb ... Dec 25 23:38:14 in-target: Unpacking popularity-contest (1.64) ...^M Dec 25 23:38:14 in-target: Setting up popularity-contest (1.64) ... Dec 25 23:38:15 in-target: (Reading database ... 15073 files and directories currently installed.) Dec 25 23:38:15 in-target: Removing popularity-contest (1.64) ... Dec 25 23:38:15 in-target: Purging configuration files for popularity-contest (1.64) ... Dec 25 23:38:16 pkgsel: starting tasksel Dec 25 23:39:30 in-target: Reading package lists...
Bug#849508: add GO BACK choice to save logs question
Package: installation-reports Using DISTRIB_RELEASE="9 (stretch) - installer build 20161212-00:04" when getting to the question about saving logs, the user is prompted with /mnt . At this point the user wants to GO BACK to choose "open a shell" to inspect what places are in fact mounted. However at this point there is no GO BACK choice, only Continue! In fact you might check for other questions that lack GO BACK to see if they sould have it added or not.
Bug#849278: zapps USB somehow
Package: os-prober Version: 1.71 With os-prober installed and then running update-grub and grub-install all I know is after rebooting I couldn't use any USB stuff after Debian started the main boot choice. As I depend on a USB keyboard, the only way to regain control of my computer again was to hit the power button, and upon reboot quickly pick recovery mode from the grub menu. If I just instead sit there my computer starts X windows and the only way out is the power button. No I don't know why but it must have to do with those eerie kernel messages you see, grub-syslog.txt.gz Description: log Anyway I have now "aptitude purge"d os-prober and ran update-grub and grub-install and now my computer is working again! Yes there are a few less boot menu choices but it is worth it.
Bug#582231: dpkg: warning: while removing os-prober, directory '/var/lib/os-prober' not empty so not removed
found 582231 1.71 thanks Removing os-prober (1.71) ... dpkg: warning: while removing os-prober, directory '/var/lib/os-prober' not empty so not removed # find /var/lib/os-prober -ls 1443133 4 drwxr-xr-x 2 root root 4096 Dec 24 12:21 /var/lib/os-prober 1442408 4 -rw-r--r-- 1 root root9 Dec 24 12:21 /var/lib/os-prober/labels # find /var/lib/os-prober -delete
Bug#840351: pstrees
OK, I have captured both: $ pstree -al During the first occasion: `-aptitude safe-upgrade |-sh -c /usr/sbin/dpkg-preconfigure --apt || true | `-dpkg-preconfigu -w /usr/sbin/dpkg-preconfigure --apt | |-(dpkg-preconfigu) | |-keyboard-config /tmp/keyboard-configuration.config.BvbEEk configure 1.150 | `-whiptail --backtitle Package configuration --title Configuring keyboard-configuration --output-fd 12 --default-item Generic 105-key (Intl) PC --menu Please select the model of the keyboard of this machine.\012\012Keyboard m During the second occasion: `-aptitude safe-upgrade |-dpkg --status-fd 38 --no-triggers --configure --pending | `-frontend -w /usr/share/debconf/frontend /var/lib/dpkg/info/keyboard-configuration.postinst configure 1.150 | |-keyboard-config /var/lib/dpkg/info/keyboard-configuration.config configure 1.150 | `-whiptail --backtitle Package configuration --title Configuring keyboard-configuration --output-fd 11 --default-item Generic 105-key (Intl) PC --menu Please select the model of the keyboard of this machine.\012\01 They only happen a few minutes apart, during upgrade.
Bug#840351: user asked same question twice upon upgrade
Package: keyboard-configuration Version: 1.151 During upgrade the user gets asked the same question twice. The first time is at Preconfiguring packages ... The second time is when (viewed with pstree -al): `-frontend -w /usr/share/debconf/frontend /var/lib/dpkg/info/keyboard-configuration.postinst configure 1.150 | |-keyboard-config /var/lib/dpkg/info/keyboard-configuration.config configure 1.150 | `-whiptail --backtitle Package configuration --title Configuring keyboard-configuration --output-fd 11 --default-item Generic 105-key (Intl) PC --menu Please select the model of the keyboard o... Even though in both cases he says to the default-item.
Bug#838332: keyboard-configuration/unsupported_config_layout bad question
Package: keyboard-configuration Version: 1.149 Severity: wishlist We are asked "Keep the current keyboard layout in the configuration file? The current keyboard layout in the configuration file /etc/default/keyboard is defined as ... . Please choose whether you want to keep it. If you choose this option, no questions about the keyboard layout will be asked and the current configuration will be preserved." OK, but it seems if we answer 'yes' then maybe we are missing out on an update to an even better configuration. And also staying 'subscribed' for future updates. And if we answer 'no' then maybe vooosh... our keyboard gets turned off, forever, who knows. And maybe we are using an unsupported_config_layout and should 'get back on the bandwagon' via answering 'no'... who knows.
Bug#698491: closed by Andreas Glaeser (old report done)
I hope the main focus of everything is memory sticks these days.
Bug#780011: say what --install does
Package: busybox $ busybox #or $ busybox --help should say what --install and --list do, as there is no way to cautiously find out when offline. I was going to report this upstream, but there are big browser warnings about https certificate expired on their site. Version 1.23. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87zj7om1cc@jidanni.org
Bug#757316: whole disk one big partition is a bad default
Well OK, I hope they will mostly make swap. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87siji3shh@jidanni.org
Bug#762426: setup.exe does work, it just pops up an extra browser window
Package: installation-guide Severity: wishlist Regarding ! 5.1.2. Booting from Windows ! ! To start the installer from Windows, you can either ! ! obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in Section 4.1, “Official Debian GNU/Linux CD/DVD-ROM Sets” respective Section 4.3, “Preparing Files for USB Memory Stick Booting” or ! ! download a standalone Windows executable, which is available as tools/win32-loader/stable/win32-loader.exe on the Debian mirrors, ! ! If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing setup.exe. ! ! After the program has been started, a few preliminary questions will be asked and the system will be prepared to reboot into the Debian GNU/Linux installer. Please change that last line to: After the program has been started, a few preliminary questions will be asked and then a browser (Internet Explorer) will be launched with some documentation, whereupon the user should note the program didn't fail!: _there are remaining questions in their window that are still there_ and can be selected from the bar at the bottom of the screen and then only after filling them all out the system will be prepared to reboot into the Debian GNU/Linux installer. At least that's how it was when I used a 2010 installation disk I had lying around last week. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87r3z4p1wj@jidanni.org
Bug#757316: whole disk one big partition is a bad default
1% would be fine... Else one day when they e.g., want to upgrade from ext4 to ext5 etc. and face http://www.debian-administration.org/article/643/Migrating_a_live_system_from_ext3_to_ext4_filesystem and end up with Kernel panic – not syncing Attempted to kill init when something goes wrong. All because they had no more room to copy /sbin etc. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87oavwe90n@jidanni.org
Bug#757316: whole disk one big partition is a bad default
Package: debian-installer Please do not make the default for beginners making the whole disk one big partition anymore. Just leave a little free space just in case... You never know when they might need to tune their unmounted file system etc... -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87fvh8olhe@jidanni.org
Bug#427939: mention discover1/discover difference in Descriptions
Package: discover1 Version: 1.7.21 Severity: wishlist May I suggest putting something about the difference between discover1 and discover in the package Descriptions, and not wait until the user has installed the package only to find in the Readme: Discover 1.5 has only minimal support for kernel 2.6 (see below). As discover 2.0 is now in Debian (package discover), you're probably better off using this package if you run on 2.6. Mention it in both packages and both library and data packages' Descriptions. (Or else we think "1" must be better than "", but then the libraries are "2" must be better than "1".) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389890: discover: deprecated PCMCIA ioctl usage
Package: discover1 Version: 1.7.18 Severity: normal File: /sbin/discover saw in dmesg: pcmcia: Detected deprecated PCMCIA ioctl usage from process: discover. pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new t ools. pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Changing the wording of countrychooser main question
> "Choose a country, territory or area:" How about just one of "Choose a territory:" or "Choose an area:" or "Choose a region:"? One size fits all. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
why must Debian call Taiwan a "Province of China"?
Why why must Debian call Taiwan a "Province of China"? Why can't it just stick with a neutral "Taiwan". Why single out a geographical name and append a political statement to it? Sticks out and looks kind of silly. Who cares what the two governments' official names for Taiwan are. Why thrust Debian into politics, where there was no big problem before? Anything more neutral than just "Taiwan"? I'm all ears. Oh great, poison energetic free software enthusiasts with politics. How am I going to explain to folks here in Taiwan that that is just a superficial or temporary part of Debian, or doesn't represent the view of all of Debian? Oh great, just after we moved everybody over from Redhat because of the flag issue. Anyway, my buddy Andrew Lee sent me this for me to proofread, but instead I felt I'll just post it more widely for him, (naturally before researching the issue further :-)) Hi Dan, I don't know have you heard about the Debian-installer use China replace Taiwan for the menu of language chooser, I felt it's such a Discrimination Against us. Here I want to speak up on the Debian list, before I speak up, I hope you can readjust my point of view to be more fairly to both side. Thanks in advance. Here is the mail: Hi Herbert Xu, I read your message from: http://lists.debian.org/debian-boot/2004/debian-boot-200404/msg00342.html Please do not say it'd be much better if you didn't use Debian at all to anybody. Debian is a free software and it is likely everyone can use it with freedom. It would be in doubt if Debian is not allowed to be use at all. As we all in the group of Debian developer and understand how it was been use for all this days. Debian is free for everyone, and it should be No Discrimination Against Persons or Groups. I respect you are a Debian developer, but I am wishing you have same equally respect to other Debian users, contributers and developers. However, there is no rules against us to continue us using Debian software for such uncertain law. I heard of that Debian-installer choose a list of ISO-3166 codes for list contry names during installation, I felt the decision are quite wrong, even you guys calling it's "most official" and don't want to face to the truth, the truth are always still only one there. My dad and my mum are both migrate from mainland China a half century ago, and I was born in Taiwan, and I am living in Taiwan, my country is officially naming "Republic of China" however it was and however it will, I can not change it myself how could you a foreigner do? [ Taiwan Linux Users Group ] Andrew Leehttp://wiki.debian.org.tw Winkler Partners http://www.winklerpartners.com My [EMAIL PROTECTED]: +886 2 2311 2345 cell: +886 968749 055 Wild at Heart Legal Defense Association http://ecosophy.org More from me, Dan Jacobson: next thing you know, we'll need a non-China in addition to non-US. I'm big on standards: http://jidanni.org/lang/pinyin/ , but what if Debian appended statements to each land like that? What, will Debian lose some "contracts"? Maybe there could be a political-correctness package that could adjust Debian for use in each country as needed. But apparently they are talking about names one sees before even installing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: during boot, penguin's colors go wacko
Well, if it's a known issue, fix it fast because "customers" are getting the "I knew it, Linux is broken" message within 30 seconds of encountering linux. And of course "the geeks don't see the problem" with it nor their geeky pencil protectors, etc. OK, geeky compromise: replace it with the ANSI graphics penguin until you fix the problem. -- http://jidanni.org/ Taiwan(04)25854780 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
during boot, penguin's colors go wacko
Booting woody, after the computer boots a bitmapped penguin appears above the "dmesg" messages. But halfway through those messages the penguin's colors "go wacko". Maybe this is on purpose, an art effect. Do others see this? -- http://jidanni.org/ Taiwan(04)25854780 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "for installation instructions see www.debian.org"
Ch> Having said that, the instructions are in the install directory on Ch> the CD, which is where you'd have to look for the installer Ch> program anyway. And the README.txt in the root directory includes Ch> the location of the instructions. I guess you could blindly boot Ch> with the CD in the drive without reading the instructions first on Ch> some platforms, however. Yes, at the install fest we were told to take these disks home and boot from the first one. Or must you assume one's computer must have some previous operating system to enable one to poke around the CDs... hmmm, never mind that. Anyway, we pop in the debian CD and hit reboot expecting our new Debian lives to begin... only to be told that even though we have 8 whole CDs there are still some fragments we are missing -- the instructions! So we trundle down the mountain back to the lab to connect to www.debian.org to get outdated instructions for our woody CDs... Anyway, alls you gots to do is, during those installation screens, when it gets to the part saying to go to www.debian.org to get instructions, mention also "by the way, also look first on your installation CD, floppy, etc.! The instructions are probably right there too!" -- http://jidanni.org/ Taiwan(04)25854780 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
woody installation script first impressions
Dan Jacobson reflects on his brush with the 8 debian woody CDs:
When one installs from the CD's one is directed to www.debian.org for
instructions from one of those installation screens... one might not
notice that the instructions are right on disk... so the installation
screen should mention it. Sorry to bring this up again.
OK, I'm in install/doc/ch-preparing.en.html and it says to click
.../current/md5sum.txt but that isn't found. No, I'm not really
interested in seeing it, just wanted to inform you of a failed click
Anyway, back to what one sees with the CDs: I see mention of hitting
F3 for help on the first screen. Ok, I go there, but there is no
comforting way back to that first screen.
when one hits RET at "" it is quite disturbing to see some
stuff flash by too fast ... one wonders how could they intentionally
make me wonder and worry like this. Yes I see it is mentioned in the
instructions, but we are just reading the screens as presented and
dont see mention. Mention or no mention, it makes one think something
is wrong. Or, if you mention "never mind that" then indeed, a real
problem flitting by too fast to be read would also be assumed to just
be another one of those intentional too-fast screens.
/var/log/installer.log is a mess with all those ANSI graphic escapes.
How is one supposed to read this?
/var/lib/apt/lists/ is a mess with 171 character long file names. How
How is one supposed to read this? With some apt tool I haven't
learned yet I'm sure, but, pray tell, have you seen any other tool go
so hog wild with file names... reminds me of /c/windows/Application
Data/Identities/{1A52B6E0-D263-11D3-9BF7-AB2B6E60B450}/
which at least will fit in my emacs window.
It says one can read a page about each module... but the bsd_comp,
etc. module doesn't have a page.
I remember that I should have nls_cp950 installed to read Chinese off
MS-windows or something, but it is disturbingly not asked about while
other nls_cpXXX are . In Contents-i386.gz I see
lib/modules/2.2.20/fs/nls_cp950.o base/kernel-image-2.2.20
which I bet means it is already installed. But is would be best to
have some comforting words during installation about why one's number
isn't shown.
"Scanning CD for index files": well my CD player is 10 meters away
from my monitor. I have two CD players. I wish the install screens
would say how to put them both to work during the install process.
After the media change notice one pops in the new cd and things seem
to stall, but actually it is reading files but not saying anything,
until a few minutes later.
For my Logitech trackball I should say Intellimouse. I remember Mandrake
reminds us of this quirk, but not debian.
Configuring this and that... "remember to edit ..." it says. Good
luck remembering... maybe there should be a file presented to the
user with all the things to remember in one place after installation.
When we are going thru the installation screens it would be nice to
in a corner see a "02/47" meaning page 2 of 47 total...
--
http://jidanni.org/ Taiwan(04)25854780
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "for installation instructions see www.debian.org"
Oh and by the way, when we go to www.debian.org for installation instructions, we might be getting information that is not appropriate for the CD's at hand. E.g. at www.debian.org I see instructions for 2.2 installation, but I have 3.0 CD's. Therefore saying where to look on the CD's themselves for installation instructions is important. Dan> During woody installation I remember it says "for installation Dan> instructions see www.debian.org". Dan> You could also in addition say "or see /some/directory/html/ right on Dan> this installation CD!", as 1. we might not want to make a phone call Dan> to check instructions. 2. we might not even have a modem we might be in an isolated rural laboratory, thinking that we had all we needed with the 8 CD's before we arrived in camp. -- http://jidanni.org/ Taiwan(04)25854780 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
"for installation instructions see www.debian.org"
During woody installation I remember it says "for installation instructions see www.debian.org". You could also in addition say "or see /some/directory/html/ right on this installation CD!", as 1. we might not want to make a phone call to check instructions. 2. we might not even have a modem, nor fancier connection. 3. we wonder why, with 8 installation CD's, there is not room or forethought for putting the instructions on one of the CD's or at least mentioning where they are. If you feel this is a bug please report it in my stead. -- http://jidanni.org/ Taiwan(04)25854780 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
new debian ships with non-new emacs
The following message is a courtesy copy of an article that has been posted to gnu.emacs.bug as well. I got debian woody and emacs is 20.7. I thought debian was supposed to real advanced or something, but why old emacs? -- http://jidanni.org/ Taiwan(04)25854780 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian wwwoffle purge
>>>>> "Adam" == Adam Di Carlo <[EMAIL PROTECTED]> writes: Adam> Dan Jacobson <[EMAIL PROTECTED]> writes: >> >>>>> "Andrew" == Andrew M Bishop <[EMAIL PROTECTED]> writes: >> >> >> i noticed that a default debian instalation will purge one's cache >> >> right away... somethng to warn about say if one were to boot debian >> >> one day with a shared chache on one's main disk >> Andrew> You need to tell the Debian package maintainer, not me. >> >> OK, I hereby tell the Debian installation team. Adam> I'm confused. Purge which cache? Adam> Can someone file a bug on this? Debian's wwwoffle setup by default does regular 'wwwoffle -purge' when in these days and age, a paying by the minute modem user might as well let the disk fill up, as the big disks of today would probably wear out before filling up... I'd say don't be over helpful, and let the user deal with too many files if it becomes a problem... sort of like "no need for enforced haircuts, thanks". -- http://www.geocities.com/jidanni Tel886-4-25854780 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
debian wwwoffle purge
> "Andrew" == Andrew M Bishop <[EMAIL PROTECTED]> writes: >> i noticed that a default debian instalation will purge one's cache >> right away... somethng to warn about say if one were to boot debian >> one day with a shared chache on one's main disk Andrew> You need to tell the Debian package maintainer, not me. OK, I hereby tell the Debian installation team. Same with news expiry... sure setting limits is nice but sometimes dangerous... maybe take the passive approach and let the user deal with it one day if his disk actually fills up. -- http://www.geocities.com/jidanni Tel886-4-25854780 ¿n¤¦¥§ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Impressions on using the debian potato installation Cds
> "J" == John H Robinson, IV <[EMAIL PROTECTED]> writes: >> I use chrony on my other linux distribution. please ask the user if >> he agrees to writing the software clock to the hardware clock before >> doing this in the rc. scripts! the first time we notice it it is too >> late. J> during the install, you are asked if the real time clock is set to J> localtime or GMT. it does not actually set the hardware clock. well, I chose localtime. But in any case, at least add the warning "please note: the file /etc/init.d/hwclock.sh will copy the software clock time to the hardware clock at each shutdown of this system. If this will interfere with other timekeeping procedures you are already using, you might consider editing that file to prevent that action." >> ALT F2 shell window of ramdisk: I set set -o emacs but still couldn't >> use ^P J> the shell on the boot-floppies is ash, not bash. ash has no sense of history. J> i beleive the shell warns you of this when you start it. I think I even saw misleading $ set -o output too :-( >> v19 emacs the default?! how about a newer default J> emacs19, emacs20, and xemacs21 are all available in the potato (stable) hmm, it could have asked me 'which one would you like the command "emacs" to refer too' or something >> before writing any files on the hard disk, please ask about the time zone >> or something. the installation leaves files that seem 8 hrs younger >> than now [I'm a Taiwan localtime user ] J> time stamps are written in GMT. if you correctly answered the question J> about if the RTC is set to GMT or localtime, then the timestamps should J> be correct. well, I think lots of stuff is written to disk before that question[?], now looking at /etc/* it looks like I was installing that night, not in the daytime! Same happened with mandrake. Let's get it straight before the first file is written! I'm not to sure what is going on, but for us localtime folks that's what happens on linux installations. After the fisrt reboot one realizes the first set of files written assumed gmt or something. >> red/blue for default choice might not always work for perhaps >> color blind on your yes no questions. J> a black/white screen is also available. one of the first questions you J> are asked is color or b/w. (default is color) maybe throw in an underline or arrow or something just in case... well, I'm just thinking one day there will be a user in whose' culture certain colors have different habitual meanings... ok never mind. >> I'm actually glad that x windows isn't a requirement to run your >> installer script. J> me too. And thanks for [already] answering this... at least i know somebody's home... a basic requirement for further debian exploration confidence :-) >> no message on how to redo screwed up parts of the install from the shell J> in the install itself (before the reboot) you can go back in the menu J> and correct almost any step you might have made a mistake on. [I was thinking of for after the reboot] -- http://www.geocities.com/jidanni Tel886-4-25854780 ¿n¤¦¥§ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Impressions on using the debian potato installation Cds
sure hope non subscribers can mail to this group, and hope one day to be able to read it via nntp. also the name "boot" doesn't 100% match the description "installation' ... - Impressions on using the debian potato installation Cds --- [just me talking to me, but may be useful for improving the debian docs.] : why so many submenus with no way to back out, only one choice, "" some choices make one wonder, will choosing this cause the change right away, or am i allowed to adjust details inside that choice... if not i had better not choose it... on the very first screen, it has a button with no advice on hit SPC or RET or what... one fears a wrong hit might miss a 2nd page, etc. i switched around what cd drive i was using during the installation, so it didn't ask again abut my 2nd cd... anyway, it thinks you won't switch around or something... it didn't catch it. I use chrony on my other linux distribution. please ask the user if he agrees to writing the software clock to the hardware clock before doing this in the rc. scripts! the first time we notice it it is too late. could at least tell user '35/44 steps thru installation' or something so we have some idea on screen. 'read a page about propose of module'... not really choose path : disconcerting XF86setup: big disaster for me please when asking the user about 'initializing' disks, use the word 'format' as that better implies the danger. why not when giving the list of partitions to format, mention which ones have already been formatted. ALT F2 shell window of ramdisk: I set set -o emacs but still couldn't use ^P module selecting: yucky some grammar errors: 'make linux bootable hard disk' when debian gets larger, perhaps do the installation that doesn't need answering questions in the background at the same time as that that does? many questions aren't clear about what will happen if one hits RET only. v19 emacs the default?! how about a newer default before writing any files on the hard disk, please ask about the time zone or something. the installation leaves files that seem 8 hrs younger than now [I'm a Taiwan localtime user ] arrow keys sometimes not used by installation script. red/blue for default choice might not always work for perhaps color blind on your yes no questions. I'm actually glad that x windows isn't a requirement to run your installer script. depending on a separate installation instructions document isn't feasible well, unless you tell a user how to see it at the same time on ALT F4 etc. windows. entering passwds: no echo *** chars: bad no message on how to redo screwed up parts of the install from the shell -- http://www.geocities.com/jidanni Tel886-4-25854780 ¿n¤¦¥§ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
