bug#28912: chmod (2) – Issues report

2017-10-20 Thread Ricky Tigg
>From the followings inputs it should be expected to produce regarding the
input format either error or a warning messages. As empty sets all the
input tests have been conducted.


Format of input that were validated with no kind of message from coreutils:

# chmod [ugoa][+-=][rwxXst] 


[ugoa] – all parameter combinations with no length restriction or an empty
parameter are allowed.

[=+-] – all parameter combinations with no length restriction are allowed.

[rwxXst] – no value has to be specified.


Steps to Reproduce:

1. Open a terminal, log in as root and move to the folder containing the
target file for testing purpose.


2. For testing purpose as well input has to meet that condition: After the
symbolic mode parameter [+-=]  the set of permissions that should be
added/removed must not be specified which means has to be left empty.


Examples of such validated combinations of format:

# chmod o- 

# chmod + 

# chmod agogagagouugogogaauagooaguaguououau=+++==-----



… and so on.



Note:


Web sites that TLS protocols are systematically better ranked by the major
www search engines which may not be trivial in a competitive environment
for publicity.


On Linux in terminal, by invoking "man chmod 2" it is noticeable from the
output that links related to internet sites are mentioned without HTTPS
format while they are currently available:

“GNU coreutils online help: 

Report chmod translation bugs to ”


The above mentioned knowledge in consideration, should reasonably be enough
to motivate the update of the documentation with proper updated links.


bug#28914: chmod (2) – Issues report

2017-10-20 Thread Ricky Tigg
Current issue was also reported as Bug 1504053
 and closed by someone
not at the right place as notabug.


bug#33622: coreutils v. 8.30 – Tail prints the first row in 'tail -n '

2018-12-05 Thread Ricky Tigg
OS: *Fedora*. Component: coreutils.x86_64 8.30-6.fc29 @System

Tail prints the first row in 'tail -n '

Command executed:
$ dnf repoquery --requires bash --recursive --resolve | grep -E
'.x86_64$|.noarch$' | tail -n 1
Last metadata expiration check: 0:28:25 ago on Wed Dec  5 11:09:16 2018.
tzdata-0:2018g-1.fc29.noarch

Expected result: command to only print N rows, which means without printing
the first row.


bug#33823: coreutils v.8.30 – Command, pasted from text editor to GUI terminal, not displayed though applied

2018-12-21 Thread Ricky Tigg
Component: coreutils.x86_64  8.30. Observation not reported at pixelbeat.org
.

Command executed in *GUI terminal* (*Gnome terminal*):
$ cat > 1
A

End file (*Ctrl D*) after 'A'. Copy from terminal both previous input and
output as pattern
'cat > 1
A'

Paste it to a text editor keeping a *mono-space* font as font applied to
text.
>From text editor copy that same pattern.
Paste it into terminal as new command.
Press *Enter*-key.
End file (*Ctrl D*).

Results in terminal are:
$ cat > 1

$ cat 1
A

Pasted text content 'A' is not exhibited. Thought once queried it does
exist. Probably a bug. Regards, R.T.


bug#33824: coreutils v.8.30 – An expression part of a cat command is interpreted as "ambiguous redirect" when applied to a target.

2018-12-21 Thread Ricky Tigg
Component: coreutils.x86_64  8.30. Observation not reported at pixelbeat.org
.

Command executed:
$ cat a* >> b*
bash: b*: ambiguous redirect

Thought the same syntax is used with success when applied only to source
files:
$ cat a* >> b
$

Probably a bug. Regards, R.T.


bug#33823: coreutils v.8.30 – Command, pasted from text editor to GUI terminal, not displayed though applied

2018-12-23 Thread Ricky Tigg
Thanks.

su 23. jouluk. 2018 klo 6.54 Assaf Gordon (assafgor...@gmail.com) kirjoitti:

> tags 33823 notabug
> close 33823
> stop
>
> Hello,
>
> On 2018-12-21 8:06 a.m., Ricky Tigg wrote:
> >
> > Paste it to a text editor keeping a *mono-space* font as font applied to
> > text.
> >  From text editor copy that same pattern.
> > Paste it into terminal as new command.
> > Press *Enter*-key.
> > End file (*Ctrl D*).
> >
> [...]
>
> > Pasted text content 'A' is not exhibited. Thought once queried it does
> > exist. Probably a bug.
>
> This might be a bug in your terminal or a configuration
> issue in the clipboard of your X system - but it is not a bug
> in coreutils (the cat(1) program did what you asked it to do).
>
> As such I'm closing this as "notabug", but discussion can continue by
> replying to this thread.
>
>
> -assaf
>


bug#34115: coreutils v. 8.30– Document's content gets deleted using cat(1)

2019-01-17 Thread Ricky Tigg
Hi. On *Fedora Desktop 29*,  using *GNU bash*, v. 4.4.23(1), in a *GUI*
terminal emulator – *gnome-terminal* was used – under your home directory,
create if not present file *.inputrc* a follow:

$ cat > .inputrc
set enable-bracketed-paste on

Press *Return*, then *Ctrl D*.

$ cat .inputrc
set enable-bracketed-paste on

*Copy* the first two-lined command at once then *paste* it into a *GUI*
text editor – *Gedit* was used –. .Log out from the terminal's session,
then log in as same user. Results are:

$ cat > .inputrc
set enable-bracketed-paste on
$ cat .inputrc
$

Content of *.inputrc*,  which is expected to be still present, has been
deleted.
Regards.


bug#34309: coreutils v. 8.30 – Output ignores paths specified.

2019-02-04 Thread Ricky Tigg
bash v.4.4.23. Output ignores paths specified.Commands executed:

$ df -h
FilesystemSize  Used Avail Use% Mounted on
devtmpfs  1.9G 0  1.9G   0% /dev
tmpfs 1.9G   90M  1.8G   5% /dev/shm
tmpfs 1.9G  1.8M  1.9G   1% /run
tmpfs 1.9G 0  1.9G   0% /sys/fs/cgroup
/dev/mapper/fedora-juuri   18G  7.2G  9.6G  43% /
tmpfs 1.9G   16K  1.9G   1% /tmp
/dev/mapper/fedora-koti   894G  6.9G  842G   1% /home
/dev/sda1 976M  221M  689M  25% /boot
tmpfs 374M   44K  374M   1% /run/user/1000
/dev/sdc1 7.3G   34M  6.9G   1% /run/media/yk/USB

$ df -h /run/media/
Filesystem  Size  Used Avail Use% Mounted on
tmpfs   1.9G  1.8M  1.9G   1% /run

Expected result: since path '/run/media/' had been specified, a correct
whole output would be

/dev/sdc1 7.3G   34M  6.9G   1% /run/media/yk/USB


bug#34345:

2019-02-09 Thread Ricky Tigg
Covered object by values '1994 s', '2014.25 s' seems to be a unique
time elapsed. Those values can therefore be expected to be identical,
either '1994 s' or '2014.25 s' – 2014 s and 25 hundredths of s –.


bug#34487: dd (coreutils) 8.30 – A written ISO image cannot not be booted from BIOS

2019-02-15 Thread Ricky Tigg
Hi. An ISO image cannot not be booted from BIOS

Initial device state:
# parted /dev/sdc unit s print free
Model: (...) (scsi)
Disk /dev/sdc: 15638480s
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End   SizeType   File system   Flags
   2s15638479s 15638478s  Free Space

Then commands executed were (Note: a non-live ISO image is involved):

# dd if=debian-9.7.0-amd64-DVD-3.iso of=/dev/sdc bs=4M oflag=direct && sync
$ df -hT | tail -n1
/dev/sdciso9660   4.4G  4.4G 0 100% /run/media/yk/Debian 9.7.0
amd64 3
# parted /dev/sdc unit s print free
Error: /dev/sdc: unrecognised disk label
Model: (...) (scsi)
Disk /dev/sdc: 15638480s
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

That dd command was also executed without option/parameter 'oflag=direct'.
but final result remained identical. I could notice that *dd* erased
existent *partition table* and didn't add flag *boot.* Once at last the
system was rebooted, then proper device selected from BIOS , the following
message was produced:

> *Reboot and select proper boot device or insert boot media in selected
> boot device and press a key.*
>


bug#34487:

2019-02-15 Thread Ricky Tigg
That's was just a *live image* that was required, The equivalent of the
present CD/DVD's ISO was then *debian-live-9.7.0-amd64-gnome.iso*.


bug#37062: Changes set are no applied to a locally plugged external device

2019-08-17 Thread Ricky Tigg
Component under* Linux Fedora*: coreutils.x86_64   8.31-2.fc30  @updates

Changes set are no applied to a locally plugged external device

Commands executed:
# whoami
root
# cd /run/media/yk/maxell/Varmuuskopiot/Fedora/
# chown -R root:citser ../Fedora/ && chmod -R 750 ../Fedora/
# ls -l ../; ls -l
[...]
drwxrwxrwx. 1 yk yk  440 16. 8. 23:32 Fedora
[...]
-rwxrwxrwx. 1 yk yk 155 16. 8. 23:32 config

As noticeable owner and groups mentions are both yk while they respectively
should be root, citser.


bug#37062:

2019-08-19 Thread Ricky Tigg
Hey. Partition is with its default settings.

$ mount | fgrep /run/media/$USER
/dev/sdc1 on /run/media/yk/maxell type fuseblk
(rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
$ lsblk -bo name,maj:min,fstype,mode,type,mountpoint,tran
NAMEMAJ:MIN FSTYPE  MODE   TYPE MOUNTPOINT
 TRAN
[...]
sdc   8:32  brw-rw disk
usb
└─sdc18:33  ntfsbrw-rw part /run/media/yk/maxell


bug#41792: dd function – message: "No boot sector on USB device""

2020-06-10 Thread Ricky Tigg
*Component*: coreutils.x86_64  8.32-4.fc32.; *OS*: Linux Fedora

Source of file:
https://www.microsoft.com/en-us/software-download/windows10ISO

Disc image file
- checked against its SHA-256 checksum was correct
- written successfully with that command:
# dd if=Win10_2004_Finnish_x64.iso of=/dev/sdc bs=4M oflag=direct
status=progress && sync

Once written, the partition is as follows:
$ mount | fgrep /run/media/$USER
/dev/sdb on /run/media/yk/CCCOMA_X64FRE_FI-FI_DV9 type udf
(ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2)

While the USB device was booted in BIOS, the following message was
produced  "*No boot sector on USB device*"".

Using *Gparted*, while the device's partition was unmounted, the flags
could not be managed thus no boot flag was added. The following warning was
present:
*2.66 GiB of unallocated space within the partition.*


bug#41792: dd function – message: "No boot sector on USB device"

2020-06-10 Thread Ricky Tigg
$ file -b Win10_2004_Finnish_x64.iso
ISO 9660 CD-ROM filesystem data 'CCCOMA_X64FRE_FI-FI_DV9' (bootable)


bug#41792: Acknowledgement (dd function – message: "No boot sector on USB device"")

2020-06-12 Thread Ricky Tigg
The difference of device path is due to the fact that the USB media was
plugged out after the write-operation was achieved on the Linux computer
then plugged into a computer –Asus– whose Windows OS has to be restored,
then plugged back to the same computer but to a *different* USB port. It's
safe to open the present issue-ticket.

*Source media*:
https://www.microsoft.com/en-us/software-download/windows10ISO

*Rufus v4.1.4* – I couldn't use it since The Windows OS installed is
missing some system's files. Will convert it to fit on Fedora at release of
version 33 which will update the uniformly mingw component and thus
mingw64-headers which is old and is the cause of a known issue.

I wrote the disc image as well using those tools then booted the USB device
having the disc image written on.:

*Fedora Media Writer v4.1.4* – Officially does not support Microsoft
Windows disc images. I did not know that before writing.

*Unetbootin v677* – It writes partially the disc image thus the installer
is operational partially. Issue was already reported by someone on Git.

*Woeusb v3.3.1* – Installer is operational on BIOS but not on EFI systems.
Issue was already reported by someone on Git.

*Balena Etcher v1.5.9*8 x64 as AppImage format – The device is not listed
at boot.

ke 10. kesäk. 2020 klo 18.51 GNU bug Tracking System (help-debb...@gnu.org)
kirjoitti:

> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  bug-coreutils@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 41...@debbugs.gnu.org.
>
> Please do not send mail to help-debb...@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 41792: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=41792
> GNU Bug Tracking System
> Contact help-debb...@gnu.org with problems
>


bug#49335: v.8.32 - stat(1) | Symbolic link interpreted as hard link

2021-07-02 Thread Ricky Tigg
Hello, symbolic link counted as hard link. To reproduce:

$ touch t; ln -sr t l; stat -c '%i %h %n %F' t l
4172493 1 t regular empty file
4172494 1 l symbolic link

'%h' reports *1* despite no hard link is involved. Isn't rather *0*
expected?


bug#49381: v.8.32 – du(1) | Calculating the total size of files | One file covered instead of all

2021-07-04 Thread Ricky Tigg
*OS:* Fedora; Tested in Bash v.5.1.

Hello. Task: Printing total size of files *alone*.
To reproduce:

$ stat -c '%i %h %s %n %F' k l
4198568 2 34 k regular file
4198568 2 34 l regular file

$ find . -type f
./k
./l

Those  'du' commands cover only one file instead of all files.

$ find . -type f -exec du -acb {} +
34 ./k
34 total

$ find . -type f -print0 | du --files0-from=- -cb
34 ./k
34 total

Isn't rather *68* expected?


bug#63968: 'ls' prints in columns

2023-06-09 Thread Ricky Tigg
coreutils v.: *9.1*
OS: *Fedora*
Shell: *Bash v. 5.2.15*

Hello.

Steps to reproduce:

$ cd /etc/yum.repos.d/
$ sudo rm .repo
$ ls

Files are now printed in columns.


bug#68892: 'tr' function | Outputs printed before the command prompts

2024-02-02 Thread Ricky Tigg
OS: Fedora v86_64. coreutils v.: 9.3. Shell: bash v. 5.2.26.

Hello. Normally outputs are printed after the command prompt; "#" "$" on my
system.

(...)@(...):~$ rpm -ql coreutils | head -2
/usr/bin/[
/usr/bin/arch

Unexpectedly, through a pipe invoking 'tr', outputs are printed before the
command prompts.

(...)@(...):~$ rpm -ql coreutils | head -2 | tr '\n' ' '
/usr/bin/[ /usr/bin/arch (...)@(...):~$

Regards.