Kickstart install: what disk name should I tell Anaconda to use? (Installer running from USB thumb drive.)

I’m running the CentOS 7.6 installer from a USB thumb drive using a kickstart file. I’m installing to a system that has only one disk.

In the bash shell of the installer, my system’s hard drive shows up as /dev/sdb. The installer sees the USB drive it booted from as /dev/sda. Should I be telling Anaconda to use /dev/sdb? Seems like a bad idea.

When building a custom CentOS 7.6 iso I end up with an image that is unbootable from USB thumb drive

balenaEtcher says my image file is not bootable and it’s right. When I mkisofs I see what look like errors such as

Using ABRT_003.RPM;1 for  ./Packages/abrt-addon-xorg-2.1.11-52.el7.centos.x86_64.rpm (abrt-addon-kerneloops-2.1.11-52.el7.centos.x86_64.rpm) Using ABRT_004.RPM;1 for  ./Packages/abrt-addon-kerneloops-2.1.11-52.el7.centos.x86_64.rpm (abrt-addon-pstoreoops-2.1.11-52.el7.centos.x86_64.rpm) Using ABRT_005.RPM;1 for  ./Packages/abrt-addon-pstoreoops-2.1.11-52.el7.centos.x86_64.rpm (abrt-addon-python-2.1.11-52.el7.centos.x86_64.rpm) Using 389_D000.RPM;1 for  ./Packages/389-ds-base- (389-ds-base-libs- 

This started happening today when I started using CentOS-7-x86_64-DVD-1810.iso. I’m pretty sure I was using CentOS-7-x86_64-Minimal-1810.iso and had an easy time building bootable isos.

Am I building using the wrong tool? mkisofs not good for DVD builds? Using

mkisofs -o /tmp/656.iso -b isolinux/isolinux.bin -c isolinux/ –no-emul-boot –boot-load-size 4 –boot-info-table -joliet-long -R -V “RHEL-7.3\x20Server.x86_64” .

These builds finish without printing actual errors. /bin/file says
“ISO 9660 CD-ROM filesystem data ‘RHEL-7.3\x20Server.x86_64’ (bootable)”
The iso is 4.3G.

I hate wasting DVDs so I’m writing to USB stick. Maybe that’s the problem.

Is there a rule of thumb for whether I should hide the navigation menus on scroll?

I’m working on an Android app, and I’ve implemented layout behavior to hide the top app bar and the bottom navigation menu on scrolling a list page.

At the moment, I just did it because I could and it seemed like a nice-to-have for the software architecture from a developer’s perspective, which I realize is often at odds with UI and UX.

I’ve gone through hundreds of mobile app UI and interaction designs on Dribbble and I haven’t been able to figure out a pattern to when this scrolling behavior is used yet.

Could someone please provide their decision making process when it comes to whether the bottom navigation menu should be hidden on scroll or persistent?

My app will have 5 different top-level pages that can be reached from the bottom navigation menu. It’s likely that any list in these pages will have about 2 full mobile screen lengths of content at most, which is what made me question whether I was really doing the right thing.

Some of the questions I ran into are below.

  • Is this generally a UI pattern best served for infinite scrolling apps or does it have its uses for smaller static lists as well?
  • Should I hide both the top bar and bottom navigation menu? Or keep the bottom navigation menu and only hide the top bar?
  • I’ve noticed a lot of the really visually appealing designs have a persistent top bar. Is this a sentiment shared by others or is it just me? It seems like it’s easier to make a page look good when the toolbar and navigation menus are static, while hiding them only leaves a boring looking list to look at.
  • Is there a minimum amount of data you require before using this pattern? e.g. I have a page with about 15 list items, that might not require this pattern. However, the search functionality on this page looks for data one level deeper which can result in a 100 items. Would you then implement this pattern for both the list and search results? Or just the search results? Or not at all for both cases?
  • With mobile screens getting larger, will this pattern become less beneficial or are there still other advantages regardless of screen size?

I don’t really need answers to every one of these questions, but I’d really love to know the thought process that goes into navigation menus and scrolling decisions.