SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Tested on -current as of Mon Jun 13 07:07:39 UTC 2016; builds and installs fine. For changed files in the package see attached diff. KDE seem to work well.
Already included.
And on that note, consider the kernel golden. No more version bumps will be accepted unless they fix important bugs, and other bugs must be close to showstoppers for consideration at this point. I passed on "file" since it's a complex program that has been known to introduce regressions in the past and nobody could point to an important bug that's fixed by the latest version. Cheers!
When booting from a Slackware64-current install DVD and running fdisk, I type in 'm' to display the available fdisk commands.
Not all of the commands show on my screen. Some of them scroll off the top...
My screen is not able to catch all of the lines of output.
What I see is something like this:
Code:
l list known partition types
n add a new partition
p print the partition table
t change a partition type
v verify the partition table
i print information about a partition
Misc
m print this menu
u change display/entry units
x extra functionality (experts only)
Script
I load disk layout from sfdisk script file
O dump disk layout to sfdisk script file
Save & Exit
w write table to disk and exit
q quit without saving changes
Create a new label
g create a new empty GPT partition table
G create a new empty SGI (IRIX) partition table
o create a new empty DOS partition table
s create a new empty Sun partition table
Command (m for help):
But what I want to see is this:
Code:
Help:
DOS (MBR)
a toggle a bootable flag
b edit nested BSD disklabel
c toggle the dos compatibility flag
Generic
d delete a partition
F list free unpartitioned space
l list known partition types
n add a new partition
p print the partition table
t change a partition type
v verify the partition table
i print information about a partition
Misc
m print this menu
u change display/entry units
x extra functionality (experts only)
Script
I load disk layout from sfdisk script file
O dump disk layout to sfdisk script file
Save & Exit
w write table to disk and exit
q quit without saving changes
Create a new label
g create a new empty GPT partition table
G create a new empty SGI (IRIX) partition table
o create a new empty DOS partition table
s create a new empty Sun partition table
Command (m for help):
If I were new to fdisk, this would be a problem...
Last edited by aaazen; 06-16-2016 at 07:27 PM.
Reason: Brain freeze, fdisk not lilo...
Shift+PgUp should allow you to scroll up with the terminal and see anything that went off screen (as long as it is still within the terminal's buffer (I think generally 500 lines)).
Last edited by bassmadrigal; 06-16-2016 at 11:39 PM.
Reason: Fixed missing closing parenthesis
Shift+PgUp should allow you to scroll up with the terminal and see anything that went off screen (as long as it is still within the terminal's buffer (I think generally 500 lines)).
Thanks, I like this solution as it works for any program not just fdisk and it requires no code changes.
Shift+PageDown works to scroll down too. But how does a new user know this?
Maybe this information can be put in one of the startup screens...
Thanks, I like this solution as it works for any program not just fdisk and it requires no code changes.
Shift+PageDown works to scroll down too. But how does a new user know this?
Maybe this information can be put in one of the startup screens...
While I agree that many may not know this really helpful feature, there's a lot of other relatively unknown features that many should probably know. This would likely lead to what would eventually become a massive document with all the cool nifty features that are available. Personally, I wouldn't know where to draw the line...
Is there any reason to not upgrade findutils to version 4.6.0 ?
I ask for this because find (4.4.2) emits a warning as below unless I pass the option -noleaf :
Code:
$ find / -iname lilo.conf
/etc/lilo.conf
WARNING: Hard link count is wrong for `/proc/fs' (saw only st_nlink=8 but we already saw 6 subdirectories): this may
be a bug in your file system driver. Automatically turning on find's -noleaf option. Earlier results may have failed
to include directories that should have been searched.
$ find / -iname lilo.conf -noleaf
/etc/lilo.conf
Notes:
* find 4.6.0 does not emit this warning, even when the option -noleaf is not used.
* I found this bug report in which that kind of issue is reported.
Notes:
* find 4.6.0 does not emit this warning, even when the option -noleaf is not used.
I've had a SlackBuild for this here since it came out, but it hits an error in the docs and the compile fails. Anyway, it's a little too late to take a chance on breaking find to try to eliminate a warning.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
