Can't delete persistent silly fileRm can't delete fileWhy can't I delete this file as root?Can't delete a fileDelete /x02 character from a fileHow to delete a file with corrupt filename?Can I Delete 70-persistent-net.rules?Delete file based on condition

A question about the Tannaka-Krein reconstruction of finite groups

Generate an array with custom index

How does an Evocation Wizard's Overchannel ability interact with Chaos Bolt?

Rules on "Pets on shoulder"

Can I exit and reenter a UK station while waiting for a connecting train?

I'm half of a hundred

Can I use Oko's ability targetting a creature with protection from green?

Cutting a 4.5m long 2x6 in half with a circular saw

Is it okay to request a vegetarian only microwave at work ? If, yes, what's the proper way to do it?

Why is Mars cold?

Confused about the meaning of the word "open" in this sentence

Raise Error Concatenation in SQL Server

Most optimal hallways with random gravity inside?

Visualize a large int

Would a spacecraft carry arc welding supplies?

Is it really better for the environment if I take the stairs as opposed to a lift?

Why did my relationship with my wife go down by two hearts?

What would a chair for a Human with a Tail look like?

Why do baby boomers have to sell 5% of their retirement accounts by the end of the year?

When applying for a visa has there ever been a case of embassy asking for proof of right to be in the present country?

Meaning of “Bulldog drooled courses through his jowls”

How can a stock trade for a fraction of a cent?

Use GPLv3 library in a closed system (no software distribution)

Prisoner's dilemma formulation for children



Can't delete persistent silly file


Rm can't delete fileWhy can't I delete this file as root?Can't delete a fileDelete /x02 character from a fileHow to delete a file with corrupt filename?Can I Delete 70-persistent-net.rules?Delete file based on condition






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









1

















Linux Mint 18.3 (based on Ubuntu Xenial)



This is a dual-boot machine with W10, which may be significant



I'm trying to delete some backintime jobs. Using rm -rf top-level-dir doesn't work: I get an unexpected message saying "directory not empty".



Drilling down into the offending directory, I get to:



mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ ls -lsa
total 13
// TOTAL THIRTEEN??? WHY IS ONLY ONE FILE LISTED?
8 drwxrwxrwx 1 root root 8192 Oct 11 23:35 .
4 drwxrwxrwx 1 root root 4096 Oct 11 23:35 ..
1 -rwxrwxrwx 0 root root 200 May 27 2018 computer:
// OH DEAR, THE FILENAME ENDS WITH A COLON: LOOKS OMINOUS
// HERE I'M TRYING TO REMOVE THIS ONE FILE
mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ rm computer:
rm: cannot remove 'computer:': No such file or directory
mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ cat computer:
�meta&op�� [
�&0Khnemo-list-view-sort-columnnemo-list-view-sort-reversednemo-list-view-zoom-level���[
�'/���1falsenamemike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/gvfs-metadata $ e
// HERE I'M TRYING TO MV IT TO A MORE SENSIBLE NAME (NOT ENDING IN COLON)
mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ mv computer: spot
mv: cannot stat 'computer:': Input/output error


I switch to root:



mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ su
Password:
M17A gvfs-metadata # ls -lsa
ls: cannot access 'computer:': Input/output error
total 12
8 drwxrwxrwx 1 root root 8192 Oct 11 23:44 .
4 drwxrwxrwx 1 root root 4096 Oct 11 23:35 ..
? -????????? ? ? ? ? ? computer:
// WELL I APPEAR TO HAVE DONE SOMETHING TO THIS "FILE" ... BUT WHAT?
M17A gvfs-metadata # rm computer
rm: cannot remove 'computer': No such file or directory
M17A gvfs-metadata # rm computer:
rm: cannot remove 'computer:': Input/output error
M17A gvfs-metadata # mv computer: spot
mv: cannot stat 'computer:': Input/output error









share|improve this question


























  • Did you try escaping the : in the same way that you did in cat computer: ?

    – steeldriver
    10 hours ago






  • 1





    Sounds like an NTFS problem. There might be a mount flag to let you bypass certain protections...?

    – Aaron D. Marasco
    10 hours ago






  • 1





    I guess, it's time to fsck that partition ...

    – Bodo Thiesen
    2 hours ago











  • 'Why 13?' see info ls then 'what information is listed' then the item for -l/--format=long/--format=verbose in the third paragraph. Note colon is prohibited in filenames in Windows but perfectly fine in Unix including Linux.

    – dave_thompson_085
    1 hour ago












  • input/output error and the ?'s mean something that rm, ls, mv etc have no technical means to deal with. It's an issue in the lower storage layers. It could be hardware failure (cable, disk platter), filesystem failure (prepare backups and do fsck, beware it can break the whole filesystem)

    – ignis
    1 hour ago

















1

















Linux Mint 18.3 (based on Ubuntu Xenial)



This is a dual-boot machine with W10, which may be significant



I'm trying to delete some backintime jobs. Using rm -rf top-level-dir doesn't work: I get an unexpected message saying "directory not empty".



Drilling down into the offending directory, I get to:



mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ ls -lsa
total 13
// TOTAL THIRTEEN??? WHY IS ONLY ONE FILE LISTED?
8 drwxrwxrwx 1 root root 8192 Oct 11 23:35 .
4 drwxrwxrwx 1 root root 4096 Oct 11 23:35 ..
1 -rwxrwxrwx 0 root root 200 May 27 2018 computer:
// OH DEAR, THE FILENAME ENDS WITH A COLON: LOOKS OMINOUS
// HERE I'M TRYING TO REMOVE THIS ONE FILE
mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ rm computer:
rm: cannot remove 'computer:': No such file or directory
mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ cat computer:
�meta&op�� [
�&0Khnemo-list-view-sort-columnnemo-list-view-sort-reversednemo-list-view-zoom-level���[
�'/���1falsenamemike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/gvfs-metadata $ e
// HERE I'M TRYING TO MV IT TO A MORE SENSIBLE NAME (NOT ENDING IN COLON)
mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ mv computer: spot
mv: cannot stat 'computer:': Input/output error


I switch to root:



mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ su
Password:
M17A gvfs-metadata # ls -lsa
ls: cannot access 'computer:': Input/output error
total 12
8 drwxrwxrwx 1 root root 8192 Oct 11 23:44 .
4 drwxrwxrwx 1 root root 4096 Oct 11 23:35 ..
? -????????? ? ? ? ? ? computer:
// WELL I APPEAR TO HAVE DONE SOMETHING TO THIS "FILE" ... BUT WHAT?
M17A gvfs-metadata # rm computer
rm: cannot remove 'computer': No such file or directory
M17A gvfs-metadata # rm computer:
rm: cannot remove 'computer:': Input/output error
M17A gvfs-metadata # mv computer: spot
mv: cannot stat 'computer:': Input/output error









share|improve this question


























  • Did you try escaping the : in the same way that you did in cat computer: ?

    – steeldriver
    10 hours ago






  • 1





    Sounds like an NTFS problem. There might be a mount flag to let you bypass certain protections...?

    – Aaron D. Marasco
    10 hours ago






  • 1





    I guess, it's time to fsck that partition ...

    – Bodo Thiesen
    2 hours ago











  • 'Why 13?' see info ls then 'what information is listed' then the item for -l/--format=long/--format=verbose in the third paragraph. Note colon is prohibited in filenames in Windows but perfectly fine in Unix including Linux.

    – dave_thompson_085
    1 hour ago












  • input/output error and the ?'s mean something that rm, ls, mv etc have no technical means to deal with. It's an issue in the lower storage layers. It could be hardware failure (cable, disk platter), filesystem failure (prepare backups and do fsck, beware it can break the whole filesystem)

    – ignis
    1 hour ago













1












1








1








Linux Mint 18.3 (based on Ubuntu Xenial)



This is a dual-boot machine with W10, which may be significant



I'm trying to delete some backintime jobs. Using rm -rf top-level-dir doesn't work: I get an unexpected message saying "directory not empty".



Drilling down into the offending directory, I get to:



mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ ls -lsa
total 13
// TOTAL THIRTEEN??? WHY IS ONLY ONE FILE LISTED?
8 drwxrwxrwx 1 root root 8192 Oct 11 23:35 .
4 drwxrwxrwx 1 root root 4096 Oct 11 23:35 ..
1 -rwxrwxrwx 0 root root 200 May 27 2018 computer:
// OH DEAR, THE FILENAME ENDS WITH A COLON: LOOKS OMINOUS
// HERE I'M TRYING TO REMOVE THIS ONE FILE
mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ rm computer:
rm: cannot remove 'computer:': No such file or directory
mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ cat computer:
�meta&op�� [
�&0Khnemo-list-view-sort-columnnemo-list-view-sort-reversednemo-list-view-zoom-level���[
�'/���1falsenamemike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/gvfs-metadata $ e
// HERE I'M TRYING TO MV IT TO A MORE SENSIBLE NAME (NOT ENDING IN COLON)
mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ mv computer: spot
mv: cannot stat 'computer:': Input/output error


I switch to root:



mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ su
Password:
M17A gvfs-metadata # ls -lsa
ls: cannot access 'computer:': Input/output error
total 12
8 drwxrwxrwx 1 root root 8192 Oct 11 23:44 .
4 drwxrwxrwx 1 root root 4096 Oct 11 23:35 ..
? -????????? ? ? ? ? ? computer:
// WELL I APPEAR TO HAVE DONE SOMETHING TO THIS "FILE" ... BUT WHAT?
M17A gvfs-metadata # rm computer
rm: cannot remove 'computer': No such file or directory
M17A gvfs-metadata # rm computer:
rm: cannot remove 'computer:': Input/output error
M17A gvfs-metadata # mv computer: spot
mv: cannot stat 'computer:': Input/output error









share|improve this question















Linux Mint 18.3 (based on Ubuntu Xenial)



This is a dual-boot machine with W10, which may be significant



I'm trying to delete some backintime jobs. Using rm -rf top-level-dir doesn't work: I get an unexpected message saying "directory not empty".



Drilling down into the offending directory, I get to:



mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ ls -lsa
total 13
// TOTAL THIRTEEN??? WHY IS ONLY ONE FILE LISTED?
8 drwxrwxrwx 1 root root 8192 Oct 11 23:35 .
4 drwxrwxrwx 1 root root 4096 Oct 11 23:35 ..
1 -rwxrwxrwx 0 root root 200 May 27 2018 computer:
// OH DEAR, THE FILENAME ENDS WITH A COLON: LOOKS OMINOUS
// HERE I'M TRYING TO REMOVE THIS ONE FILE
mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ rm computer:
rm: cannot remove 'computer:': No such file or directory
mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ cat computer:
�meta&op�� [
�&0Khnemo-list-view-sort-columnnemo-list-view-sort-reversednemo-list-view-zoom-level���[
�'/���1falsenamemike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/gvfs-metadata $ e
// HERE I'M TRYING TO MV IT TO A MORE SENSIBLE NAME (NOT ENDING IN COLON)
mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ mv computer: spot
mv: cannot stat 'computer:': Input/output error


I switch to root:



mike@M17A /media/Shared/backintime/backintime/M17A/root/1/20180731-120001-297/backup/home/mike/.local/share/gvfs-metadata $ su
Password:
M17A gvfs-metadata # ls -lsa
ls: cannot access 'computer:': Input/output error
total 12
8 drwxrwxrwx 1 root root 8192 Oct 11 23:44 .
4 drwxrwxrwx 1 root root 4096 Oct 11 23:35 ..
? -????????? ? ? ? ? ? computer:
// WELL I APPEAR TO HAVE DONE SOMETHING TO THIS "FILE" ... BUT WHAT?
M17A gvfs-metadata # rm computer
rm: cannot remove 'computer': No such file or directory
M17A gvfs-metadata # rm computer:
rm: cannot remove 'computer:': Input/output error
M17A gvfs-metadata # mv computer: spot
mv: cannot stat 'computer:': Input/output error






bash files rm delete






share|improve this question














share|improve this question











share|improve this question




share|improve this question










asked 10 hours ago









mike rodentmike rodent

4644 silver badges11 bronze badges




4644 silver badges11 bronze badges















  • Did you try escaping the : in the same way that you did in cat computer: ?

    – steeldriver
    10 hours ago






  • 1





    Sounds like an NTFS problem. There might be a mount flag to let you bypass certain protections...?

    – Aaron D. Marasco
    10 hours ago






  • 1





    I guess, it's time to fsck that partition ...

    – Bodo Thiesen
    2 hours ago











  • 'Why 13?' see info ls then 'what information is listed' then the item for -l/--format=long/--format=verbose in the third paragraph. Note colon is prohibited in filenames in Windows but perfectly fine in Unix including Linux.

    – dave_thompson_085
    1 hour ago












  • input/output error and the ?'s mean something that rm, ls, mv etc have no technical means to deal with. It's an issue in the lower storage layers. It could be hardware failure (cable, disk platter), filesystem failure (prepare backups and do fsck, beware it can break the whole filesystem)

    – ignis
    1 hour ago

















  • Did you try escaping the : in the same way that you did in cat computer: ?

    – steeldriver
    10 hours ago






  • 1





    Sounds like an NTFS problem. There might be a mount flag to let you bypass certain protections...?

    – Aaron D. Marasco
    10 hours ago






  • 1





    I guess, it's time to fsck that partition ...

    – Bodo Thiesen
    2 hours ago











  • 'Why 13?' see info ls then 'what information is listed' then the item for -l/--format=long/--format=verbose in the third paragraph. Note colon is prohibited in filenames in Windows but perfectly fine in Unix including Linux.

    – dave_thompson_085
    1 hour ago












  • input/output error and the ?'s mean something that rm, ls, mv etc have no technical means to deal with. It's an issue in the lower storage layers. It could be hardware failure (cable, disk platter), filesystem failure (prepare backups and do fsck, beware it can break the whole filesystem)

    – ignis
    1 hour ago
















Did you try escaping the : in the same way that you did in cat computer: ?

– steeldriver
10 hours ago





Did you try escaping the : in the same way that you did in cat computer: ?

– steeldriver
10 hours ago




1




1





Sounds like an NTFS problem. There might be a mount flag to let you bypass certain protections...?

– Aaron D. Marasco
10 hours ago





Sounds like an NTFS problem. There might be a mount flag to let you bypass certain protections...?

– Aaron D. Marasco
10 hours ago




1




1





I guess, it's time to fsck that partition ...

– Bodo Thiesen
2 hours ago





I guess, it's time to fsck that partition ...

– Bodo Thiesen
2 hours ago













'Why 13?' see info ls then 'what information is listed' then the item for -l/--format=long/--format=verbose in the third paragraph. Note colon is prohibited in filenames in Windows but perfectly fine in Unix including Linux.

– dave_thompson_085
1 hour ago






'Why 13?' see info ls then 'what information is listed' then the item for -l/--format=long/--format=verbose in the third paragraph. Note colon is prohibited in filenames in Windows but perfectly fine in Unix including Linux.

– dave_thompson_085
1 hour ago














input/output error and the ?'s mean something that rm, ls, mv etc have no technical means to deal with. It's an issue in the lower storage layers. It could be hardware failure (cable, disk platter), filesystem failure (prepare backups and do fsck, beware it can break the whole filesystem)

– ignis
1 hour ago





input/output error and the ?'s mean something that rm, ls, mv etc have no technical means to deal with. It's an issue in the lower storage layers. It could be hardware failure (cable, disk platter), filesystem failure (prepare backups and do fsck, beware it can break the whole filesystem)

– ignis
1 hour ago










1 Answer
1






active

oldest

votes


















5


















This is an old solution, which means only old guys like me remember it.



Find the inode of the file with ls -i. Let's say it is 1611645009. Then in the directory you mention execute the command
find $NAME_OF_DIRECTORY -inum 1611645009 -exec /bin/rm ;



If that doesn't do it, then I'm baffled too.






share|improve this answer









New contributor



llywrch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );














    draft saved

    draft discarded
















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f546412%2fcant-delete-persistent-silly-file%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown


























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    5


















    This is an old solution, which means only old guys like me remember it.



    Find the inode of the file with ls -i. Let's say it is 1611645009. Then in the directory you mention execute the command
    find $NAME_OF_DIRECTORY -inum 1611645009 -exec /bin/rm ;



    If that doesn't do it, then I'm baffled too.






    share|improve this answer









    New contributor



    llywrch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.

























      5


















      This is an old solution, which means only old guys like me remember it.



      Find the inode of the file with ls -i. Let's say it is 1611645009. Then in the directory you mention execute the command
      find $NAME_OF_DIRECTORY -inum 1611645009 -exec /bin/rm ;



      If that doesn't do it, then I'm baffled too.






      share|improve this answer









      New contributor



      llywrch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.























        5














        5










        5









        This is an old solution, which means only old guys like me remember it.



        Find the inode of the file with ls -i. Let's say it is 1611645009. Then in the directory you mention execute the command
        find $NAME_OF_DIRECTORY -inum 1611645009 -exec /bin/rm ;



        If that doesn't do it, then I'm baffled too.






        share|improve this answer









        New contributor



        llywrch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        This is an old solution, which means only old guys like me remember it.



        Find the inode of the file with ls -i. Let's say it is 1611645009. Then in the directory you mention execute the command
        find $NAME_OF_DIRECTORY -inum 1611645009 -exec /bin/rm ;



        If that doesn't do it, then I'm baffled too.







        share|improve this answer









        New contributor



        llywrch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.








        share|improve this answer




        share|improve this answer






        New contributor



        llywrch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.








        answered 10 hours ago









        llywrchllywrch

        613 bronze badges




        613 bronze badges




        New contributor



        llywrch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.




        New contributor




        llywrch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.

































            draft saved

            draft discarded















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f546412%2fcant-delete-persistent-silly-file%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown









            Popular posts from this blog

            Invision Community Contents History See also References External links Navigation menuProprietaryinvisioncommunity.comIPS Community ForumsIPS Community Forumsthis blog entry"License Changes, IP.Board 3.4, and the Future""Interview -- Matt Mecham of Ibforums""CEO Invision Power Board, Matt Mecham Is a Liar, Thief!"IPB License Explanation 1.3, 1.3.1, 2.0, and 2.1ArchivedSecurity Fixes, Updates And Enhancements For IPB 1.3.1Archived"New Demo Accounts - Invision Power Services"the original"New Default Skin"the original"Invision Power Board 3.0.0 and Applications Released"the original"Archived copy"the original"Perpetual licenses being done away with""Release Notes - Invision Power Services""Introducing: IPS Community Suite 4!"Invision Community Release Notes

            Canceling a color specificationRandomly assigning color to Graphics3D objects?Default color for Filling in Mathematica 9Coloring specific elements of sets with a prime modified order in an array plotHow to pick a color differing significantly from the colors already in a given color list?Detection of the text colorColor numbers based on their valueCan color schemes for use with ColorData include opacity specification?My dynamic color schemes

            Ласкавець круглолистий Зміст Опис | Поширення | Галерея | Примітки | Посилання | Навігаційне меню58171138361-22960890446Bupleurum rotundifoliumEuro+Med PlantbasePlants of the World Online — Kew ScienceGermplasm Resources Information Network (GRIN)Ласкавецькн. VI : Літери Ком — Левиправивши або дописавши її