STOP mailing list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Send users mailing list submissions to
> 	users@xxxxxxxxxxxxxxxxxxxxxxx
>
> To subscribe or unsubscribe via email, send a message with subject or
> body 'help' to
> 	users-request@xxxxxxxxxxxxxxxxxxxxxxx
>
> You can reach the person managing the list at
> 	users-owner@xxxxxxxxxxxxxxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of users digest..."
>
> Today's Topics:
>
>    1. Re: Output text color (was dnf list color bad) (Samuel Sieb)
>    2. Bootable USB and a Windows ISO-file (Robin Lee)
>    3. Re: Bootable USB and a Windows ISO-file (Samuel Sieb)
>    4. Re: Bootable USB and a Windows ISO-file (Robin Lee)
>    5. Re: Bootable USB and a Windows ISO-file (Samuel Sieb)
>    6. Re: Output text color (was dnf list color bad) (Beartooth)
>    7. Re: Output text color (was dnf list color bad) (Samuel Sieb)
>
>
> ----------------------------------------------------------------------
>
> Date: Sun, 5 Jul 2020 11:43:01 -0700
> From: Samuel Sieb <samuel@xxxxxxxx>
> Subject: Re: Output text color (was dnf list color bad)
> To: users@xxxxxxxxxxxxxxxxxxxxxxx
> Message-ID: <d4be6549-3280-da0d-903f-bff1585845d8@xxxxxxxx>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> On 7/5/20 10:52 AM, Beartooth wrote:
>> On Sun, 05 Jul 2020 12:59:10 -0400, Todd Zullinger wrote:
>> 	[....]
>>> I'm pretty sure those are in /etc, not /etc/dnf.  If they're in the
>>> latter, can you confirm that and check what package provides them (rpm
>>> -qf /etc/dnf/DIR_COLORS*)?  I don't see anything providing them.
>>
>> 	You're right. My bad. They're in /etc. And I get # rpm -qf /etc/
>> dnf/DIR_COLORS*
>> error: file /etc/dnf/DIR_COLORS*: No such file or directory
>
> But this is the wrong file anyway.  The configuration for dnf colors is
> in /etc/dnf/dnf.conf.  See "man dnf.conf" for details, see the section
> under "[MAIN] OPTIONS - COLORS".
>
>> 	Am I remembering wrong? Istr that I could tell a given machine
>> *once* that I want to see dot files, and it would *always* display them.
>
> I don't know how you would do that.  Maybe there's a config for ls or
> you can add "-a" to the ls alias.
>
>>> After you edit it, you must source /etc/profile.d/colorls.sh to pick up
>>> the changes.
>>
>> 	"source" is a verb?? Sorry -- you lost me. What does it mean?
>
> There's a bash command called "source" that executes the script file in
> the current context.  That means that any environment variables that are
> set will stay in effect.
>
>>> You can also copy the proper DIR_COLORS* file to your home dir to avoid
>>> having a clean install overwrite your changes in /etc.  The paths which
>>> the colorls.sh script uses are:
>>>
>>>      $HOME/.dir_colors.$TERM $HOME/.dircolors.$TERM $HOME/.dir_colors
>>>      $HOME/.dircolors
>>>
>>> The first one found is used.
>>
>> 	Sigh. The curse of the autodidact strikes again. I know that
>> "HOME" in all upper case has a standard meaning, and I suppose "TERM"
>> must, too. But I can never remember what it is, nor where to look it up.
>
> Those are environment variables.  "HOME" contains the current home
> directory and "TERM" contains the name of the current terminal emulation.
>
> ------------------------------
>
> Date: Sun, 05 Jul 2020 21:01:11 +0200
> From: Robin Lee <robinlee@xxxxxxxxxxx>
> Subject: Bootable USB and a Windows ISO-file
> To: users@xxxxxxxxxxxxxxxxxxxxxxx
> Message-ID:
> 	<06f83eb8b1df03e25b0dbd10876b74fb40ddb015.camel@xxxxxxxxxxx>
> Content-Type: text/plain; charset="UTF-8"
>
> I'm trying to do a very simple task on my Fedora 32 desktop but somehow
> I can't make it happen.
>
> I've downloaded a Windows installer ISO-file from microsoft.com that I
> put on a USB-stick and tried to install Windows on physical machine,
> but it won't boot from the USB. It shows up in the BIOS boot menu, but
> it won't boot.
>
> I've tried to install the same ISO-file in Boxes and that went fine.
> I've tried both Brasero and Disk Image Writer, I've tried two different
> USB-sticks and two different physical target machines.
>
> What am I doing wrong? Or is this nefarious scheming by Linux to stop
> people from experimenting with alternative operating systems?
>
> ------------------------------
>
> Date: Sun, 5 Jul 2020 12:21:07 -0700
> From: Samuel Sieb <samuel@xxxxxxxx>
> Subject: Re: Bootable USB and a Windows ISO-file
> To: users@xxxxxxxxxxxxxxxxxxxxxxx
> Message-ID: <fdbec98f-6201-af8c-2350-eef4d576e163@xxxxxxxx>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> On 7/5/20 12:01 PM, Robin Lee wrote:
>> I've downloaded a Windows installer ISO-file from microsoft.com that I
>> put on a USB-stick and tried to install Windows on physical machine,
>> but it won't boot from the USB. It shows up in the BIOS boot menu, but
>> it won't boot.
>>
>> I've tried to install the same ISO-file in Boxes and that went fine.
>> I've tried both Brasero and Disk Image Writer, I've tried two different
>> USB-sticks and two different physical target machines.
>
> Boxes will make it a DVD drive, not USB.
>
> Isn't Brasero only for writing to optical media?  Anyway, I would just
> use dd to write it to the flash drive.
>
> In a terminal (change sdc to whatever your flash drive is):
> sudo dd if=windows.iso of=/dev/sdc bs=1M status=progress
>
> ------------------------------
>
> Date: Sun, 05 Jul 2020 21:48:03 +0200
> From: Robin Lee <robinlee@xxxxxxxxxxx>
> Subject: Re: Bootable USB and a Windows ISO-file
> To: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx>
> Message-ID:
> 	<27bead4367d17c11fa3805c3255d0bdff2570f07.camel@xxxxxxxxxxx>
> Content-Type: text/plain; charset="UTF-8"
>
> On Sun, 2020-07-05 at 12:21 -0700, Samuel Sieb wrote:
>> On 7/5/20 12:01 PM, Robin Lee wrote:
>> > I've downloaded a Windows installer ISO-file from microsoft.com
>> > that I
>> > put on a USB-stick and tried to install Windows on physical
>> > machine,
>> > but it won't boot from the USB. It shows up in the BIOS boot menu,
>> > but
>> > it won't boot.
>> >
>> > I've tried to install the same ISO-file in Boxes and that went
>> > fine.
>> > I've tried both Brasero and Disk Image Writer, I've tried two
>> > different
>> > USB-sticks and two different physical target machines.
>>
>> Boxes will make it a DVD drive, not USB.
>>
>> Isn't Brasero only for writing to optical media?  Anyway, I would
>> just
>> use dd to write it to the flash drive.
>>
>> In a terminal (change sdc to whatever your flash drive is):
>> sudo dd if=windows.iso of=/dev/sdc bs=1M status=progress
>
> Same result.
>
> Also tested creating a bootable USB-stick with a Centos ISO-file. No
> problem.
>
> ------------------------------
>
> Date: Sun, 5 Jul 2020 12:51:18 -0700
> From: Samuel Sieb <samuel@xxxxxxxx>
> Subject: Re: Bootable USB and a Windows ISO-file
> To: users@xxxxxxxxxxxxxxxxxxxxxxx
> Message-ID: <aa25c71f-54b1-bfd8-988b-6f66ef9747fc@xxxxxxxx>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> On 7/5/20 12:48 PM, Robin Lee wrote:
>> On Sun, 2020-07-05 at 12:21 -0700, Samuel Sieb wrote:
>>> On 7/5/20 12:01 PM, Robin Lee wrote:
>>>> I've downloaded a Windows installer ISO-file from microsoft.com
>>>> that I
>>>> put on a USB-stick and tried to install Windows on physical
>>>> machine,
>>>> but it won't boot from the USB. It shows up in the BIOS boot menu,
>>>> but
>>>> it won't boot.
>>>>
>>>> I've tried to install the same ISO-file in Boxes and that went
>>>> fine.
>>>> I've tried both Brasero and Disk Image Writer, I've tried two
>>>> different
>>>> USB-sticks and two different physical target machines.
>>>
>>> Boxes will make it a DVD drive, not USB.
>>>
>>> Isn't Brasero only for writing to optical media?  Anyway, I would
>>> just
>>> use dd to write it to the flash drive.
>>>
>>> In a terminal (change sdc to whatever your flash drive is):
>>> sudo dd if=windows.iso of=/dev/sdc bs=1M status=progress
>>
>> Same result.
>>
>> Also tested creating a bootable USB-stick with a Centos ISO-file. No
>> problem.
>
> Maybe that file can't be booted from usb.  Are there any instructions
> from Microsoft about how to do it?  I know I have done it a couple of
> times in the past.
>
> ------------------------------
>
> Date: Sun, 5 Jul 2020 19:58:09 -0000 (UTC)
> From: Beartooth <Beartooth@xxxxxxxxxxx>
> Subject: Re: Output text color (was dnf list color bad)
> To: users@xxxxxxxxxxxxxxxxxxxxxxx
> Message-ID: <rdtbch$2i6$3@xxxxxxxxxxxxx>
> Content-Type: text/plain; charset=UTF-8
>
> On Sun, 05 Jul 2020 11:43:01 -0700, Samuel Sieb wrote:
> 	[....]
>> But this is the wrong file anyway.  The configuration for dnf colors is
>> in /etc/dnf/dnf.conf.  See "man dnf.conf" for details, see the section
>> under "[MAIN] OPTIONS - COLORS".
>
> 	Well, as /etc/dnf/dnf.conf I see only this:
>
> [main]
> gpgcheck=1
> installonly_limit=3
> clean_requirements_on_remove=True
> best=False
> skip_if_unavailable=True
>
> 	I'll make a separate post for the rest, with effusive thanks for
> the clarifications.
> --
> Beartooth Staffwright, Not Quite Clueless Power User
> Remember I know little (precious little!) of where up is.
>
> ------------------------------
>
> Date: Sun, 5 Jul 2020 13:01:44 -0700
> From: Samuel Sieb <samuel@xxxxxxxx>
> Subject: Re: Output text color (was dnf list color bad)
> To: users@xxxxxxxxxxxxxxxxxxxxxxx
> Message-ID: <d3739daf-bf3f-42cb-845f-caf6aa64bdfe@xxxxxxxx>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> On 7/5/20 12:58 PM, Beartooth wrote:
>> On Sun, 05 Jul 2020 11:43:01 -0700, Samuel Sieb wrote:
>> 	[....]
>>> But this is the wrong file anyway.  The configuration for dnf colors is
>>> in /etc/dnf/dnf.conf.  See "man dnf.conf" for details, see the section
>>> under "[MAIN] OPTIONS - COLORS".
>>
>> 	Well, as /etc/dnf/dnf.conf I see only this:
>
> If you want to override the default values, you need to add them there
> as described in the man page.
>
>> 	I'll make a separate post for the rest, with effusive thanks for
>> the clarifications.
>
> Ok, if you can't figure it out, then I'll reply there.
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
>
>
> ------------------------------
>
> End of users Digest, Vol 197, Issue 34
> **************************************
>


_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux